 | | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) I'd say this is the way to leave it, since it seems to be how you meant it in the first place. It's just very annoying to take out the batteries if ON/OFF is pressed by mistake while something is running. (...) Don't know, I've never used (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS limitation
|
|
Hey, this is a small but frustrating one. This is in legOS 1.7 but I beleive it will still be in 2.0 as it's caused by the 1 priority to a task requirement. If you write code like the following: while(1){ wait(for something); kill(t1); t1 = (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) If ON/OFF is desired while programs run, just drop the if. If ON/OFF isn't to work while programs run, it has to be this: if(nb_tasks<=3) { killall(PRIO_HIGHEST); return 0; // killall doesn't kill self } break; What does standard firmware do? (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) Following up to myself, but here's the error (kernel/program/.c) lines 255-260: case KEY_ONOFF: // works only if no programs are running. if(nb_tasks<=3) { killall(PRIO_HIGHEST); } return 0; ^^^^ This should be 'break'. The way the code is (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | IR questinos and more
|
|
Hi All. I'm trying to build an IR proximity sensor with LegOS, by using the on-board transmitter and light sensor. I'm having problems figuring out how to send data, however. I tried using lnp_logical_write(), but 'cu -l /dev/ttyS0' doesn't show any (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) That would be nice, actually. I have only one problem with stability - every once in a while, the "Run" key stops working, and all the other keys as well (don't remember exactly, but I think that's how it is). The program keeps running (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: fast firmware downloader
|
|
(...) Count me in. I'm ditching the Tcl interface - it's just too damn goofy! A standard firmware downloader would be great - especially if it ran on all platforms. As far As I know, Dave Baum is the only guy here who has got a downloader for the (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: fast firmware downloader
|
|
(...) If there's interest in a stand-alone firmware downloader running on the Mac, please let me know. I can certainly add the approriate quad-speed stuff into NQC, and can also make a stand-alone version if Mac users are using pbFORTH or something (...) (25 years ago, 27-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | Re: LegOS 0.2.0a multi-threading problem
|
|
Hi, yes, currently, you'll have to make main() your first function. version 0.2.1 will support arbitrary starting offsets. could you report about the stability of repeated program runs? if this works fine, I'll change the ON/OFF behaviour to (...) (25 years ago, 26-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS 0.2.0a multi-threading problem
|
|
(...) [snip] Heh. I've spent 2 days on this, so I know how you feel :). main() must be the first function in your source file, otherwise really weird stuff happens. -- Regards, Modemch (25 years ago, 25-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8 tools problems on Linux
|
|
(...) Hi! I got the precompiled tools from the LegOS page, tried with both the 'old' and the 'new' set... by the way, the Windows version works fine. Not 0.2.0, but that's not the tools' fault... thanks for all the help Vlad (25 years ago, 26-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8 tools problems on Linux
|
|
Thanks for the plug, Jacob. I in fact have received a set of instructions for gcc 2.9.5, and began the work of integrating them into the HOWTO last night. However, I was interrupted and will not have time to finish the task tonight, so do expect gcc (...) (25 years ago, 25-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8 tools problems on Linux
|
|
(...) I've compiled LegOS under RedHat 5.2 without problems. I recently upgraded to 6.0 and I still have no problems. Have you downloaded some odd version of gcc or binutils? I've experienced problems when compiling gcc 2.95, but they can (easily) (...) (25 years ago, 24-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | LegOS 0.2.0a multi-threading problem
|
|
I have been attempting to us the thread API for a LegOS project. I have been following the examples I found on the LegOS How-To page with out much success. If I run some simple code inside the main function it works fine but if I try the same code (...) (25 years ago, 25-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8 tools problems on Linux
|
|
(...) Vlad- First off, I'd suggest building your own tools, instead of downloading the pre-built tools (which, like anything pre-built, tends to work only on systems very similar to the original builder's.) There are pretty clear directions (I (...) (25 years ago, 24-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8 tools problems on Linux
|
|
(...) I'll let someone else address the rest of your question, but: there is no "Linux 5.2". The latest stable version of Linux is 2.2.13, and the latest devel release is 2.3.22. Perhaps you mean Red Hat 5.2? In that case, I'd suggest upgrading -- (...) (25 years ago, 24-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | H8 tools problems on Linux
|
|
Hi all! The H8 tools on Linux won't work for me - it's Linux 5.2 and the C compiler complains about "null char when parsing input" for anything else than a comment... I tried with both the old and new tools form the legOS site.... any ideas? thanks (...) (25 years ago, 24-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | 0.2.0a patch
|
|
Hello, apparently I introduced a glitch when adding last-minute support for non-patched standard egcs. This and a broken symlink in the archive prevented dllback from compiling on the host. A patched version of legOS is available on (URL) for the (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | RCX-enhanced egcs
|
|
Hello, I just posted the final RCX interrupt handling patch for egcs. There is no need for wrappers anymore. Interrupt handlers can be declared like this now: void handler() __attribute__((rcx_interrupt)); void handler() { // do stuff } For a leaf (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Annoying Journalist's Request
|
|
To the list: this morning is a break for me, so I'm going to use it to type this out. Hope no one minds that it gets sent to the "annoying journalist" as well. Here at Duke, we are teaching a class with the mindstorms. Recently, we completed a class (...) (25 years ago, 18-Oct-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS 0.2.0 released
|
|
Well, this is a bad week to say the least, but I hope to have rudimentary HOWTO stuff for 0.2.0 within two weeks. Thanks for everything, Markus! Luis (...) ###...### Profanity is the one language that all programmers understand. -Anonymous ###...### (25 years ago, 18-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | legOS 0.2.0 released
|
|
Hello, legOS 0.2.0 is out. If you like to program your Mindstorms in C, or if you would like to try, it has become better than ever. Dynamic linking and program loading are fully supported now, as well as unreliable LNP datagram networking. Lots of (...) (25 years ago, 19-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | RCX Firmware and SP
|
|
Hi All, After a very frustrating weekend of fiddling with pbFORTH, I caved and asked Kekoa to help with a problem I was having with read_sensor() and pbFORTH. The problem we (mostly he) unearthed has to do with the SP and RCX firmware routines, so I (...) (25 years ago, 17-Oct-99, to lugnet.robotics, lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth)
|
| |
| | Re:Solved?? rotation sensor problem
|
|
On Sep.10,I posted the message regarding rotation-sensor problem. I realized that the first threshold value '0x6fc0' in CURRENT_STATE is too small. Some sensors give raw values around 0x7000. #define CURRENT_STATE (raw<0x6fc0?STATE_0:...STATE_3))) (...) (25 years ago, 17-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: firmdl3 @ 41.13s
|
|
(...) If you deactivate complements or headers in the ROM protocol, then the ROM does not transmit exactly what you might want it to. See the comments for init_serial in lib/rom.h of the Librcx distribution. If you use the default mode settings, or (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: firmdl3 @ 41.13s
|
|
(...) Bug, what bug? Have I missed something? My Tcl based uploader broke when Scriptics released 8.2, and now it works again. Seems I wasn't handling the rcx_recv parameter in my equivalent functions... Anyways, could you elaborate on the bug a (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: firmdl3 @ 41.13s
|
|
(...) I'll have to test it out in my office, which has difficult lighting. Errors in transmission can often break things in unexpected ways, leaving you in states that are hard to recover from, often resulting in the downloader aborting after giving (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | firmdl3 @ 41.13s
|
|
Hi, on my machine, original firmdl3 took 45.2s to download firm0309.lgo. - I increased packet size to 240 bytes, gaining roughly 2 seconds. - Added packet size prediction and bytewise decoding with a state machine (The decoder spent 50 ms per packet (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: fast firmware downloader
|
|
(...) Is this the movie where there are guys competing in unassisted (except by a huge weight) deep dives? Those guys are mental... Cheers, Ralph Hempel - P.Eng ---...--- Check out pbFORTH for LEGO Mindstorms at: (URL) ---...--- Reply to: rhempel at (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: fast firmware downloader
|
|
(...) [mlnoga@mauve mlnoga]$ make firmdl3 cc firmdl3.c -o firmdl3 firmdl3.c:146: rcx_comm.h: No such file or directory firmdl3.c:569: srec.h: No such file or directory make: *** [firmdl3] Error 1 Seems to me we're both getting a little hasty here (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: fast firmware downloader
|
|
(...) The URL is: (URL) in the nick of time? The original firmdl.c was dated 10/3/98. It is currently 10/3/99 (PDT at least). This was not planned! Like firmdl.c, firmdl3.c is a single file joined from smaller ones for simplicity. I will link a .tgz (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | Re: couldn't keep myself from it ;-)
|
|
(...) Whoa. Not so fast. My firmdl3 does the job in 44 seconds, not 53 seconds, so I think firmdl4 is a step backwards. :) Just hold on a bit while I finish packing it up. It is almost done, I promise. The new version (firmdl3) will be MPL. If you (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | couldn't keep myself from it ;-)
|
|
Hi Kekoa, I herewith jettison fastdl. - added code to remove parity and disable complements to your stub - split up firmdl2 into nice little modules - figured out how to deal with complement-disabled packets - optimized delays, fixed numerous little (...) (25 years ago, 4-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: fast firmware downloader
|
|
(...) Oops, I meant complements, not checksums, throughout the above paragraph. After reviewing my notes, it seems that the ROM properly obeys the complement flag when receiving but not when sending. When the ROM is sending a "long" message, it (...) (25 years ago, 3-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | RE: fast firmware downloader
|
|
(...) This is what I like so much about the "Extreme Team"...usually more than one way to skin a cat. I must have missed those posts, Kekoa. I try to use as much as possible of the ROM code in the brick too. The next step for pbFORTH is to link (...) (25 years ago, 3-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | Re: fast firmware downloader
|
|
(...) Just for the record, I implemented a dual-speed downloader a few months ago and mailed John Tamplin with information about it with regards to the JVM port that seems to have died. I used a different strategy to hack the dual speed downloads. (...) (25 years ago, 3-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | egcs-1.1.1 patch, legOS projects structure
|
|
Hi, this night is proving productive. I went ahead and tweaked egcs to produce RCX-specific interrupt handler prologues and epilogues. Apply this patch against egcs-1.1.1/gcc/confi...0/h8300.c, and you will be able to create interrupt handlers the (...) (25 years ago, 3-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: fast firmware downloader - and compilers
|
|
(...) Not at all ;-) fast.srec works like this: - load new image, storing it immediately behind fast.srec - fix stack pointer, you'll start new firmware anyways - relocate a small routine immediately below SP - call that routine - relocate the (...) (25 years ago, 3-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: fast firmware downloader - and compilers
|
|
I'll have to try fastdl at some point. My pbFORTH image is assembled to live at 0x8000 and be loaded just like "real" firmware. If I use fastdl, how do I have to change my firmware assembly output to accomodate it? On the subject of configurable (...) (25 years ago, 3-Oct-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: fast firmware downloader
|
|
(...) Erm, hrm, well... the reason I didn't ship it yet is that it won't compile with any released version of legOS. In order to gain full configurability, I had to set up a seperate directory structure, with its own include tree and stripped down (...) (25 years ago, 3-Oct-99, to lugnet.robotics.rcx.legos)
|
