 | | RCX Bytecode compiler in Tcl
|
|
Greetings, I had become quickly frustrated by the limitations of the Mindstorms programming environment. Fueled by the RCX bytecode knowlege provided by Kekoa, I have recently written an RCX program interpreter/compiler in Tcl, a freely available (...) (26 years ago, 24-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
Has anyone be able to unpack the LegOS file. I have the CYGNUS GCC on my Wintel system. Using GZIP I get this error "Invaled Compressed Data - Format Violation" I would like to try out LegOS and see if it will allow memory storage/retrieval. I have (...) (26 years ago, 24-Nov-98, to lugnet.robotics)
|
| |
| | Re: RCX Bytecode compiler in Tcl
|
|
Hey, looks like you did a great job extending my initial implementation, but changing a couple of variables and proc naming does not allow you to appropriate everything without even giving due credit !!! Please re-read the License terms on my (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | legOS
|
|
Hi, Does anyone use legOS? I read that there are possible risks to getting other ROM images. What are the risks? I am using a GNU/Linux machine. Is there anything else involved in using legOS other than getting GNU binutils, building a gcc cross (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
(...) Did you get a ROM image? Did you disassemble the firmware? Even if you did, is there anything to forbid you from using that information to write new firmware? Not that I'm supplying you with an answer, but it seems to me that it's your RCX, (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
Hi, Thanks for your response. I have been reading your pages over the past few days. I do not have the RCX (yet), but I am very interested. I learned of it this weekend and have been reading the specs. I am as interested in playing with operating (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: RCX Bytecode compiler in Tcl
|
|
Laurent has a good point. While I did not use and modify his code, I did find it during my development and fear I have studied it too closely in places, without crediting him. I have removed access to my files from the server so we can discuss this. (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | RE: legOS
|
|
(...) For some Pilot <--> RCX information take a look at (URL) if you haven't yet. This honestly is quite lagging on progress, but I _have_ been working on it in my very limited spare time. Hopefully within a week or two I'll have some much more (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
(...) Hi, You can get legOS at (URL) . There is a note that some people have a problem with the file after downloading. Instead of clicking on the file, right click and select save link. It will save as legOS-0.1.2.tgz . Then run tar -xzf (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
I have downloaded OK and since it is both tared and zip, you hve to first unzip it using "GZIP". GZIP is like Compress. Gzip (compress) -d legOS-0_1_2.tgz - uncompress the file tar -xzf legOS-0_1_2.t unarchive it. I am getting the error when I try (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
(...) The only snags with legOS at the moment (that I'm aware of) are: a) You have to pull a battery out to clear the RAM b) It seems to have a problem with corrupting itself somewhere that I can't work out, and so far nor has Markus. It only shows (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: RCX Bytecode compiler in Tcl
|
|
Let me correct myself here. I did end up using some of Laurent's communications code in the bytecode compiler, after having experimented with some different approaches. Honestly, I simply forgot to track down and credit the source, which is no (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
(...) Hi, When you run tar with the -xzf parameters, it first ungzips it then it untars it, all in the one command. The "z" is for gzip. The "x" is for extract the tar file. The "f" specifies the file. , __ _ _ , /|/ \o | | | | /| | | __/ | | | | (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
(...) I think he meants risks as in "I installed LegOS, and it got wedged, and I can't reinstall the official Lego stuff, so now I've got a very very expensive lego brick that does nothing". It seems to me that Lego's position would logically be "If (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
(...) Such risks are unknown. You have to trust, in the case of LegOS, that Markus did a reasonable job. He in turn probably has some amount of trust that I did a reasonable job, at least with regards to some aspects. If you're not sure about (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
Guys, Everyone seems to be missing one point: The RCX does have ROM code (this is what loads the firmware the first time, right?). If you were to "jam up" the firmware, you could just simply remove the batteries, let the firmware (which must be in (...) (26 years ago, 25-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
(...) Er? Since when you rewrite the firmware, you can take full control of the i/o pins of the H8, it seems perfectly possible to me to drive inputs as outputs and fry something you didn't mean to fry... You have to be careful to make sure you (...) (26 years ago, 26-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS
|
|
I managed to get my Cybermaster into a "vibrating" state with the motors humming and the unit shaking! (downloaded some commands while it was running) None of the buttons worked and it did not sound very healthy so I ripped the batteries out (...) (26 years ago, 26-Nov-98, to lugnet.robotics)
|
| |
| | legOS corruption
|
|
(...) Hi, In what way does it corrupt itself? Thanks, , __ _ _ , /|/ \o | | | | /| | | __/ | | | | |___| | \| |/ |/ | |\ |(__/|_/|__/|__/ | |/ It's a troublesome world. All the people who're in it are troubled with troubles almost every minute. You (...) (26 years ago, 26-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS corruption
|
|
(...) I have code that should just increment/decrement some counters and display them. The numbers get reset to strange values. This looks like stack or register corruption, but I haven't yet found where or why (yet). Wish I still did embedded (...) (26 years ago, 27-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS corruption
|
|
Ben Laurie wrote in message <365E93F5.63ABFE6B@a....co.uk>... (...) I do embedded systems WITHOUT a logic analyser. You can do about 99% of what you need to with a monitor and an oscilloscope. The logic analyser (or emulator) is the big gun for the (...) (26 years ago, 27-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS corruption
|
|
(...) Agree with you totally there! However, I have always found it useful to have a debugging version of the kernel which allows you to use something like gdb to debug your embedded system through a serial port. (...) Sadly, the last embedded (...) (26 years ago, 27-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS corruption
|
|
Fred Read wrote in message <365EA592.62DE2792@c...net.uk>... (...) That's what I meant by monitor - sorry I wasn't more clear... Cheers, Ralph Hempel - P.Eng ---...--- The train stops at the train station, The bus stops at the bus station, So why (...) (26 years ago, 27-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS corruption
|
|
(...) Yeah, yeah. I'm sure we've all got "I debugged that with no more than an LED and 3 inches of wire" stories, but only a fool would spurn a logic analyser when it was available. Cheers, Ben. (26 years ago, 28-Nov-98, to lugnet.robotics)
|
| |
| | Re: legOS corruption
|
|
Ben Laurie wrote in message <36606582.FFA56883@a....co.uk>... (...) Aha, the flame war has begun :-) I agree with you too Ben, only a fool would spurn the analyser, but if you instrument your project properly and really KNOW the system, you can (...) (26 years ago, 29-Nov-98, to lugnet.robotics)
|
