Jetson AGX Orin starting up question

Hello there,

Can anyone help to find out the solution for the following issue during Jetson AGX Orin module’s booting up. When powering on, the Module stucked at very beginning and output the following information,

**[0000.063] I> MB1 (version: 1.4.0.1-t234-54845784-08e631ca)
[0000.069] I> t234-A01-1-Silicon (0x12347) Prod
[0000.073] I> Boot-mode : Coldboot
[0000.076] I> Entry timestamp: 0x00000000
[0000.080] I> last_boot_error: 0x0
[0000.083] I> BR-BCT: preprod_dev_sign: 0
[0000.087] I> rst_source: 0x0, rst_level: 0x0
[0000.091] I> Task: SE error check
[0000.094] I> Task: Bootchain select WAR set
[0000.098] I> Task: Enable SLCG
[0000.101] I> Task: CRC check
[0000.104] I> Task: Initialize MB2 params
[0000.108] I> MB2-params @ 0x40060000
[0000.112] I> Task: Crypto init
[0000.114] I> Task: Perform MB1 KAT tests
[0000.118] I> Task: NVRNG health check
[0000.122] I> NVRNG: Health check success
[0000.126] I> Task: MSS Bandwidth limiter settings for iGPU clients
[0000.132] I> Task: Enabling and initialization of Bandwidth limiter
[0000.138] I> No request to configure MBWT settings for any PC!
[0000.143] I> Task: Secure debug controls

It stucked there don’t go further, how do I troubleshoot this issue? What are the possible causes for this issue?**

Hi,

Please record the full serial console log for us to review.

Thanks

Hi David,

Thank you for the response. But I can’t get the full serial console log, The Orin module stopped outputting logs and seemed exited from running automatically on the newly designed carrier board, the current dropped to a very low level, but the power supplies to the sys_vin_HV and the sys_vin_MV pins of the Orin module are staying on.

The Jetson AGX Orin module has been running fine on the old carrier board, but fails on the newly designed carrier board. What the newly designed carrier board differs from the old carrier board are summarized below,

- Replacement of new type of MOSFETs for the power-in circuitry. (and tested ok)

- Fixes for identified electrical issues. (and tested ok)

- Replacement of the new deserializers for cameras. The old deserializers are RN6864N from Richnex which accept AHD video(1920x1080 25FPS) and translate it to MIPI CSI 4lanes, the new deserializers are Max96722 from Maxim which accept GMSL2 video(1920x1080 25FPS) and translate it to MIPI CSI 4lanes.

When the Jetson AGX Orin module is powered on by the newly designed carrier board, it was stuck but didn’t go further, here is the snapshot for the serial output [check below Serial logs],

Some say it probably be caused by incorrect power on sequences, but I think that the power of sequences are the same with the old carrier board. I have tested all the power supplies, all are working well.

[Serial logs]
[0000.064] I> MB1 (version: 1.4.0.1-t234-54845784-08e631ca)
[0000.070] I> t234-A01-1-Silicon (0x12347) Prod
[0000.074] I> Boot-mode : Coldboot
[0000.077] I> Entry timestamp: 0x00000000
[0000.081] I> last_boot_error: 0x0
[0000.084] I> BR-BCT: preprod_dev_sign: 0
[0000.088] I> rst_source: 0x0, rst_level: 0x0
[0000.092] I> Task: SE error check
[0000.095] I> Task: Bootchain select WAR set
[0000.099] I> Task: Enable SLCG
[0000.102] I> Task: CRC check
[0000.105] I> Task: Initialize MB2 params
[0000.109] I> MB2-params @ 0x40060000
[0000.112] I> Task: Crypto init
[0000.115] I> Task: Perform MB1 KAT tests
[0000.119] I> Task: NVRNG health check
[0000.123] I> NVRNG: Health check success
[0000.126] I> Task: MSS Bandwidth limiter settings for iGPU clients
[0000.132] I> Task: Enabling and initialization of Bandwidth limiter
[0000.139] I> No request to configure MBWT settings for any PC!
[0000.144] I> Task: Secure debug co▒ (The logs stopped here.)

Can you help to address it. Thank you.

An additional information,
The SYS_RESET_N pin (L60) goes high after powering up and lasts for 150mS, then it is pulled to the ground by the Jetson AGX Orin Module. The Orin Module pulls the SYS_RESET_N pin to the ground after staying high for 150mS. I cannot upload oscilloscope screenshots here.

I tested the following parameters on both the old and the newly designed carrier boards.

1, FORCE_RECOVERY_N (pin L10 of the module), this pin is weakly pulled-up to 1.8V via a resistor both on the old and the newly designed carrier boards.

  • On the old carrier board: When powering up, this pin is pulled-up and held at 1.8V.
  • On the newly designed carrier board: When powering up, this pin is pulled-down to LOW by Orin Module following shortly pulled-up for around 200mS.

2, UART5_TX (pin J58 of the module), this pin is connected to UART Tx both on the old and the newly designed carrier boards.

  • On the old carrier board: When powering up, this pin is pulled-up and held at 1.8V.
  • On the newly designed carrier board: When powering up, this pin is pulled-up to around 0.8V.

3, UART5_RTS (pin K58 of the module) is not connected, it is leaved open both on the old and the newly designed carrier boards.

4, SYS_RESET_N (pin L60 of the module)

  • On the old carrier board: When powering up, this pin is pulled-up and held at 1.8V.
  • On the newly designed carrier board: When powering up, this pin is pulled-down to LOW following shortly pulled-up to 1.8V for around 150mS.

All the above tests were done with the same Jetson AGX Orin Module. However, the Orin module works properly on the old carrier board but fails on the newly designed carrier board, it cannot boot up normally on the newly designed carrier board, refer to previous info in this post for the serial console logs.
Anyone gives me advices on how to troubleshoot it will be appreciated.

Can someone help, what problems on the carrier board could cause the Jetson AGX Orin Module to behave like this? Please help me with troubleshooting it.

An incorrect output from MCU at the carrier board caused this problem. It is now OK.