 | | RE: How much RAM is left?
|
|
(...) Nope, the memory is allocated linearly from the end of the image. The current image size is 12 or 13K. New dictionary entries and ALLOTed memory are interspersed as they occur. NOTE WELL that there is a subtle bug in the RCX ROM routines when (...) (24 years ago, 5-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | How much RAM is left?
|
|
(...) I believe that. 32k of RAM is a luxury for forth. That's another thing people don't generally understand about forth, they way it effectively compresses runtime software. I've heard of ram reductions of a factor of 5-10 for forth when compared (...) (24 years ago, 5-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Which terminal on Linux? plus random thoughts.
|
|
(...) Umm, I mean cover the tower and the RCX with a box.... :-) (...) No, Ernst's idea has a preamble byte for the transfer, and then the RCX grabs all of the chars and sums them. If the sum is wrong, then it NAKs the packet and the host sends it (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Which terminal on Linux? plus random thoughts.
|
|
(...) I missed that. What do you mean by simply covered. (...) No surprise there. I implemented XMODEM a long time ago on a spectrometer. I don't remember the details but obviously it stayed with me. Besides all protocols tend to look the same at (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Which terminal on Linux? plus random thoughts.
|
|
(...) I have beta quality Tcl code that sends an SRECORD firmware imge up to the RCX (fast or slow) and has basic terminal capabilities. It also strips comments and whitespace out of files as they are uploaded to reduce the time. I'd like to put a (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Which terminal on Linux? plus random thoughts.
|
|
I'm interested in other people's experience with various terminal emulators on Linux. I've been using minicom with indifferent results, probably because it doesn't support delays between lines which possibly overruns pbforth's serial input. minicom (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: sensor questions plus
|
|
(...) The ROM stuff is documented in Kekoa Proudfoot's internals document, see (URL) for all the details. The RCX interface words in pbForth call into the ROM... (...) It actually *processes* the results of a sensor read by the OCIA interrupt (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | sensor questions plus
|
|
You said to keep asking questions. I'm taking you at your word. Questions I've got. o - Sensor questions: Could you explain how the sensor code works? How does it interact with the ROM. Is this (ROM stuff) documented elsewhere? What does SENSOR_READ (...) (24 years ago, 3-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Banging on the tasker
|
|
(...) That's my plan. The nice thing about the tasker is that people can write code in a format they are more used to. The same things can be done with event driven single task code but it inverts the control flow. It is more meaningful for most (...) (24 years ago, 3-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Multitasking questions
|
|
(...) Ummm, I'm in the process of verifying all of the old scripts I package with pbForth. It looks like HAT is what actually works, and I've managed to change the documentation and not the code. HAT is in the origianl hForth implementation but I (...) (24 years ago, 3-May-00, to lugnet.robotics.rcx.pbforth)
|
