| | 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)
|
|
| | Re: controlling rcx with remote control
|
|
(...) No luck... It's for the lego remote... (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
|
| | Re: LNP packet handler
|
|
(...) Hi :-) I had problem the same. After brushing code source per some days, I finished discovering that the problem was with the versions. I installed logOS 0.2.5 and everything functioned well. (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
|
| | Re: Release candidate brickos-0.2.6.08 avail for testing
|
|
(...) I spoke too soon. There is a problem with cygwin and Makefile.Common in the new release. The host utilities are not built with -D_WIN32 which (of course) causes them to not work at all. In Makefile.Common there is a place where CFLAGS is set (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
|
| | I solved a small problem in lnp :-)
|
|
Hi :-) The problem is: When compiling programs made in language 'C++' using: # g++ myprogram.c -llnp The g++ would not compile and the follow messages appeared: /tmp/ccXFr7VZ.o: In function `main': /tmp/ccXFr7VZ.o(.text+0x95): undefined reference to (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|
|
| | Re: Interruptions in BrickOS
|
|
Good questions! See responses below... "Martin De Wulf" <madewulf@ulb.ac.be> wrote in message news:H51ItF.Ax1@lugnet.com... <snip> (...) You may want to check out the latest (now called BrickOS) at (URL) For us, real-time properties of the platform (...) (22 years ago, 4-Nov-02, to lugnet.robotics.rcx.legos)
|