Craig Shelley
New Member
- Joined
- Jan 2, 2014
- Messages
- 20
- Reaction score
- 20
- Country
- United Kingdom
In the nand, there are two data partitions, which get mounted as nand1 and nand2 after Linux has booted.
The config.bin file ends up getting copied to nand1. I'm fairly sure that these partitions do not get touched when the bootable SD cards are used to reprogram.
I know that after doing a chip erase of the nand, installing from the bootable SD, the nand partitions are automatically initialised.
I also know that the bootable SD card does not perform a chip erase, instead it erases only what is needed to put the firmware components into the correct locations.
The only way I currently know of doing a chip erase is via the debug Port.
After fully erasing the nand, the RBL will automatically try to boot off the SD card without having to press and hold m on startup.
I would like to modify SDBoot to make it do a chip erase. But this is potentially dangerous because if the process goes wrong, the device could enter a boot loop, automatically booting off the SD card, repeatedly erasing the nand.
After not to long the nand will be burnt out.
I'm going to have to look at recompiling SDBoot to add the extra functionality.
This still does not solve the problem with the wrong firmware version being displayed.
I have a feeling that I'll be taking the camera back out of the car, and moving those surface mount resistors after all.
EDIT:
I've confirmed that SDBoot does erase the entire nand flash memory before reprogramming the firmware.
The config.bin file ends up getting copied to nand1. I'm fairly sure that these partitions do not get touched when the bootable SD cards are used to reprogram.
I know that after doing a chip erase of the nand, installing from the bootable SD, the nand partitions are automatically initialised.
I also know that the bootable SD card does not perform a chip erase, instead it erases only what is needed to put the firmware components into the correct locations.
The only way I currently know of doing a chip erase is via the debug Port.
After fully erasing the nand, the RBL will automatically try to boot off the SD card without having to press and hold m on startup.
I would like to modify SDBoot to make it do a chip erase. But this is potentially dangerous because if the process goes wrong, the device could enter a boot loop, automatically booting off the SD card, repeatedly erasing the nand.
After not to long the nand will be burnt out.
I'm going to have to look at recompiling SDBoot to add the extra functionality.
This still does not solve the problem with the wrong firmware version being displayed.
I have a feeling that I'll be taking the camera back out of the car, and moving those surface mount resistors after all.
EDIT:
I've confirmed that SDBoot does erase the entire nand flash memory before reprogramming the firmware.
Last edited: