|
|
 | | Re: Firmdl3 updated
|
| (...) So my 18k kernel actually only takes 9k of RCX memory? Suddenly my apparent out-of-memory errors make a lot less sense.... (24 years ago, 20-Dec-00, to lugnet.robotics.rcx.legos)
| | | | | Re: Firmdl3 updated
|
| (...) I wasn't completely sure how much extra data there was in there; I knew it was larger but didn't realize by how much. Regardless, I'll merge in the changes anyway, since I don't want our tree to diverge too much from the One True tree. Luis (...) (24 years ago, 20-Dec-00, to lugnet.robotics.rcx.legos)
| | | | | Re: Firmdl3 updated
|
| (...) Isn't the actual size of the kernal about half the .srec size? That file contains ascii codes for for hex bytes, a pair of characters would be one byte. Rossz (24 years ago, 20-Dec-00, to lugnet.robotics.rcx.legos)
| | | | | Re: Firmdl3 updated
|
| (...) Actually, the kernel can hit 21-22K (depending on the compile-time options.) My current legOS.srec sits at 21232 bytes. So, I'm going to do the update. Luis (sort of wishing that Markus had not made so many little changes to firmdl) ---...--- (...) (24 years ago, 20-Dec-00, to lugnet.robotics.rcx.legos)
| | | | | transmission distances
|
| When I muck about with Exploration Mars software, the RCX doesn't go out of range until it's out of the room. With pbForth, the RCX receives the commands over just as far a range, but can only send its "ok" feedback when it is quite close to the (...) (24 years ago, 19-Dec-00, to lugnet.robotics.rcx.pbforth)
|
|
