Custom Jetson Orin Nano Carrier Board: How to Build DTB and Validate Flash Config?

Hi, I’m currently designing a custom carrier board for the Jetson Orin Nano and running into a couple of things I’m not sure about. Would really appreciate any help!

  1. I’ve made changes to some .dtsi files to match our board, and I’m wondering what the proper way is to build the final .dtb from them. Is there a script in the L4T BSP that handles this, or do I need to set up the compilation step myself?
  2. Also, before I actually try flashing on the hardware, I’d love to verify that the device tree and flash config don’t have any obvious issues. Is there a way to do some kind of check without the board being connected?

Thanks a lot!

Hi juwonn,

What’s the Jetpack version in use?

Which .dtb do you mean?
There are many device tree files in BSP package like pinmux dtsi, MB1/MB2 BCT, kernel device tree, uefi device tree, bpmp-dtb ..etc.

If you have customization in kernel device tree according to your design, please refer to the following instruction to apply the change.
Kernel Customization — Building the DTBs

Thank you for your reply.

I am currently using JetPack 6.2.
After checking the documentation, I found the build flow for the final kernel DTB, so my first question is resolved.

I still want to ask about the second question:
Is there any way to check whether the generated device tree and flash configuration have obvious issues before flashing, and without the board connected?

Thank you.

What do you mean about “obvious issues”?
If the DTB is built and it can be flashed correctly, then you need a board to check if it can boot successfully.
Please just confirm your customizations(in board config or device tree) match the design of your custom carrier board before flash.

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