 | | Re: NQC wishlist
|
|
(...) I believe the simplest way to do it would be to have an extra preprocessing pass... it will slow down compilation a little, it's true, but maybe not that much as to matter (compilation is anyway so much faster than the downloading anyway) then (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Speed of RCX interpreting bytecodes: slow
|
|
(...) Hmm. If so, an interesting option for a theoretical replacement-but- compatible firmware to have would be the ability to do things as fast as possible. (Of course, it'd have to be an option, since it's possible that some badly-designed code (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Re: Speed of RCX interpreting bytecodes: slow
|
|
Its been a long time since I looked at the firmware in detail, but is it possible that the bytecode interpreter is driven from one of the timer chains? If this was the case, it wouldn't matter if the CPU could execute the bytecode in 200 cycles...it (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Re: NQC wishlist
|
|
(...) No, this sort of thing isn't covered in my book. There are several ways to send commands to the RCX. The first is the official SDK from TLG (spirit.ocx) which runs under Windows. The SDK contains a reasonable amount of documentation on the (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
| |
| | Re: (Failed) Getting LegOS 0.2.2 working on Windows
|
|
G'day, (...) When trying to apply the patch I get 3 rejects and a bad formated patch file error message. So I applied the patches by hand. Using your patches, I can compile everything without warning (good on yer!!!) and download legOS.srec as well (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx.legos)
|
