TX2: Error in burning OS image with sdk manager

Hello,

I’m trying to burn 4.2.1 to the module using sdk manager.
I got the following errors:

23:09:05 ERROR : Drivers for Jetson TX2 & TX2i : E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.88.31 80]

23:09:05 ERROR : Drivers for Jetson TX2 & TX2i : E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-backports/main/binary-arm64/Packages 404 Not Found [IP: 91.189.88.31 80]

23:09:05 ERROR : Drivers for Jetson TX2 & TX2i : NV_L4T_DRIVERS_TX2_COMP command /tmp/tmp_NV_L4T_DRIVERS_TX2_COMP.sh finished with error

23:09:05 ERROR : Drivers for Jetson TX2 & TX2i : command terminated with error

23:09:05 ERROR : install ‘Drivers for Jetson TX2 & TX2i’ failure, command < cd ‘/home/zvivered/nvidia/nvidia_sdk/JetPack_4.2.1_Linux_GA_P3310’ ; ‘/opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter’ -a=‘install’ -c=‘eyJpZCI6Ik5WX0w0VF9EUklWRVJTX1RYMl9DT01QIiwibmFtZSI6IkRyaXZlcnMgZm9yIEpldHNvbiBUWDIgJiBUWDJpIiwiZGVz

/logs/JetPack_4.2.1_Linux_GA’ -p=‘16112’ -t=‘P3310’ -e=’/home/zvivered/Downloads/nvidia/sdkm_downloads/Jetson_Linux_R32.2.0_aarch64.tbz2’ > terminated with error

23:09:05 ERROR : Unavailable components detected, please check log

23:09:05 ERROR : File System and OS Skipped. Due to its dependencies fail to install: Drivers for Jetson TX2 & TX2i,

23:09:06 ERROR : Flash skipped due to component(s) download/install failure

23:09:06 ERROR : Flash skipped due to component(s) download/install failure

Before running this from SDK manager I set the TX2 in recovery mode.

Is there an option to burn 4.2.1 with flash.sh ?

Thank you,
Zvika

Hi veredz72,

Are you following the installation guide?
https://docs.nvidia.com/sdk-manager/install-with-sdkm-jetson/index.html

Just a comment on this particular error:

23:09:05 ERROR : Drivers for Jetson TX2 & TX2i : E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/binary-arm64/Packages 404 Not Found [IP: 91.189.88.31 80]

In some cases people cannot find a server. This is not one of those cases. Instead, this is a failure to find a particular file or directory on a server which is otherwise valid. I took a look at this, and there is no “binary-arm64” provided on this particular official Ubuntu server. You will find this much of the file path on the server does exist:
http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/

Most configurations of “apt” specify more than one server, e.g., a main server for initial packages, an updates server for future updates, another server for third parties not part of the official Ubuntu system, and yet another for packages which might have some sort of intellectual property issue…something sometimes free but also not one of the GPL family of licenses. Within each of these servers there are directories for different architectures (and “noarch” is an architecture of no architecture dependence). This particular server never added arm64.

If you don’t need anything from that particular server, then the log message is just for information. Perhaps none of those packages are needed. On the other hand, if you do have a package being installed and “apt” thinks there is a dependency, and if the dependency is not found on any server, then there is a problem.

There are not enough log lines included to know what part is missing and mandatory. We can only see there is an error that “something” is missing. If you have a complete log, and give the file a “.txt” suffix, then you can attach this to the forum thread. If you hover your mouse over the quote icon in the upper right of one of your existing posts, then you’ll see other icons show up. The “paper clip” icon is for attaching files. Or, you can click on “code block” (looks like “</>”), and then paste between the code block tags.

Hi linuxdev,

Thank you very much for the detailed answer.
How can I upload here zip with all log files ?

Till the sdk manager will burn OS, I have to burn with the old way (flash.sh)
In the link:

What download contains flash.sh ?

BTY: The download + install of the host tools works great with the sdk manager.

Thank you,
Zvika

I don’t know what package formats are allowed on forum file uploads, but “.txt” works. You might need to attach each one individually. Probably tar or zip works, but I haven’t tried.

It used to be you could download driver package and sample rootfs separately, but for some releases this is not separately available (I think you are in luck though for R32.2). You can use JetPack/SDK Manager to do this. Tell JetPack you want to flash, but don’t actually flash…then flash.sh will exist. I don’t know if the tar archive of the sample rootfs is downloaded and saved other than being unpacked into the “rootfs/” directory, but if your SD card is mounted on that rootfs directory, then unpack will go directly into that partition.

Currently the R32.2 downloads (JetPack4.2.1) is here:
https://developer.nvidia.com/embedded/linux-tegra

The “L4T Driver Package (BSP)” creates the “Linux_for_Tegra/” directory when unpacked (unpack without sudo). The “Sample Root Filesystem” should be unpacked into “rootfs/” (or the SD card) using sudo. Then the “apply_binaries.sh” script should be run sudo (use the “-r /some/where/else/rootfs/” if not using the default location of “Linux_for_Tegra/rootfs/”). You will still need to add the “/boot” content, which can be copied from a running system, or would be added if you mount the SD partition on “rootfs/” prior to a flash.

This does not necessarily do what you want in all cases, but it is a start and doesn’t require dd or clone. You may need to do things like edit “boot/extlinux/extlinux.conf” or the “chosen” entry of the device tree (I haven’t built an SD card image in a long time so I can’t tell you what issues you will run into on newer releases).