I have a Jetson Xavier NX board. I installed JetPack on an SD card and it booted fine. However, after turning off, the board is not powering up again. The power LED stays on, but nothing comes up on display. I disconnected all peripherals (except Monitor) and also tried using a different power supply, but no luck. Can someone please help figure out how to solve this problem? Can I hard reset the board somehow? Thanks
Hi,
Please try re-flashing with SDK Manager first.
Thanks @DaveYYY for the reply. I don’t have a ready access to an Ubuntu machine to run the SDK manager. Can I just reinstall the image on the SD card? What exactly do I need to flash? The OS on the SD card or is there EPROM on Xavier itself that needs reflashing. Can you share the exact commands to run (or point to documentation) please? Thank you
I cannot tell.
Sometimes it works by just re-flashing the SD card itself, which can be done on Windows or Mac, but it may also be the case that the bootloader on the QSPI memory (not EEPROM) of the module is corrupted, which needs to be re-flashed with a Linux PC.
For a full re-flash, please refer to:
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/IN/QuickStart.html
Thanks. I was able to set up an Ubuntu 20.04 system and install the SDK Manager on it.
The SDK manager correctly detects the board and starts the flashing process, but fails with the following error:
INFO: Flash Jetson Xavier NX - flash: [ 6.5383 ] Sending bct_mem
INFO: Flash Jetson Xavier NX - flash: [ 6.5853 ] […] 100%
ERROR: Flash Jetson Xavier NX - flash: command terminated with error
SUMMARY: DateTime Target Setup - target: Depends on failed component
I have tried this multiple times, with JetPack 5.1.2 as well as JetPack 5.1.1/JetPack 5.0.2 but I get the same error every time.
I also noticed that the board is permanently staying in the recover mode, whether or not I jump the FC REC pin.
I am actually not sure if I was able to flash the QSPI memory as I couldn’t find instructions for it from running from a host machine.
How do I get past these issues? Thanks
More information:
The SDK manager detects it as Jetson Xavier NX Development board with:
P3668-0000 module
P3509-0000 carrier board
I have also tried with alternate SD cards but with no luck.
When I try to flash the board manually by following the steps in:
https://docs.nvidia.com/jetson/archives/r35.1/DeveloperGuide/text/IN/QuickStart.html
I get the following error:
1.9662 ] adding BCH for mem_rcm_aligned.bct
[ 1.9966 ] tegrasign_v3.py --key None --list mem_rcm_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key
[ 1.9967 ] Assuming zero filled SBK key
[ 1.9979 ] Warning: pub_key.key is not found
[ 1.9722 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mem_rcm_aligned_sigheader.bct.encrypt mem_rcm_aligned_sigheader.bct.hash zerosbk
[ 1.9735 ] Copying signatures
[ 1.9753 ] tegrahost_v2 --chip 0x19 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[ 2.3751 ] Boot Rom communication
[ 2.3807 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml
[ 2.3843 ] BR_CID: 0x88021911647176460800000002000240
[ 2.7979 ] RCM version 0X190001
[ 3.2100 ] Boot Rom communication completed
[ 5.2333 ] tegrarcm_v2 --isapplet
[ 5.2366 ] Applet version 01.00.0000
[ 6.0641 ] Sending BCTs
[ 6.0693 ] tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt --download bct_mem mem_rcm_sigheader.bct.encrypt
[ 6.0727 ] Applet version 01.00.0000
[ 6.9000 ] Sending bct_bootrom
[ 6.9003 ] […] 100%
[ 6.9016 ] Sending bct_mb1
[ 6.9066 ] […] 100%
[ 6.9107 ] Sending bct_mem
[ 6.9580 ] […] 100%
Error: Return value 8
Command tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt --download bct_mem mem_rcm_sigheader.bct.encrypt
Failed flashing t186ref.
@DaveYYY Can you provide some insights please on how to fix this problem? Thanks
Can you please try to dump serial console log during flashing?
Does flashing with Ubuntu 18.04 make any difference? Also, are you using a real host PC instead of a virtual machine?
@DaveYYY
I am using a real host machine where I freshly installed Ubuntu 20.04
I don’t have access to an Ubuntu 18.04 machine.
How do I dump the serial console log? Thanks
Check this:
Hi @DaveYYY I was able to connect the board with a USB to Serial console cable following instructions in the video. When I plugin the power to Jetson Xavier NX, the output on minicom becomes garbled.
Just to confirm that I was using the minicom correctly and the cable is good, I tried this with another Jetson Orin Nano, and there I got the boot prompt correctly through minicom.
Also, dmesg --follow correctly prints:
1932.482686] usb 1-2: Manufacturer: Prolific Technology Inc.
[ 1932.484167] pl2303 1-2:1.0: pl2303 converter detected
[ 1932.485203] usb 1-2: pl2303 converter now attached to ttyUSB0
[ 1933.087905] pl2303 ttyUSB0: pl2303_get_line_request - failed: -32
2061.516112] usb 1-3: new high-speed USB device number 24 using xhci_hcd
[ 2061.665001] usb 1-3: New USB device found, idVendor=0955, idProduct=7e19, bcdDevice= 1.02
[ 2061.665017] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2061.665023] usb 1-3: Product: APX
[ 2061.665027] usb 1-3: Manufacturer: NVIDIA Corp.
statserial output:
Device: /dev/ttyUSB0
Signal Pin Pin Direction Status Full
Name (25) (9) (computer) Name
FG 1 - - - Frame Ground
TxD 2 3 out - Transmit Data
RxD 3 2 in - Receive Data
RTS 4 7 out 1 Request To Send
CTS 5 8 in 0 Clear To Send
DSR 6 6 in 0 Data Set Ready
GND 7 5 - - Signal Ground
DCD 8 1 in 0 Data Carrier Detect
DTR 20 4 out 1 Data Terminal Ready
RI 22 9 in 0 Ring Indicator
So you don’t get anything meaningful from the serial console during flashing?
No, nothing meaningful (just a few more lines of more garbled output) on the serial console while flashing. However, The sdkmanager recognizes the board, even almost completes the flashing but then eventually throws an error.
Also, please note that this device is perpetually staying in the Recovery mode. I don’t even have to put the jumper.
Here is the log from the SDK Manager. @DaveYYY
sdkmanager-log.txt (4.3 KB)
Then maybe the module is broken.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.