Jetson Orin AGX on custom board can't boot properly


Sorry to bother you with another topic, but this is toward our Jetson Orin booting on a custom carrier board. My previous topic was about switching UART debug port so we would be able to receive debug log from boot but it did not work so we decided to solder a cable to the 699-pins connector to the UART3 pin. (here’s the link if interested: Custom carrier board debugging/not booting - #10 by KevinFFF)

Now that we are not blind anymore it was easy to see that to be able to pass the mb1 and mb2 configuration we had to modify the eeprom using this fix and the MGBE since we did add a camera module (here).

I also followed this guide to change the default display configuration from DP to HDMI following this to be able to connect to a display since we only have HDMI on our custom board.

From there, we recorded the boot log data and it seemed that it was able to boot correctly up to mb2 (see bootlog_pt1.txt).
bootlog_pt1.txt (29.1 KB)

However after few minutes of shwing nothing else, the log console shows other stuff but this is where it gets weird. I have joined the second part of the log console in another file but note that it is the same log but separated by a certain delay.
bootlog_pt2.txt (29.4 KB)

Also it is cut it after a few second since this line kept getting repeated : dce: dce_mailbox_set_full_interrupt:165 Intr bit set multiple t]. It is like the jetson is stuck in an infinite loop.

Could you tell me what to do to try and fix this please?

Thank you and have a great week!


From your first log, it seems stuck in UEFI. You may need to build debug UEFI to enable more logs to know where it gets stuck.

Does your board stuck here at the end?

How did you flash your board?
Could you help to provide the full flash log for further check?


Thanks for your quick answer!

I followed what was written and switched the uefi binaries to debug after rebuilding it from source. Here is your flash log and boot log:

boot_log.txt (265.3 KB)
flash_log.txt (529.7 KB)

No, it keeps writting the same error line without stopping (i had to stop it manually to record the data) :
dce: dce_mailbox_set_full_interrupt:165 Intr bit set multiple t]

Finally, I flashed my board using this command : sudo ./ jetson-agx-orin-devkit mmcblk0p1.

I modified the flashing files this way. Thats all.

Please let me know if you need more information!


Could you share the serial console log with timestamp enabled so that I would know where it get stuck?

Have you logged-in when you see these messages?
(i.e. could you interact with your board at this moment?)


I dont think its booting so i get no display and i cant ping it (if i understand correctly).

For the timestamps, I will share it with you tomorrow when ill have access to the board.

Thank you,


You could just try to interact with your board through serial console w/o display.

In addition, we would suggest disabling HDMI to debug the current issue.
You could disable HDMI through removing the node display@13800000 in your device tree (Linux_for_Tegra/kernel/dtb/tegra234-p3701-0000-p3737-0000.dtb)


So I did re-download the kernels and update only the eeprom and the MGBE (and the uefi in debug mode) but NOT the hdmi and it does seem to boot properly!! Here is the log:
boot_nohdmi.log (210.8 KB)

The reason might be because when i followed the guide for modifying the DP to HDMI it said to change the following files but it doesnt seem to be actually modifying the dtb file.

What i mean is that I have the compiled kernel inside Linux_for_Tegra/source/kernel_out but the Linux_for_Tegra/ script doesnt seem to be able to retrieve them. Is that normal ? What do i need to do to use the newly builded kernels and turn them into the dtb so that the flash script updates correctly the device tree.

For the serial part,

It is going to be hard since only the receiver line of the debug UART is connected (see pictures below) and not the transmitter line (pin H62). I’m trying to connect via USB serial to see if it works.

Thanks alot for your help!


You may need to refer to the instruction to replace the files in BSP package(Linux_for_Tegra) with the image you built. The flash script will use the files in BSP package to flash the board.

Device tree is .dts and dtsi in source and build into .dtb and .dtbo.

Yes, you would need a serial console cable from your host PC to interact with your board through TXD.

[2023-07-13 13:15:34] [   42.313420] Please complete system configuration setup on the serial port provided by Jetson's USB device mode connection. e.g. /dev/ttyACMx where x can 0, 1, 2 etc.

It seems you have entered into system configuration step.

You could also refer to the following steps to pre-config this before flash.
Flashing Support — Skipping oem-config


Sorry for late reply,

I have used the script to skip oem config and now have acces to a debug console. We are currently connecting the TXD line to be able to send data.

Our next objective is to make the hdmi work, and from what you said, following this guide should work. But this is what i did last time (

) and it did not work.

I will try once again just to be sure.

Let me know what should i do to fix our hdmi display!

Thank you,


FYI, here is the dmesg output log of the jetson orin agx on our custom carrier board.
dmesg.log (84.9 KB)

It seems you could boot up your custom board successfully.

Please file another topic for HDMI porting issue.

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