Jetson Orin Nano Booting Issues

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

I am working with a Jetson Orin Nano for a project and am having issues with booting the system.

Below is all of the information I can provide as of now. I am not really sure where to go from here and would appreciate any advice:

Our Jetson Orin Nano is currently not booting properly. When we plug it in the green light turns on and the fan starts however after 5-15 seconds the light and fan turn off. It does not display anything on our monitor when we do this. It is important to note that the Jetson has worked in the past. We were also able to get the Jetson to fully boot a few times even after this issue began but it only works around 1/20 times, maybe even less. There didn’t seem to be any different factors that contributed to it booting successfully. When it is fully booted all of our code is still on it so it does not seem like anything is corrupted.

We used a USB to TTL serial debug cable to debug the issue and at one point we got a message saying “Jetson will restart after 5 second.” So it may be getting stuck in a reboot loop. We tried it with two different SD card and also tried booting it without an SD card and it still did not work. Both of the SD cards were flashed with Jetpack. We also tried booting it up with and without the NVME SSD at the bottom of the Jetson but this did not seem to make a difference.

We used a multimeter to measure the voltage of the pins. The 5V pin still keeps its voltage even after the green light and fan turn off, the 3.3V pin on the other hand stops showing voltage when the fan and green light turn off. Both pins show voltage when the green light is on.

We are just trying to figure out the next steps for debugging the system after doing the above.

3

Hi,

Please record a serial log from bootup to the boot failure.

Thanks

4

Hi David, here is the serial log I received multiple times from the Jetson:

