 | | RE: Firmware download troubles
|
|
The size of the firmware isn't going past the 0xcc00 boundary, is it? The firmware in the RCX only does a sum on the bytes up to 0xCBFF in the downloaded firmware, as far as I recall... Cheers, Ralph (22 years ago, 13-Dec-02, to lugnet.robotics.rcx)
|
| |
| | Re: BrickOS Threading...
|
|
Joe, (...) Maybe a special kernel build for testing purposes that increments the lower sys_time word by 0x4000 instead of 1. This will greatly increase the opportunity for this glitch to occur (from once every 65 seconds to once every 4ms.) You (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Firmware download troubles
|
|
(...) The problem he's describing, if it's the same one I have, is independant of the position, direction, and power level of the tower. It seems to have something to do with BrixCC itself. The only thing I find puzzling is that Matt (the other Matt (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx)
|
| |
| | Re: BrickOS Threading...
|
|
Steve, I checked in some changes this morning (into cvs) to put the motor controller back at the 1 ms interval. However, I want to complete the get_sys_time() updates that Mark Riley has proposed; so that can be tested as well. I am not sure when (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Firmware download troubles
|
|
(...) It's funny that you should bring this up - I've had exactly the same problems with several RCX's and downloading firmware from BrixCC. The only solution I've been able to find is to download the firmware using the RIS2.0 software and then (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx)
|
