SDK Manager: No SDKs are available for your account

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

I upgraded SDK Manager from 1.8.4 to 1.9.1. After installation, the SDK Manager displays: “OOPS No SDKs are available for your account”

After this, I tried rebooting. No change. I purged sdk manager, manually deleting the /opt/nvidia/ and ~.nvsdkm folders. Manual install of 1.91 did not work, nor did 1.9.0. So I reinstalled 1.8.4, which worked as expected.

After installing 1.8.4, I upgraded to 1.9.1 again. Same OOPS message. I rebooted the machine.

After rebooting, the SDK Manager appeared to work correctly. I terminated the program, and started it again. After startup, the SDK Manager displays: “OOPS No SDKs are available for your account”

Looking through the log, it appears that the computed file paths are incorrect. For example:

17:17:07.380 - info: Loading hw data from server... https:/developer.download.nvidia.com/sdkmanager/hw-config/sdkmhw2_Jetson.json

I would expect https:// as a prefix. I at first thought this was an error in the logging mechanism, now I’m not sure.

This is on a native Ubuntu 18.04 machine.
Downgrading back to SDK Manager 1.8.4 works as expected, without access to newer releases of Jetson Linux of course.

I’ve attached a log from a failed run.
Suggestions as to what might be wrong?

sdkm-2023-02-14-17-16-19.log (45.7 KB)

3

Hi Kangalow,

Do you run SDKM with sudo?
You could try to remove ~/.nvsdkm and restart SDKM again w/o sudo.

1 Like
4

@KevinFFF I did not run sdkmanager with sudo.
I removed ~/.nvsdkm and tried again. Result: “OOPS! No SDKs are available for your account”
I then removed ~/.nvsdkm , rebooted and tried again. Result: “OOPS! No SDKs are available for your account”

The new logs are similar to the attached, the server files all start with http:/ instead of https://
Is there some missing locale information that needs to be setup? When it constructs the URL to download, the prefix appears to be constructed incorrectly. The version that did work had the correct prefix.

7

From the log, it shows that it was caused by temporary network issue.
Could you try again to see if it’s still not working? Thanks

8

@kaycc It still does not work. I built a new system on a different machine, and SDK Manager works correctly there. It appears to be something specific to the older machine. The logs on the new machine appear to be correct, with the proper https:// prefix, the older machine logs appear to have improperly formed URLs.

I won’t be using SDK Manager anymore, I’ll just use the BSP flashing scripts from now on.

Thanks for your work on this.

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.