TX2 Development Kit not able to flash via sdkmanager

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hello!

I wanted to reinstall my TX2 with the latest version of software.

But i allways get the Error:

The target is in a bad state
The Jetson target is in a bad state and cannot be flashed. Please manually put the target into recovery mode and then retry flashing.

13:35:56 DEBUG: Flash Jetson TX2 - flash: using adapter to install NV_L4T_FLASH_TX2_WITH_OS_IMAGE_COMP@JETSON_TX2_TARGETS to /home/me/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_TX2_TARGETS
13:35:56 INFO: Flash Jetson TX2 - flash: sudo ./nvsdkmanager_flash.sh
13:35:57 INFO: Flash Jetson TX2 - flash: *** Checking ONLINE mode … OK.
13:35:57 INFO: Flash Jetson TX2 - flash: *** Checking target board connection … 1 connections found.
13:36:02 ERROR: Flash Jetson TX2 - flash: Put the target board in RCM mode and retry.
13:36:02 ERROR: Flash Jetson TX2 - flash: command terminated with error

also on the target manually doing:
jetson@jet-03:~$ sudo -s
[sudo] password for jetson:
root@jet-03:~# reboot --force forced-recovery
Rebooting with argument ‘forced-recovery’.
[ 22.062243] reboot: Restarting system with command ‘forced-recovery’

yields:

./nvautoflash.sh --print_boardid
*** Checking ONLINE mode … OK.
*** Checking target board connection … 1 connections found.
*** Reading ECID … *** Error: ECID read failed.
Put the target board in RCM mode and retry.

Does not matter if i do manual recovery mode or let it automatically reboot into recovery mode.

Following JetPack 4.2 Flashing Issues and how to resolve i did:

cold boot the tx2 dev board:
NOTICE: BL31: v1.3(release):5b49e7f80
NOTICE: BL31: Built : 08:54:11, Jul 9 2021
ipc-unittest-main: 1519: Welcome to IPC unittest!!!
ipc-unittest-main: 1531: waiting forever
ipc-unittest-srv: 329: Init unittest services!!!
hwkey-agent: 40: hwkey-agent is running!!
hwkey-agent: 197: key_mgnt_processing …
hwkey-agent: 189: Setting EKB key 0 to slot 14
hwkey-agent: 167: Init hweky-agent services!!
luks-srv: 40: luks-srv is running!!
luks-srv: 157: Init luks-srv IPC services!!
platform_bootstrap_epilog: trusty bootstrap complete
[0001.335] I> Welcome to Cboot
[0001.337] I> Cboot Version: t186-747521d4
[0001.341] I> CPU-BL Params @ 0x275800000
[0001.345] I> 0) Base:0x00000000 Size:0x00000000
[0001.349] I> 1) Base:0x277f00000 Size:0x00100000
[0001.354] I> 2) Base:0x277e00000 Size:0x00100000
[0001.359] I> 3) Base:0x277d00000 Size:0x00100000
[0001.363] I> 4) Base:0x277c00000 Size:0x00100000
[0001.368] I> 5) Base:0x277b00000 Size:0x00100000
[0001.372] I> 6) Base:0x277800000 Size:0x00200000
[0001.377] I> 7) Base:0x277400000 Size:0x00400000
[0001.381] I> 8) Base:0x277a00000 Size:0x00100000
[0001.386] I> 9) Base:0x277300000 Size:0x00100000
[0001.390] I> 10) Base:0x276800000 Size:0x00800000
[0001.395] I> 11) Base:0x30000000 Size:0x00040000
[0001.399] I> 12) Base:0xf0000000 Size:0x00100000
[0001.404] I> 13) Base:0x30040000 Size:0x00001000
[0001.408] I> 14) Base:0x30048000 Size:0x00001000
[0001.412] I> 15) Base:0x30049000 Size:0x00001000
[0001.417] I> 16) Base:0x3004a000 Size:0x00001000…

Interrupted via [hold]rec, [push]reset, wait 2 seconds, [release]rec

the on the host execute:

sudo ./flash.sh jetson-tx2 mmcblk0p1

[sudo] password for me:
###############################################################################

L4T BSP Information:

R32 , REVISION: 7.1

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

$ uname -a ; cat /etc/issue ; dpkg -l sdkmanager
Linux windowspc 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 18.04 LTS \n \l

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
++±=================================-=====================-=====================-========================================================================
ii sdkmanager 1.7.3-9053 amd64 NVIDIA SDK Manager

how can i get this fixed?

thanks for any help.

2

Are you using a VM?

3

no

4

Is this your first time flashing any jetson device?

5

no, i did it last time one year ago.

i also have full access to the device. if that helps.

edit: with serial console & networkaccess

6

I don’t feel this experience might help.

no, i did it last time one year ago.

Also try to use other host machine to flash your board. And those host machines cannot be VM.

If you have other TX2 boards, then try to flash them too.

Check if lsusb gives out jetson device after your attempt to put it into recovery mode.

7

The Vm thing i got! Its everywhere. Thanks. I dont use VM. i swear!

heres my cpu info:

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core™ i5-3320M CPU @ 2.60GHz
stepping : 9
microcode : 0x21
cpu MHz : 1200.000
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds
bogomips : 5187.94
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

…and so on :)

ok, so i should setup up another ancient ubuntu machine to get this
crappy setuptool going. ok. then ill have to do it.

why should it be a problem with my host computer?
is there known chipset or cpu combinations that dont work?

seems like i waste of time

8

Hi,

I didn’t mean there must be an issue on your host.
You can firstly try to check the lsusb on your host after you put jetson into recovery mode. And see if it can detect it.

Please be aware you can also dump uart log, then you put the board into RCM, the uart log shall stop printed if it is in RCM.

9

yes it does stop printing.

not a very good choice btw. doing nothing to show you something :)

10

And is your host side able to see it in lsusb?

11

Bus 003 Device 019: ID 0955:7c18 NVIDIA Corp. T186 [TX2 Tegra Parker] recovery mode

12

Have you tried the version that was working before? I mean flash the same jetpack version as you did last year.

13

kind of the reason why i want to reflash it is that i dont know what i did to this device anymore. so i want to put it into a known state again.
how do i see what version is on the device?
also i overwrote the host disk. cause who needs ubuntu 18 :) these days

besides…nvidia :)

14

If your board is still able to boot up, then below node shall tell you the version that was in use.

cat /etc/nv_tegra_release | head

15

R32 (release), REVISION: 5.2, GCID: 27767740, BOARD: t186ref, EABI: aarch64, DATE: Fri Jul 9 16:05:07 UTC 2021

16

Ok, could you try to use jetpack32.5.2 or 32.5.1 from sdkmaanger and see if it can flash your board?

17

hmh, no, how? the list of jetpacks does not include such versions.

4.6.1, 4.6, 4.5.1 (which i all tried !!! none worked)
4.5
3.3.4

18

Oh. Sorry. I mean l4t 32.5.2/32.5.1 which is mapping to jetpack4.5 and jp4.5.1.

If you tried them all and none of them work, then I can only suggest you try different some other micro usb cables or ubuntu host.

19

woudnt there be any errors visible on the operating system layer if i had bad usb cable problems??? disconnects, retransmits, … like its allways the case…when there usb problems…

im feeling a bit "have you tried to reboot your computer"ish

20

well, ill be back when the setup of the 18.04 ubuntu host is done.