 | | Rotation sensor bug found (maybe!)
|
|
I think I might have found a bug in the ds_rotation_handler (direct-sensor.c). The problem arises when the STATE_0_VALUE is checked using the IN_RANGE macro. As STATE_0_VALUE is 1023U<<6, which is about the max value for an unsigned, adding to it (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) Actually, no. On attempt 16, you reserve some more bits further down for the new version number :-) Cheers, Ben. -- (URL) grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) I'd prefer 11111b for broadcast, in keeping with TCP/IP. Cheers, Ben. -- (URL) grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
I personally can't see needing more than about 7 tasks listening at one time anyway. Keep in mind that the resources on the lego are very very small. As far as reserving an address for IPC that would be fine. We could reserve 00000b for IPC and (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LNP Repost
|
|
(...) I can see this. but it is starting to feel a little cramped on the ports, though. What functionality is port 0 reserved for? Actually, I was thinking of reserving a host address (such as 0x0) for IPC. I'd probably want to have more than 3 (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rotation sensor help (some progress)
|
|
Again about my problems with legOS and the rotation sensor. First of all I checked the four values returned by both my two rotation sensor. They are different from the ones inside direct-sensor.c but anyway inside the specified range legOS: (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
I figured that out... Thanks... I am subscribed via email now! Much nicer... I am just too lazy to remeber to go check news groups. -Jake (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
Jacob S. Barrett <jsbarrett@acm.org> wrote in message news:3716681C.D5C8C6...acm.org... (...) You can subscribe to this newsgroup as a mailing list. I would prefer to see it on this group (or less thing to subscribe to) or to have lugnet make a new (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | LNP Repost
|
|
I thought it might be good to repost this with some changes... Okay a little smaller... Only a 4 byte header... |0|1|2|3|4|5|6|7|0|1...3|4|5|6|7| ---...--- | 0xF | VER | TOADDR | PORT| FRADDR | PORT| PAYLOADLEN | ---...--- / PAYLOAD / ---...--- / (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) I am not in position right now, time-wise, to contribute to the LNP, but I am very interested, and may have time to contribute soon. In the mean time, I'd like to keep up with the project. I don't know if you realize, Jacob, but if you prefer (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
This would almost have to be a UDP like protocol just because the RCX has such limited resources and the complexity of adding transmision control to the protocol would be nasty. I really hate news groups, I like having messages sent to me directly. (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Rotation sensor help
|
|
I need some help with legOS and rotation sensors. I compiled and downloaded the demo/rotation-sensor.c program. The behaviour I get on my RCX is not what I expected. When I turn the sensor clockwise, the LCD toggles between 0 and -1, while (...) (25 years ago, 15-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) Sounds good. Does it provide a stream interface or datagrams only? My faulty memory suggests that it might be the latter. If the network implementation supports packet reassembly (packets larger than MTU), there may not be a need for a stream (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS Network Protocol
|
|
(...) I too may be interested in this, although probably only the higher level stuff ie I'm not too sure how good I'd be at interfacing with the IR. Anyway, I had a look around and I found some references on a protocol layered on top of IP called (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: firmdl error
|
|
(...) [Luis sent me the .srec file so I could take a look at it.] The problem is the length of the first line of the srec file. The first line is 80 characters long, which is too long. The cryptic error message is because the line passed into the (...) (25 years ago, 14-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | firmdl error
|
|
Can anyone here help me out with this error? I have no idea where to even begin. When downloading my binary (light-brait-with-debug.srec) I get the following error message: [usr@cs liv]# legOS-0.1.7/util/firmdl light-brait-with-debug.srec (...) (25 years ago, 13-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS is great!
|
|
(...) Luis, this would be great. Obviously I don't have anything at all to contribute at present moment, but will do as soon as I have something worth to be shared. (...) Yes please. I wait for your URL. Thanks Mario (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS is great!
|
|
(...) I'd love to set-up (and even host) such a depository. However, at the moment, I don't have much to contribute. As I'm working my rear-end off right now, that should change by friday, but :-) (...) Yeah. I was thinking about a HOWTO, in fact. I (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS is great!
|
|
Last weekend I finished setting up my PC (win 95) to use legOS. It took some more than a while to be ready, but now I'm absolutely happy with it. legOS is simply great and I'm very intrigued with it now. I'd like to thank Markus L. Noga and all the (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Installation trouble with Linux
|
|
My system is a Redhat 5.1, i586. I had some problems installing the LegOS. Here are the steps I took. 1. I successfully installed binutils, unpacked the legOS-0.1.7 package. 2. I installed the egcs-1.1b package with the exact options given in the (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | PS
|
|
As an addendum to my light message, I checked direct-sensor.h, and the numbers there seem to work out just fine. Could this be a compiler problem on my part? Just another thought- Luis ###...### "They call the faithful to their knees to hear the (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | light values?
|
|
Another question before I call it a night- under LegOS 0.1.6, light-sensor values were restricted to the range 0-100. Under 0.1.7, I'm now getting a max value (pointed straight at a light bulb) of about 263, or once even 272. 255 would make sense to (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Updated Win32 toolchain
|
|
I've put an updated Windows 95/98/NT H8/300 cross-compiler, based on EGCS 1.1.2 (basically, the EGCS 1.1.2 release plus Mumit Kahn's Win32 patches, plus a couple of source hacks), on (URL) - this time, I've bundled in enough to compile without (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: floats
|
|
Thanks, Kekoa. (...) Well, as it appears I don't have much of an option, I'll stick to ints then :-) -Luis ###...### "They call the faithful to their knees to hear the softly spoken magic spell:" "There's no place like home... There's no place like (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: floats
|
|
(...) The errors you see are due to the fact that there is no hardware support for floating point. The compiler substitutes calls to the software equivalents, which do not exist; hence the linker errors you see. The math routines that do exist are (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | floats
|
|
When I try to use a float in my code, I get a compiler message somewhere along these lines: <begin error message> ../code/light-brait....t-brait.c: undefined reference to `__floatsisf' ../code/light-brait....t-brait.c: undefined reference to (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) legOS has a software solution built-in - when you are ready to quit, hold down the on/off button and press the 'prog' button. Hope this helps! Cheers, Richard (26 years ago, 9-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Web based LegOs compiler for the underprivileged?
|
|
I recently downloaded a program for the palm pilot that displays up to date movie times and locations based from perl parsed data from movies@yahoo.com It is a great program, but getting and setting up Perl on my system was a real pain. Luckily (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: loading s/w
|
|
(...) I skipped something here. The assumption I made is that you want to load new custom firmware. If you want to load the Lego firmware, find the Firm0309.lgo file in your Mindstorms directory, and load that into the RCX exactly as you would (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) I belive LegOS breaks firmware deletion, in the sense that the "delete firmware" opcode is not supported by the IR routines, but I could be wrong about that. If you are using an AC adapter and no batteries, the easiest thing to do is to turn (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) I observed the same phenomenon, only I was using gcc-2.8.1. I never did find out what was wrong, but I assumed it might have something to do with the new libgcc stuff which appeared in 0.1.7. I eventually got working by installing egcs-1.1.1. (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: loading s/w
|
|
(...) Have you tried the firmdl program in the utils directory? You might need to recompile the executable manually, as on my system it gets compiled for the h8 :) And there's an environment variable that you can set RCXTTY or something - if you (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | xanim plays mod files
|
|
The new version of Xanim (xanim2801.tar.gz) will play the mod files on the Lego MindStorms CD. (URL) hosted LegOS embedded - cool! (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | loading s/w
|
|
After successfully downloading and running tm-and-ir.srec (Linux host), I cannot download to it any longer. Upon power up, the LCD displays LEGO!5 and I can select any other program slots. I could just re-load firmware in '95 but I don't want to (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
OK, I have some more information now. When I build 0.1.6 in my new environment it works fine. 0.1.7 and the snap exhibit the problem. The problem is that when using tm-and-ir, the 'view' button (which is supposed to send the message "Hello World") (...) (26 years ago, 8-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) The helpful folks on the crossgcc mailing list told me that this error indicates that no libstdc was found, so no binary could be generated for the target (not host) platform. Since legOS provides a replacement library, there is no problem (...) (26 years ago, 7-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
This site is quite useful: (URL) found it via ftp.cygnus.com/pub/crossgcc. I hope it helps you out. Cheers, Vic (...) LANGUAGES="c (...) that (...) (26 years ago, 7-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
I got everything to build using egcs 1.1.2, but I am having problems with the tm-and-ir demo (after modifying it for the new execi syntax) which make me think maybe egcs is not generating correct code. I used the build instructions at (URL) did use (...) (26 years ago, 7-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) I did not have this problem. Sounds like Fortran. Did you 'make LANGUAGES="c c++"' or just 'make'? The latter makes the Fortran stuff, too. Remember that if you specify LANGUAGES when building, you should specify the same value when (...) (26 years ago, 6-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) I got the same message, and your reasoning about the content of the message sounds AOK by me. But then I did a make install, and that crudded out on me, with the message In file included from ../../../egcs-1.1.2/...com.c:198: (...) (26 years ago, 6-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
I have. I got the same message. I assume it is part of the test suite. I just bit the bullet and did a "make install" anyway, and it works fine. I take it as saying that it cannot generate an executable for the host platform, which would be true, (...) (26 years ago, 6-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) Has anyone successfully built the above target using egcs-1.1.2? My attempt failed in libiberty: ... configure: error: installation or configuration problem: C compiler cannot create executables. make: *** [configure-target-libiberty] Error 1 (...) (26 years ago, 6-Apr-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: cputs / argc,argv / snapshot
|
|
Oops. Did I say David? That's what you get for speaking on the phone and typing simultaneously. I meant Dan, of cause! (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | cputs / argc,argv / snapshot
|
|
Hi, I implemented a cleaner cputs(). Should work with all compilers, also 20% smaller. I went ahead and implemented argc/argv parameter passing for execi as well. This prompted a bugfix for memcpy, which I did create. As I was at it, I also merged (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: cputw
|
|
(...) By "doesn't work", I assume the patch applied successfully and your compiler barfed with some sort of error message or generated incorrect code. That would tend to (at least slightly) indicate that the problem that I was trying to fix may have (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | cputw
|
|
Maybe we'd better opt for unsigned char c=word&0xff; cputc_... cputc_... c=word>>8; cputc_... cputc_... instead - your patch doesn't work with my compiler version! This may generate better assembly code, too, as word is already in a register. (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS ...
|
|
Hi Mark, you might consider joining the legOS mailing list www.lugnet.com. We're currently working on network protocols for the IR device. POSIX compliance is very worthwile. I'm considering to make all devices files. Yes, even sensors. That way, we (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: motor speed
|
|
Hi Lou, that's great. Markus. (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Uploading *.prg To RCX
|
|
Adamski wrote in message ... (...) I've been out of the (this) loop lately. I don't recall; were .prg the compiled versions or the text file versions? (You can use Mind Control to interprete and upload text files. ) Eric Brok Visit LEGO ON MY MIND: (...) (26 years ago, 30-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | Passing arguments to task
|
|
Is there an accepted method of passing arguments to a task which is spawned with execi? I have a method which I have instrumented, but it is awkward. -- No honest business is promoted by spam with the possible exception of Hormel. (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Speed Fix
|
|
(...) I've been busy. I have also added a patch for control of arbitrary motors. (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Motor Speed Fix
|
|
Oops! The URL is (URL) have also added a patch to fix cputw(). (...) (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Motor Speed Fix
|
|
I have a patch on my legOS page which fixes a problem with motor speed control in legOS-0.1.7. -- No honest business is promoted by spam with the possible exception of Hormel. (26 years ago, 30-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | I found out why I couldn't compile demo/first-c++
|
|
Make clean doesn't remove object files in lib/mint, lib/c++, or lib/c, and legOS is shipped with compiled objects in there. Markus' environment is somehow different from mine, and sensor.o was looking for a symbol (something to do with getting a (...) (26 years ago, 29-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Uploading *.prg To RCX
|
|
Is there a program that allows you to download the prg files created from the Lego CD-ROM to the RCX without loading the Lego CD program? Help Appreciated! Adamski _______ <adamski2000@adamski...rve.co.uk> (26 years ago, 28-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | legOS Network Protocol
|
|
Markus, I have been away for the last week or so. What have I missed in the discussion on LNP? I would like to get cracking on this. I have 2 or 3 guys over here who want to get into this too. -Jake Jacob S. Barrett jsbarrett@acm.org (26 years ago, 28-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: gcc build instructions for linux
|
|
(...) week ago. (26 years ago, 26-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | gcc build instructions for linux
|
|
Linux Tools for Hitachi H8/300 Microprocessor Development (URL) came across this site today. It has good instructions for building the gcc h3000 compiler on Linux. I thought people here might also be interested in the crt0.s 'C' startup source. I (...) (26 years ago, 26-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: names
|
|
(...) Will you resist the temptation 2nd time around it TLGs lawyers decide that the 'LegOS' name is a possible infringement? :) Richard(OS) (26 years ago, 25-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | names
|
|
Hello, some friends asked me today why I did resist the temptation of putting my name in the OS name. (It just never occurred to me.) However, there was somebody around who speaks Polish. He pointed out that Noga is Polish for leg. Totally caught me (...) (26 years ago, 25-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Compiler
|
|
Hi Lou, new binaries would be nice. I did create an archive, but I didn't feel like pumping those Megabytes over my modem yet. Mine is about 3.3MB, though - did your install script really strip all those executables? Markus. (26 years ago, 25-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
On the subject of licences: I always forget the details, coz they bore me, but as a result of working on Apache, I do know a few things: 1. There is an LGPL that is less restrictive than GPL. 2. GPL licences are not compatible with all other (...) (26 years ago, 24-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) I am by no means an license expert, but I just happen to have been reading about the GPL, and the MPL is pretty similar, though there are, of course, differences. The doc that I read stated that you can apply the GPL only to the files that you (...) (26 years ago, 24-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Compiler
|
|
(...) That does appear to have been the problem after all. (...) I eventually managed to build egcs on a different computer and copy it over to mine. Markus -- if you want the binary (bzip2 cpio) of binutils and egcs, I could point you at it for (...) (26 years ago, 24-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) Read the MPL again. It's not clear to me that you need to MPL all your code if you include unmodified source from something that is covered by MPL. But if you include MPL'd source, you certainly have to make it clear what code is covered by (...) (26 years ago, 23-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) Yes, I believe GNU configure is covered by GPL. I already changed legOS licensing to MPL because Kekoa's math routines are MPL. I'm not sure if we may continue to use them if we change yet again. What's the status on menuconfig? Are those (...) (26 years ago, 23-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) What about a simplified gnu 'configure' ? Or would using that scheme mean incorperating the GNU license as well? :) Richard (26 years ago, 23-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Compiler
|
|
I have discovered that the instructions for building the compiler on the legOS site have changed. They now say to build egcs, whereas they used to say to build gcc. This could, conceivably, be why I cannot build good files with 0.1.7, since I'm (...) (26 years ago, 23-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
Menuconfig would be a great thing. Xconfig would be even better, but I agree with Markus' concern about portability. The Linux kernel distributions get around the portability by simply providing all three config tools and letting you use the most (...) (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: How do I convert light sensor data into image bmp?
|
|
(...) Sorry, but I don't understand. Adamski _______ <adamski2000@adamski...rve.co.uk> (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) Exactly. Can you say "make config"? Ah, no, that won't do. "make menuconfig", maybe? We'd have to stay portable, though. That rules out "make xconfig" :-( (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
(...) That would be funky :) * Location of H8300 binutils * Location of perl (mergemap script) * Serial Port (RCXPORT) variable? * Compile Options? eg --disable-task-management ? That sort of thing? Richard (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: toolchain
|
|
How about a ./configure script? It just needs to ask two questions... write the answers in .config or Makefile.common or whatever suits your fancy and you're done once and for all. (26 years ago, 22-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Reworked Scheduler
|
|
I have gotten my scheduler changes to work. There is a patch against 0.1.7 on my legOS page ((URL) will apply most of the way against 0.1.6, but there are some bits that you will have to apply by hand due to differences in comments. I wouldn't be (...) (26 years ago, 21-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | How do I convert light sensor data into image bmp?
|
|
Hi: I would like to build a lego scanner using a single light sensor. I have found a number of sites which explain how to build them, however, I could use some assistance with how to convert the data collected into an actual image map. I understand (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) That is true. (...) Yes, we do, but is that something the tasks need to worry about? If the kernel has buffered 3 datagrams since the last timeslice, the next 3 waits would return immediately, since their criterion (datagram ready for reading) (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS-0.1.7 released
|
|
I finally got my scheduler working on 0.1.6. Porting it to 0.1.7 wasn't too painful. But when I tested it (I have been testing with demo/tm-and-ir), I found that there is junk (not necessarily alphanumeric characters) displayed on the LCD. Thinking (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) Try delay(). It's the non-scheduler version of msleep(). If you have a version that's better calibrated, please patch delay() in conio.c to reflect that. (...) A branch to itself is probably the best you can do, as you need an atomic (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8300 Stack and SLEEP
|
|
Sorry I'm late. I believe this is not an issue with legOS. legOS only calls the ROM powerdown function at the end of its kmain() loop, where the stack pointer should be in the on-chip RAM area anyway. When sleeping in the idle task, legOS directly (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) Yes, it's a start byte. Jacob suggested using 0xFn to identify protocol versions, 0xFF being the LEGO standard. (...) Actually, you wouldn't have to change much, just treat P_SUSPENDED tasks like they're P_WAITING and the condition failed. (...) (26 years ago, 20-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) Cool! (...) I had been thinking along the same lines. (...) What is the ID? Is it for framing? Is it a byte that is not currently taken up by a Lego bytecode? Do we even care about colliding with Lego's communication protocol? (...) (...) (26 years ago, 19-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | mailing list / 0.1.7
|
|
Hi Jacob, maybe you should join the legOS discussion group. lugnet.robotics.rcx.legos is available via NNTP, WWW and email from www.lugnet.com. Ah, by the way, 0.1.7 is out. Markus. (26 years ago, 19-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
Hi Lou, I'm discussing datagram networking with Jacob Barrett currently. They have some people working on it. The idea is to provide 1 byte of address space, using a per-host hostmask, just like TCP/IP uses per-net netmasks. A host with address 0x10 (...) (26 years ago, 19-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | legOS-0.1.7 released
|
|
Hello, legOS is an embedded OS for the LEGO Mindstorms RCX. It can be programmed in C, assembler, and some language elements of C++. Preemptive multitasking, access to all 32k RAM and low-level hardware control are some of its most prominent (...) (26 years ago, 19-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) It's what I'm doing for now in my debugger work. I haven't tried it out yet, though. (...) I carefully looked at the opcodes, and found that the shortest opcodes are all 2 bytes, and hand-coded the 2 byte instruction that jumps to itself. The (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) However, last night, I wrote a brute force (spin loop) msleep which works fine in the scheduler. I found that 800 iterations of an empty for loop with a 16 bit index comes pretty close to 1ms. Granted, I cheated a little, knowing that the (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) Oh, you're doing stuff inside the scheduler. Yeah, msleep doesn't work too well there :-) Yes, the pauses were only so I could see what was going on. Another thing you could do is print messages out the IR port; but I'm not sure how it would (...) (26 years ago, 17-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) I don't think it does. Of course, the source would answer definitively, but I also know that until I remembered to put the refreshes in there, I didn't get useful output. (...) I did that too. In my case, the lower byte was the priority (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Debugging
|
|
(...) That's the method I've used. Just be sure to put an lcd_refresh() after the cputw() call - I can't remember if cputw() does the lcd_refresh() or not. Another thing I've done is write out a number where the upper byte indicates a position in (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: H8300 Stack and SLEEP
|
|
Kekoa wrote: <<snipped original description of problem>> (...) <<snipped description of tests>> Once again, Kekoa goes the extra mile and proves what many of us are happy to be merely confident about. Someday, I'd like to be reincarnated as a grad (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Re: FW: H8300 Stack and SLEEP
|
|
(...) To be more precise, it applies to sleep mode and software standby mode as long as you set port 5 bit 2 to high before activating either mode. It does not apply to hardware standby mode, since that does not save registers or end with an (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: H8300 Stack and SLEEP
|
|
(...) After talking with Ralph over the weekend, I suggested a test he might do to figure out if port 5 bit 2 really does what he suggested it might. I don't think he did this test, so I fired up my RCX and hacked it together. I verified that port 5 (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Debugging
|
|
Do you guys have an established mechanism for debugging? I'm thinking of writing certain numbers to the display using cputw(). The idea being that the number frozen forever on the display will be the (approximately) last place the code was ok before (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Program Wanted
|
|
Does anyone have a program for the Recycler robot? Please help! Adamski _______ <adamski2000@adamski...rve.co.uk> (26 years ago, 15-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.legos)
|
| |
| | FW: H8300 Stack and SLEEP
|
|
(...) Markus, (and anyone else listening) I think it applies to the RCX power_shutdown() function as described in Kekoa's reference. The key is that this function puts the external RAM into low-power mode. If you are not calling power_shutdown() or (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | H8300 Stack and SLEEP
|
|
Hi All, If this is old news, ignore it... I just figured out this weekend (thanks Kekoa) that the H8/300 stack pointer (r7) and the power-down function in the RCX have a close relationship. The stack pointer MUST be in the on-chip RAM area (0xFD80 (...) (26 years ago, 15-Mar-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth, lugnet.robotics)
|
| |
| | Re: Idle process
|
|
I guess my earlier posting got out after all. I got the message from the NNTP server telling me to register. That is why a slightly different version of my message appears later in the group. (...) I plan to keep the idle task, now that I understand (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) The idle task actually has the lowest priority in my scheme, but there was some efficiency gained in making the task list loop around. If the idle task is always there, it makes for simplified code in multitasking startup if you rely on that. (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
Sorry this message is so late, I had to get registered for posting from my work address. (...) I, too, consider power saving to be a valuable (indispensible) feature. That is precisely the sort of thing that I feared I might be overlooking. Up 'till (...) (26 years ago, 11-Mar-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Idle process
|
|
(...) I, too, consider power saving to be a valuable (indispensible) feature. That is precisely the sort of thing that I feared I might be overlooking. Up 'till now, I had not worked on an embedded project which would benefit from using (...) (26 years ago, 9-Mar-99, to lugnet.robotics.rcx.legos)
|
