Hi, we have a custom board that includes the Orin module. I attempted to flash Ubuntu to the Orin module by putting it into recovery mode. While holding the recovery button on our custom board, I powered the system, then released the recovery button. However, the Orin module was not detected via USB.
To troubleshoot, I removed the Orin module from the custom board and connected it to a developer kit. I followed the same procedure: held the recovery button while powering the system, but this time, the LED light on the Orin briefly turned on and then immediately shut off. The Orin module did not boot up. I powered it down, and without pressing any buttons, I tried powering it on again. However, the same issue occurred—only a brief flash of the LED before it turned off.
When I press the power button, the light flashes briefly but does not stay on, and the Orin does not boot. Interestingly, when the module is connected, my host PC shows its serial number and other information in the kernel logs, but I do not receive any logs through the UART interface.
The lsusb output and kernel logs seem to indicate that the device listed corresponds to the carrier board.
lsusb Output:
Bus 003 Device 003: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Kernel Logs:
[ 1588.439090] usb 3-3: new full-speed USB device number 4 using xhci_hcd
[ 1588.589176] usb 3-3: New USB device found, idVendor=0955, idProduct=7045, bcdDevice= 0.01
[ 1588.589181] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1588.589182] usb 3-3: Product: Tegra On-Platform Operator
[ 1588.589183] usb 3-3: Manufacturer: NVIDIA
[ 1588.593623] hid-generic 0003:0955:7045.0003: hiddev0,hidraw0: USB HID v1.10 Device [NVIDIA Tegra On-Platform Operator] on usb-0000:00:14.0-3/input0
[ 1588.593872] cdc_acm 3-3:1.1: ttyACM0: USB ACM device
[ 1588.594124] cdc_acm 3-3:1.3: ttyACM1: USB ACM device
[ 1588.594366] cdc_acm 3-3:1.5: ttyACM2: USB ACM device
[ 1588.594624] cdc_acm 3-3:1.7: ttyACM3: USB ACM device
The carrier board is our own design. Previously, we always flashed the Ubuntu image to the Orin module using the developer kit’s carrier board, and we never encountered any issues. The module functioned properly on our custom board as well.
This is the first time we tested the recovery button on our custom board, and this issue appeared afterward.
Additionally, I tested the developer kit’s carrier board with another Orin module, and there were no problems. I also tested our custom carrier board, and it worked fine without any issues.
Yes, I tried running the flashing procedure on the devkit with the SOM that is showing problems. However, as shown in the video, when I attempt to start it in either recovery mode or normal mode, the LED briefly lights up and then immediately turns off, and the system does not boot.
The kernel and lsusb logs I shared earlier appear when I connect the UART USB. I believe I incorrectly described this in my previous message.
When I run the flash.sh bash script, I get the following error:
###############################################################################
# L4T BSP Information:
# R35 , REVISION: 5.0
# User release: 0.0
###############################################################################
ECID is
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
I appreciate any guidance you can offer regarding this issue.
Sorry for the late reply, I have been focusing on a project form one of our customers.
To be honest, my thoughts right now are that it could have been that the custom carrier board could have damaged the SOM when trying to flash through the force recovery mode feature.
That being said, it is very difficult to test without risking damaging more HW.
What I would recommend in your case is trying to get access to boot logs through UART.
Would it be difficult for you to try that?
regards,
Andrew
Embedded Software Engineer at ProentusNova