Hi,
I’m trying to flash a new board for a custom carrier board we have developed. It was getting stuck at the eeprom step and so I changed the tegra234-mb2-bct-misc-p3767-0000.dts file however did it incorrectly.
First I changed the CVM to 0x0 ( it was meant to be CVB)
cvm_eeprom_read_size = <0x0>;
cvb_eeprom_i2c_instance = <0x0>;
Then in fixing that I actually changed cvb_eeprom_i2c_instance to 0x100.
When i tried flashing it raised an exception that was mostly just numbers.
I went back and fixed that file to the following:
include “tegra234-mb2-bct-common.dtsi”
/ {
mb2-misc {
eeprom {
cvm_eeprom_i2c_instance = <0>;
cvm_eeprom_i2c_slave_address = <0xa0>;
cvm_eeprom_read_size = <0x100>;
cvb_eeprom_i2c_instance = <0x0>;
cvb_eeprom_i2c_slave_address = <0xae>;
cvb_eeprom_read_size = <0x0>;
};
};
};
Which should be correct however now the flashing program gets hung up almost immediately at:
*** no-flash flag enabled. Exiting now… ***
"User can run above saved command in factory environment without
providing pkc and sbk keys to flash a device
*** no-flash flag enabled. Exiting now… ***
User can run above saved command in factory environment without
providing pkc and sbk keys to flash a device
Example:
$ cd bootloader
$ sudo bash ./flashcmd.txt
Error: /home/teva/Documents/CleanFlash/Linux_for_Tegra/bootloader/signed/flash.idx is not found
Error: failed to relocate images to /home/teva/Documents/CleanFlash/Linux_for_Tegra/tools/kernel_flash/images
Cleaning up…
serial_debug.txt (6.6 KB)
flash_log.txt (34.6 KB)
I have attached the log files for the debug uart port and the outputs from the flash file.
How can I fix this?
Is it safe to try the commands the error has suggested?
Best,
Teva