 | | Re: Programming in Assembly
|
|
Cool, thanks I was able to find the doc here: (URL) post about the motor seems helpful, so if I understand right the way to run motor A forward would be "mov 0x030003,r0h mov 0x80,r0h" and for the motor C the same except 0x06? How does the (...) (21 years ago, 17-Jul-03, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Programming in Assembly
|
|
Here's a more direct link for the H8 docs: (URL) down to the literature section and download the two PDFs. For assembly, I would recommend starting off with an installation of BrickOS and perusing the various source code files for the kernel. You'll (...) (21 years ago, 16-Jul-03, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Programming in Assembly
|
|
(...) find the old documentation files is a bit tricky, it took me some time to figure them out. Anyway, take a look at: (URL) look at the product list. Regards, Michael (21 years ago, 16-Jul-03, to lugnet.robotics.rcx.legos)
|
| |
| | Programming in Assembly
|
|
I was interested in writing some assembly code for the lego mindstorm, I don't plan on writing an incredibly complex program though. I am learning asm for the z80 chip so I have a little experience. I only want a single threaded application with one (...) (21 years ago, 16-Jul-03, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Re: Modifying the BrickOS source code
|
|
Thanks Joe, it makes sense now and I understand it is something that is difficutl to explain esp, through a message board. Thanks for helping me out... Mike (21 years ago, 15-Jul-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Modifying the BrickOS source code
|
|
Here is a visual representation: [ KERNEL ]mm_start[ HEAP ] The heap will contain ALL of the following: User Programs, User Allocated memory, Kernel allocated memory (not including static/global variables and constants). The only thing that is prior (...) (21 years ago, 15-Jul-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Modifying the BrickOS source code
|
|
(...) Thanks for the description Joe, but in the above paragraph you seem to contradict yourself, you say that mm_start is the end of kernel mode, but alos that user programs are located above mm_start I do not understand that part, did you mean (...) (21 years ago, 15-Jul-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Modifying the BrickOS source code
|
|
Mike, IIRC, mm_start is the beginning of the heap. When the system or a user program requests memory (new in C++ or malloc/calloc in C) the memory is taken from this block (from mm_start to the end of memory) What might be confusing is how the (...) (21 years ago, 15-Jul-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Modifying the BrickOS source code
|
|
Thanks to all with the help, I finally got my new News setup info (my original login wasnt working so I had to re-sign up but it took about 2 weeks to hear from lugnet, so Charlie posted some stuff for me). I am looking at mm.c for my project and I (...) (21 years ago, 15-Jul-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: BrickOS motor-output: Subject to change?
|
|
Do you use another firmware downloader besides firmdl3? Recent changes to BrickOS changed the memory layout a bit and this could be an issue. For example, I just discovered that the nqc firmware downloader doesn't like firmware files with (...) (21 years ago, 15-Jul-03, to lugnet.robotics.rcx.legos)
|
