|
|
 | | New newsgroups lugnet.robotics.edu & lugnet.edu
|
| lugnet.robotics.edu and lugnet.edu have just been created. For background information on how these came to be, please see the following messages and related threads: (URL) <-- especially this one (URL) <-- and this one (3 URLs) new discussion groups (...) (25 years ago, 28-Oct-99, to lugnet.admin.general, lugnet.robotics, lugnet.robotics.rcx.nqc, lugnet.robotics.events, lugnet.robotics.edu, lugnet.edu, lugnet.loc.us.ma.bos, lugnet.dacta, lugnet.general, lugnet.announce)
| | | | | RE: Double echo
|
| Hi Ralph, (...) Yea, no stack-hungry applications... Just to be sure, do you plan to add an automatic stack boundary alignment to HAT word? I think it could be a good solution. And memory, you are right, with Forth we have enough memory ;-> (...) (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.pbforth)
| | | | | RE: Double echo
|
| (...) There are no "tasks really, just a big loop that executes a bunch of opcodes...I'm paraphrasing here. The memory waste issue isn't that big a deal. The average distance to a boundary is 128 bytes, right. Say we allocate a 32 element data stack (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.pbforth)
| | | | | Re: Double echo
|
| Hi Ralph, (...) Means that we will have to waste memory a lot... Do you know how the standard LEGO firmware works? Does it allocate stack frame for each task or may be it's not an issue at all? (...) Yes, "4th" was always my favourite. Only question (...) (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.pbforth)
| | | | | Re: fast firmware downloader
|
| (...) I'm willing to cover the DOS port since I'm working on a DOS->RCX comm project already. I already have my HP LX200 doing minimal comm with the RCX with hopes of having it ride alongside as a computational component. -Wes Matchett (25 years ago, 28-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
| | | | | 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)
|
|
