I installed JetPack 5.1 to Xavier NX P3518. I did not remember to ever flash the QSPI. So, I thought it won’t work, but it does work and I can set up the installation, including installing the chromium-browser. However, after a reboot, it won’t start again. Flashing the SD Card to JetPack 4.6.1 does not help and the device still won’t boot. How to fix this?
I use MacBook Pro M2 to flash the SD Card.
Please prepare a x86_64 ubuntu 18.04 host and use sdkmaanger to flash your jetson board.
Is it possible to use NVIDIA SDK Manager from Docker and use it to flash the Jetson device? SDK Manager | NVIDIA Developer
Hello, please refer to this
https://docs.nvidia.com/sdk-manager/docker-containers/index.html
Hi, I have downloaded JetPack 5.1, I plan to try it tonight.
Can I use the downloaded JetPack 5.1 in the sdkmanager?
I got this command from the link you provided but did not see an sdk file. Do I need to download the JetPack 5.1 everytime I call sdkmanager in Docker (The recommended way is to use docker run --it -rm, so I was assuming that sdkmanager is intended for one time use)?
docker run -it --privileged -v /dev/bus/usb:/dev/bus/usb/ -v /dev:/dev -v /media/$USER:/media/nvidia:slave
--name JetPack_NX_Devkit --network host sdkmanager --cli install --logintype devzone --product Jetson --target P3668-0000 --targetos Linux --version 4.4.1 --select 'Jetson OS' --deselect 'Jetson SDK Components' --flash all --license accept --staylogin true --datacollection enable --exitonfinish
sdkmanager is a network layer on top of JetPack. If you run sdkmanager, then you are running JetPack (JetPack is a GUI front end to the actual flash software, which is the driver package).
Originally there was only command line, and this is the “driver package”. Then JetPack was added as a GUI front end, but all downloads were more or less manual. Once sdkmanager was added it more or less automated a lot of download functions, but SDKM and JetPack are more or less integrated these days.
but SDKM and JetPack are more or less integrated these days.
Docker Images :: NVIDIA SDK Manager Documentation
According to the document the docker version is CLI mode only. I am having difficulty to run
$ docker run -it --rm --platform linux/amd64 --privileged -v /dev/bus/usb:/dev/bus/usb/ -v /dev:/dev -v /media/$USER:/media/nvidia sdkmanager --ver
It throws error
docker: Error response from daemon: Mounts denied:
The path /media/jason is not shared from the host and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> Resources -> File Sharing.
See https://docs.docker.com/desktop/mac for more info.
ERRO[0000] error waiting for container: context canceled
I intend to virtualize Ubuntu Server 18.04 ARM64, is it possible to run NVIDIA SDK Manager with this ISO image? or should I try to debug the docker container problem as ARM64 can’t flash jetson devices?
I can’t help with docker :(
Normally only an actual native host is supported. I know there are docker images out there which people have succeeded in using, but I’ve never worked with it. Also, one needs access to loopback mount and not just actual hard drive mount (not sure if that is related to your mount issue or not).
Note that unless your docker emulates amd64 (which is possible), then no flash is possible. There is binary executable content which is not open source, and which has to run on a desktop PC architecture.
I borrowed a friend laptop to flash Jetson Xavier NX P3518 Developer Kit.
It failed to Flash Jetson Linux.
What I’ve tried:
sudo sdkmanager but sdkmanager tell that it do not support sudo mode.One thing that I believe could be the problem is that when I started the SDK Manager. It asked me whether it is a:
However, the product that I bought is a P3518 model.
Hi,
There is a export logs button on sdkmanager. Could you flash it and export the logs here?
P3509+ P3668 is the p3518 devkit, so that is not the problem. Flash failure comes from something else.
Ok, I saw the log. Not quite easy to read in the justpaste.it …
08:22:34.185 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: Using rootfs directory of: /media/godata/Apps/HWImage/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs
08:22:34.191 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: ||||||||||||||||||||||| ERROR |||||||||||||||||||||||
08:22:34.191 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: -----------------------------------------------------
08:22:34.191 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: 1. The root filesystem, provided with this package,
08:22:34.191 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: has to be extracted to this directory:
08:22:34.192 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: /media/godata/Apps/HWImage/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs
08:22:34.192 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: -----------------------------------------------------
08:22:34.192 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: 2. The root filesystem, provided with this package,
08:22:34.192 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: has to be extracted with 'sudo' to this directory:
08:22:34.192 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: /media/godata/Apps/HWImage/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/rootfs
08:22:34.192 - info: NV_L4T_FILE_SYSTEM_AND_OS_COMP@JETSON_XAVIER_NX_TARGETS: -----------------------------------------------------
Please make sure that disk where the “/media/godata/Apps/HWImage/JetPack_5.1_Linux_JETSON_XAVIER_NX_TARGETS” is stored, is formated as ext4. It has nothing to do with whether sdkmanger runs in sudo or not.
Can confirm it works on ext4 formatted partitioned disk.
What I’ve tried:
Note: In recovery mode the Jetson shows up with lsusb. In fully booted mode, if and only if the software services are running correct, then the Jetson also shows up with lsusb (however, it is a different kind of USB device in recovery mode versus fully booted; if flash works, then it is doing what it should; if USB services show up fully booted, then that too is good).
If at any time the content of “Linux_for_Tegra/” is not on ext4 (especially “Linux_for_Tegra/rootfs/”), then even if the flash works, it will not function correctly. If you have installed and have 64 GB free, then you are ok. Check with “df -H -T”.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.