 | | Re: NXT Firmware source code
|
|
(...) This is very good news. Thanks for the update. I've been waiting for this for a long time, particularly to have a look at the rather weak graphics capabilities. I've had an expanded font (and a much smaller one) kicking around for a while now. (...) (18 years ago, 12-Dec-06, to lugnet.robotics.nxt)
|
| |
| | RE: NXT Firmware source code
|
|
(...) I've downloaded firmware to NXT 100s of times with no apparent ill effect. (18 years ago, 12-Dec-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Firmware source code
|
|
(...) Flash memories all have a limited number of write cycles before they become unreliable. Usually, the on-chip write controller will "load-balance" the writes so that different memory locations all get used the same number of times, (...) (18 years ago, 12-Dec-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Firmware source code
|
|
(...) I am curious; have you ever had a situation where bad firmware locked up the NXT? And if so, what was the process to restore it to working order? (I don't have a bricked brick, I'm just asking for future reference.) (18 years ago, 12-Dec-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Firmware source code
|
|
(...) If this limitation had applied to the rcx, I'd have suggested this. Because you can control the outputs and read the inputs direct from a pc you could run an emulation of the rcx firmware running your program on the pc. The rcx would then (...) (18 years ago, 15-Dec-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Firmware source code
|
|
(...) Now that's a cool idea. I've been messing around with remote-controlling the NXT via Bluetooth from a PC application, and it seems pretty solid. You'd definitely have some timing issues running a remote emulation like you describe, but this (...) (18 years ago, 15-Dec-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Firmware source code
|
|
> This is very good news. Thanks for the update. I've been waiting for this for > a long time, particularly to have a look at the rather weak graphics > capabilities. I've had an expanded font (and a much smaller one) kicking around > for a while (...) (18 years ago, 16-Dec-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Firmware source code
|
|
(...) About a year ago, I got involved in doing some hacking on the Sony PSP, and wrote a Windows utility that will rip any font at a chosen size as a bitmapped C array. If I can figure out which computer I left the sources on, I'll make it (...) (18 years ago, 16-Dec-06, to lugnet.robotics.nxt, FTX)
|
| |
| | Re: NXT Firmware source code
|
|
(...) Ralph - I'll send them to you. If you want, mail me the byte format and I'll see if I can run a conversion. I presume it's in the vertical byte format that the screen uses? I did a full 256 character set that includes upper case, lower case, (...) (18 years ago, 18-Dec-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Firmware source code
|
|
"Steve Lane yahoo.co.uk>" <stevenrobertlane@<n...pamplease> wrote in message news:JABnK0.15z@lugnet.com... (...) Fortunately the most common failure mode is a reduction in the "longevity" of storage. Out of box, the Atmel ARM flash is specified to (...) (18 years ago, 18-Dec-06, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Firmware source code
|
|
(...) Not to put too fine a point on it, but the 100 cycle limit is only on the lock bits, I think. This is specified at the extreme limits of voltage and temperature. At normal room conditions, actual NXTs were reflashed (which cycles the lock (...) (18 years ago, 19-Dec-06, to lugnet.robotics.nxt)
|
