This is my first time using the BalenaCloud to which I want to connect my Jetson Nano device. After flashing the image to an SD card and plugging in the Nano with the image, no new devices show up in the application after waiting more than 10 minutes. I’ve tried connecting via both Ethernet and Wifi (I installed a Wifi adapter on the Nano) to no success. Is there something else that I’m missing like does my PC need to be connected to the same network as the Nano?
I’m using the 4GB Jetson Nano Model.
Additionally, I tried again connecting the Nano to a screen and it would get stuck on the NVIDIA logo boot-up screen.
This is likely an issue with a device that has already been installed with JetPack 4.5. Devices that have been flashed with JetPack 4.5 have their SPI flash overwritten, and will no longer boot balenaOS.
Once the device is flashed back to JetPack 4.4, you can try booting up your balenaOS SD Card, and it should work (show up in the Dashboard, push containers, etc.)
Unfortunately after I flashed to JetPack 4.4 and then booted up the Nano with a BalenaOS SD card it still wouldn’t work. This time no image showed up when connecting to a screen and the lights by the ethernet port were not flashing.
@PLanza just a quick confirmation, you used the Nvidia SDK Manager and hooked up the Nano via USB cable to the micro-USB port on the Nano, correct? Simply writing a JetPack 4.4 SD Card is not enough to overwrite the SPI, I don’t believe. Just want to make sure, thanks!
@dtischler Yes, I flashed it using the SDK Manager while I had a completely formatted SD card in the Jetson. I then took that SD card out and flashed it with BalenaOS using Etcher but it wouldn’t boot up. Is there something wrong that I’m doing in terms of the procedure?
What I did was reflash using SDK Manager the 4.4.1 Jetpack onto an empty SD card, and then I did the full installation of Ubuntu on it as if I were going to use it. I then flashed BalenaOS onto a separate SD card and placed that one into the Nano. This time it worked when I booted it up!
That is actually what I was going to recommend next, ha! I suspect that the installation routine “completes” the reset in some way. Glad you are up and running!