Stuck at "tegrarcm_v2 --isapplet"

Autonomous Machines Jetson & Embedded Systems Jetson TX2
,
#1

Hi,
i’m working on a system that use 6 jetson tx2i with a custom carrier board. One of this cannot boot properly due to damaged files in /usr. So i try to back up from a working system using the tx2 cloning tutorial on elinux.org . Any times that i try to backit up the flash freeze at “tegrarcm_v2 --isapplet”.
I try to install new L4T on the jetson tx2i system that won’t boot and it work but the usb or network aren’t working. So i’m trying again to backup a good tx2i but i get stuck at same poi “tegrarcm_v2 --isapplet”.

Any suggestion?

thanks

#2

So there are two issues

  1. After flash, usb and network does not work

  2. None of your board is able to clone out the APP partition

Are above correct?

For (1), please dump the dmesg.

For (2), please share the command you are using for cloning.

#3

Hi,
I’m trying to clone again the nvidia tx2i that is working using this command:

sudo ./flash.sh -r -k APP -G backup.img jetson-tx2i mmcblk0p1

but i get stuck again at:

…
[ 7.0109 ] tegrahost_v2 --chip 0x18 --generateblob blob.xml blob.bin
[ 7.0121 ] number of images in blob are 9
[ 7.0134 ] blobsize is 4087784
[ 7.0140 ] Added binary blob_nvtboot_recovery_cpu_sigheader.bin.encrypt of size 225152
[ 7.0172 ] Added binary blob_nvtboot_recovery_sigheader.bin.encrypt of size 122272
[ 7.0192 ] Added binary blob_preboot_d15_prod_cr_sigheader.bin.encrypt of size 58384
[ 7.0215 ] Added binary blob_mce_mts_d15_prod_cr_sigheader.bin.encrypt of size 2298464
[ 7.0215 ] Added binary blob_bpmp_sigheader.bin.encrypt of size 534816
[ 7.0216 ] Added binary blob_tegra186-a02-bpmp-storm-p3489-a00-00-ta795sa-ucm1_sigheader.dtb.encrypt of size 76160
[ 7.0216 ] Added binary blob_tos-trusty_sigheader.img.encrypt of size 403264
[ 7.0217 ] Added binary blob_eks_sigheader.img.encrypt of size 1440
[ 7.0217 ] Added binary blob_tegra186-quill-p3489-1000-a00-00-ucm1_sigheader.dtb.encrypt of size 367680
[ 7.0218 ]
[ 7.0219 ] Sending bootloader and pre-requisite binaries
[ 7.0246 ] tegrarcm_v2 --download blob blob.bin
[ 7.0261 ] Applet version 01.00.0000
[ 7.0483 ] Sending blob
[ 7.0488 ] […] 100%
[ 16.8942 ]
[ 16.8979 ] tegrarcm_v2 --boot recovery
[ 16.8993 ] Applet version 01.00.0000
[ 16.9243 ]
[ 17.9291 ] tegrarcm_v2 --isapplet

if i run dmesg i get this output:

[ 6883.255174] usb 3-2: new high-speed USB device number 33 using xhci_hcd
[ 6883.406218] usb 3-2: New USB device found, idVendor=0955, idProduct=7018, bcdDevice= 0.00
[ 6883.406221] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6883.406222] usb 3-2: Product: APX
[ 6883.406223] usb 3-2: Manufacturer: NVIDIA Corp.
[ 6883.406223] usb 3-2: SerialNumber: 00000
[ 7130.133370] INFO: task tegrarcm_v2:55502 blocked for more than 120 seconds.
[ 7130.133376] Not tainted 5.4.0-100-generic #113~18.04.1-Ubuntu
[ 7130.133378] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
[ 7130.133380] tegrarcm_v2 D 0 55502 55324 0x20020000
[ 7130.133384] Call Trace:
[ 7130.137735] __schedule+0x292/0x720
[ 7130.137935] schedule+0x33/0xa0
[ 7130.137970] schedule_timeout+0x15d/0x320
[ 7130.138908] ? __next_timer_interrupt+0xe0/0xe0
[ 7130.138917] wait_for_completion_timeout+0xb3/0x140
[ 7130.139003] ? wake_up_q+0x80/0x80
[ 7130.139668] usb_start_wait_urb+0xe3/0x180
[ 7130.139674] usb_bulk_msg+0xb8/0x160
[ 7130.139697] proc_bulk+0x257/0x3a0
[ 7130.139704] usbdev_do_ioctl+0x93d/0x1490
[ 7130.140356] ? handle_mm_fault+0xcb/0x210
[ 7130.140449] usbdev_compat_ioctl+0x10/0x20
[ 7130.140541] __ia32_compat_sys_ioctl+0x105/0x230
[ 7130.140592] do_int80_syscall_32+0x5b/0x130
[ 7130.140596] entry_INT80_compat+0x85/0x90
[ 7130.140598] RIP: 0023:0x807a744
[ 7130.140603] Code: Bad RIP value.
[ 7130.140604] RSP: 002b:00000000ffd97a58 EFLAGS: 00000283 ORIG_RAX: 0000000000000036
[ 7130.140606] RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00000000c0105502
[ 7130.140607] RDX: 00000000ffd97a80 RSI: 0000000000000010 RDI: 0000000008eaf688
[ 7130.140608] RBP: 00000000ffd97ae0 R08: 0000000000000000 R09: 0000000000000000
[ 7130.140608] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 7130.140609] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000

For the other board, the one where i flashed with last jetpack 4.6 and that the usb isn’t working, i do the following:
1 - power it in recovery mode
2 - connect it to ubuntu 18
and this is the dmesg and lsusb output:

[ 7593.079670] usb 3-2: New USB device found, idVendor=0955, idProduct=7018, bcdDevice= 0.00
[ 7593.079674] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7593.079676] usb 3-2: Product: APX
[ 7593.079678] usb 3-2: Manufacturer: NVIDIA Corp.

Bus 003 Device 037: ID 0955:7018 NVidia Corp.

I try to replace the dtb Linux_for_Tegra/kernel/dtb/tegra186-quill-p3489-1000-a00-00-ucm1.dtb with the downloaded file File:Tegra186-tx2-usb-base.tar.gz - eLinux.org as suggested in the elinux tutorial Jetson/TX2 USB - eLinux.org and flash it using the command:

sudo ./flash.sh -r -k kernel/dtb/tegra186-quill-p3489-1000-a00-00-ucm1.dtb jetson-tx2i mmcblk0p1

but after flashing it won’t boot…

What i’m doing wrong?

Thanks for reply

#4

I mean jetson’s dmesg. Not your host dmesg.

#5

I’m sorry but how can i do dmesg on the jetson if usb and network aren’t working?
From the screen using the HDMI i can see

ina3221 reset failure status
and a timeout “(1 of 2) A start job is running for configure usb flashing port for device mode (42s / no limits)”

#6

Please use the uart to communicate with the board.

#7

there isn’t tx rx on this custom carrier board. I think i will buy a carrier board to do that… then i will post dmesg here.

thanks

#8

I think there is something wrong in your concept.

If this is custom board, in most of time, you cannot just randomly download a dtb from the Internet and flash it to your board.

Custom board usually need customized dtb from the board vendor. And it needs the hardware detail from the board vendor.

Thus, you cannot just download a dtb from elinux page to your board. Especially when that page hasn’t updated for 5 years. Those dtb are probably some early release version (rel-28). If you are using rel-32 based jetpack, then it won’t work for sure.

#9

I understand. Ok i will try to contact the board vendor.

Thank you

#10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.