Compatibility of NVIDIA Reference Board Flash Configuration with a Custom Jetson Orin NX / Orin Nano Carrier Board

Dear NVIDIA Jetson Team,

We are developing a custom carrier board supporting the following Jetson modules:

  • NVIDIA Jetson Orin NX 16GB
  • NVIDIA Jetson Orin Nano 8GB

Our custom carrier board is designed based on the NVIDIA Orin Nano reference carrier board. We have followed the reference design for the relevant SoM interface pin connections, including USB, PCIe, NVMe, power, reset, and recovery signals, as applicable to each module.

We would like to perform initial flashing and boot testing using the existing NVIDIA reference-board flashing configuration before undertaking custom carrier-board Device Tree and BSP configuration.

Could you please clarify the following questions?

  • If our custom carrier board follows the same relevant pin connections as the NVIDIA reference carrier board, can we use the existing NVIDIA reference-board flashing configuration for basic flashing tests?
  • Is it possible to flash the Jetson Orin NX 16GB and Jetson Orin Nano 8GB using their respective reference-board configurations without modifying the Device Tree, pinmux, MB1/MB2 configuration, ODM data, or flash configuration, provided the corresponding hardware connections are compatible?
  • What are the minimum hardware and software requirements for successfully entering USB Force Recovery Mode, flashing the module, and booting Linux from an NVMe SSD on a custom carrier board?
  • Which differences between our custom carrier board and the reference design would require modifications before initial flashing or booting can succeed?
  • If the reference-board configuration is sufficient for initial flashing, which custom carrier-board configurations must still be completed before we can validate all peripherals and consider the board fully operational?

Our immediate objective is to verify the hardware and demonstrate basic flashing functionality before proceeding with complete custom carrier-board software configuration.

We understand that matching the reference-board pin connections may not guarantee complete software compatibility, and we would appreciate your recommendations on the minimum configuration required for this initial test.

Thank you for your support.

Best regards,

Hardware Development Team

Just to clarify. You don’t provide much information about how is the exact design here, so what I could comment is limited.

2 key items for making flash passed.

  1. USB device mode needs to be configured correctly.
  2. NVMe needs to be detected correctly.

Most likely your USB design would lead to flash failure because I actually didn’t see much custom board really has same design as devkit in USB part.

This document has the details for how to configure device tree when your USB design is different from devkit.

As for rest of I/O, it could be case by case and you may file sub topic for them.

Dear Wayne,

Thank you for your response.

As mentioned earlier, we are developing a custom carrier board supporting two SoMs: Jetson Orin NX 16GB and Jetson Nano 8GB.

As per our design requirement, we intend to use a single USB-C connector to flash/program both SoMs. We have implemented the USB interface based on the NVIDIA design guidelines.

Could you please review the attached schematic, particularly the USB-C flashing/programming section, and advise whether the current implementation is correct and compatible with both SoMs?

Please let us know if any modifications or additional circuitry are required to ensure reliable flashing of both SoMs through a single USB-C interface.

Your feedback and recommendations would be highly appreciated.

USB-C_Flash.pdf (229.5 KB)

NV devkit is using FUSB301 for the type C solution. If this one is not present on your design, then you definitly need to modify device tree.

It is not about the SOM. It is just default device tree won’t work for your board. Configuring device tree for a custom board is a very common step to do.

As mentioned earlier, we are developing a custom carrier board supporting two SoMs: Jetson Orin NX 16GB and Jetson Nano 8GB.

This does not provide much helpful info. Same NV devkit is also supporting all Orin NX/Nano SOM but their device trees are all different.

And for hardware design, please refer to the design guide document as well.

Hi wayne,

I hope you have had an opportunity to review my schematic. I would appreciate your suggestions regarding any changes required to ensure proper booting and successful flashing of both SoMs.

I have a few specific questions regarding the USB-C interface:

  1. Is it advisable to include a USB FUSB301 IC in the current design to support USB device detection and programming?

  2. If I include this IC, will it support proper USB-C detection, device enumeration, and successful flashing of the selected SoM?

  3. Since we are using two SoMs (Jetson Orin NX 16GB and Jetson Nano 8GB), do we need two separate USB FUSB301 ICs, or can a single IC with jumper-based selection support both SoMs?

  4. Are there any additional control signals or design considerations required to ensure reliable USB detection and flashing of both SoMs?

  5. Could you please review the USB-C architecture and suggest the appropriate implementation to achieve reliable device detection and successful flashing of either SoM through a single USB-C connector?

Your guidance would be very helpful in finalizing the design.

Truly,
Nikhil.

  1. We don’t review schematic here. Please follow design guide document.

  2. What does that mean using two SoMs? Are you trying to use one carrier board to have 2 SOM on it running at same time? We don’t support any kind of such design here.

I am not sure what is your point here because I already mentioned, If you don’t have FUSB301, then you need to modify device tree. You don’t need to 100% use devkit design. Part of the work may need the help from your USB solution vendor. For example, if they have their own device tree setting, then they may guide you how to write.