 | | Release candidate brickos-0.2.6.10 avail for testing
|
|
The brickOS team is pleased to announce our next test release. We are heading for our formal brickos-1.0.0 release but anticipate at least one more test release before then. Details regarding how to provide feedback are at (URL) can download from (...) (22 years ago, 18-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | More warning cleanup - const qualifier ignored on asm
|
|
In include/sys/bitops.h : // g++ warns about __asm__ const. we define the problem away. // the CXX symbol is predefined in the Makefile // #ifdef CXX # define ASMCONST #else # define ASMCONST const #endif But CXX is *not* defined in the Makefile. In (...) (22 years ago, 16-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | Trivial warning fix
|
|
This avoids an "implicit declaration of exit" warning. Max. Index: util/firmdl/mkimg.c ===...=== RCS file: /cvsroot/brickos/bri.../mkimg.c,v retrieving revision 1.1 diff -u -p -r1.1 mkimg.c --- util/firmdl/mkimg.c 20 Aug 2002 03:04:29 -0000 1.1 +++ (...) (22 years ago, 15-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Declaration of kernel_critsect_count
|
|
(...) Your request couldn't be more timely as I'm wrapping up a 0.2.6.10 test release this weekend. I've made this change in CVS and you will see it in the .10 test release. As I publish the 0.2.6.10 test release I'll post a message here explaining (...) (22 years ago, 15-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: How could I tell if I'd cooked the motor controllers ?
|
|
I presume you did all the usual things: Clean the RCX terminals, try other motors, check for unusual friction in the drivetrain (like, something is out of adjustment) ...etc? Jerry (...) (22 years ago, 15-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Declaration of kernel_critsect_count
|
|
kernel_critsect_count is declared volatile in kernel/critsec.c, but without the volatile keyword in include/sys/critsec.h - this upsets gcc3. Please could these declarations be reconciled? Thanks, Max. (22 years ago, 15-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | Re: no long range IR from laptop says Lego
|
|
Use a powered USB hub with the laptop. The power required for the USB IR Tower will come from the powered hub, rather than the laptop. - Rob (...) (22 years ago, 15-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: no long range IR from laptop says Lego
|
|
(...) No idea. I think these values are used for accounting, to ensure that all devices together don't exceed available power. But I don't know how well this is implemented. (...) Linux makes them available in readable form in /proc/bus/usb/devices (...) (22 years ago, 14-Feb-03, to lugnet.robotics.rcx)
|
| |
| | Re: dll and the USB tower
|
|
I have the same problem (I posted a note 3 days ago "Problem with Brickos ..." # 20311). In addition I don't get firmdl3 to download the firmware. Are you running Windows or Linux? Hans (...) (22 years ago, 14-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
| | How could I tell if I'd cooked the motor controllers ?
|
|
We had an informal Robo-Sumo thing at my work place tonight and I'm wondering if I killed my RCX. My 'bot had two gearmotors on A and two more on C to drive the wheels. Could they have drawn enough current when the 'bot was stalled to harm the RCX ? (...) (22 years ago, 14-Feb-03, to lugnet.robotics.rcx)
|
