I cannot flash Jetson device with SDK Manager

sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 2.1

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

lsusb
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 118: ID 0955:7c18 NVidia Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Does this happen to only one TX2 module or many of them?

Thank you. The problem has been solved.

May I ask how did you resolve it?

I can plug the micro-b USB cable directly into the motherboard. Before that, I connected the micro-b USB cable to the USB port in the front of the chassis. The connection cable between the USB interface on the front of the chassis and the motherboard may be the cause of the problem

Now I have a new problem.

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

L4T BSP Information:

R32 (release), REVISION: 1.0, GCID: 14531094, BOARD: t186ref, EABI: aarch64,

DATE: Wed Mar 13 07:41:08 UTC 2019

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

Target Board Information:

Name: jetson-tx2, Board Family: t186ref, SoC: Tegra 186,

OpMode: production, Boot Authentication: NS,

###############################################################################
./tegraflash.py --chip 0x18 --applet “/home/yuan/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3310/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin” --skipuid --cmd “dump eeprom boardinfo cvm.bin”
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.0060 ] Generating RCM messages
[ 0.0100 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 0 --download rcm /home/yuan/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3310/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin 0 0
[ 0.0114 ] RCM 0 is saved as rcm_0.rcm
[ 0.0168 ] RCM 1 is saved as rcm_1.rcm
[ 0.0173 ] List of rcm files are saved in rcm_list.xml
[ 0.0323 ]
[ 0.0323 ] Signing RCM messages
[ 0.0333 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0353 ] Assuming zero filled SBK key
[ 0.0590 ]
[ 0.0592 ] Copying signature to RCM mesages
[ 0.0612 ] tegrarcm_v2 --chip 0x18 0 --updatesig rcm_list_signed.xml
[ 0.0753 ]
[ 0.0754 ] Boot Rom communication
[ 0.0808 ] tegrarcm_v2 --chip 0x18 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0875 ] RCM version 0X180001
[ 0.1666 ] Boot Rom communication completed
[ 1.3077 ]
[ 2.3126 ] tegrarcm_v2 --isapplet
[ 2.3158 ] Applet version 01.00.0000
[ 2.4350 ]
[ 2.4361 ] Retrieving EEPROM data
[ 2.4361 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/yuan/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3310/Linux_for_Tegra/bootloader/cvm.bin
[ 2.4370 ] Applet version 01.00.0000
[ 2.5524 ] 000000000098006: I
[ 2.6088 ]
[ 2.6199 ] tegradevflash_v2 --oem platformdetails eeprom cvm /home/yuan/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3310/Linux_for_Tegra/bootloader/cvm.bin
[ 2.6209 ] CPU Bootloader is not running on device.
[ 2.7430 ]
Error: Return value 4
Command tegradevflash_v2 --oem platformdetails eeprom cvm /home/yuan/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3310/Linux_for_Tegra/bootloader/cvm.bin
Reading board information failed.

What is the[s] meaning of “error: return value 4”?

We still need more information about this error. The return value mostly not help in debugging such issue.

  1. Does this issue happen to all your tx2 modules or only one of them?

  2. Are you using a fresh out-of-box TX2?
    If yes, why do you use “-r,-k” in flash script?
    If no, does it ever get flashed before

  3. Is this on devkit?

  4. Are you able to get UART log from device during flash?

  1. This problem only occurs on one TX2 module.
  2. This TX2 module has used the network cable to flash device.
  3. I’m not using devkit.
  4. How do I get the UART log from the device during flash?

I built a customized tegra186-quill-p3310-1000-c03-00-base.dtb and was trying to flash that into TX2 ,But my Ubuntu18.04 host and Ubuntu16.04 vm both failed and showed the same error.

I have tried fresh installs of the JetPack software and attempted multiple times though command line. The error that keeps appearing is: CPU bootloader not running on device.

I have been using all the cables that came with the development kit.Using lsusb command the device is found .

  1. This TX2 module has used the network cable to flash device.

We don’t support to flash through network cable but only usb otg cable so I don’t get your point here.

I built a customized tegra186-quill-p3310-1000-c03-00-base.dtb and was trying to flash that into TX2 ,But my Ubuntu18.04 host and Ubuntu16.04 vm both failed and showed the same error.

Please also try full flash. Though I think it may not work.

  1. How do I get the UART log from the device during flash?
    Find a devkit and try to dump uart log.
    https://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/
    If your host is able to flash other tx2 modules, then it means this problematic one may have hardware issue or maybe wrong eeprom value. Is this TX2 still able to boot up?

Thank you, I solved this problem by using SDKmanager to upgrade NVIDIA jetson tx2 to 18.04.
I suspect the problem may be caused by the host’s system version being different from the tx2 version.