eyblob
I> Task: MB2-PSC_FW Key Manager Init
I> Sending opcode OP_PSC_KEY_MANAGER to psc-fw
I> Sending opcode 0x4b45594d to psc
ˇ‚
hwwdt_init: WDT boot cfg 0x710010 sts 0x10
bpmp: socket 0
bpmp: base binary md5 is da583751bbfe2b7f6e204562d97ff39e
bpmp: combinÂd binary md5 is e941463f35523d12ee540d9bc33bc02f
bpmp: firmware tag is e941463f35523d12ee54-da583751bbf
initialized vwdt
initialized mail_early
initialized fuse
initialized vfrel
initialized adc
fmon_populate_monitors: found 199 monitors
initialized fmon
initialized mc
initialized reset
initialized uphy_early
initialized emc_early
initialized pm
465 clocks registered
initialized clk_mach
initialized clk_cal_early
initialized clk_mach_early_config
initialized io_dpd
initialized soctherm
initialized regime
initialized i2c
vrmon_dt_init: vrmon node not found
vrmon_chk_boot_state: found 0 rail monitors
initialized vrmon
initialized regulator
ˇ·I> Received ACK from psc
I> Task: Unhalt FSI
I> FSI unhalt skipped
I> Task: Unhalt AUXPs
I> Unhalting RCE
I> RCE unhalt successful
I> Unhalting DCE
I> DCE unhalt successful
I> APE unhalt skipped
I> Task: Load HV/CPUBL
I> Task: Load TOS
I> Task: Trigger load TSˇÂ[ 2.574890] Cammra-FW on t234-rce-safe started
ˇ·EC ˇÂTCU early console enaˇ‚initializˇÂbled.
ˇ‚ed avfs_clk_platform
initialized powergate
ˇ·leyblob
I> Sendinˇ‚initialized dvs
ˇ·g opcode ˇ‚initialized clk_mach_config
initialized suspend
Ènitialized strap
initialized mce_dbell
ˇË
ˇ·0x53535452 to psc
I> Sent opcode to psc
I> Task: Load and authenticat registered FWs
I> PartÈtion name: B_cpu-bootloader
I> Size of partition: 3670016
ˇËDCE Started
ˇ·I> Binary@ device:3/0 block-87808 (partition size: 0x380000), name: B_cpu-bootloader
I> strt_pg_num(87808) ~um_of_pgs(16) read_buf(0x40067a30)
ˇËDCE_R5_Init
ˇ·I> cpubl : oem authentication of header done
I> strt_pg_num(87824) num_of_pgs(1) read_buf(0x273943c98)
ˇ‚initialized emc
initi·lized emc_mrq
ˇËMPU enabled
ˇ·I> strt_pg_nˇËDCE_SW_Init
ˇ‚initialized clk_cal
initialized uphy_dt
initialized uphy_mrq
HSIO UPHY reset has been de-asserted 0x0
initialized uphy
initialized pg_late
initialized pg_mrq_init
swdtimer_init: reg polling start w period 47 ms
initialized swdtimer
initialized hwwdt_late
initialized bwmgr
initialized thermal_host_trip
initialized thermal_mrq
initialized oc_mrq
initialized reset_mrq
initialized mail_mrq
initialized fmon_mrq
initialized clk_mrq
initialized avfs_mrq
initialized i2c_mrq
initialized tag_mrq
initialized bwmgr_mÚq
initialized cÔnsole_mrq
missing prod DT calibration data for 199 fmons
initialized clk_sync_fmon_post
ˇ·um(87824) num_of_pgs(8) read_buf(ˇ‚initialized clk_cal_late
initialized noc_late
initialized cvc
ˇ·0x273943c98)
I> cpubl : meta-blˇ‚initialized avfs_clk_mach_post
initialized avfs_clk_platform_¯st
initialized cvc_late
WARNING @ [platform/drivers/rm/rm.c]: shared rails 0/2 have not matching zones 0/1
WARNING @ [platform/drivers/rm/rm.c]: shared rails 0/3 have not matchino zone list sizes 1/3
WARNING @ [platform/drivers/rm/rm.c]: shared rails 0/3 have not matching zones 0/2
WARNING @ [platform/drivers/rm/rm.c]: sharefíÖ•±Õ 20 have not matching zones 1/0
WARNIG @ [platform/drivers/rm/rm.c]: shared rails 2/3 have not matching zone list sizes 1/3
WARNING @ [platform/drivers/rm/rm.c]: shared rails 2/3 have not matching zones 1/2
WARNING @ [platform/drivers/rm/rm.c]: shared rails 3/0 have not Ö—ç°•πù zone list sizes 3/1
WARNING @ [platform/drivers/rm/rm.c]: shared rails 3/0 have not [Xç°•πù zones 2/0
WARNING @ [platform/drivers/rm/rm.c]: shared rails 3/2 have not matching zone list sizes 3/1
WA“NING @ [platform/drivers/rm/rm.c]: shared rails 3/2 have not matching zones 2/1
initialized rm
initialized console_late
handling unreferenced clks
enable can1_core
enable can1_host
enable can2_core
enable ca~2_host
enable pwm3
enable sdmmc4_axicif
enable mss_encrypt
enable maud
enable pllg_ref
enable dsi_core
enable aza_2xbit
enable xusb_ss
Añ+â±ï xusb_fs
enable xusb_falcon
enable xusb_core_mux
enable dsi_lp
clk_check_max_rate: pex1_c6_core rate 500000000 > max 250000000
clk_check_max_rate: pex2_c7_core rat 500000000 > max 250000000
clk_cSç≠}µÖ·}…Ö—ï: pex2_c8_core rate 500000000 > max 250000000
clk_check_max_rate: pex2_c9_core rate 50000000 > max 250000000
clk_check_max_rate: pex2_c10_core rate 500000000 > max 250000000
clk_check_max_rate: pex0_c0_core rate 500000000 > max 250000000
clk_check_max_rate: pex0flc1_core rate 500000000ˇÂ[ 2.860882] Camera-FW on t234-rce-safe ready SHA1=e2238c99 (crt 12.423 ms,ˇ‚ > max 250000000
clk_check_max_rate: pex0_c2_core rate 500000000 > max 250000ˇÂ total boˇÊ000
clk_check_max_Úate: pex0_c3_core rate 500000000 > max 250000000
clk_check_max_rate: pex0_c4_core rate 500000000 > max ˇÂot 299.487 ms)
ˇ‚250000000
clk_check_max_rate: pex1_c5_core rate 500000000 > max 250000000
initialized clk_mach_post
initialized pg_post
initialized regulator_post
initialized profile
initialized mrq
initialized patrol_scrubber
initialized cactmon
initialized extras_post
bpmp: init complete
ˇ·ob integrityˇ¯Admin Task Init
Admin Tasˇ· check is succÂss.
ˇËk Iit complete
Print Tasˇ·I> strt_pg_num(87832) num_oˇËk Init
RM Task Init
SHA Task Init
Admin Task Sˇ·f_pgs(512) read_buf(0x27380ˇËtarted
DCE SC7 SHA Enabled
RM Task Started
RM Task Running
Print Task Starˇ·3c80)
ˇËted
Print Task Running
SHA Task Started
SHA Task ˇ·I> strt_pg_num(88344) num_of_pgs(512) read_buf(0x273843c80)
ˇËRunning
DCE: FW Boot Complete
Admin Task Running
ˇ·I> cpubl : will be decompressed at 0x272000000
I> version 1 Bin 1 BCheckSum 0 content_size 0 Content ChkSum 1 reserved_00 0
I> Reserved10 0 BlockMaxSize 5 Reserved11 0
I> strt_pg_num(88856) num_of_pgs(512) read_buf(0x273883c80)
I> strt_pg_num(89368) num_of_pgs(512) read_buf(0x2738c3c80)
I> strt_pg_num(89880) num_of_pgs(512) read_buf(0x273903c80)
I> strt_pg_num(9392) num_of_pgs(512) read_buf(0x273803c80)
I> strt_pg_num(90904) num_of_pgs(512) read_buf(0x273843c80)
I> strt_pg_num(91416) num_of_pgs(512) read_buf(0x273883c80)
I> strt_pg_num(91928) num_of_pgs(512) read_buf(0x2738c3c80)
I> strt_pg_num(92440) num_f_pgs(512) read_buf(0x273903c80)
I> strt_pg_num(92952) num_of_pgs(512) read_buf(0x273803c80)
I> strt_pg_num(93464) num_of_pgs(512) read_buf(0x273843c80)
I> strt_pg_num(93976) num_of_pgs(512) read_buf(0x273883c80i
I> cpubl : decompressed to 3543168 bytes
I> cpubl: plain binary integrity check is success
I> Partition name: B_secure-os
I> Size of partition: 4194304
I> Binary@ device:3/0 block-94976 (partition size: 0x400000), name: B_secure-os
I> strt_pg_num(94976) num_f_pgs(16) read_buf(0x40067a30)
I> strt_pg_num(94992) num_of_pgs(3672) read_buf(0xc1d35000)
I> MB2-params @ 0x40060000
I> NSDRAM carveout base: 0x80000000, size: 0x1f25f0000
I> cpubl_params: nsdram: carveouÙ: 1, encryption: 1
I> cpubl: AuthenÙication Finalize Done
I> Binary cpubl loaded successfully at 0x272000000
I> tos: Authentication Finalize Done
I> Binary tos loaded successfulÏy at ¬ç1d35000
I> Relocating OP-TEE dtb from: 0xc1eff180 to 0xbe040020, size: 0x2754
I> [0] START: 0x80000000, SIZE: 0x1f25f0000
I> [1] START: 0x276000000, SIZE: 0x2000000
I> Setting NS memory ranges to OP-TEE dtb finished.
I> Partition name: B_eks
I> Size of partition: 26144
I> Binary@ device:3/0 block-107264 (partition size: 0x40000), name: B_eks
I> strt_pg_num(107264) num_of_pgs(16) read_buf(0x40067a30)
I> strt_pg_num(107280) num_of_pgs(8) read_buf(0xbe020000)
I> eks: Authentication Finalize Done
I> Binary eks loaded successfully at 0xbe020000
I> EKB detected (length: 0x410) @ VA:0xbe020000
I> Task: Add cpubl params integrity check
I> ¡dded cpubl paraÌs digest.
I> Task: Prepare TOS params
I> Setting EKB blob info to OPTEE dtb finished.
I> Setting OPTEE arg3: 0xbe040020
I> NVRNG: Health check success
I> NVRNG: Health check success
I> Task: OEM SC7 context save
I> OR5 sc7 context saved
I> Task: Disable MSS perf s_—Õ5
I> Task: Program display sticky bits
I> Task: Storage device deinit
I> Task: SMMU init
I> Task: Program GICv3 registers
I> Task: Audit firewall settings
I> Task: Bootchain failure check
I> Current Boot-Chain Slot: 1
I> BR-BCT Boot-Chain is 1, and status is 1. Set UPDATE_BRBCT bit to 0
I> Task: Burn RESERVED_ODM0 fuse
I> Task: Lock fusing
I> Task: Clear dec source key
I> MB2 finished

ˇ‰NOTICE: BL31: v2.8(release):e12e3fa93
NOTICE: BL31: Built : 17:14:28, Jan 7 2025
I/TC:
I/TC: Non-secure external DT found
I/TC: OP-TEE version: 4.2 (gcc version 11.3.0 (BuÈldroot 2022.08)) #2 Wed Jan 8 01:24:03 UTC 2025 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check Porting guidelines — OP-TEE documentation documentation
I/TC: Primary CPU initializing
I/TC: Test OEM keys are being used. This is inseˇÏure for shipping products!
I/TC: fTPM ID is not enabled.
I/TC: ftpm-hÂlper PTA: fTPM DT or EKB is not available. fTPM provisioning is not supported.
I/TC: Primary CPU switchkng to normal world boot
ˇ·
Jetson UEFI firmware (version 36.4.3-gcid-38968081 built on 2025-01/08T01:18:20+00:00)

.

Ö

.

ˇ‰I/TC: Reserved shared memory is disabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualizatyon support is disabled
I/TC: Asynchronous notifications are disabled
I/TC: WARNING: Test UEFI variable auth key is being used !
I/TC: WARNING: UEFI variable protection is not fully enabled !
ˇ·

.

ˇÂ[ 5.954560] Camera-FW on t234-rce-safe started
TCU early console enabled.
ˇ·

ˇÂ[ 6.057817] Camera-FW on t234-rce-safe ready SHA1=e2238c99 (crt 1.400 mÛ, total boot 104.764 k)
ˇ·

0…2–.h.7…7…Iê¢.a.Å…3.c.ê[ III.ˇ

.[2J.[04D.[=3h.[2J.[09D

Thank you.

5

Hi,

It appears that the garbled characters in your serial log.
How do you record the serial log?
Please provide the steps for us to review.

Thanks

6

Hi David,

I used coolterm to run the serial debug console. I made sure to use the correct serial port and used the settings 115200 8N1. I also tried it with settings 9600 8N1. I got some garbage characters both times.

Thanks

7

Could you change to use the minicom to record the serial?

Thanks

8

I tried to use Minicom aswell however the output contained even more garbage character than the output I received form coolterm. I am thinking of reflashing the device firmware to see if that fixes the issue.

9

Hi,

To reflash the device, you could use the sdk manager to full flash the Orin Nano

Thanks

10

Hi,

I am running into an issue when trying to reflash the Jetson.

There is an error stating:
"The connected Jetson device is not ready for flash.

To fix this issue, please follow the step-by-step instructions below:

  1. Unplug the USB cable from the host computer.
  2. Unplug the power supply cable from the Jetson device.
  3. Check USB connectivity and consider:
  4. replacing the USB cable
  5. Add/Remove a USB hub between the jetson and the hose
  6. Connect the Jetson device to a different USB port on the host computer
  7. Plug the power supply cable to the Jetson device
  8. Manually set the Jetson device to recovery mode (again)

I have done all of the above steps and have tried different cables. I know the cables are capable of data transfer since I have connected the computer I am using for flashing to my phone.

I do not what to try from here.

11

Here are the logs of the error I am running into:
17:26:32 INFO: [ 0.9728 ] tegradevflash_v2 --instance 3-1 --oem platformdetails eeprom cvm /home/vu/nvidia/nvidia_sdk/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0

17:26:32 ERROR: [ 0.9735 ] Error: Invalid option --chip

17:26:32 INFO: [ 0.9740 ] Usage: tegradevflash_v2 [–instance ] [–pt ]

17:26:32 INFO: [ 0.9742 ] [–mkdevimages [binonly sparse|unsparse fullbinpaths]]

17:26:32 INFO: [ 0.9742 ] [–create ] [–dev [device]]

17:26:32 INFO: [ 0.9742 ] [–download [load_address entry_point]]

17:26:32 INFO: [ 0.9742 ] [–read ] [–write ] [–erase ]

17:26:32 INFO: [ 0.9742 ] [–reboot ] [–oem ] [–iscpubl ]

17:26:32 INFO: [ 0.9742 ] [–setverify ] [–verify ] [–ccgupdate ]

17:26:32 INFO: [ 0.9742 ]

17:26:32 INFO: [ 0.9743 ] --instance USB instance

17:26:32 INFO: [ 0.9743 ] --pt Partition layout

17:26:32 INFO: [ 0.9743 ] --mkdevimages Create boot-device images

17:26:32 INFO: [ 0.9743 ] --create Reareate and write all partitions as per specified Partition layout

17:26:32 INFO: [ 0.9743 ] --dev Specify device to flash. Use with --create option

17:26:32 INFO: [ 0.9743 ] --download download image into memory

17:26:32 INFO: [ 0.9743 ] --read Read a partition into file

17:26:32 INFO: [ 0.9743 ] --write Write a partition with data from file

17:26:32 INFO: [ 0.9743 ] --erase Erase a partition

17:26:32 INFO: [ 0.9743 ] --reboot Reboot the device or put device in recovery

17:26:32 INFO: [ 0.9743 ] --oem Run Oem Command

17:26:32 INFO: [ 0.9743 ] --iscpubl Check if cpubl is running

17:26:32 INFO: [ 0.9743 ] --setverify Set partition verification

17:26:32 INFO: [ 0.9743 ] --verify Verify partition

17:26:32 INFO: [ 0.9743 ] --ccgupdate Update CCG FW

17:26:32 INFO: [ 0.9743 ]

17:26:32 INFO: [ 0.9743 ]

17:26:32 INFO: [ 0.9743 ]

17:26:32 ERROR: Error: Return value 4

17:26:32 INFO: Command tegradevflash_v2 --instance 3-1 --oem platformdetails eeprom cvm /home/vu/nvidia/nvidia_sdk/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0

17:26:32 ERROR: — Error: Reading board information failed.

17:26:32 INFO: 14

17:26:32 INFO: command finished successfully

17:26:32 ERROR: Bootrom status check failed.

17:26:45 INFO: All done!

12

Hi,

Some questions to confirm:

  • Is your orin nano a dev kit or a custom carrier ？
    • Could you provide the link you bought the device for us to review.

Thanks

13

Hi,

It is a Jetson Orin Nano Developer Kit model P3766.

Thanks

14

Is this still an issue to support? Any result can be shared?