SDK Manager incorrectly detects Xavier AGX

I have an Xavier AGX that I have been using for a while. Now that things are settled down and our software is relatively set for the moment, I would like to make a document that shows every step for installing our software so that what we have can be replicated in the future. I have personally done this in the past but am hitting a roadblock right at the beginning this time. Step 1 is to overwrite everything with the SDK manager so that I can start with a fresh system. When I hook up our Xavier AGX, the SDK manager pops up a window saying “SDK Manager detected device connected. Please select the target Hardware” It then gives me a choice between the NX and the NX dev kit version. I have tried manually selecting the AGX after canceling out of that screen but the install fails. I am installing jetpack 4.4 since that is what we used last time. The system that I am installing from is an Ubuntu 18.04 system. I have tried installing with one of the two NX modules selected but that failed. I have tried different USB ports on my laptop. I have tried different USB cables going to the Xavier module. Once, it seemed to have detected the system as an AGX and it went through the install fully and it said that it had finished successfully but after a reboot,I found that it still had everything that I previously had installed onto the system.

The Xavier module is connected to the dev kit carrier board, which has a camera carrier board attached to it. We have a SSD attached to it as well. Besides that, there is nothing else connected. What am I missing?

Hi vendors3,

Can you package the folder ~/.nvsdkm and send us to analyze?

Here is the directory.

nvsdkmDirectory.zip (805.7 KB)

Hi vendors3,

We checked the log. And found that SDKM detected the board as NX board correctly. You thought it was an Jetson AGX Xavier board, however, it is not. It is indeed Jetson Xaiver NX or Jetson Xaiver NX devkit board.

The reason is that when in recovery mode, lsusb output of the boards are different:
Jetson AGX Xaiver board contains 0955:7019
Jetson Xavier NX or Jetson Xaiver NX devkit board contains 0955:7e19
In the log, it shows 0955:7e19.

Would you please help to confirm which board you used?

I also suggest you can check the file you’ve shared.

You shared all the sdkmanager flash log to us. Not only includes current case but also what you’ve done to previous board. For example, I can see you flashed jetpack4.2.3, 4.4.1 last year and 4.4 on 5/18, 4.5.1 on 5/15.

Please just give us the log that is doing current flash work. Also, as Kay’s comment here, I didn’t see you flash the Xavier. But only NX.


I have uploaded an image of my “NX” It can be found directly under the AGX dev board that we are using since we haven’t developed our own carrier board yet. I would hope that it is now clear that despite the log telling you that I have a NX module, what I actually have is an AGX. We have never purchased a NX module so if the logs all say that we have been programming NX modules then it has been incorrect all along.

The difference between now and previously is that in the past I had always been programming virgin systems but now I am trying to wipe an existing system so that full setup of our software can be documented step by step.

My question still remains. How do I program my AGX when SDK Manager is identifying it as an NX module?

You can directly use the flash.sh inside Linux_for_Tegra and use the board name of AGX instead of NX.
So that it will try to flash this board.

I just tried using flash.sh to load things into the Xavier module. It didn’t work. Below is the command that I used:

sudo ./flash.sh -r jetson-xavier-maxn mmcblk0p1

This outputs:
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 4.3
###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.

Thinking that maybe I hadn’t put it into recovery mode properly, I ran lsusb but that seems to indicate that the board is indeed in recovery mode:

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b221 Chicony Electronics Co., Ltd integrated camera
Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
Bus 001 Device 027: ID 0955:7020 NVidia Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

What should I try now?

please check this session, To determine whether the developer kit is in Force Recovery mode.
0955:7020 is not type of Jetson module.
the picture you take it does looks like bottom of Jetson AGX Xavier, that should be a camera adapter board, and there’re other stuffs connected.

could you please try again to simply the board by removing all peripherals.
thanks

I just removed everything from the xavier board but am still getting the same result with SDK manager.

With lsusb I am seeing the device as 0955:7020 when in recovery mode and 0955:7e19 when booted normally.

I also tried per Wayne’s suggestion using
sudo ./flash.sh -r AGX mmcblk0p1
but it rejected AGX as a board type.

I then tried all three types of board types for Xaviers as indicated in this document:
https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3242/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide%2Fquick_start.html%23wwpID0EAAO0YB0HA

eg:
sudo ./flash.sh -r jetson-xavier mmcblk0p1
sudo ./flash.sh -r jetson-xavier-maxn mmcblk0p1
sudo ./flash.sh -r jetson-xavier-slvs-ec mmcblk0p1

What now?

As a side question, since my Xavier is identifying with a different signature, would it be an easy thing to either
A: Change this signature back to the factory default
or
B: Change flash.sh to accept the signature that it is giving me?

One further comment, I see that a little farther down on the page that I referenced previously that my system is identifying correctly as what it is (the 8GB version) when it boots normally. I tried doing an automatic install from a regular boot but that fails as well. Presumably this is because once it has shifted into recovery mode it no-longer has the correct signature.

Just to clarify, what is the exact board we are using now? Xavier 32GB or 8GB?

The board config that flash.sh is using is actually just some .conf file under Linux_For_Tegra. Thus, your attempt for “AGX” will not work because there is no “AGX.conf” existing there.

If your board is a xavier 8GB board, then I remember you should use some board name with 8gb suffix.

That did the trick! For anyone else following this thread, I used the following command:
sudo ./flash.sh -r jetson-xavier-8gb mmcblk0p1

After the script said it was done, I hooked up a monitor to the Xavier and it appeared to have rebooted an was waiting from something from the PC with no time limit. Since flash.sh had finished, I decided to reset the Xavier to see what would happen. It rebooted into the normal initial setup screen that I am used to.

Thanks to all for your help!