 | | 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)
|
| |
| | New pbForth GUI
|
|
I'd like to announce the availability of an early trial version of a GUI for pbForth. It's written in TclTk, a free scripting language, but that's transparent to the user. (URL) The GUI runs under Windows and Linux, and as soon as I can find a (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx)
|
| |
| | New pbForth GUI
|
|
You are receiving this email because you are on the pbForth mailing list. If you wish to be removed, click on the following link: <mailto:rhempel@bmts...subscribe> I'd like to announce the availability of an early trial version of a GUI for pbForth. (...) (24 years ago, 16-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: serial port interrupts
|
|
(...) I'm not suggesting that it isn't hard. Compared to native debugging with printf and gdb in an emacs window it is quite hard. It's just that you build up a bag of tricks after a while or take up application development instead. :-) One of the (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | University-Level ROBOLAB examples
|
|
(URL) (24 years ago, 15-May-00, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| |
| | RE: serial port interrupts
|
|
(...) It's amazing, but I get all kinds of comments on how it's impossible to debug systems like the RCX brick. I guess if you're used to deeply embedded systems, figuring out how to let it tell you what's going on is a big part of the magic... (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: lnp communication question
|
|
Hello Tobias, (...) Why do you think there's only 1 byte that can be sent? If your data buffer is longer, bytes are sent one-by-one serially in a packet... (...) look into lnp.c and you will see that both lnp_integrity_xxx and lnp_addressing_xxx are (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: serial port interrupts
|
|
(...) Actually that's what I was intending but I couldn't remember the words at my keyboard. To make debugging easier I will use parallel words that can be merged in later. I was going to use the following debugging strategy: Put the isr init in a (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | due to popular demand
|
|
The HOWTO and other legOS archives will be available (until I get it to sourceforge) at (URL) for the people who wrote and volunteered to serve it- the archives now total something like ~100 meg (several different copies of compilers are in there) (...) (24 years ago, 15-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | lnp communication question
|
|
Hi! When using lnp_integrity_write(&data, length), what is the length argument used for? The data can only be one byte long if I understand it correctly. Can I use the length argument to send an additional byte of information? Is there anyway I can (...) (24 years ago, 14-May-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: serial port interrupts
|
|
(...) Sounds good Steve, see notes below for some pointers... (...) Absolutely. All we have to do is enable the interrupts on the receiver throw the chars into a buffer. I'd keep the standard FORTH words that already exist so less system source (...) (24 years ago, 14-May-00, to lugnet.robotics.rcx.pbforth)
|
