 | | Re: leJOS & LDCC IRP
|
|
(...) Receiving IR commands from a Lego Remote, IR Tower or possibly another RCX. They're not DCC signals, but LDCC IRP messages. Roughly the same data, different medium and different protocol. (...) LDCC IRP is still unstable, but it will support (...) (22 years ago, 12-Sep-03, to lugnet.robotics.rcx.java, lugnet.trains)
|
| |
| | Re: Low level programming of the RCX
|
|
(...) Speaking of Quite C, I am working on figuring out a good way to integrate Quite C into the BricxCC system. It is a bit different from the other languages BricxCC supports in that you compile to an SREC and download it as a new firmware rather (...) (22 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Low level programming of the RCX
|
|
(...) [snip] (...) [snip] I'll second that. The BrickOS source code provides a good example of using the FRC as well as other low-level I/O. Between that source and the H8 manuals, you should be set. If you have specific questions, there are quite a (...) (22 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Re: Low level programming of the RCX
|
|
(...) Quite C is your best place to start with a language. C can give you direct access to the timer. The timer is considered an I/O device, but all I/O on the H8 is memory mapped. Having said that, if you know the address of the timer, you can (...) (22 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
| |
| | Low level programming of the RCX
|
|
Hello everybody, I try to program the RCX at low level. I want to be able to program using the Hitachi h8/3292 directly. For example, I want to use the free-running timer, define own interrupt handlers and so on. In fact, I *really* need to control (...) (22 years ago, 12-Sep-03, to lugnet.robotics.rcx)
|
