Jetpack OS installation error

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

I have a jetson Xavier NX emmc board, it has been installed with Jetpack 4.6.1.But it seems not be supported now, so I want to update it to jetpack 5.2.1.
My environment is Virtualbox installed Ubuntu 20.04, and I use SDK manager to flash the OS, but it failed many times. The progress always stayed at 99.5% and noticed me that “Installation of Flash Jetson Linux’ is taking longer than expected.”
I have tried to restart the PC, the Hardware, and check my USB wire, but it doesn’t work.
How can I solve the problem? Or May I have another way to update it without SDK manager?
Thank you.

微信截图_20231103150926
微信截图_202311031509261440×899 123 KB

The notice screenshot is above.

And this terminal log, but it doesn’t show any warning or error.
14:36:37 INFO: Flash Jetson Linux - flash: [ 2.3176 ] tegrahost_v2 --chip 0x19 0 --magicid PLDT --appendsigheader nvtboot_applet_t194_aligned.bin zerosbk

14:36:37 INFO: Flash Jetson Linux - flash: [ 2.3185 ] adding BCH for nvtboot_applet_t194_aligned.bin

14:36:37 INFO: Flash Jetson Linux - flash: [ 2.3289 ] tegrasign_v3.py --key None --list nvtboot_applet_t194_aligned_sigheader.bin_list.xml --pubkeyhash pub_key.key

14:36:37 INFO: Flash Jetson Linux - flash: [ 2.3291 ] Assuming zero filled SBK key

14:36:37 INFO: Flash Jetson Linux - flash: [ 2.3322 ] Warning: pub_key.key is not found

14:36:37 INFO: Flash Jetson Linux - flash: [ 2.3317 ] tegrahost_v2 --chip 0x19 0 --updatesigheader nvtboot_applet_t194_aligned_sigheader.bin.encrypt nvtboot_applet_t194_aligned_sigheader.bin.hash zerosbk

14:36:37 INFO: Flash Jetson Linux - flash: [ 2.3417 ] tegrarcm_v2 --download mb2 nvtboot_applet_t194_sigheader.bin.encrypt

14:36:37 INFO: Flash Jetson Linux - flash: [ 2.3439 ] Applet version 01.00.0000

14:36:37 INFO: Flash Jetson Linux - flash: [ 2.4129 ] Sending mb2

14:36:38 INFO: Flash Jetson Linux - flash: [ 2.4129 ] […] 100%

14:36:38 INFO: Flash Jetson Linux - flash: [ 2.5084 ] tegrarcm_v2 --boot recovery

14:36:38 INFO: Flash Jetson Linux - flash: [ 2.5096 ] Applet version 01.00.0000

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.6158 ] tegrarcm_v2 --isapplet

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.6911 ] tegrarcm_v2 --ismb2

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.6925 ] MB2 Applet version 01.00.0000

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.7636 ] tegrarcm_v2 --ismb2

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.7653 ] MB2 Applet version 01.00.0000

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.8349 ] Retrieving board information

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.8376 ] tegrarcm_v2 --oem platformdetails chip chip_info.bin

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.8383 ] MB2 Applet version 01.00.0000

14:36:39 INFO: Flash Jetson Linux - flash: [ 3.9750 ] Saved platform info in chip_info.bin

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.0169 ] Chip minor revision: 2

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.0169 ] Bootrom revision: 0xf

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.0170 ] Ram code: 0x2

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.0170 ] Chip sku: 0xde

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.0170 ] Chip Sample: non es

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.0473 ] Retrieving EEPROM data

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.0473 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/dai/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/cvm.bin

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.0489 ] MB2 Applet version 01.00.0000

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.1847 ] Saved platform info in /home/dai/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/cvm.bin

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.3000 ] Rebooting to recovery mode

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.3027 ] tegrarcm_v2 --ismb2

14:36:39 INFO: Flash Jetson Linux - flash: [ 4.3038 ] MB2 Applet version 01.00.0000

14:36:40 INFO: Flash Jetson Linux - flash: [ 4.3744 ] Rebooting to recovery mode

14:36:40 INFO: Flash Jetson Linux - flash: [ 4.3779 ] tegrarcm_v2 --reboot recovery

14:36:40 INFO: Flash Jetson Linux - flash: [ 4.3798 ] MB2 Applet version 01.00.0000

14:36:42 INFO: Flash Jetson Linux - flash: — Reading board information succeeded.

14:36:42 INFO: Flash Jetson Linux - flash: Parsing module EEPROM:

14:36:42 INFO: Flash Jetson Linux - flash: — Parsing board ID (3668) succeeded.

14:36:42 INFO: Flash Jetson Linux - flash: — Parsing board version (301) succeeded.

14:36:42 INFO: Flash Jetson Linux - flash: — Parsing board SKU (0003) succeeded.

14:36:42 INFO: Flash Jetson Linux - flash: — Parsing board REV (B.0) succeeded.

14:36:42 INFO: Flash Jetson Linux - flash: jetson-xavier-nx-devkit-emmc found.

14:36:42 INFO: Flash Jetson Linux - flash: *** Finding boot device … Boot device mmcblk0p1 found.

14:36:42 INFO: Flash Jetson Linux - flash: “/home/dai/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/flash.sh” jetson-xavier-nx-devkit-emmc mmcblk0p1

14:36:42 INFO: Flash Jetson Linux - flash: ###############################################################################

14:36:42 INFO: Flash Jetson Linux - flash: # L4T BSP Information:

14:36:42 INFO: Flash Jetson Linux - flash: # R35 , REVISION: 4.1

14:36:42 INFO: Flash Jetson Linux - flash: # User release: 0.0

14:36:42 INFO: Flash Jetson Linux - flash: ###############################################################################

3

VMs can be made to work, but what you are experiencing is due to the VM not handling USB correctly. During flash USB disconnects and reconnects, and a VM not properly configured will fail the reconnect. There is no way for the flash software to know about its VM environment, and there are many VMs, so basically you’ll have to figure out how to configure the VM. You’ll be a lot less frustrated if you can install an actual Ubuntu 20 host, perhaps dual booting (it uses a lot of disk space, so beware of that). Often adding a second hard drive to leave the original alone and put Linux on the second drive is the easiest way to do that.

1 Like
4

Hi,

Please avoid using virtual machines and find a real Ubuntu PC instead.
Also, don’t crop the log yourself and please put the full one here.

1 Like
5

Thank you, guys. I installed a real Ubuntu environment and solved this problem. Thank you very much!

7

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