Hi,
I have inadvertently corrupted the EEPROM on a Jetson Nano (the original, not the Orin) which now fails to boot or flash. Is there a way it can be booted or flashed so that it can be recovered?
Thanks
Hi tony.aldhous,
Are you using the devkit or custom board for Jetson Nano?
What’s the Jetpack version in use?
Please try entering force recovery state and specify the BOARDID, BOARDSKU, FAB in the flash command to flash your board.
Hi, Sorry, I should have specified in my original post. I am using a custom board based on the devkit board, and firmware built using Yocto and the meta-tegra layer, using V32.7.4 of Linux for Tegra.
I tried specifying the BOADID, BOARDSKU and FAB, but it gives the same error:
export BOARDID=3448
export BOARDSKU=0002
export FAB=401
doflash.sh
…
[ 1.1790 ] Sending BCTs
[ 1.1826 ] tegrarcm --download bct anm-jetson-imetrum.bct
[ 1.1841 ] Applet version 00.01.0000
[ 1.2561 ] Sending bct
[ 1.2562 ] […] 100%
[ 1.3432 ]
[ 1.3433 ] Sending bootloader and pre-requisite binaries
[ 1.3464 ] tegrarcm --download ebt cboot.bin.signed 0 0 --download rp1 tegra210-p3448-0002-xxxx-boot.dtb.signed 0
[ 1.3478 ] Applet version 00.01.0000
[ 1.4241 ] Sending ebt
[ 1.4892 ]
Error: Return value 1
Command tegrarcm --download ebt cboot.bin.signed 0 0 --download rp1 tegra210-p3448-0002-xxxx-boot.dtb.signed 0
Sorry that we don’t support/verify yocto project currently.
For L4T(Linux for Tegra), you can specify those information in the flash command to let flash script use them instead of reading from EEPROM.
For flash script, it might be something like the following:
$ sudo BOARDID=3448 BOARDSKU=0002 FAB=401 ./flash.sh jetson-nano-devkit mmcblk0p1
I understand. It is not a problem.
Regards