We designed a customized carrier board for our application with only Ethernet and CSI camera interfaces. Display-related interfaces were not implemented.
Current observations:
- Input power: 24V
- DC-DC converter output: 5V is verified and stable.
- CPU fan PWM signal is active and varying, indicating that the module is at least partially powering up.
- Ethernet is not functioning.
- Ethernet ACT and SPEED signals remain continuously high.
Since no display interface is available, it is difficult to confirm whether the CPU is booting successfully. We request suggestions for debugging and methods to verify the boot status of the CPU.
Checks already completed:
- 5V supply verified
- RESET signal high
- POWER_EN signal high
Please advise on further hardware and software debugging steps.
Hello @udhayakumar.p!
Based on the title and content of your topic, it looks like it may receive better visibility and feedback in a different category. We took the liberty of moving it for you.
If this was an incorrect assessment, please send me a direct message.
Disclaimer: this moderation suggestion and message were generated with AI assistance.
— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —
To debug the booting issue of the Jetson Orin Nano on your customized carrier board, follow these steps:
Hardware Debugging Steps
- Verify Power Supply: Ensure that the 5V power supply is stable and within the recommended voltage range. Although you’ve mentioned that the 5V supply is verified and stable, double-check the voltage levels at different points on the board to rule out any voltage drops.
- Check RESET and POWER_EN Signals: You’ve confirmed that the RESET signal is high and the POWER_EN signal is high, which is correct for normal operation. However, ensure that these signals are not being driven low inadvertently at any point during the boot process.
- Ethernet Interface: Since the Ethernet ACT and SPEED signals remain continuously high, it might indicate an issue with the Ethernet interface or its configuration. Verify that the Ethernet PHY (Physical Layer) chip is properly configured and powered. Check the datasheet of the Ethernet PHY chip used on your board for specific requirements.
- CSI Camera Interface: Although the CSI camera interface is not directly related to the boot process, ensure that it is properly connected and configured. Any issues here might not directly affect booting but could indicate a problem with the board’s design or assembly.
Software Debugging Steps
Given the lack of a display interface, debugging the software aspect requires alternative methods:
- Serial Console: Use a serial console (UART) to monitor the boot logs. This is the most straightforward way to diagnose boot issues without a display. Connect a USB-to-TTL serial adapter to the UART pins on your carrier board (typically available on the Jetson Orin Nano module) and use a terminal program on your host PC to monitor the serial output at the appropriate baud rate (usually 115200).
- JTAG/SWD Debugging: If available, use JTAG or SWD (Serial Wire Debug) interfaces for more detailed debugging, including halting the CPU and examining memory contents. This requires specific hardware and software tools.
- Network Boot or Recovery Mode: If the Ethernet interface is functional but not detected during normal boot, try booting the Jetson Orin Nano in recovery mode. This might allow you to flash a new image or update the device tree configuration to fix any issues related to the Ethernet interface.
Additional Steps
- Review Documentation: Double-check the Jetson Orin Nano documentation and your carrier board’s design files to ensure that all necessary signals are properly connected and configured.
- Compare with Reference Designs: NVIDIA provides reference designs for carrier boards. Comparing your design with these references might highlight any discrepancies or omissions in your design.
- Seek Community Support: The NVIDIA developer forums and other community resources can be invaluable for troubleshooting specific issues related to the Jetson Orin Nano and custom carrier board designs.
By following these steps, you should be able to gather more information about the boot status of your Jetson Orin Nano on the customized carrier board and potentially identify and resolve the issue preventing successful booting.
— We support team will also look into your issue to have further suggestions soon. please stay tuned. —
For NV devkit, you could check UART serial console with this method.
For a custom board, you need to wiring out the UART interface too and check the logs.