Jetson failing to boot after module removal

I’ve been working on this Jetson Orin Nano Devkit for some time now, it had been through a multitude of flashes through SDKManager. One day while trying to fit it into a custom case we had made we realized it would be a tight fit a peer of mine put it in nontheless and when we went to boot it seemed as though the Module itself had been slightly taken out of the board and the standoff screw had gone missing (replaced it). At first boot everything seemed fine. It booted fine, but we did notice the fan itself was blowing extremely fast something we didn’t really see before. After this we went about our day till the next, when we came back to push some updates on our project, we noticed that we weren’t getting any feedback from the Displayport cable connected to our monitor. Tried a couple of times, took the module out and back in. Until we thought maybe the best thing to do would be reflashing it through SDKManager. Here is some information before I proceed.

Details:
Jetson Orin Dev Kit 8GB
Jetpack 6.2 flashed onto a SSD through SDKManager
No SD Card in slot

Here are some things to note while I was trouble shooting:

  • Same host has flashed multiple times
  • Multiple superspeed cables from host to Jetson have been used
  • Orin power on light is on
  • Fan continues to blow at high speed whenever plugged in even with no SD Card/ SSD plugged in
  • No hdmi/display port feed
  • Recovery Mode allows the sdkmanager to detect it
  • Flashed Micro SD with Jetpack 5.1.2 inserted still does not boot
  • SDKManager would fail and would give USB Write Errors
    “To fix this issue, please follow the step-by-step instructions below:
    Unplug the USB cable from the host computer.
    Unplug the power supply cable from the Jetson device.
    Check USB connectivity and consider:
    Replacing the USB cable.
    Add/Remove a USB hub between the Jetson and the host.
    Connect the Jetson device to a different USB port on the host computer.
    Plug the USB cable to the host computer.
    Plug the power supply cable to the Jetson device.
    Manually set the Jetson device to recovery mode (again).
    Click ‘OK’ and then try to flash again.”
  • Ran
    sudo sed -i ‘s/GRUB_CMDLINE_LINUX_DEFAULT="[a-z ]*/& usbcore.autosuspend=-1/’ /etc/default/grub
    sudo update-grub2
    reboot
    sudo sysctl -w net.ipv6.conf.all.disable_ipv6=0
    *Flash now gets stuck at 99% on SDKManager

I feel like i’ve tried a bunch of stuff to no avail any assistance would be great! This Jetson is around a year old or so.

I’d also like to mention, I was using a D435i Camera and pretty sure I had to make a new kernel version to get the USB module to work. I followed Jetsonhack’s video on it. I don’t know if this is apart of the issue just through i’d put that here.

Hi,

Let’s focus on the flashing issue.
If you want to flash with clean environment,
Try to download Driver Package (BSP) and Sample Root Filesystem from Jetson Linux | NVIDIA Developer.
And follow the Quick Start — NVIDIA Jetson Linux Developer Guide to flash your device.

Thanks

**********************************************
*                                            *
*  Step 1: Build the flashing environment    *
*                                            *
**********************************************
Create flash environment 0
/home/david/Downloads/Linux_for_Tegra/bootloader /home/david/Downloads/Linux_for_Tegra
/home/david/Downloads/Linux_for_Tegra
Finish creating flash environment 0.
****************************************************
*                                                  *
*  Step 2: Boot the device with flash initrd image *
*                                                  *
****************************************************
/home/david/Downloads/Linux_for_Tegra/temp_initrdflash/bootloader0 /home/david/Downloads/Linux_for_Tegra
./tegraflash.py --bl uefi_jetson_minimal_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev  --bldtb tegra234-p3768-0000+p3767-0005-nv.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --instance 3-5 --cmd "rcmboot"  --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt  --bins "psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; tsec_fw tsec_t234_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; pva_fw nvpva_020_sigheader.fw.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0003-3509-a02_with_odm_sigheader.dtb.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot0.img; kernel_dtb tegra234-p3768-0000+p3767-0005-nv.dtb"    --bct_backup 
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 

 Entering RCM boot

[   0.0172 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[   0.0172 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[   0.0172 ] rcm boot with presigned binaries
[   0.0181 ] tegrarcm_v2 --instance 3-5 --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.0186 ] BR_CID: 0x80012344705DF1DF640000000BFE8100
[   0.0256 ] Sending bct_br
[   0.0314 ] Sending mb1
[   0.0319 ] Sending psc_bl1
[   0.0447 ] Sending bct_mb1
[   0.0522 ] Generating blob for T23x
[   0.0553 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[   0.0570 ] The number of images in blob is 19
[   0.0573 ] blobsize is 99886121
[   0.0574 ] Added binary blob_uefi_jetson_minimal_with_dtb_sigheader.bin.encrypt of size 2043968
[   0.0871 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 310768
[   0.0874 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 187120
[   0.0875 ] Added binary blob_tsec_t234_sigheader.bin.encrypt of size 176128
[   0.0875 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 279808
[   0.0876 ] Not supported type: mb2_applet
[   0.0877 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 440944
[   0.0878 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[   0.0879 ] Added binary blob_nvpva_020_sigheader.fw.encrypt of size 2164640
[   0.0885 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 12070560
[   0.0929 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[   0.0942 ] Added binary blob_bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt of size 1027008
[   0.0946 ] Added binary blob_tegra234-bpmp-3767-0003-3509-a02_with_odm_sigheader.dtb.encrypt of size 204736
[   0.0947 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 458096
[   0.0949 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 415008
[   0.0949 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[   0.0950 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1887312
[   0.0958 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[   0.0959 ] Added binary blob_boot0.img of size 77230080
[   0.1228 ] Added binary blob_tegra234-p3768-0000+p3767-0005-nv.dtb of size 249497
[   0.1719 ] tegrarcm_v2 --instance 3-5 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[   0.1726 ] BL: version 1.4.0.4-t234-54845784-e89ea9bc last_boot_error: 0
[   0.3132 ] Sending bct_mem
[   0.3325 ] Sending blob
[   0.4148 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 3-5 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Cleaning up...
david@david-Surfac

Still getting a USB write error after following every single step.

HI,

Please provide a full log.
Also record a serial console log at the same time.

Thanks

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