 | | Re: LegOS on LinuxPPC
|
|
(...) Ah, excellent. I saw this post when you posted it, but didn't think about it much at the time. I'll give this a shot and report back. Thanks very much. -- "Do not go gentle into that good night. Rage, rage against the dying of the light." - (...) (24 years ago, 11-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: LegOS on LinuxPPC
|
|
In article (...) I have had better luck with egcs-1.1.2 rather than gcc 2.95.2. I've heard that there's a problem with the way gcc 2.95.2 generates code for memcpy. I've also heard that the fix is to use an assembly version of memcpy instead of (...) (24 years ago, 11-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | LinuxPPC gcc errors
|
|
Ok, I have some error messages here. I'm following the exact instructions in the HOWTO, except for using gcc 2.95.2 instead of egcs 1.1.2. I recall trying egcs with similar results. The make proceeds fine for a while. Then I get this message, and (...) (24 years ago, 11-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Expanding the available input/output ports of the RCX
|
|
in article NEBBIHKHBKAFAGKCCILO...s@olf.com, Ram Meenakshisundaram at rmeenaks@olf.com wrote on 7/7/00 9:58 AM: (...) I am a Lego purist, so I don't want to modify my pieces. Of course, if Lego ever creates an official multiplexer, I'll probably get (...) (24 years ago, 10-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | LegOS on LinuxPPC
|
|
I recall somebody writing to this list about a problem with LegOS under LinuxPPC, and the message seemed to imply that things were mostly happy. I can't make the compiler compile. I'm using gcc 2.95.2. The make proceeds for a good while, then I get (...) (24 years ago, 10-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Expanding the available input/output ports of the RCX
|
|
Ram Meenakshisundaram schreef: (...) You could use the sensors that came with the Cybermaster kit, they have a built-in resistor so it should be possible to hook up two of those on one input port and by using RAW values see which switch is pressed. (24 years ago, 10-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | RE: Expanding the available input/output ports of the RCX
|
|
Sure you can try using just three input/output ports, but eventually you end up scaling back you designs. Of course, you can always buy another RCX to increase the number of ports, which will throw you back $200. Adding a multiplexor is such an easy (...) (24 years ago, 9-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | Re: Expanding the available input/output ports of the RCX
|
|
(...) [imho] It's sometime very creative to build your own multiplexer as it is a part of the project. [/imho] The site of Michael Gasperi has a lot of informations about those input multiplexer : (URL) (24 years ago, 9-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | (canceled)
|
|
|
| |
| | Re: Expanding the available input/output ports of the RCX
|
|
(...) How about coming up with creative solutions within the limits of the hardware? In the real world, you can't always make it bigger and better, sometimes you have to do it another way. It's a much more interesting problem to "do it with only (...) (24 years ago, 8-Jul-00, to lugnet.robotics, lugnet.robotics.rcx)
|
