when I tried to install SDK manager on my ubuntu 18.04 for setting up my Jetson AGX Xavier, I was unable to install SDK Manager properly.
At first I downloaded it from Nvidias homepage and after installing it, I could log in. But there were some buttons missing, for example in Step 02 there was no option for a license agreement. Therefore I could not continue with the setup.
So I decided to remove and reinstall the SDK Manager. I still could log in but I could not reach more than step 01, because there was the error log: “OOPS! No SDKs are available for your account”
Ok. Then I tried to re-download the .deb file. And it did not work. I can reach every nvidia link, but if I click on “Download SDK Manager” on this link: https://developer.nvidia.com/embedded/jetpack it loads for several minutes (waiting for developer.download.nvidia.com) and then tells me that this site could not be reached.
Also tried apt remove and restart everything, but it made no difference.
It is a completely new installation of Ubuntu and the SDK Manager is the first program I install there.
So it would be nice, to recieve some help to fix this issue.
If you need some more information, please let me know.
Note that there are two login types you can select. One is for the developer zone, the other is for partners. Be sure you logged in to the correct one.
I’m glad it worked, but be careful about using Ubuntu mechanisms for changing which release you have (restoring a release could have similar issues, but it looks like it worked for this case).
thanks for your answer. If I am honest I do not completely understand your answer. (Probably because I am new in Ubuntu)
So if you have the time, It would be very helpful if you could explain some scenarios that could happen if I use ubuntu mechanism to solve this problem?
A desktop PC has a BIOS or UEFI at startup which takes care of issues such as setting up power rails and clocks in the right order, training memory, so on. The BIOS itself is custom to each motherboard of this type, but presents a uniform interface for people writing boot loaders and operating systems. Embedded systems do not have this, and thus everything which a BIOS/UEFI might do must be custom software instead for that particular board (this is why there are so many partitions other than the rootfs…this is for boot).
Ubuntu mechanisms tend to have no understanding of the boot requirements of a custom board (after all, it is custom, so how could it?). Much of the running operating system is just standard Ubuntu, though perhaps with direct hardware access drivers on top of it (mostly those direct access drivers could be skipped, but you would lose function of hardware acceleration). However, should an upgrade mechanism change anything related to boot, then likely the install would be a loss and require a fresh flash.
Even if the boot succeeds after a new release of Ubuntu is installed via the Ubuntu mechanism (which it is unlikely to survive), then if the kernel has changed in either configuration or features, the provided direct hardware access drivers would fail.
