Cann't flash the jetson nx module

Hi everyone,
some thing wrong when i type :
sudo ./flash.sh -r p3449-0000+p3668-0001-qspi-emmc mmcblk0p1
with a carrier board (with jetson nx module (16g emmc)) we did.

ub@ub:~/data/aiboxv1.2/Linux_for_Tegra$ sudo ./flash.sh -r p3449-0000+p3668-0001-qspi-emmc mmcblk0p1
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 4.3
###############################################################################
# Target Board Information:
# Name: p3449-0000+p3668-0001-qspi-emmc, Board Family: t186ref, SoC: Tegra 194,
# OpMode: production, Boot Authentication: NS,
###############################################################################
copying soft_fuses(/home/data/aiboxv1.2/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)... done.
./tegraflash.py --chip 0x19 --applet "/home/data/aiboxv1.2/Linux_for_Tegra/bootloader/mb1_t194_prod.bin" --skipuid --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg --bins "mb2_applet nvtboot_applet_t194.bin" --cmd "dump eeprom boardinfo cvm.bin;reboot recovery"
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.0030 ] Generating RCM messages
[   0.0048 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/mb1_t194_prod.bin zerosbk
[   0.0064 ] Header already present for /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/mb1_t194_prod.bin
[   0.0140 ]
[   0.0154 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0169 ] Assuming zero filled SBK key
[   0.0172 ]
[   0.0189 ] tegrasign_v2 --key None --file /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin --offset 2960 --length 1136 --pubkeyhash pub_key.key
[   0.0205 ] Assuming zero filled SBK key
[   0.0216 ]
[   0.0232 ] tegrahost_v2 --chip 0x19 0 --updatesigheader /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.hash zerosbk
[   0.0303 ]
[   0.0321 ] tegrabct_v2 --chip 0x19 0 --sfuse tegra194-mb1-soft-fuses-l4t.cfg.pdf sfuse.bin
[   0.0339 ]
[   0.0357 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x19 0 --sfuses sfuse.bin --download rcm /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin 0 0
[   0.0369 ] RCM 0 is saved as rcm_0.rcm
[   0.0413 ] RCM 1 is saved as rcm_1.rcm
[   0.0413 ] RCM 2 is saved as rcm_2.rcm
[   0.0413 ] List of rcm files are saved in rcm_list.xml
[   0.0413 ]
[   0.0414 ] Signing RCM messages
[   0.0431 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key --getmontgomeryvalues montgomery.bin
[   0.0447 ] Assuming zero filled SBK key
[   0.0458 ]
[   0.0458 ] Copying signature to RCM mesages
[   0.0474 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
[   0.0492 ]
[   0.0493 ] Boot Rom communication
[   0.0511 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml --skipuid
[   0.0521 ] RCM version 0X190001
[   0.0535 ] Boot Rom communication completed
[   1.0686 ]
[   2.0720 ] tegrarcm_v2 --isapplet
[   2.0739 ] Applet version 01.00.0000
[   2.0920 ]
[   2.0942 ] tegrarcm_v2 --ismb2
[   2.1275 ]
[   2.1297 ] tegrahost_v2 --chip 0x19 --align nvtboot_applet_t194.bin
[   2.1319 ]
[   2.1340 ] tegrahost_v2 --chip 0x19 0 --magicid PLDT --appendsigheader nvtboot_applet_t194.bin zerosbk
[   2.1359 ] adding BCH for nvtboot_applet_t194.bin
[   2.1400 ]
[   2.1419 ] tegrasign_v2 --key None --list nvtboot_applet_t194_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   2.1429 ] Assuming zero filled SBK key
[   2.1433 ]
[   2.1527 ] tegrahost_v2 --chip 0x19 0 --updatesigheader nvtboot_applet_t194_sigheader.bin.encrypt nvtboot_applet_t194_sigheader.bin.hash zerosbk
[   2.1559 ]
[   2.1568 ] tegrarcm_v2 --download mb2 nvtboot_applet_t194_sigheader.bin.encrypt
[   2.1584 ] Applet version 01.00.0000
[   2.1758 ] Sending mb2
[   2.1760 ] [................................................] 100%
[   2.1887 ]
[   2.1908 ] tegrarcm_v2 --boot recovery
[   2.1925 ] Applet version 01.00.0000
[   2.2152 ]
[   3.2182 ] tegrarcm_v2 --isapplet
[   3.2364 ]
[   3.2383 ] tegrarcm_v2 --ismb2
[   3.2400 ] MB2 Applet version 01.00.0000
[   3.2723 ]
[   3.2744 ] tegrarcm_v2 --ismb2
[   3.2763 ] MB2 Applet version 01.00.0000
[   3.3122 ]
[   3.3134 ] Retrieving EEPROM data
[   3.3135 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/cvm.bin
[   3.3150 ] MB2 Applet version 01.00.0000
[   3.3503 ] 0000000036260706: E> I2C: Timeout while polling for transfer complete. Last value 0x00000002.
[   3.4148 ]
[   3.4148 ]
[   3.4170 ] tegradevflash_v2 --oem platformdetails eeprom cvm /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/cvm.bin
[   3.4188 ] CPU Bootloader is not running on device.
[   3.4218 ]
Error: Return value 4
Command tegradevflash_v2 --oem platformdetails eeprom cvm /home/data/aiboxv1.2/Linux_for_Tegra/bootloader/cvm.bin
Reading board information failed.

If you are using a VM, then it probably lost USB. Also, some “charger” cables (actually, most charger cables) don’t work well with sustained data transfer. Basically it seems your recovery mode Jetson was not found, or else was found then lost. Is this using a VM? If not, then you might try unplugging and replugging the USB cable when this occurs.

Thank you @linuxdev I used Host PC with Ubuntu16.04 not VM, cable from the Jetson Xavier Developer Kit.
the eeprom(i2c0 address is 0x50) on this module can’t read.
image

If the eeprom is totally empty, you better sharing the full boot log with us…

CVM eeprom fails to work is serious problem and we would suggest to RMA.

But firstly we better checking the log and see what is going on…

thank you.I found the scl and sda are shorted (i2c2 ).

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.