Dear community,
I am looking for help, having lost 2 units trying to install the latest Jetpack.
Full story: We have a fleet of devices running with Xavier AGX, that we setup by flashing an image we made some time ago (Jetpack 4.1). These days, I wanted to catch up with the latest developments, and setup a unit from scratch with jetpack 4.5.1. Hence the installation of the SDK manager, following the procedures, and having a successfull installation announced by the SDK manager (logs attached)
SDKM_logs_JetPack_4.5.1_Linux_for_Jetson_AGX_Xavier_2021-04-13_13-25-07.zip (172.5 KB)
Except the Xavier would not power up at all. I still can activate the recovery mode, and therefore I try to rollback the device and I flash back our old-good-4.1 release. But without success. Unit remains silent.
What would you recommend to do ?
I have already tried the same process with a second unit:
- flash our old image (with the flashing CLI from the SDK manager) → OK
- flash the new Jetpack image (from GUI) → says installation OK, but unit DEAD (2nd logs attached)
- flash the new Jetpack image (from flashing CLI) → DEAD
- try to flash our old image (CLI) → DEAD
Any suggestion highly appreciated,
Emmanuel
SDKM_logs_JetPack_4.5.1_Linux_for_Jetson_AGX_Xavier_2021-04-13_17-10-49.zip (120.8 KB)
What you are sharing are all host side log from sdkmanager.
If the installation is good but the device is not able to boot, then what we should check is the boot up log from device but not the host sdkmanger log.
Also, how did you tell the device is not powered up?
And also, how is the result of something like jetpack 4.2 /4.3/4.4 here?
then what we should check is the boot up log from device but not the host sdkmanger log.
I agree, but I am not sure how to get the logs from the device. How can I access them ?
Also, how did you tell the device is not powered up?
There is nothing displayed on the screen whereas there was the booting and ubuntu screen before the “killing”. Not one log, not even power (the screen displays ‘no signal’)
I posted the method in previous comment.
And also, how is the result of something like jetpack 4.2 /4.3/4.4 here?
Not tried. I just wanted to try the latest, just following the official procedure from scratch. Do you think I should download and try older versions ?
I posted the method in previous comment.
Ah yes, didn’t catch it. I will try tomorrow when back to the office
You can firstly use those xavier devices which are still “alive” to verify your setup to dump log.
Once you are sure those log would be printed out on your host side, move to those dead unit and see what is going on.
BTW, since this module was on jp4.1… I guess it was bought for about 2 years ago? What is the DDR size on your device? 16GB or 32GB?
I guess it was bought for about 2 years ago? What is the DDR size on your device? 16GB or 32GB?
Our first units were bought at this time yes. We kept the image from them until now for all fleet. They are 32GB indeed
1 Like
I will do this. Nice idea
it must be 16GB RAM,but 32GB eMMC unit.
for troubleshooting with usb cable connected to serial port [ mini usb ] picocom could be installed to the Host PC then used:
sudo apt install picocom -y
sudo picocom /dev/ttyUSB3
# or with usb-c connection via the recovery port it might work with /dev/ttyACM0
However it is suggested to remove the sdmanager installation/ folder
then reinstall the sdkmanager trying with headless approach
sdkmanager --cli install --product Jetson --version 4.5.1 --targetos Linux --target P2888-0001 --flash all --additionalsdk DeepStream
it must be 16GB RAM,but 32GB eMMC unit.
Hi Andrey1984,
How do you know about this? Any similar experience before?
yes, 16GBRAM and 32GB hard drive
I did not connect DDR to the RAM…
I feel clumsy since I could not get anywhere with @WayneWWW advices:
I first try with a working unit, started normally with a cable connected to the micro USB. There is no /dev/ttyUSB* at all available on the host:
ls /dev/tty*
/dev/tty /dev/tty18 /dev/tty28 /dev/tty38 /dev/tty48 /dev/tty58 /dev/ttyS0 /dev/ttyS19 /dev/ttyS29
/dev/tty0 /dev/tty19 /dev/tty29 /dev/tty39 /dev/tty49 /dev/tty59 /dev/ttyS1 /dev/ttyS2 /dev/ttyS3
/dev/tty1 /dev/tty2 /dev/tty3 /dev/tty4 /dev/tty5 /dev/tty6 /dev/ttyS10 /dev/ttyS20 /dev/ttyS30
/dev/tty10 /dev/tty20 /dev/tty30 /dev/tty40 /dev/tty50 /dev/tty60 /dev/ttyS11 /dev/ttyS21 /dev/ttyS31
/dev/tty11 /dev/tty21 /dev/tty31 /dev/tty41 /dev/tty51 /dev/tty61 /dev/ttyS12 /dev/ttyS22 /dev/ttyS4
/dev/tty12 /dev/tty22 /dev/tty32 /dev/tty42 /dev/tty52 /dev/tty62 /dev/ttyS13 /dev/ttyS23 /dev/ttyS5
/dev/tty13 /dev/tty23 /dev/tty33 /dev/tty43 /dev/tty53 /dev/tty63 /dev/ttyS14 /dev/ttyS24 /dev/ttyS6
/dev/tty14 /dev/tty24 /dev/tty34 /dev/tty44 /dev/tty54 /dev/tty7 /dev/ttyS15 /dev/ttyS25 /dev/ttyS7
/dev/tty15 /dev/tty25 /dev/tty35 /dev/tty45 /dev/tty55 /dev/tty8 /dev/ttyS16 /dev/ttyS26 /dev/ttyS8
/dev/tty16 /dev/tty26 /dev/tty36 /dev/tty46 /dev/tty56 /dev/tty9 /dev/ttyS17 /dev/ttyS27 /dev/ttyS9
/dev/tty17 /dev/tty27 /dev/tty37 /dev/tty47 /dev/tty57 /dev/ttyprintk /dev/ttyS18 /dev/ttyS28
# For information
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Therefore the pipocom command fails (as expected)
$ sudo picocom /dev/ttyUSB2
picocom v2.2
port is : /dev/ttyUSB2
flowcontrol : none
baudrate is : 9600
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,
FATAL: cannot open /dev/ttyUSB2: No such file or directory
Same If I switch to recovery mode. no /dev/ttyUSB* available on the host, but I can see the Xavier on device 006.
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 0955:7019 NVidia Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried to pipocom on /dev/tty6 (which connected sucessfully: Terminal ready ) but I did not get any output, neither rebooting the unit
I will try the headless approach suggested by Andrey now
Are you using xavier devkit?
No, we are using a Xavier mounted on a device
Then does that carrier board have any UART port?
The “ttyUSB3” comes out from UART port but not any usb port on your device. Thus, you see something from lsusb in reocvery mode. That is good and expected, but not related to what we are doing now.
ah. Ok. I am using the same port I use for flashing purpose. I will have to ask the manufacturer for the UART port.
Let me give an explanation about what those interface are doing so that you will not get confused.
From Andrey1984’s comment:
sudo picocom /dev/ttyUSB3
or with usb-c connection via the recovery port it might work with /dev/ttyACM0
ttyUSB3 → This log will provide full one which include the bootloader and kernel. This is from UART.
ttyACM0 → This log will only print “kernel” log. Thus, if your board fails before entering kernel, this interface won’t provide help. And this is from flashing/recovery port.
1 Like
It works from the host perspective
===== INSTALLATION COMPLETED SUCCESSFULLY. =====
- Drivers for Jetson: Installed
- File System and OS: Installed
- Device Mode Host Setup in Flash: Installed
- Flash Jetson AGX Xavier 16GB/32GB: Installed
===== Installation completed successfully - Total 4 components =====
===== 4 succeeded, 0 failed, 0 up-to-date, 0 skipped =====
but the unit still does not restart.