Mismatch in jetpack version

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

Hi, I flashed my jetson tx2i using jetpack 4.6.5 and my custom OS image. But after the jetson is flashed, I am getting the jetpack version as 4.4.1. Am I missing something while flashing?

2

One of the reason for such case is the boot device is not same as what you flashed.

Do you have any USB/NVMe SSD/ sdcard connected on the board?

3

I connected the jetson to my system (ubuntu-18.04) using micro USB and flashed it. Is it because of my OS Image?

I am flashing the jetson using docker. I installed Jetpack-4.6.5 and orbitty package inside my docker itself

4

Hi,

What you told are all not mattering here.

If you are sure your flash with jetpack4.6.5 is correct, then I only want to check the status of your board.

Please share serial console log for the boot process.

5

This is what I am getting after running

sudo picocom -b 115200 /dev/ttyACM0 

picocom v2.2

port is        : /dev/ttyACM0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,

I tried minicom and screen command but none of them are printing any logs. Any alternative would be really helpful or how do you check serial console log for the boot process?

Thanks

6

If you are sure your board can “boot” into Linux/Ubuntu, then it is definitely your method to dump the serial console log is wrong.

I don’t know what board you are using. This is the method to dump UART log from NV devkit.

If your board is not like this kind, check with your board vendor for help.