 | | 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: Using CAN to Have More Than 3 Motors/Sensors
|
|
(...) Mark! This is great work! I am always impressed when someone goes beyond wishing for stuff that LEGO did not provide us with and then actually builds a working model. Your idea of a modular motor/input module is one of the great benefits of (...) (24 years ago, 22-Jul-00, to lugnet.robotics.rcx)
|
| |
| | Re: New to PBforth - a few questions
|
|
Hi David, (...) Actually the power difference is hard to notice, regardless of platform. The different power levels are achieved using pulse width modulation, but something about the motors (maybe the flywheels) means that it's hard to notice much (...) (24 years ago, 21-Jul-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | 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)
|
