Hello NVIDIA Team,
I am currently bringing up a custom carrier board based on the Jetson Orin NX 8GB production module.
Hardware:
- Module: Jetson Orin NX 8GB
- Carrier board: Custom-designed carrier board
- SoC: NVIDIA T234
- Boot storage: QSPI + eMMC
- External storage: NVMe
- QSPI Flash: Macronix 64MB
Software:
- Jetson Linux: r36.5.0
- JetPack: 6.2.x
- Ubuntu: 22.04
I am requesting technical support for the BSP/source code and the flashing configuration for Jetson Linux r36.5.0, especially the files required for adapting a custom carrier board to the Orin NX 8GB module.
The main problem is that flashing the system fails.
The board can enter RCM mode successfully, and MB1/MB2/MB2-Applet can run normally.
The following components appear to work:
- RCM USB communication
- MB1 loading
- MB2-Applet loading
- DRAM initialization
- eMMC flashing
- NVMe partition creation and image writing
However, the QSPI operation eventually fails.
Important log:
tegra-qspi 3270000.spi: transfer timeout
tegra-qspi 3270000.spi: error in transfer, fifo status 0x00400005
spi_master spi0: failed to transfer one message from queue
spi-nor: probe of spi0.0 failed with error -2
Earlier in the MB2-Applet stage, the QSPI Flash can be detected:
QSPI Flash: Macronix 64MB
QSPI-0l initialized successfully
This makes us suspect that the problem may be related to the QSPI configuration, device tree/BCT configuration, BSP configuration, or QSPI hardware timing/signal configuration.
There are also some warnings/errors such as:
OCR failed, error = 39390706
STORAGE: Failed to open SDMMC: 3.
and:
Firewall readback mismatch
However, the flashing process can continue and the eMMC/NVMe can be written successfully.
Could you please help us determine:
- Is Jetson Linux r36.5.0 fully supported on Jetson Orin NX 8GB?
- Which exact BSP/device-tree/BCT configuration should be used for a custom carrier board with Orin NX 8GB?
- Is there a recommended reference configuration for QSPI on a custom carrier board?
- Are there any known QSPI timing/configuration issues with r36.5.0?
- Which source packages contain the relevant MB1 BCT, MB2 BCT, QSPI configuration and device-tree source files?
- Could you provide or point us to the complete Jetson Linux r36.5.0 source/BSP package required for custom carrier board adaptation?
- Is there any NVIDIA recommended QSPI hardware checklist or reference design that we should verify?
We can provide the complete serial console log, flashing log, schematic, QSPI schematic, device-tree files, MB1/MB2 BCT configuration and board information if required.
We would appreciate your help in identifying whether this is a BSP/software configuration issue or a hardware/QSPI signal integrity issue.
Thank you.
uav-ds01-dts-bct_20260813_065957.zip (483.7 KB)
debug_flash.txt (95.9 KB)