NVIDIA Nano

Robotics & Edge Computing Jetson Systems Jetson Nano
1

jetpack 4.5.1
32.5.1
flashing command :sudo ./flash.sh --no-systemimg JET_JN_NN mmcblk0p1

*** Flashing target device started. ***
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[ 0.0024 ] tegrasign --getmode mode.txt --key None
[ 0.0034 ] Assuming zero filled SBK key
[ 0.0038 ]
[ 0.0039 ] Generating RCM messages
[ 0.0061 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[ 0.0070 ] RCM 0 is saved as rcm_0.rcm
[ 0.0077 ] RCM 1 is saved as rcm_1.rcm
[ 0.0077 ] List of rcm files are saved in rcm_list.xml
[ 0.0077 ]
[ 0.0077 ] Signing RCM messages
[ 0.0099 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0108 ] Assuming zero filled SBK key
[ 0.0161 ]
[ 0.0161 ] Copying signature to RCM mesages
[ 0.0186 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0211 ]
[ 0.0211 ] Parsing partition layout
[ 0.0235 ] tegraparser --pt flash.xml.tmp
[ 0.0247 ]
[ 0.0249 ] Using default ramcode: 0
[ 0.0249 ] Disable BPMP dtb trim, using default dtb
[ 0.0249 ]
[ 0.0249 ] Creating list of images to be signed
[ 0.0271 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --list images_list.xml
[ 0.0379 ]
[ 0.0380 ] Generating signatures
[ 0.0403 ] tegrasign --key None --list images_list.xml --pubkeyhash pub_key.key
[ 0.0412 ] Assuming zero filled SBK key
[ 0.1361 ]
[ 0.1362 ] Generating br-bct
[ 0.1387 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.cfg --chip 0x21 0
[ 0.1436 ]
[ 0.1436 ] Updating boot device parameters
[ 0.1458 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatedevparam flash.xml.bin
[ 0.1468 ] Warning: No sdram params
[ 0.1471 ]
[ 0.1471 ] Updating bl info
[ 0.1489 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[ 0.1508 ]
[ 0.1509 ] Updating secondary storage information into bct
[ 0.1531 ] tegraparser --pt flash.xml.bin --chip 0x21 0 --updatecustinfo P3448_A00_lpddr4_204Mhz_P987.bct
[ 0.1552 ]
[ 0.1553 ] Updating Odmdata
[ 0.1575 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatefields Odmdata =0xa4000
[ 0.1584 ] Warning: No sdram params
[ 0.1587 ]
[ 0.1587 ] Get Signed section of bct
[ 0.1609 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --listbct bct_list.xml
[ 0.1620 ]
[ 0.1621 ] Signing BCT
[ 0.1669 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key
[ 0.1681 ] Assuming zero filled SBK key
[ 0.1688 ]
[ 0.1688 ] Updating BCT with signature
[ 0.1736 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatesig bct_list_signed.xml
[ 0.1750 ]
[ 0.1751 ] Copying signatures
[ 0.1773 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[ 0.1871 ]
[ 0.1872 ] Updating BFS information on BCT
[ 0.1897 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatebfsinfo flash.xml.bin
[ 0.1906 ] BFS:
[ 0.1923 ] 0: [PT ] crc-flash.xml.bin (size=131072/131072)
[ 0.1929 ] 1: [TBC] nvtboot_cpu.bin.encrypt (size=65760/196608)
[ 0.1935 ] 2: [RP1] kernel_tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt (size=241264/1048576)
[ 0.1942 ] 3: [EBT] cboot.bin.encrypt (size=485392/655360)
[ 0.1947 ] 4: [WB0] warmboot.bin.encrypt (size=3952/131072)
[ 0.1951 ] 5: [BPF] sc7entry-firmware.bin.encrypt (size=3376/262144)
[ 0.1956 ] BFS0: 131072 @ 2560 SUM 4734d204 over 2883584 bytes
[ 0.1962 ] BFS:
[ 0.1971 ] 0: [PT-1] crc-flash.xml.bin (size=131072/131072)
[ 0.1979 ] 1: [TBC-1] nvtboot_cpu.bin.encrypt (size=65760/196608)
[ 0.1989 ] 2: [RP1-1] kernel_tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt (size=241264/1048576)
[ 0.1997 ] 3: [EBT-1] cboot.bin.encrypt (size=485392/655360)
[ 0.2002 ] 4: [WB0-1] warmboot.bin.encrypt (size=3952/131072)
[ 0.2007 ] 5: [BPF-1] sc7entry-firmware.bin.encrypt (size=3376/262144)
[ 0.2013 ] 8: [VER_b] emmc_bootblob_ver.txt (size=80/32768)
[ 0.2019 ] 9: [VER] emmc_bootblob_ver.txt (size=80/32768)
[ 0.2023 ] BFS1: 131072 @ 8704 SUM 4734d204 over 2981888 bytes
[ 0.2028 ] KFS:
[ 0.2379 ] 0: [DTB] kernel_tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt (size=241264/1048576)
[ 0.2387 ] 1: [TOS] tos-mon-only.img.encrypt (size=54208/6291456)
[ 0.2391 ] 2: [EKS] eks.img (size=1028/81920)
[ 0.2394 ] 3: [LNX] boot.img.encrypt (size=667648/67092480)
[ 0.2397 ] KFS0: 1048576 @ 29376546 SUM 3823fe98 over 8089600 bytes
[ 0.2461 ] KFS:
[ 0.2834 ] 0: [DTB-1] kernel_tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt (size=241264/1048576)
[ 0.2843 ] 1: [TOS-1] tos-mon-only.img.encrypt (size=54208/6291456)
[ 0.2848 ] 2: [EKS-1] eks.img (size=1028/81920)
[ 0.2852 ] 3: [LNX-1] boot.img.encrypt (size=667648/67092480)
[ 0.2857 ] KFS1: 1048576 @ 29522082 SUM 3823fe98 over 8089600 bytes
[ 0.2926 ]
[ 0.2927 ] Boot Rom communication
[ 0.2957 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[ 0.2966 ] BR_CID: 0x3210100164457783080000000a040480
[ 0.3226 ] RCM version 0X210001
[ 0.3664 ] Boot Rom communication completed
[ 1.3735 ]
[ 1.3735 ] Sending BCTs
[ 1.3760 ] tegrarcm --download bct P3448_A00_lpddr4_204Mhz_P987.bct
[ 1.3773 ] Applet version 00.01.0000
[ 1.4037 ] Sending bct
[ 1.4039 ] […] 100%
[ 1.6267 ]
[ 1.6291 ] tegrahost --chip 0x21 --align cboot.bin
[ 1.6300 ]
[ 1.6322 ] tegrahost --magicid EBT --appendsigheader cboot.bin cboot.bin_blheader
[ 1.6346 ]
[ 1.6373 ] tegrasign --key None --list cboot.bin_list.xml
[ 1.6387 ] Assuming zero filled SBK key
[ 1.6517 ]
[ 1.6544 ] tegrahost --updatesigheader cboot.bin_blheader.encrypt cboot.bin_blheader.hash zerosbk
[ 1.6574 ]
[ 1.6613 ] tegrahost --chip 0x21 --align tegra210-p3448-0000-p3449-0000-b00.dtb
[ 1.6626 ]
[ 1.6649 ] tegrahost --magicid DTB --appendsigheader tegra210-p3448-0000-p3449-0000-b00.dtb tegra210-p3448-0000-p3449-0000-b00.dtb_blheader
[ 1.6674 ]
[ 1.6702 ] tegrasign --key None --list tegra210-p3448-0000-p3449-0000-b00.dtb_list.xml
[ 1.6716 ] Assuming zero filled SBK key
[ 1.6788 ]
[ 1.6816 ] tegrahost --updatesigheader tegra210-p3448-0000-p3449-0000-b00.dtb_blheader.encrypt tegra210-p3448-0000-p3449-0000-b00.dtb_blheader.hash zerosbk
[ 1.6835 ]
[ 1.6840 ] Sending bootloader and pre-requisite binaries
[ 1.6866 ] tegrarcm --download ebt cboot.bin.encrypt 0 0 --download rp1 tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt 0
[ 1.6886 ] Applet version 00.01.0000
[ 1.7618 ] Sending ebt
[ 1.7626 ] […] 100%
[ 1.8711 ] Sending rp1
[ 1.8751 ] […] 100%
[ 1.9322 ]
[ 1.9375 ] tegrarcm --boot recovery
[ 1.9422 ] Applet version 00.01.0000
[ 2.0187 ]
[ 2.0188 ] Retrieving storage infomation
[ 2.0214 ] tegrarcm --oem platformdetails storage storage_info.bin
[ 2.0226 ] Applet is not running on device. Continue with Bootloader
[ 2.5629 ]
[ 2.5653 ] tegradevflash --oem platformdetails storage storage_info.bin
[ 2.5665 ] Cboot version 00.01.0000
[ 2.5960 ] Saved platform info in storage_info.bin

after this saved platform into in storage_info.bin it is been paused , there is no change

2

Really don’t understand what is your expectation from the command you are using here.

3

This is flashing command for release image
After the last line in present in the log , the flashing log is paused and action takes place

4

Why do you run with --no-systemimg ?

Also, it seems a custom board flash command, if this is something taught by the vendor, then please consult with them first.

5

Already system image is present
I tried with jetson xavier using same command with “no-systemimg”
I was able to flash

6

Then try to dump the serial console log and see what got printed.

Or try full flash instead of this command.

7

Iam not able to get seriel log
I can access minicom using console with loopback
but when connected to devkit , Iam unable to get minicom

8

Is the board still able to power up? If it can power, then it can at least show some logs in UART serial console. If it does not have log, your setup of serial console could be wrong.

9

its not showing logs
what can be done?

10

Check if your uart cable is really fine. Try on NV devkit.

We don’t guarantee your board is fine as that is your board.

11

I tried on NV devkit but not getting logs
I checked the console is able to get loopback but when connected to devKIt
no logs to show.

12

Could you take a picture of your setup of these cables?

13

image
image512×683 56.8 KB

pins are connected from GND to GND , UART_TX to TX , UART_RX to RX

14

Do you have USB-ttl cable to do this work?

15

And are you sure your jetson is powered on? There should be power LED to indicate this.

16

No we use jumpers to get console

17

yes board was powered , while capturing it was not powered

18

…you need to capture the log when it is powered on…

19

no log when powered

20

Do you have other Jetson nano on your side that can do the test?

Cannot dump serial console log could be consider as hardware defect and you need to RMA your device.

If multiple devices have same issue, I would think your cable or serial console setup is still wrong.