 | | 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
|
|
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)
|
| |
| | 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: 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)
|
| |
| | 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)
|
| |
| | serial port interrupts
|
|
Ralph, I'm getting tired of losing characters going to the RCX on the serial port because forth is busy. It is making my work more complex than it needs to be. If you are not going to do serial port interrupts I will take a shot at it if you give me (...) (24 years ago, 13-May-00, to lugnet.robotics.rcx.pbforth)
|
