Jetson Nano is not turning ON

Wayne, Should the Empty SD card is inserted or the SD with the Image is Inserted?

With image.

And sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1 is the Flash command or only flash.sh?

sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1

Dear Wayne,
With the same setup for a serial console, I am getting
~/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_NANO_DEVKIT/Linux_for_Tegra$ sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 4.3

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.

Hi,

Read the error please… seems your board is not in recovery mode…

Nothing to do with the serial console.

Hi Wayne,

  1. With a Serial console.
  2. With SD card with the image inserted.
  3. With board in Recovery mode.
  4. With board connected to Power and to host through micro USB port.

After I run the command: ubuntu@ubuntu-HP-Laptop-15-bs0xx:~/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_NANO_DEVKIT/Linux_for_Tegra$ sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1.

I get the log pasted below:

[ 0.0070 ] tegrasign --key None --getmode mode.txt
[ 0.0084 ] Assuming zero filled SBK key
[ 0.0136 ]
[ 0.0136 ] Generating RCM messages
[ 0.0161 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[ 0.0171 ] RCM 0 is saved as rcm_0.rcm
[ 0.0208 ] RCM 1 is saved as rcm_1.rcm
[ 0.0210 ] List of rcm files are saved in rcm_list.xml
[ 0.0210 ]
[ 0.0210 ] Signing RCM messages
[ 0.0218 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0225 ] Assuming zero filled SBK key
[ 0.0276 ]
[ 0.0276 ] Copying signature to RCM mesages
[ 0.0285 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0296 ]
[ 0.0297 ] Parsing partition layout
[ 0.0350 ] tegraparser --pt flash.xml.tmp
[ 0.0433 ]
[ 0.0434 ] Creating list of images to be signed
[ 0.0456 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --list images_list.xml
[ 0.0662 ]
[ 0.0662 ] Generating signatures
[ 0.0674 ] tegrasign --key None --list images_list.xml --pubkeyhash pub_key.key
[ 0.0681 ] Assuming zero filled SBK key
[ 0.1484 ]
[ 0.1484 ] Generating br-bct
[ 0.1506 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.cfg --chip 0x21 0
[ 0.1514 ] Copying Sdram info from 0 to 1 set
[ 0.1609 ] Copying Sdram info from 1 to 2 set
[ 0.1610 ] Copying Sdram info from 2 to 3 set
[ 0.1610 ]
[ 0.1611 ] Updating boot device parameters
[ 0.1623 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatedevparam flash.xml.bin
[ 0.1635 ] Warning: No sdram params
[ 0.1637 ]
[ 0.1638 ] Updating bl info
[ 0.1646 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[ 0.1789 ]
[ 0.1789 ] Updating secondary storage information into bct
[ 0.1805 ] tegraparser --pt flash.xml.bin --chip 0x21 0 --updatecustinfo P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct
[ 0.1818 ]
[ 0.1819 ] Updating Odmdata
[ 0.1843 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatefields Odmdata =0x94000
[ 0.1860 ] Warning: No sdram params
[ 0.2405 ]
[ 0.2407 ] Get Signed section of bct
[ 0.2450 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --listbct bct_list.xml
[ 0.2483 ]
[ 0.2484 ] Signing BCT
[ 0.2562 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key
[ 0.2605 ] Assuming zero filled SBK key
[ 0.2625 ]
[ 0.2626 ] Updating BCT with signature
[ 0.2656 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatesig bct_list_signed.xml
[ 0.2701 ]
[ 0.2702 ] Copying signatures
[ 0.2772 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[ 0.2965 ]
[ 0.2967 ] Updating BFS information on BCT
[ 0.3003 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatebfsinfo flash.xml.bin
[ 0.3043 ]
[ 0.3044 ] Boot Rom communication
[ 0.3074 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[ 0.3127 ] BootRom is not running
[ 0.3556 ]
[ 0.3557 ] Sending BCTs
[ 0.3613 ] tegrarcm --download bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct
[ 0.3690 ] Applet version 00.01.0000
[ 0.3900 ] Sending bct
[ 0.3905 ] […] 100%
[ 0.5707 ]
[ 0.5739 ] tegrahost --chip 0x21 --align cboot.bin
[ 0.5776 ]
[ 0.5809 ] tegrahost --magicid EBT --appendsigheader cboot.bin cboot.bin_blheader
[ 0.5920 ]
[ 0.5966 ] tegrasign --key None --list cboot.bin_list.xml
[ 0.6030 ] Assuming zero filled SBK key
[ 0.6566 ]
[ 0.6616 ] tegrahost --updatesigheader cboot.bin_blheader.encrypt cboot.bin_blheader.hash zerosbk
[ 0.6652 ]
[ 0.6685 ] tegrahost --chip 0x21 --align tegra210-p3448-0000-p3449-0000-a02.dtb
[ 0.6698 ]
[ 0.6709 ] tegrahost --magicid DTB --appendsigheader tegra210-p3448-0000-p3449-0000-a02.dtb tegra210-p3448-0000-p3449-0000-a02.dtb_blheader
[ 0.6726 ]
[ 0.6739 ] tegrasign --key None --list tegra210-p3448-0000-p3449-0000-a02.dtb_list.xml
[ 0.6749 ] Assuming zero filled SBK key
[ 0.6824 ]
[ 0.6850 ] tegrahost --updatesigheader tegra210-p3448-0000-p3449-0000-a02.dtb_blheader.encrypt tegra210-p3448-0000-p3449-0000-a02.dtb_blheader.hash zerosbk
[ 0.6870 ]
[ 0.6876 ] Sending bootloader and pre-requisite binaries
[ 0.6889 ] tegrarcm --download ebt cboot.bin.encrypt 0 0 --download rp1 tegra210-p3448-0000-p3449-0000-a02.dtb.encrypt 0
[ 0.6902 ] Applet version 00.01.0000
[ 0.7050 ] Sending ebt
[ 0.7053 ] […] 100%
[ 0.8108 ] Sending rp1
[ 0.8139 ] […] 100%
[ 0.8657 ]
[ 0.8734 ] tegrarcm --boot recovery
[ 0.8765 ] Applet version 00.01.0000
[ 0.8960 ]
[ 0.8961 ] Retrieving storage infomation
[ 0.9014 ] tegrarcm --oem platformdetails storage storage_info.bin
[ 0.9048 ] Applet is not running on device. Continue with Bootloader
[ 0.9301 ]
[ 0.9422 ] tegradevflash --oem platformdetails storage storage_info.bin
[ 0.9462 ] Cannot Open USB
[ 1.0754 ]
Error: Return value 8
Command tegradevflash --oem platformdetails storage storage_info.bin
Failed flashing t210ref.![WhatsApp Image 2020-09-07 at 3.30.02 PM|666x500]

(upload://4L6gNRp3U2RGfwHpLmWGDoRwDZH.jpeg)

err…

This is host log. You already shared this three times… I don’t need this log anymore…

  1. The log from your host. You already shared that. -> You shared this 3 times…
  2. The serial log from UART you said you cannot dump. -> I need this

Do you see anything from serial console when you type the command?

Make it more easier to understand…

You need 2 terminals to observe the logs

One terminal is to run the flash.sh and you will see the log you shared 3 times.

The second terminal is to run picocom/minicom.

Wayne,
Thanks for your time, thanks for your response.

There is nothing I can see in the serial console after I run the command.

Do you have other jetson nano device to verify your UART setup is correct?

Dear Wayne,
I have only one Jetson nano device with me.
Is there any other way to debug this?

Are you able to see any log from serial console if you power device up without sdcard?

Also, please note that the order is important.

If you enable picocom after device boots up, it may not record the log.

There is still no log from the console if I power up without SD Card inserted.

https://forums.developer.nvidia.com/t/serial-console-setup-parameters

Hi darshancganji12,

Please connect TX/RX/GND cable in J44. (please make sure you connect to the right pins)
Using Jumper to connect J40 pins 3 & 4, then plug-in power supply, now your device is into recovery mode.
You can use “lsusb” to check on your host machine.
Now you can use minicom/picocom to open uart log:

ll /dev/ttyUSB*
sudo picocom -b 115200 /dev/ttyUSBx

You can check more detail on Nano User Guide.

Hi Wayne and Carolyuu,
I connected TX/RX/GND perfectly on J44, but still the same(No Log on Serial Console).
I also tried TX/RX/GND on J41, still the same.

Dear Wayne, Carolyuu,
I created only one partition in the SD card and flashed an Image(as shown in Pic below). Is it fine that I am flashing an Image in SD card with only one partition?

Hi

If you cannot dump the log and don’t know whether your device is still alive or not.

I would suggest you to RMA your jetson nano and get a new one.

Dear @Wayne, may I know how to RMA the Jetson Nano?
Is it a Warranty Policy?

The RMA FAQ is here:
https://developer.nvidia.com/embedded/faq#rma-process