TX2 SDK Manager 1.4.0 Error

Good afternoon everyone,

I just got a new TX2 in and am trying to flash it via the recommended SDK Manager method. In the past I have flashed countless TX1’s using the ./flash.sh -r method using a custom system.img file, but from what I have read that is not the recommended way now. First, is that true?

When I use the SDK Manager I get the following errors:

15:48:15 INFO: Drivers for Jetson: 404 Not Found [IP: 80]

15:48:17 INFO: Drivers for Jetson: Reading package lists…

15:48:17 INFO: Drivers for Jetson: E: The repository ‘http://ppa.launchpad.net/jderose/couchdb-1.7.0/ubuntu bionic Release’ does not have a Release file.

I have searched the googles and these forms but have not had any luck in the past three days.

Is this something I can skip? I know I do not need couchdb.

Any help would be greatly appropriated,!

So far as I know the “sudo ./flash -r jetson-tx2 mmcblk0p1” command is the normal way of reusing an image. The part which probably won’t work is if you use flash software with a release version different than the version which created the original image.

Don’t know about the network issue, but that is the Ubuntu repository (not one of NVIDIA’s servers).

I have done a bit of research on the Ubuntu repository and it is no longer active. Is their a way to modify the SDKManager software to not use it? Is their a config file somewhere I could modify? I was expecting it to be an easy 3 clicks to flash but it is not seeming to be that painless.

Are you using the most recent SDKM? I don’t know of a way to tell it to change its repository addresses, especially for the Ubuntu servers which are not controlled by NVIDIA. However, there have been changes of older versus newer SDKM releases which might matter.

I downloaded sdkmanager_1.4.0-7363_amd64.deb, which I believe is the latest version. Is this the correct link to grab it from? [https://developer.nvidia.com/nvidia-sdk-manager]

I am just trying to flash a base image and I read that was the best method to do so. Is their an alternative way for me to get L4T on the TX2?

Yes, I show sdkmanager_1.4.0-7363_amd64.deb as the most recent.

If you reinstall this to make sure there is nothing related to bad download issues, then you might start by deleting your “~/.nvsdkm/” directory, and perhaps also your “~/nvidia/nvidia_sdk/” content just to be certain (and then run sdkmanager again to start with fresh content).

I do want to emphasize that any release can clone a Jetson, but only the same matching release of L4T can be used to flash a reused rootfs image. JetPack/SDKM is only a front end, and the “Linux_for_Tegra/” directory is downloaded and installed as a convenience. The actual package producing “Linux_for_Tegra/” is the “driver package”. You can manually download and unpack this package. If you were to do this manually, and wanted to flash normally with a default image, then you’d also have to populate the “Linux_for_Tegra/rootfs/” directory with the sample rootfs.

The URL for listing the various L4T releases is here:
(check your “head -n 1 /etc/nv_tegra_release” to know any Jetson’s current L4T release)

What release is your reused image from?

Hi jake.streett,

As mentioned by linuxdev, this looks like a local issue with APT repository at your machine.
You can try removing the repository that causes you issues with the following approach –
List the current repositories, apt policy

Find the name of the repository and remove it, should be something like -
sudo add-apt-repository --remove ppa:jderose/couchdb.

To be clear neither SDK Manager or JetPack are using it, but it blocking using other APT commands.

Thank you, that seemed to do the trick. I feel bad that the issue was not related to the TX2 but rather my local machine.

Thank you everyone that has helped. Now onto the next issue at hand!