Sdkmanager failues on ubuntu 18.04 for Jetson Nano (cannot create symlink)


During installation of jetpack 4.4 running on Ubuntu vm I am getting the following errors. (Jetson Nano not connect at this time)


2020-05-13 09:30:23.632 - info: Found file /media/sf_Download/NVIDIA/Jetson/Jetpack_4.4/cuda-repo-l4t-10-2-local-10.2.89_1.0-1_arm64.deb with correct checksum, skip downloading.
2020-05-13 09:30:26.213 - info: Reading package lists…
2020-05-13 09:30:26.281 - info: *begin sudo apt-get install -y pigz lbzip2, 5
2020-05-13 09:30:26.488 - info: Reading package lists…
2020-05-13 09:30:27.041 - info: Building dependency tree…
2020-05-13 09:30:27.045 - info: Reading state information…
2020-05-13 09:30:27.577 - info: lbzip2 is already the newest version (2.5-2).
2020-05-13 09:30:27.578 - info: pigz is already the newest version (2.4-1).
2020-05-13 09:30:27.578 - info: 0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.
2020-05-13 09:30:27.701 - error: tar: Linux_for_Tegra/jetson-xavier-as-xavier-nx.conf: Cannot create symlink to ‘p2822+p2888-0001-as-p3668-0001.conf’
2020-05-13 09:30:27.710 - error: : Operation not permitted
2020-05-13 09:30:27.720 - error: tar: Linux_for_Tegra/jetson-xavier-nx-devkit.conf: Cannot create symlink to ‘p3509-0000+p3668-0000-qspi-sd.conf’: Operation not permitted
2020-05-13 09:30:27.909 - error: tar: Linux_for_Tegra/p3449-0000+p3668-0000-qspi-sd.conf: Cannot create symlink to ‘p3509-0000+p3668-0000-qspi-sd.conf’: Operation not permitted
2020-05-13 09:30:29.022 - info: cd473861fdbcf4b560abfabe6cebfd92 /media/sf_Download/NVIDIA/Jetson/Jetpack_4.4/Tegra_Linux_Sample-Root-Filesystem_R32.4.2_aarch64.tbz2

Eventually I upgraded my Jetpack 4.4 to JetPack 4.4 manually:

2. Upgrading JetPack

[L4T - To upgrade to a new point release]

jetson-stats 2.1.0

But…the problem with sdkmanager is still there !

Your working directory /media/sf_Download/ suggests you are using a mounted shared drive. Make sure this isn’t NTFS or some other format that doesn’t support symlinks.


Yes, I determined this already. I was using a VirtualBox Ubuntu 180.04 LTS VM that did not have enough local disc space so I used a folder shared with the Windows 10 host.

Windows 10 host, does not support symbolic links.

Thus, I added another *.vhd virtual disk to the Ubuntu VM and that solved the issue for now.

(Atttached is an image where I am now. So far making progress).

Some comments:

  1. The gui version of sdkmanager does not show Nano options. Only Xavier. So I am using the CLI mode. Arrived at installation point, not yet done but it appears to be making progress. Can you advise how to cause the sdkmanager to show nano?

  2. I am using the USB-TTL cable at 112500bps. It is very slow. Is it possible to use the USB connection instead? when the USB cable is plugged, I see the device as a disk with some files.

  3. Although it is installing now, I could never enter Forced Recovery Mode. I mean I performed the procedure but it did not appear to be starting with any OS or any prompt on the serial port not anything appearing on the USB connection nothing appears on the HDMI screen.

  4. Please note the CLI command I used bellow with –flash skip as I simple want to update my DP4.4 that had some missing parts. When it finished the local install in the host folder it asked me whether to continue with the device install and I answered “yes” (chose option 1).

  5. Documentation is between horrendous and horrible. Everything has to be guessed.

  6. –logs gives and error so I found the logs in ~/.nvsdkm

  7. names of Product and Software - undocumented. I used --query to get a list and it was found there.

  8. my password starts with “-” (minus) which caused your command line parser to think it is a list of unsupported options :). Nothing helped. Not double quotes, not single quotes. So I am manually typing it in every time.

  9. Using a VM is challenging as in case the board need to reboot, virtual USB devices may disconnect. In VirtualBox, it is possible to define a USB filer that automatically reconnects USB devices as soon as they re-appear on the host. See below.

  10. You disk space estimator is faulty. I gave an initial space of 40GB. It said there is not enough space. I increased to 60GB and it was ok. Eventually, it used only …12GB.

  11. What is is the –host option? what is expected to be install on the Ubuntu host? Not explained anywhere.




Made it to the final line. Now need to check it.