Hi,
I was testing the I2C bus of nano with a C++ lib and accidentally I changed EEPROM content (at I2C adress 0x50). After that the nano can’t boot
I know well x86/Windows but I come recently to linux/nano world.
My board is a Nano dev Kit B01.
data: I get only one Nano dev Kit (not starting) and I don’t get any computer with linux OS
I try to reburn an OS image on th SD card but it does not solve the problem.
I read deeply this forum post : after i2cset test, nano can't boot
but the process to fix that seems not easy and repeatable.
Is there an easy way or a well documented procedure to reflash the EEPROM in this situation ?
I will install Ubuntu as double Boot with W10. The last version of Ubuntu is 20.04 LTS. Do i need absolutely a 16.04 or 10.04 as you mentioned ?
Bernard
Hi wayne,
Ok now I’ve installed Ubuntu 18.04 and the sdk manager.
Could you give me the procedure to modify the files in#2 ?
Must I install all components?
I cannot find a clear nvidia doc on how to burn a SD card from SDK manager.
I guess, because of my Nano not starting, that I cannot connect a physical link between my host computer (where is Ubuntu 18.04 and the sdk manager) and the nano.
I come recently to linux/nano world, can someone help ?
I read the sdk manager documentation but it explains the different menus, it’s not a real application guide and there is nothing on how to create an image for an SD card.
Yes sdk manager created a folder “Linux_for_Tegra” in /home/bernard/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_NANO_DEVKIT
When we are going to developing something or check system issue, we don’t create sdcard image but directly using the driver package downloaded by sdkmanager to flash the board.
Now you have the driver package folder, how about checking if the file mentioned in patch is existing there or not?
Please also check the quick start guide in below page.
Hi,
Yes the 2 files mentioned in the patch exist (in the main folder JetPack_4.4_Linux_JETSON_NANO_DEVKIT and in one of its subfolder).
So what’s the process now :
I can see the Nano connected when I do an lsusb
But when I launch the flash command (sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1) I get an error. I try several times. same results.
See below (terminal on HOST ubuntu computer):
###############################################################################
./tegraflash.py --chip 0x21 --applet “/home/bernard/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_NANO_DEVKIT/Linux_for_Tegra/bootloader/nvtboot_recovery.bin” --skipuid --cmd “dump eeprom boardinfo cvm.bin”
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0015 ] Generating RCM messages
[ 0.0026 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/bernard/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_NANO_DEVKIT/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
[ 0.0033 ] RCM 0 is saved as rcm_0.rcm
[ 0.0040 ] RCM 1 is saved as rcm_1.rcm
[ 0.0040 ] List of rcm files are saved in rcm_list.xml
[ 0.0040 ]
[ 0.0041 ] Signing RCM messages
[ 0.0049 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0056 ] Assuming zero filled SBK key
[ 0.0115 ]
[ 0.0116 ] Copying signature to RCM mesages
[ 0.0125 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0138 ]
[ 0.0138 ] Boot Rom communication
[ 0.0146 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0153 ] RCM version 0X210001
[ 0.0571 ] Boot Rom communication completed
[ 1.0639 ]
[ 1.0640 ] dump EEPROM info
[ 1.0655 ] tegrarcm --oem platformdetails eeprom /home/bernard/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_NANO_DEVKIT/Linux_for_Tegra/bootloader/cvm.bin
[ 1.0671 ] Applet version 00.01.0000
[ 1.0694 ] Saved platform info in /home/bernard/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_NANO_DEVKIT/Linux_for_Tegra/bootloader/cvm.bin
[ 1.1458 ]
Parsing board information failed.