Jetson Orin Nano 4GB with Waveshare Carrier Board Not Booting (Red Light Only)

Hardware Details:

  1. Jetson Module: NVIDIA Jetson Orin Nano 4GB (Part # 900-13767-0040-000)
    • Purchased from Arrow (NVIDIA partner in the US).
    • Shipped to India as a module-only kit (no developer kit).

  2. Carrier Board: Waveshare Jetson Orin Nano/NX Carrier Board
    • Purchased from ThinkRobotics (India).

  3. Cooling: Official Cooling Fan for Jetson Orin Nano.

  4. Power Supply: 19V 5A (85W) BIS-Certified Power Adapter (2.5mm x 5.5mm).

  5. Storage: Seagate Barracuda PCIe Gen4 NVMe SSD (250GB).
    • Flashed with jp61-orin-nano-sd-card-image.zip.

Issue Details:
After assembling the components and flashing the Jetson OS onto the SSD, I connected the SSD to the M.2 Key M slot on the carrier board.
On powering the board:
• A red light appears, indicating power.
• Nothing is displayed on the connected monitor (via HDMI or DP).

Steps Taken to Resolve:

  1. Verified the SSD was properly flashed using balenaEtcher on Mac.
  2. Ensured the carrier board connections were secure, including the Jetson module, fan, and SSD.

Additional Notes:
• I do not have the official NVIDIA Jetson Orin Nano Developer Kit, as I purchased the module-only version. Hence, I used the Waveshare carrier board for this setup.

Questions:

  1. Is the jp61-orin-nano-sd-card-image.zip compatible with my setup (module + carrier board)?
  2. Is there a specific bootloader or firmware requirement for the Waveshare carrier board?
  3. Could the SSD (Seagate Barracuda PCIe Gen4) be incompatible or require additional steps for configuration?
  4. How can I confirm if the Jetson module is functioning properly, or if this is a carrier board issue?

Attached Images:

  1. Photo of the assembled board, including SSD, fan, and carrier board.
  2. Close-up of the SSD and carrier board.
  3. Full setup with power connected.

Request:
Any guidance or troubleshooting steps to resolve this issue would be highly appreciated. Please let me know if additional details or logs are required.

Regards,
Alok

Any guidance or troubleshooting steps to resolve this issue would be highly appreciated. Please let me know if additional details or logs are required.

Yes, dump the serial console log from your board by connecting the cable.

  1. Is the jp61-orin-nano-sd-card-image.zip compatible with my setup (module + carrier board)?

This question is actually a weird one. If your carrier board has a sdcard slot, it means this carrier board is not for Orin Nano. Orin Nano design has no sdcard pin for production module (your “module-only version”). Only the devkit module has it.

Thank you for your response and clarification.

You’re absolutely right—my Orin Nano module is a production module and does not have an SD card interface. I am not using an SD card. Instead, I have flashed the jp61-orin-nano-sd-card-image.zip onto a Seagate Barracuda PCIe Gen4 NVMe SSD, which is connected to the M.2 Key M slot on my Waveshare carrier board.

I used this image based on the assumption that the Waveshare carrier board would boot from the SSD if properly configured. I understand now that the devkit and production modules have different hardware capabilities, and this image might not be compatible. Could you confirm if there’s a more suitable image for my setup?

I’ll proceed to connect the jumper and dump the serial console logs as per the instructions provided in the JetsonHacks guide. I’ll share the logs shortly for further debugging.

Regards,
Alok

I reached out to them with the same question and they never responded so we passed on the board. Typically when they ignore your question, hide critical details like that it means it does not work.

You should be able to make it work but will need a schematic for the carrier board and reconfigure your .dtsi. That is about the only issue that I see preventing you from booting. I don’t have that carrier board so this is pure conjecture.

1 Like

Thank you for your detailed response. I truly appreciate you taking the time to provide your insights. I’ll also reach out to Waveshare to obtain the carrier board schematic and verify if any configurations are required on their end.

1 Like

One other thing, burn the r35.x and jp5.x and try that one. r36.4 has a different boot loader so that could be a potential mismatch too. Just a guess, not for fact.

1 Like