Custom Carrier Board Bring Up - NVME Drive testing

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
,
1

Hi,

I’m a hardware dev and have been tasked with bringing up a custom carrier board we’ve designed for the jetson nano. I’m currently in the process of trying to show whether or not the NVME m.2 slot is operating properly.

I’ve been able to bring the jetson orin nano into recovery mode but am looking for ways to interact with it to test if it is working.

The approach I am taking currently is just to try and flash the default dev board image to the carrier board NVME but that is failing with “device failed to boot to the initrd flash kernel”. I’m not sure what to make of that. I’ve attached the logs below.

SDKM_logs_2025-01-23_14-45-55.zip (396.3 KB)

What commands and debug information can I send/recieve over recovery mode USB link? Any help in figuring this out would be greatly appreciated!

Best,

Teva

3

I am not sure if you have software engineer there that can help do the rest of work because it is more like software part now to me.

First, please enable serial console log during flash failure so that we can check the status on the board.

What commands and debug information can I send/recieve over recovery mode USB link? Any help in figuring this out would be greatly appreciated!

There is no hardware configuration that you could do for now. Please dump the log first.

1 Like
4

Unfortunately there is no software dev time available for this at the moment. I’ll get the serial log ASAP, thanks for the quick reply!

5

SSD-SD_uart_debug.txt (47.9 KB)
Hi Please find attached the serial debug data, is it possible this has to do with the lack of carrier board EEPROM? we have not implemented it on the carrier board.

6

Update to this:

For reference I was using the orin nano dev kit modules on the carrier board, though i think that was unlikely to be causing issues.

I tried a second module that had been flashed correctly on the dev kit and it seems the board has some hardware issues that may have damaged the modules (it sent the second module to a state of constant boot loop even on the dev board. Still trying to figure out root cause.

7

Hi final follow up, I got it working! fixed the hardware problem and flashed with the necessary changes to the eeprom settings and it boots up correctly!

9

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