Hi,
My Jetson Nano is automatically turning off when the SD card with an Image is inserted into it. It is ON when the SD card is not Inserted or when the SD Card without an Image is inserted into it.
Having said that, I tried to Flash the Components through SDK Manager, but at the time of Flashing, it is automatically turning Off.
It is to note that the Force recovery mode is working on the Jetson Nano.
Please help to resolve this issue.
Would be a great help.
Thanks in advance.
Hi,
Please share the log.
https://elinux.org/Jetson/General_debug
Hi,
We need the log from UART serial console too.
Hi @WayneWWW,
The above-sent log I am getting while I am flashing through SDK GUI.
And if I use flash Command(sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1 ) via Terminal I get the Log shown below:
[ 0.0079 ] tegrasign --key None --getmode mode.txt
[ 0.0125 ] Assuming zero filled SBK key
[ 0.0151 ]
[ 0.0153 ] Generating RCM messages
[ 0.0205 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[ 0.0235 ] RCM 0 is saved as rcm_0.rcm
[ 0.0274 ] RCM 1 is saved as rcm_1.rcm
[ 0.0274 ] List of rcm files are saved in rcm_list.xml
[ 0.0275 ]
[ 0.0275 ] Signing RCM messages
[ 0.0314 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0388 ] Assuming zero filled SBK key
[ 0.0621 ]
[ 0.0621 ] Copying signature to RCM mesages
[ 0.0652 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0686 ]
[ 0.0687 ] Parsing partition layout
[ 0.0774 ] tegraparser --pt flash.xml.tmp
[ 0.0859 ]
[ 0.0860 ] Creating list of images to be signed
[ 0.0894 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --list images_list.xml
[ 0.1151 ]
[ 0.1152 ] Generating signatures
[ 0.1185 ] tegrasign --key None --list images_list.xml --pubkeyhash pub_key.key
[ 0.1216 ] Assuming zero filled SBK key
[ 0.2482 ]
[ 0.2482 ] Generating br-bct
[ 0.2507 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.cfg --chip 0x21 0
[ 0.2517 ] Copying Sdram info from 0 to 1 set
[ 0.2596 ] Copying Sdram info from 1 to 2 set
[ 0.2596 ] Copying Sdram info from 2 to 3 set
[ 0.2596 ]
[ 0.2597 ] Updating boot device parameters
[ 0.2610 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatedevparam flash.xml.bin
[ 0.2625 ] Warning: No sdram params
[ 0.2627 ]
[ 0.2627 ] Updating bl info
[ 0.2635 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[ 0.2719 ]
[ 0.2720 ] Updating secondary storage information into bct
[ 0.2750 ] tegraparser --pt flash.xml.bin --chip 0x21 0 --updatecustinfo P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct
[ 0.2784 ]
[ 0.2785 ] Updating Odmdata
[ 0.2816 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatefields Odmdata =0x94000
[ 0.2872 ] Warning: No sdram params
[ 0.2897 ]
[ 0.2898 ] Get Signed section of bct
[ 0.2937 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --listbct bct_list.xml
[ 0.2972 ]
[ 0.2973 ] Signing BCT
[ 0.3030 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key
[ 0.3079 ] Assuming zero filled SBK key
[ 0.3119 ]
[ 0.3120 ] Updating BCT with signature
[ 0.3171 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatesig bct_list_signed.xml
[ 0.3216 ]
[ 0.3218 ] Copying signatures
[ 0.3251 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[ 0.3461 ]
[ 0.3462 ] Updating BFS information on BCT
[ 0.3493 ] tegrabct --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatebfsinfo flash.xml.bin
[ 0.3534 ]
[ 0.3535 ] Boot Rom communication
[ 0.3584 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[ 0.3626 ] BootRom is not running
[ 0.4089 ]
[ 0.4090 ] Sending BCTs
[ 0.4138 ] tegrarcm --download bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.bct
[ 0.4210 ] Applet version 00.01.0000
[ 0.4242 ] Sending bct
[ 0.4250 ] […] 100%
[ 0.6034 ]
[ 0.6083 ] tegrahost --chip 0x21 --align cboot.bin
[ 0.6136 ]
[ 0.6173 ] tegrahost --magicid EBT --appendsigheader cboot.bin cboot.bin_blheader
[ 0.6255 ]
[ 0.6297 ] tegrasign --key None --list cboot.bin_list.xml
[ 0.6359 ] Assuming zero filled SBK key
[ 0.6903 ]
[ 0.6935 ] tegrahost --updatesigheader cboot.bin_blheader.encrypt cboot.bin_blheader.hash zerosbk
[ 0.6984 ]
[ 0.7031 ] tegrahost --chip 0x21 --align tegra210-p3448-0000-p3449-0000-a02.dtb
[ 0.7059 ]
[ 0.7100 ] tegrahost --magicid DTB --appendsigheader tegra210-p3448-0000-p3449-0000-a02.dtb tegra210-p3448-0000-p3449-0000-a02.dtb_blheader
[ 0.7145 ]
[ 0.7171 ] tegrasign --key None --list tegra210-p3448-0000-p3449-0000-a02.dtb_list.xml
[ 0.7185 ] Assuming zero filled SBK key
[ 0.7275 ]
[ 0.7290 ] tegrahost --updatesigheader tegra210-p3448-0000-p3449-0000-a02.dtb_blheader.encrypt tegra210-p3448-0000-p3449-0000-a02.dtb_blheader.hash zerosbk
[ 0.7304 ]
[ 0.7309 ] Sending bootloader and pre-requisite binaries
[ 0.7337 ] tegrarcm --download ebt cboot.bin.encrypt 0 0 --download rp1 tegra210-p3448-0000-p3449-0000-a02.dtb.encrypt 0
[ 0.7353 ] Applet version 00.01.0000
[ 0.7505 ] Sending ebt
[ 0.7512 ] […] 100%
[ 0.8623 ] Sending rp1
[ 0.8659 ] […] 100%
[ 0.9172 ]
[ 0.9217 ] tegrarcm --boot recovery
[ 0.9255 ] Applet version 00.01.0000
[ 0.9294 ]
[ 0.9296 ] Retrieving storage infomation
[ 0.9337 ] tegrarcm --oem platformdetails storage storage_info.bin
[ 0.9393 ] Applet is not running on device. Continue with Bootloader
[ 0.9697 ]
[ 0.9871 ] tegradevflash --oem platformdetails storage storage_info.bin
[ 0.9908 ] Cannot Open USB
[ 1.1284 ]
Error: Return value 8
Command tegradevflash --oem platformdetails storage storage_info.bin
Failed flashing t210ref.
Yes, I know where this log comes from.
But this log is not what I want … please do read the website again to understand what is serial console log…
Thank you for your kind response Wayne.
One last confirmation: Jetson Nano Style - Serial Console - JetsonHacks Is this the blog to be referred? If yes, then I will continue with the steps and share the log.
Thanks in advance
Yes, that is the steps to dump serial console log.
Ok thanks a lot.
@WayneWWW, I followed the same blog(Jetson Nano Style - Serial Console - JetsonHacks) to dump the serial console, I set up the minicom and TTL serial cable connections were perfect, but after Connecting to the power cable to the nano, there is nothing on Minicom like shown in this https://youtu.be/Kwpxhw41W50?t=468 .
Would like to here from you for the further steps.
Thank you
Hi,
Please check if any log is dumped from board when you start the flash process.
Wayne, this is the log I can only find under ~/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_NANO_DEVKIT/Linux_for_Tegra/rootfs/var/log dpkg.log (25.0 KB)
Hi,
That log has nothing to do with your problem.
I want your log from serial console…
Please tell us the command you are using to dump serial console.
In brief, the only logs that can help your problem are:
The log from your host. You already shared that.
The serial log from UART you said you cannot dump.
All the other logs don’t/cannot help your problem.
Thus, I want to know how you setup (2) and what is your commands to use.
Dear @WayneWWW,
Thanks very much for this quick reply.
I have this setup for a Serial console.
May I know the next steps/commands to follow?
On your host machine, please check if there is a /dev/ttyUSB0 device.
If so, please use console tool like minicom or picocom with baud rate 115200.
For example,
sudo picocom -b 115200 /deb/ttyUSB0
Wayne, as per your guidance I had set up the Minicom with the same configuration as above and ttyUSB0 is detected.
Then please connect the power cable or run the flash command
You should see log start to show.
Wayne, Should the Empty SD card is inserted or the SD with the Image is Inserted?
And sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1 is the Flash command or only flash.sh?
