Jetson Xavier NX BSP Flash Issue

We are trying to flash the Jetson NX customized BSP on our customized Carrier Board using emmc flashing.

Flash process hangs in between. attached the log file please suggestNX_Flash_log.txt (38.8 KB)

  1. Is same module able to get flashed if it is mounted on devkit carrier board?

  2. You can also check the log from UART during flash. It may tell us why it gets stuck.

  1. the module works with devkit carrier board, and I am able to flash it on my setup but my customer is having issue on flashing.

here is the console log:
This is the output from the command line.

[Mar31 11:01] INFO: task tegrarcm_v2:389158 blocked for more than 724 seconds.
[ +0.000007] Tainted: P W OE 5.8.0-45-generic #51~20.04.1-Ubuntu
[ +0.000003] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
[ +0.000003] tegrarcm_v2 D 0 389158 388956 0x20020000
[ +0.000005] Call Trace:
[ +0.000014] __schedule+0x394/0xa60
[ +0.000006] ? __internal_add_timer+0x2d/0x40
[ +0.000023] schedule+0x55/0xc0
[ +0.000004] schedule_timeout+0x8d/0x160
[ +0.000005] ? __next_timer_interrupt+0xe0/0xe0
[ +0.000006] wait_for_completion_timeout+0x8d/0x100
[ +0.000007] usb_start_wait_urb+0x8f/0x180
[ +0.000005] usb_bulk_msg+0xbb/0x170
[ +0.000004] proc_bulk+0x2ba/0x320
[ +0.000006] usbdev_do_ioctl+0x275/0x1010
[ +0.000006] ? handle_mm_fault+0xca/0x200
[ +0.000005] usbdev_ioctl+0xe/0x20
[ +0.000006] compat_ptr_ioctl+0x1d/0x30
[ +0.000004] __ia32_compat_sys_ioctl+0x14e/0x170
[ +0.000007] do_syscall_32_irqs_on+0x4a/0x70
[ +0.000006] do_int80_syscall_32+0x10/0x20
[ +0.000005] entry_INT80_compat+0x88/0x8d
[ +0.000005] RIP: 0023:0x807a504
[ +0.000003] RSP: 002b:00000000ffaccfc8 EFLAGS: 00000283 ORIG_RAX: 0000000000000036
[ +0.000004] RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00000000c0105502
[ +0.000003] RDX: 00000000ffaccff0 RSI: 0000000000000010 RDI: 0000000008369688
[ +0.000002] RBP: 00000000ffacd050 R08: 0000000000000000 R09: 0000000000000000
[ +0.000001] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ +0.000002] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000

  1. What is “your setup” and what is difference between your setup and your customer’s setup?

  2. Where did you get this log?
    I want the log during flash. “During flash” means you try to dump the log when the host is do the flash work.
    If you still not understand what this means, please directly ask instead of coming back later with wrong log.

There is no difference in my setup and customer set up, Similar host machine same BSP, similar carrier board and module, same flashing instruction.
2. Earlier logs flash log (log from host machine during flash) and serial console logs are from customer .Now I am attaching my flash log which run successfully without error.
NX_Flash_log_test.txt (48.0 KB)

I will try to get the log on serial from customer.


Your serial console log from customer looks like a dmesg from your customer’s host… I see ubuntu 20.04 word there.
What I want is the log from UART so please make sure this custom board is able to dump uart log first. If there is no uart pin, then there is no possible to dump such log.

Please note that only 16.04 and 18.04 host are guaranteed working now.

Yes sure. I got it, I had missed to mention it, I will ask for the log

1 Like

You mean to say, there may be issues if we use ubuntu 20.04 as host machine for flash?

Yes, it is also possible. Since same setup and board can work fine on your side, I would suggest customer could also try different host too.

Thanks for help, I will get back to you with more data from customer