 | | Re: legOS ... really a stack question
|
|
(...) All off-chip accesses to f000 or higher are memory mapped to the motors. Because accesses to addresses above fb7f are all on-chip or invalid, the motors are effectively memory mapped to f000-fb7f. (...) What are your symptoms again? One (...) (28 years ago, 2-Jan-99, to lugnet.robotics)
|
| |
 | | RE: legOS ... really a stack question
|
|
(...) .bss also contains global data initialized to 0, which is even worse if it's not cleared. -Allen -- Did you check the web site first?: (URL) (28 years ago, 2-Jan-99, to lugnet.robotics)
|
| |
 | | Small but useful change to firmdl.c
|
|
Further moping though the ROM image revealed that the address in the start firmware download message is really the firmware entry point. I modified firmdl.c to take this into account. If an entry point is stored in the s-record file, firmdl.c uses (...) (28 years ago, 2-Jan-99, to lugnet.robotics)
|
| |
 | | Re: legOS errors
|
|
(...) It is a perl program, and as shipped it expects perl to be in /usr/bin. If you have perl installed in /usr/local/bin (for example), just change the first line to #!/usr/local/bin/perl. If you don't have perl, you will need to obtain and (...) (28 years ago, 3-Jan-99, to lugnet.robotics)
|
| |
 | | binutils problem fixed
|
|
Many thanks to those of you that sent a compiled copy of kmain, I was able to determine where the error was. If you are trying to run binutils on a machine that has char as an unsigned type, you will have the same problem. I remember at least one (...) (28 years ago, 3-Jan-99, to lugnet.robotics)
|