Jetson Start-up Fail

Robotics & Edge Computing Jetson Systems Jetson Nano
23

Hi,

I still get the same issue. Just double checking that I’m supposed to be jumpering FRC pins?

24

You can use ‘lsusb’ command to check on your host machine.
The Jetson module is in Force Recovery mode if you see the message:
Bus <bbb> Device <ddd>: ID 0955: 7f21 Nvidia Corp.

25

Hi, I’ve just checked that and it appears fine. What should I do then?

26

Then you can start flash image by manually:
$ sudo ./ flash.sh jetson-nano-qspi-sd mmcblk0p1

Or run sdkmanager to flash image and install sdk components.

27

I don’t think you understand… I’ve already tried those things.

Using that command tells me that there is no command called that.

Running sdkmanager to flash the image gets stuck at 99.9% during the flash stage.

28

You check your “Linux_for_Tegra” folder have “flash.sh” script, right?
Then you can use “flash.sh” command to flash by manually.
Are you still get command not found when you use “flash.sh” command?

29

I have already checked that, the flash.sh file is there and I still get that issue.

30

Hi,

Please do not use sdkmanager at this moment. SDKmanager also uses the flash.sh tool to flash your board.

Just use the command $ sudo ./ flash.sh jetson-nano-qspi-sd mmcblk0p1

You missed the “.sh” in your previous command so it gives out error. Please use the correct command and share the log here.

We are not asking whether flash.sh exists or not. We are asking you to use it.
Also, Your previous log is only a partial one. We need the full log.

If you don’t know whether flash.sh works fine or not, please also paste the log.

Thanks.

31

Hi, I think the issue of using that command solved when I quit sdkmanager. I’ve got these errors from my console though:

###############################################################################

L4T BSP Information:

R32 , REVISION: 3.1

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

Would you like me to connect my computer to device by USB to USB and power the device by micro-USB?

32

Yes, when you are flashing the board, you need to connect the micro usb cable from host to your jetson nano and put nano into recovery mode.

33

I’m lost. I’m already connecting the USB (host) to device (micro-USB). Those are the only two connections. I’m using FRC pins and I get the same error message as per my previous post.

34

So back to comment #22, what is your result of command “lsusb” on your host after you put device into recovery mode?

Your host needs to see ID 0955: 7f21 Nvidia Corp to make flash start.

35

I get ID 0955: 7f21 when I use that command.

36

Are you using a VM on your host? I mean is your ubuntu host a VM environment?

37

I have Ubuntu 18.04 dual booted as my host

38

I just read the whole thread again and found lots of mismatch.

First, if your module has a sdcard slot on it you need to use the first command to flash. Otherwise, you need to use the emmc one.

sudo ./ flash.sh jetson-nano-qspi-sd mmcblk0p1 → this is for sdcard module.
sudo ./ flash.sh jetson-nano-emmc mmcblk0p1 → this command is for emmc module.

Back to your comment in #14, you chose the emmc module to flash and the flash process starts w/o your latest error. It is weird to use that command if the board has sdcard slot.

  • 21:35:42 INFO : Flash Jetson Nano : exec_command: sudo ./flash.sh jetson-nano-emmc mmcblk0p1
  • 21:35:42 INFO : Flash Jetson Nano : ###############################################################################
  • 21:35:42 INFO : Flash Jetson Nano : # L4T BSP Information:
  • 21:35:42 INFO : Flash Jetson Nano : # R32 , REVISION: 3.1
  • 21:35:42 INFO : Flash Jetson Nano : ###############################################################################
  • 21:35:42 INFO : Flash Jetson Nano : # Target Board Information:
  • 21:35:42 INFO : Flash Jetson Nano : # Name: jetson-nano-emmc, Board Family: t210ref, SoC: Tegra 210,
  • 21:35:42 INFO : Flash Jetson Nano : # OpMode: production, Boot Authentication: ,
  • 21:35:42 INFO : Flash Jetson Nano : ###############################################################################
  • 21:35:42 INFO : Flash Jetson Nano : ./tegraflash.py --chip 0x21 --applet “/home/tarin/Downloads/Jetpack/nvidia_sdk/JetPack_4.3_Linux_P3448-0020/Linux_for_Tegra/bootloader/nvtboot_recovery.bin” --skipuid --cmd “dump eeprom boardinfo cvm.bin”
  • 21:35:42 INFO : Flash Jetson Nano : Welcome to Tegra Flash
  • 21:35:42 INFO : Flash Jetson Nano : version 1.0.0
  • 21:35:42 INFO : Flash Jetson Nano : Type ? or help for help and q or quit to exit
  • 21:35:42 INFO : Flash Jetson Nano : Use ! to execute system commands
  • 21:35:42 INFO : Flash Jetson Nano :
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0009 ] Generating RCM messages
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0016 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/tarin/Downloads/Jetpack/nvidia_sdk/JetPack_4.3_Linux_P3448-0020/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0022 ] RCM 0 is saved as rcm_0.rcm
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0027 ] RCM 1 is saved as rcm_1.rcm
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0027 ] List of rcm files are saved in rcm_list.xml
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0027 ]
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0027 ] Signing RCM messages
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0033 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0038 ] Assuming zero filled SBK key
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0079 ]
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0080 ] Copying signature to RCM mesages
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0086 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0095 ]
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0095 ] Boot Rom communication
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0100 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
  • 21:35:42 INFO : Flash Jetson Nano : [ 0.0106 ] RCM version 0X210001
  • 21:35:43 INFO : Flash Jetson Nano : [ 0.0552 ] Boot Rom communication completed
  • 21:35:43 INFO : Flash Jetson Nano : [ 1.0620 ]
  • 21:35:43 INFO : Flash Jetson Nano : [ 1.0622 ] dump EEPROM info
  • 21:35:43 INFO : Flash Jetson Nano : [ 1.0654 ] tegrarcm --oem platformdetails eeprom /home/tarin/Downloads/Jetpack/nvidia_sdk/JetPack_4.3_Linux_P3448-0020/Linux_for_Tegra/bootloader/cvm.bin

This makes me wondering what happened in your previous setup that the host is able to flash.
Could you take a picture of your board and how you connect your board now?

39

BTW, comment #15 from you is the most important one but it seems being cut so we cannot tell why it didn’t flash successfully either.

40

Just to clarify, I’m using a micro-sd card.

Here is my setup:

IMG_6153
IMG_61533024×4032 3.9 MB
IMG_7609 2
IMG_7609 23024×4032 3.85 MB

41

It looks no problem. Not sure why it failed to start the flash process.

Your board was able to start the flash process yesterday. Did you remember what was the hardware setup at then?

42

Also, just a weird test …
Are you able to start the flash process if you use the command to flash emmc board?