Orin Nano Custom Carrier Board Design and Device Tree Generation

So I’m designing a custom carrier board based on the official reference design by NVIDIA through a third-party manufacturer, I’m making no changes except copied the USB-C UART 3 more times, removed Displayport and ethernet and modified one USB-C to have DP + PD (Displayport + Power Delivery). It also has an EEPROM similar to the Jetson Orin Nano Devkit.

I don’t know this but do I need to generate a device tree for this or will it automatically detect the USB-C DP + PD?

If not, what files do I need to change and where do I need to change to add the DP + PD USB-C? Is there a way to avoid compiling the Linux Kernel and just change the device tree? I want to use Jetpack 6.0. Any step by step documentation available for newcomers like me?

Please explain.

Hi bigmanT,

Are you using Jetpack 6.0-DP(L4T R36.2) on your custom carrier board?

It seems you have few custom designs so that you would have to modify pinmux, device tree and even kernel image to meet the capability of your board.
Please refer to the adaptation guide for Jetson Orin NX and Nano Series — NVIDIA Jetson Linux Developer Guide 1 documentation.

Hi KevinFFF,

I want to use Jetpack 6.0DP on the custom carrier board as I’m already using it on my orin nano devkit.

Thanks for linking the adaptation guide. I’m not sure what to download from here in order to follow the adaptation guide: Jetson Linux | NVIDIA Developer For example, where can I get this directory? Linux_for_Tegra

Also, when you say changing the kernel image, you mean modifying the dtsi files?

This is the BSP package and you could download and setup through the following instruction.
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation

Maybe you have custom kernel driver should be ported or modifying kernel config. Or some device tree configuration should be updated.
To rebuild and update kernel image, please refer to Kernel Customization — NVIDIA Jetson Linux Developer Guide 1 documentation.

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