|
|
 | | Re: fast firmware downloader
|
| (...) I'll start by pulling the 4x code into the NQC source base. That should make it trivial to build a stand-alone command line based downloader for Win32 (95/nt/98), Linux, Solaris, and Mac 68k/ppc under MPW. We could also get Win3.1 and DOS (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
| | | | | Re: What should be in the next version of RcxCC
|
| (...) I was considering writing an RCX bytecode simulator. If I get some free time I'll throw something together. Considering the last simulator I wrote was for an ARM 7111 with about a dozen on-chip peripherals, modeling the RCX bytecode (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.nqc)
| | | | | RE: Double echo
|
| (...) Yes, it should. The issue is that you never really know if the stack will blast through the 256 byte boundary, unless HAT checks it. You generally allocate small stacks, so HAT could be modified to FORCE the data stack to start at the boundary (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.pbforth)
| | | | | Re: Firmware behaviour
|
| (...) The on/off button is always operational. It makes a great NO! STOP THAT! button when your robot is tearing itself apart accidentally. :) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx)
| | | | | Re: Double echo
|
| (...) Standalone loader would be nice. (...) Well, the most important, of course, is the stack bug. BTW, what about multitasker? How many cells would you recommend to allocate? Should be it checked by HAT word or not? (...) Sure, I would like to (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.pbforth)
|
|
