I burned the image using Balena Etcher on a 64GB SDdcard. Placed the card on Jetson Nano e turned it on. There was an error during the boot while opening the GUI system (“The installer encontered an unrecoverable error. A desktop sessions will now be run so that you may investigate the problem or try installing again”). After that, every boot attempt halts with a “board setup failed”.
I also burned again he same SDcard with the previous old image, and it boot fine. So it seems a problem with the factory image I downloaded from Nvidia.
I didn’t found in Forum anything that matches with this (jumpers, energy issues, etc) since the old image a had performed boot without any problem.
Alternativelly, I tryed to install the brand new SO using SDK Manager, with no success. I happens that the SDK is not able to perform an apt update, even though the correct admin password is given. In fact, running such command by my own in terminal, it say that an configuration file was not found so that to “support architecture ‘i386’”.
This is the device version: # R32 (release), REVISION: 6.1, GCID: 27863751, BOARD: t210ref, EABI: aarch64, DATE: Mon Jul 26 19:20:30 UTC 2021
According to that post, the solution was installing L4T with SDK Manager. Even though I added the ppa:gnome3-team/gnome3, SDK Manager still fails because a configurantion file:
Reading package lists… Done
N: Skipping acquire of configured file ‘contrib/binary-i386/Packages’ as repository ‘Index of http://download.virtualbox.org/virtualbox/debian bionic InRelease’ doesn’t support architecture ‘i386’
E: The repository ‘Index of /fta/gnome3/ubuntu bionic Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Actually this is very common. I am not sure if you really want to debug this or just want a solution.
A quick description for your issue is “desktop GUI fails to launch”. It means the device may already boot up, but as the desktop GUI fails to show up, you feel like the device is not able to boot.
A quick solution is just reflash your whole board with sdkmanager. BTW, that requires another x86 host PC if you don’t know. And VM is not supported.
If you want us to help debug this issue, you need to check if you really boot into kernel first. Using uart serial console would help.
Connect the microUSB from Jetson into the USB from PC
Start SDK Manager, and choose the installations you want
SDK will try to test apt repos, if success, OK for you. I didn’t had that luck. It complain abou some repositories not having an configuration file. What I did was eliminate the problematic repo by removing the corresponding files at my PC (sudo rm /etc/apt/sources.list.d/fta* and sudo rm /etc/apt/sources.list.d/virtualbox.list*)
Finally, SDK Manager manage to proceed
Then “next,next, …, next, finish”
Jetson Nano reboot and you finish the setup by using a keyboard and monitor connected to nano.
