Jetpack on Jetson Orin Nano through WSL: Depends on failed component error

I am trying to install jetpack on Jetson orin nano developer kit(8 GB) through WSL2(Ubuntu 20.04). Storage device SD card. My installation process fails every time with “Depends on failed component” This is my first Jetson device. If anyone has solved this problem, please guide me. Thanks
I am attaching the log file here.

NV_L4T_FLASH_JETSON_LINUX_COMP.log (9.5 KB)

while flashing I am getting this:

//////////////////////////////////////////////////

------ 2024-03-20 13:52:15 ------
------ SDK: JetPack_6.0_DP_Linux_DP ------
13:52:15.291 - Info: [host] [ Disk Avail on Partition : 0.00 B ]
13:52:15.291 - Info: change working directory to /home/priyo/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra
13:52:15.291 - Info: [ Component Install Started ]
13:52:15.291 - Info: current working directory is /home/priyo/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra
13:52:15.291 - Info: exec_command [host]:
**********************
set -e
unset LC_ALL
FlashOptions=$(echo "--storage mmcblk1p1" | sed s/mmcblk1p1/mmcblk0p1/)
echo sudo ./nvsdkmanager_flash.sh $FlashOptions
sudo ./nvsdkmanager_flash.sh $FlashOptions
sleep 20
if [[ '--storage mmcblk1p1' == *'--nv-auto-config'* ]]; then
sleep 40
fi
**********************
13:52:15.291 - Info: exec_command: /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.priyo.sh
sudo ./nvsdkmanager_flash.sh --storage mmcblk0p1
user entered mmcblk0p1
*** Checking ONLINE mode ... OK.
*** Checking target board connection ... 1 connections found.
*** Reading ECID ... FUSELEVEL=fuselevel_production hwchipid=0x23 bootauth=NS
*** Reading EEPROM ... "/home/priyo/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash.py" --chip 0x23 --applet "/home/priyo/nvidia/nvidia_sdk/JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/mb1_t234_prod.bin" --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3701-0000.dts --misc_config tegra234-mb1-bct-misc-p3701-0000.dts --bins "mb2_applet applet_t234.bin" --skipuid --cmd "dump eeprom cvm 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.0752 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0758 ] File rcm_state open failed
[   0.0761 ] ERROR: failed to read rcm_state
[   0.0761 ] 
[   0.0771 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0773 ] Assuming zero filled SBK key
[   0.0765 ] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts
[   0.0841 ] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts
[   0.0925 ] Parsing partition layout
[   0.0934 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0946 ] Kernel DTB used: None
[   0.0946 ] WARNING: dce base dtb is not provided

[   0.0946 ] Parsing partition layout
[   0.0954 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0963 ] Creating list of images to be signed
[   0.0969 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[   0.0975 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0982 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0986 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.1051 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.1055 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1115 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1117 ] adding BCH for mb2_t234_aligned.bin
[   0.1151 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.1313 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.1316 ] adding BCH for mb2_t234_aligned.bin
[   0.1509 ] Filling MB1 storage info
[   0.1509 ] Parsing dev params for multi chains
[   0.1565 ] Generating br-bct
[   0.1573 ] Updating dev and MSS params in BR BCT
[   0.1573 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1583 ] Updating bl info
[   0.1591 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[   0.1598 ] WARNING: boot chain is not completed. set to 0
[   0.1604 ] Generating signatures
[   0.1614 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1616 ] Assuming zero filled SBK key
[   0.1730 ] Warning: pub_key.key is not found
[   0.1722 ] Parsing dev params for multi chains
[   0.1722 ] Generating br-bct
[   0.1731 ] Updating dev and MSS params in BR BCT
[   0.1731 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.1741 ] Updating bl info
[   0.1749 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.1756 ] WARNING: boot chain is not completed. set to 0
[   0.1769 ] Generating SHA2 Hash
[   0.1792 ] Sha saved in br_bct_BR.sha
[   0.1783 ] Get Signed section of bct
[   0.1791 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.1799 ] Signing BCT
[   0.1809 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1811 ] Assuming zero filled SBK key
[   0.1838 ] Sha saved in br_bct_BR.sha
[   0.1841 ] Warning: pub_key.key is not found
[   0.1831 ] Updating BCT with signature
[   0.1839 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.1846 ] Offset :4608 Len :3584
[   0.1853 ] Generating SHA2 Hash
[   0.1863 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.1865 ] Assuming zero filled SBK key
[   0.1865 ] Assuming zero filled SBK key
[   0.1893 ] Sha saved in br_bct_BR.sha
[   0.1886 ] Updating BCT with SHA2 Hash
[   0.1894 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.1900 ] Offset :4608 Len :3584
[   0.1902 ] Offset :68 Len :8124
[   0.1907 ] Generating coldboot mb1-bct
[   0.1916 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[   0.1923 ] MB1-BCT version: 0.13

[   0.1937 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.1938 ] Added Platform Config 9 data with size :- 100
[   0.1938 ] 
[   0.1939 ] Updating mb1-bct with firmware information
[   0.1945 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1964 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.1979 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.1987 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.2006 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2007 ] Assuming zero filled SBK key
[   0.2023 ] Warning: pub_key.key is not found
[   0.2021 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_cold_boot_bct_MB1_aligned_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.2032 ] Generating recovery mb1-bct
[   0.2038 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000_cpp.dtb
[   0.2044 ] MB1-BCT version: 0.13

[   0.2058 ] Parsing config file :tegra234-mb1-bct-device-p3701-0000_cpp.dtb 
[   0.2059 ] Added Platform Config 9 data with size :- 100
[   0.2060 ] 
[   0.2060 ] Updating mb1-bct with firmware information
[   0.2068 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.2086 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.2092 ] Generating SHA2 Hash for mb1bct
[   0.2113 ] Sha saved in mb1_bct_MB1_aligned.sha
[   0.2111 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.2119 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.2137 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2139 ] Assuming zero filled SBK key
[   0.2155 ] Warning: pub_key.key is not found
[   0.2155 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.2168 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.2168 ] Error: Skip generating mem_bct because sdram_config is not defined
[   0.2168 ] Copying signatures
[   0.2174 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.2234 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.2236 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.2236 ] Boot Rom communication
[   0.2244 ] tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   0.2252 ] BR_CID: 0x80012344705DF1808C00000007028280
[   0.2337 ] Sending bct_br
[   0.2338 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
13:52:25.869 - Error: [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.priyo.sh; [error]: *** ERROR: Parsing boardid failed


13:52:25.869 - Info: [ Component Install Finished with Error ]
13:52:25.870 - Info: [host] [ Disk Avail on Partition: 0.00 B ]
13:52:25.870 - Info: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 11s ]
/////////////////////////////////////

On a native Linux PC you can do this:

But this USB autosuspend control value is not available on WSL2 kernel, so the only way you can do is avoid using WSL2.

I am able to install the Jetson Linux image using VMware but skipped the SDK components because it is taking like forever. what is the average time required to install the SDK components(CUDA, TensorRT, etc.)? and are the ways to install in except SDK manager?

Then SDK Manager is not strictly needed for JetPack SDK.
Just run

sudo apt update
sudo apt install nvidia-jetpack

directly on the device.

1 Like

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