 | | Re: All Lego Ack Circuit for LDCC
|
|
(...) indeed, the construction of this beast may be very different (e.g. metallic contact, 0 resistance... and a lot of bounce almost completely avoided with conductive rubber) Philo (21 years ago, 19-Jun-03, to lugnet.trains, lugnet.robotics.rcx)
|
| |
| | Re: Error linking c++ with gcc 3.3
|
|
No, I'm sorry, it doesn't seem to quite work. But it does get rid of the 3 errors at the bottom - Now it's just the operator new/delete stuff. I replaced the stub.c with the thing below, made libc++.a, and just make in lib/c++, and then go to demo (...) (21 years ago, 19-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: All Lego Ack Circuit for LDCC
|
|
Thanks Philippe, I wasn't sure of the characteristics of the Cybermaster touch sensors. Also, I didn't want anyone thinking it was OK to use this guy: (URL) checking the resistance (yeah, I know it looks different, but you never know... :-) Mark (...) (21 years ago, 18-Jun-03, to lugnet.trains, lugnet.robotics.rcx)
|
| |
| | Re: All Lego Ack Circuit for LDCC
|
|
(...) All touch sensors I measured have a "pressed" resistance between 400 and 600 ohms (depends on touch sensors and on pressure, more pressure meaning lower resistance). Actually there is no separated resistor, you get the internal resistance of (...) (21 years ago, 18-Jun-03, to lugnet.trains, lugnet.robotics.rcx)
|
| |
| | Re: Error linking c++ with gcc 3.3
|
|
(...) You should add -fno-rtti -fno-exceptions to the CXXFLAGS in Makefile.common. To get rid of the operator new/delete errors you can replace lib/c++/stub.c with a stub.cpp containing the following. Don't forget to update the Makefile. This works (...) (21 years ago, 18-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | All Lego Ack Circuit for LDCC
|
|
Hi All, One of the features of the LDCC firmware is the ability to read the configuration variables out of a DCC decoder installed in a train motor. In order to do this, you need to connect a small circuit consisting of one or two resistors from the (...) (21 years ago, 18-Jun-03, to lugnet.trains, lugnet.robotics.rcx)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) The only time(s) I encountered this type of issue were when I compiled the .srec with different set of compiler settings (or with a different set of header files) than what was used for compiling the Demo/Application code. For instance, if I (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) As for this one, I thought I linked the library statically so you wouldn't require it. Oh well, I'll fix that and let people know when I've updated it. You shouldn't need to install the libraries to use the tools. Michael (Zapp not van der (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) <<snipped>> (...) <<snipped>> (...) I've gotten the same error with gcc 3.2.3 that I compiled and gcc 3.2.2 that the other Michael compiled. I couldn't get gcc 3.3 to compile on my machine. Running gcc -v I get the following responses: (my (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: OS X Complier problems solved--now struggling with BrickOS
|
|
(...) No, they aren't problems in your end, and no, they're also not gcc's fault. LegOS uses a now unsupported extension to C: multi-line strings. The way they can be made to work is by inserting \n\ on the end of the offending lines. I did this to (...) (21 years ago, 17-Jun-03, to lugnet.robotics.rcx.legos)
|
