Hey guys, a quick update.
I ran into problems putting the Jetson Nano in force recovery mode. I’m not sure if this Nano is A02. I compared the diagrams I found on Nvidia of what an A02 looks like compared to Nano I have and there are some differences.
Looks like I have the Jetson Nano 2GB which was just released last month so I’m not sure if that matters.
Here is a link to the board I purchased.
I had problems placing the Nano in force recovery mode mainly because the location of where to place the Jumper did not exist on my board.
In the end, I was able to get it in force recovery mode by issuing the command below from the Jetson Nano terminal
reboot --force forced-recovery
I installed Ubuntu 18.08 on VirtualBox and attempted to run the Jetson Nano L4T Driver Package flash script but it failed to connect to the board.
I then installed the SDK Manager and tried to update that way but it stopped at 99% after many attempts.
I read on the Nvidia forum that VMWare Fusion works best with the process instead of VirtualBox so I installed the VMWare Fusion/Ubuntu/SDK Manager. The update process was successful.
Note that the Nvidia moderator stated that…
When you use SDK Manager, it implicitly flashes QSPI-NOR as well as flashing the SD Card you have inserted into module
Thus I did not continue to use the flash script.
After the SDK Manager was complete I then flash the balenia OS and ended up with the same boot screen.