| | Re: Motor Control Register (0xf000)
|
|
Joe, [some reordering of comments for clarity] (...) The idea is to pick a certain number of functions that will fit in the upper RAM space (~2900 bytes) and put these functions in a seperate linker section (other than the default ".text" section). (...) (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
|
| | Re: Motor Control Register (0xf000)
|
|
Mark, This is very interesting. I have experienced strange motor behavior with programs on BrickOS before; I now wonder if this may have been the situation. I do not currently know enough about GCC to make the changes that you mentioned, but I am (...) (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
|
| | Motor Control Register (0xf000)
|
|
Seeing as how there's been little traffic here recently, I thought I'd post about something I found that's cleared up a little mystery (for me at least). It concerns the RCX register that is used to control the motors. This register lives at 0xf000. (...) (22 years ago, 13-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
|
| | how to calculate program size?
|
|
this has been asked before, but i cant seem to find the answer in my inbox. anyways, i was wondering how i could calculate the program size of the program on my rcx. im using legOS 0.2.4. any help appriciated kenneth johansen kennethj@stud.cs.uit.no (22 years ago, 5-Nov-02, to lugnet.robotics.rcx.legos)
|
|
| | Re: Release candidate brickos-0.2.6.08 avail for testing
|
|
After making this change everything worked perfectly, as far as I can tell. I had a lot of trouble trying to build the gcc cross compiler. With this build and the pre-build cross compiler from hitachi's website everything was very easy. Thanks! (...) (22 years ago, 5-Nov-02, to lugnet.robotics.rcx.legos)
|