 | | semi, sort of, not quite but almost 0.2.4
|
|
Hey, everybody- It's been a while (nearly seven months, actually) since there was a legOS release. Markus did quite a lot of work on it before he dumped it into CVS, and Paolo Massetti and I have put in a little bit of work on it over the past (...) (24 years ago, 23-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Possible bug with bss allocation
|
|
(...) I have a proposal to the legOS developers: The current tool chain to generate executables for legOS is a little off: We generate coff-h8300 from .c or .S sources, next ld generates symbolsrec relocated files from that. This step is done twice (...) (24 years ago, 22-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Possible bug with bss allocation
|
|
(...) Thanks for the fix, it works great. Dave Baum (24 years ago, 22-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Possible bug with bss allocation
|
|
(...) The common section is aligned to 16 bytes by ld. This is unknown to the tools generating the final .lx files. The fix is to force the alignment of the .bss section to 2, with this ld will generate files that work with the current tools. I (...) (24 years ago, 22-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Possible bug with bss allocation
|
|
I was having some random hangs with a legOS program. If I added a little code or subtracted a little, everything started working again. I've isolated it to a problem whereby writing a zero to the last byte of bss data will hang the RCX. This only (...) (24 years ago, 22-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) In active mode, the value you read from the light sensor depends on how you power the sensor and read the A/D converters. In particular, the delay from the time you turn off the power to the sensor to the time you do A/D conversion matters. (...) (24 years ago, 21-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | light sensor problem?
|
|
Ok, so i'm supposed to be the guru, but I don't get it: all my light sensors are currently showing a range of adjusted values between 60-310, instead of the 20-110 that I'm used to seeing. The sensor is in active mode (passive mode still shows (...) (24 years ago, 21-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: EGCS and GCC
|
|
(...) Maybe your reply got sent to the cyber-trash, too. I never saw my post or any replies. (...) Yeah, pretty simple. Hopefully there won't be too many other instances in the kernel, and they're all one-liners to fix. (...) Well, I'll probably (...) (24 years ago, 20-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LugNet links
|
|
(...) I'll take care of it... Luis ---...--- "Summertime... and the living is easy... fish are jumping and the cotton is high... So hush, little baby, baby don't you cry." -Ella ---...--- (24 years ago, 20-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LugNet links
|
|
(...) If someone could email me a list of URLs, I'll take care of it. --Todd (24 years ago, 20-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: EGCS and GCC
|
|
I am using egcs version 1.1.2. When I make cross LANGUAGES="c c++", it will run, but then display gcc:cc1 Internal error 7, or something close to that. It is an internal error to the compiler, and the error code genterated in 7. When I compile it (...) (24 years ago, 20-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: EGCS and GCC
|
|
(...) I saw it. Don't know if others did. I thought I replied? (...) one liners :) (...) That would be nice if true :) (...) It will definitely need some more HOWTO updates. That's quite OK, especially if it means we can "standardize" all the (...) (24 years ago, 20-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: EGCS and GCC
|
|
Which version of egcs? And what are the errors? Luis (...) ---...--- "Summertime... and the living is easy... fish are jumping and the cotton is high... So hush, little baby, baby don't you cry." -Ella ---...--- (24 years ago, 20-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: EGCS and GCC
|
|
Okay. Binutils compiled and installed fine, but when I try to compile egcs, I get many errors, unrelated to any libraries. When I run the failed commands manually (without make), they compile fine. Then I got an error about not having enough virtual (...) (24 years ago, 20-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: EGCS and GCC
|
|
(...) made (...) Andy (and others), Note that you can now use gcc 2.95.2 to compile legOS - I posted about this yesterday, but it seems to have got lost in the LugNet hiccup. The problem is not with the compiler, but with the options in the in-line (...) (24 years ago, 19-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: EGCS and GCC
|
|
Shouldn't. That's what my current set of tools was compiled with. When I referred (elsewhere?) to "changes with 2.95," I meant only that 2.95 has a different configuration syntax. Luis (...) ---...--- "Summertime... and the living is easy... fish (...) (24 years ago, 19-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | EGCS and GCC
|
|
I am downloading the source for egcs 1.1.2 now. I was jsut wondering if it made any difference if I was compiling this, and binutils, with GCC 2.95. I know that there are errors in it, but I did not think that this will be a problem. Just thought (...) (24 years ago, 19-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: missing posts
|
|
I think lugnet had a burp. I just got a post I sent days ago, plus (I think) the other ones that you sent. Luis (...) ---...--- "Summertime... and the living is easy... fish are jumping and the cotton is high... So hush, little baby, baby don't you (...) (24 years ago, 19-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | missing posts
|
|
i posted the diffs for the remote 2 hours ago, but they haven't appeared yet... anyone know if lugnet has trouble with posts containing chars from diff? (like the less than and greater than symbols)... chris (24 years ago, 18-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | patch 1/3
|
|
weird, i posted this an hour ago but nothing happened... i'll try posting in parts... patch util/dll-src/rcxtty.c 126c126 < dcb.Parity = 0; // 0-4=no,odd,even,mark,space --- (...) patch kernel/lnp-logical.c 212c212 < S_MR =SMR_P_NONE; --- (...) (24 years ago, 18-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS + Lego Remote
|
|
here are the diffs, apply against 0.2.4... um, not sure how to do multi-file diffs, so there are 5 files here; note that dll.exe needs to be rebuilt to handle the changed parity... still looking in the kernel for a clean place to stick in timeout (...) (24 years ago, 18-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Persistent globals
|
|
(...) <example code> This worked great for us using legOS 0.2.4. Thanks Eddie! Regards Tobias (24 years ago, 18-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS + Lego Remote
|
|
Sweet. I've got a remote, and I'd love to be able to play with it- would make the robot look much more interesting to my little brother and sister :) Luis (...) ---...--- "Summertime... and the living is easy... fish are jumping and the cotton is (...) (24 years ago, 18-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS + Lego Remote
|
|
Sure, I'll clean it up and post the diffs tomorrow... chris (...) (24 years ago, 17-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Persistent globals
|
|
(...) Mike, I don't really have time to test this tonight, but if you find that it does work, please let me know- I'd love to add this to the HOWTO. It's an interesting trick to know. Luis ---...--- "Summertime... and the living is easy... fish are (...) (24 years ago, 17-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Persistent globals
|
|
(...) [snip great gobs of neat info] (...) Assuming it works, it helps a lot! Thanks much. -- "Do not go gentle into that good night. Rage, rage against the dying of the light." - Dylan Thomas Mike Ash - (URL), <mailto:mail@mikeash.com> (24 years ago, 17-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Persistent globals
|
|
(...) legOS 0.2.3 or 0.2.4 will load .strings and .rodata sections just like the .text section. With this you can achive persistent data by storing your variables into the .strings section. There are some nice features in gcc to help with this. Just (...) (24 years ago, 16-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Persistent globals
|
|
(...) It is correct. Everytime you reload a program it re-initializes everything, including a specific program's memory, so all that kind of information is lost. I'm not sure that there is a way to duplicate that behavior, as things stand. The only (...) (24 years ago, 16-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Persistent globals
|
|
Whew, I've been writing here a lot. I guess now that things work, it's a lot more enjoyable! :) Anyway, here goes.... I recall that with older versions of legOS, global variables were only initialized once, when the program was downloaded. (...) (24 years ago, 16-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS + Lego Remote
|
|
Chris- Do you have a patch for that? I'd love to test this myself (not sure if I can- MB crash last week has me still under pretty limited capacity) and if it works reliably, integrate it into the actual source tree... Luis (...) ---...--- (...) (24 years ago, 15-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS + Lego Remote
|
|
um, never mind... i just set parity to odd for both the LegOS kernel and compiled a new version of dll.exe with odd parity, and it worked fine... have a callback that works for the remote in unofficial 0.2.4 now... a bit unexpected though, with the (...) (24 years ago, 15-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange crash (and possible fix)
|
|
(...) Well, it'd be nice to know, certainly, but I'm not going to look into it too hard. The fact is that it works wonderfully now. I compiled and downlaoded probably twenty versions of my program over the past two hours or so, and not a single one (...) (24 years ago, 14-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Strange crash (and possible fix)
|
|
Mike- I wish I knew. I have frequently seen the same kinds of "random" changes produce better results. For example, I had one piece of code that used a switch statement- 19 statements in all. I added a 20th and poof... it froze. I have no idea what (...) (24 years ago, 14-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Strange crash (and possible fix)
|
|
I had a strange experience today. My program likes to crash a lot. I accept this as a fact of life now; part of it is the difficulty in debugging it, and part seems to be the beta-ness of legOS. However, today, I tracked down one particularly evil (...) (24 years ago, 14-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LugNet links
|
|
Some time ago I asked the powers that be at lugnet to change the links, and never heard a word from them about it. Maybe it is time to hassle them about it again. Luis (...) ---...--- "Summertime... and the living is easy... fish are jumping and the (...) (24 years ago, 12-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LinuxPPC success
|
|
(...) I would like to add it to the HOWTO, or at least to someplace where it is widely publicly available- probably with the instructions at (URL) On another note, where does one find the LNP stuff these days? Arthurdent (...) /Everything/ is a bad (...) (24 years ago, 12-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | LinuxPPC success
|
|
Well, Dave's advice worked like a charm. Thanks, Dave! It seems like this would be a good thing to add to the HOWTO, although who knows how many other people want to use legOS on LinuxPPC. On another note, where does one find the LNP stuff these (...) (24 years ago, 12-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | LugNet links
|
|
Hey, everyone. I was just checking out the lugnet page, and was thinking it might be a good idea to update the LegOS links. Perhaps include a link to SourceForge, and fix the HOWTO link. What do you think? And how does one go about this? ROSCO (24 years ago, 12-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS on LinuxPPC
|
|
(...) The problem is due to a bug in gcc 2.95. The assembly version of memcpy fixes the LegOS kernel, but all your user programs are subject to the same bug. Until it's fixed in gcc, you're stuck with egcs. Regards ROSCO (24 years ago, 12-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | LegOS + Lego Remote
|
|
Hi All, I've tried patching LegOS 0.2.3 lnp_integrity_byte's state machine to capture the transmissions by the Lego remote. The problem is, I only get a response when I press some combinations of two remote buttons at a time, other combinations and (...) (24 years ago, 11-Jul-00, to lugnet.robotics.rcx.legos)
|
