 | | Re: Name of Robolab RCX2 Firmware file? —Ralf Krause
|
| | | Hi, you can see the firmware version of the file just b_e_f_o_r_e you load it into the RCX. This would spend a lot of time because every firmware download needs more than 4 minutes with normal download speed. In the newer versions the firmware (...) (23 years ago, 9-Dec-01, to lugnet.robotics)
|
| | | |
| | | | | Re: Name of Robolab RCX2 Firmware file? —Brian C. Rakitin
|
| | | | HI, Thanks for the responses. The first line of the file ROBOLAB:Engine:VI.LI...maware.txt is: S00F00006669726D3033...2E6C676F05 The first line of the file ROBOLAB:Engine:VI.LI...are325.txt is: S00F00006669726D3033...2E6C676F08 The last line of both (...) (23 years ago, 10-Dec-01, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Name of Robolab RCX2 Firmware file? —Dave Baum
|
| | | | (...) NQC is picky about line endings for firmware files. On a Mac, it assumes Mac line ending, on Windows, it expects DOS endings, Unix for Unix. There are a few cross-platform combinations that work ok, but not all work. If you have BBEdit Lite, (...) (23 years ago, 11-Dec-01, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Name of Robolab RCX2 Firmware file? —Brian C. Rakitin
|
| | | | Thanks again Dave. As it turns out, nqc on Mac OS X expects a firmware file with UNIX line endings. BBEdit Lite 6.1 for OS X did the job just fine. After saving with UNIX line endings, nqc was able to download the firmware. B. (...) (23 years ago, 11-Dec-01, to lugnet.robotics)
|
| | | | |
