 | | local variables
|
|
Hi! I read that legOS only declared varibles the first time the program is run. Does this mean I cannot use local variables. I have loops in different functions using 'i' as looping variable, which is locally declared. Should I avoid this? Tobias (24 years ago, 16-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: New pbForth GUI
|
|
This is a great idea, Ralph. I've wanted to just fool around in pbForth, but have been intimidated by the apparent front-end learning curve. I'm a mechanical guy, I don't do TclTk, Gnu, etc., I've been spoiled by GUI front ends and install programs. (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: proposed new word for deleting pbforth
|
|
(...) As a guess the following string tells the ROM that there is valid firmware. This might need to be stepped on before jumping to the reset vector. .string "Do you byte, when I knock?" (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | Re: lnp communication question
|
|
(...) So the length-argument tells lnp_integrity_write how many bytes to send? Doesn't that mean that it would be possible to send an array consisting of many integers, for example? How would this be done? (...) We plan to build a six-legged lego (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | winlegos compiler problem
|
|
I am trying out the lnp functionality with addressing and such, and of course I had to recompile the legos kernel. That, in itself, seemed to go without a hitch, but when I later tried to compile one of the demo programs, this is what I got. djecho (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: proposed new word for deleting pbforth
|
|
(...) Kekoa, feel free to jump in here... Personally, I think just jumping to the reset vector 0x0000 should do a total cold start, right? Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (URL) ---...--- Reply to: (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | proposed new word for deleting pbforth
|
|
It would be handy if there was a word that deleted firmware. It is often inconvenient to get at the batteries. At Kekoa I see the opcode but no rom entry point. Trashing the header in memory and jumping to the reset vector might do it. I wonder if (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth, lugnet.robotics.rcx)
|
| |
| | RE: More linux feedback. firmware upload doesn't work for me.
|
|
(...) This is wierd. I had it working on my Caldera Linux 2.2 which has TclTk 8.0.4 I'll try again. One of the problems is that I can't seem to get a nice NFS system running here, and I have to FTP the files around... :-( I'll try and make a better (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | More linux feedback. firmware upload doesn't work for me.
|
|
Firmware download is not working. I'm sorry but I never tried this with the first release. A second problem is that it gives no error message if the firmware download fails. I got suspicious because the download was too fast and the LCD was not (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: New pbForth GUI; linux feedback
|
|
(...) o - When will 1.2.0 sources be available? I'd rather be working from current stuff. Does the gui depend on this version of pbforth? o - rcxtk.tcl should have executable permission in the tarball. This can be done with the -p flag to tar (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth)
|
