 | | Re: Motor Control Register (0xf000)
|
| It also turns out that there are 8 bytes of external RAM that peek through at addresses 0xff80-0xff87. Writes to these locations also affect the motor control register. I suppose there's a small advantage in using these registers to control the (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
| | | | | Re: Motor Control Register (0xf000)
|
| (...) In that case, why didn't the RCX designers use an 8 input NAND to decode their addresses, to leave more of the RAM usable? Maybe there werent aware of this possibility? Jürgen (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
| | | | | Re: Motor Control Register (0xf000)
|
| (...) As it is, it seems[1] that two of the three NAND gates in the 74HC10 are being used as a driver for speaker output (it's odd that it's two, not one though). So, this leaves one three input NAND gate to do the decoding. Now that I think about (...) (22 years ago, 14-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
| | | | | Re: Motor Control Register (0xf000)
|
| (...) Yeah, I missed that, I'll add that to the notes. (...) Too bad they didn't document the hole well enough to make it obvious to the people at Lego, who apparently had no idea. They use "mov.w rx,@0xf000:16" all over the place instead of the (...) (22 years ago, 20-Nov-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
| |
