firmware flash could lock NXT ?

This is where you talk about the NXJ hardware related topics such as the brick, sensors, LEGO pieces, etc.

Moderators: roger, imaqine, 99jonathan

New User
Posts: 4
Joined: Wed Jan 24, 2007 6:20 pm

firmware flash could lock NXT ?

Postby raph » Thu Jan 25, 2007 9:09 pm

Hi folks,

I am new to NXJ and didn't have enough time to review the code . Does each

Code: Select all

lejosdl demo.bin
actualy rewrite flash memory and could potentialy hang the device ?

See below a quotation of the libnxt library/bootloader primary source...

The main problem is that the SAM-BA firmware flashing utility, while useful, puts the flash chip under a lot of stress : the lock bits, which let firmwares write-protect themselves, are only guaranteed for about a hundred toggles. Each SAM-BA firmware flash results in two toggles of the lock bits of the first two pages of flash memory.


User avatar
Site Admin
Posts: 392
Joined: Fri Aug 04, 2006 4:03 pm

Postby bbagnall » Sat Jan 27, 2007 9:01 pm

The lock bits was a concern for us too. Apparently there is a limit of something like 100 firmware uploads, then the lock bits might stop functioning and you've got a dead NXT on your hands.

Not to worry though, the 100 upload limit does not apply as long as you leave the NXT in firmware upload mode. However, basically every time you push the button on your NXT to put it in SAMBA mode/upload LEGO firmware it counts towards the 100. But you can keep uploading NXT programs forever without wearing out the lock bits.

Apparently the 100 number is a very conservative estimate, so it can probably go much higher than this. If you are worried, my suggestion is don't jump between LEGO firmware and NXT frequently.

Return to “NXJ Hardware”

Who is online

Users browsing this forum: No registered users and 3 guests