I have two Jetson Nano boards, but I’m not sure what model they are, or how to check. The back says they are JP3450, but it doesn’t state the amount of RAM.
I can’t get either board to show a splash screen (any more). Here’s what I’ve tried:
Using multiple power supplies
Flashing both the Jetson 4GB and the Jetson 2GB developer kit images to the SD card
Trying multiple SD cards
Multiple HDMI cables
In all cases, the result is that the board shows a green power LED, but does not produce any display output. I plugged in an FTDI cable, and the log messages indicate that the bootloader is corrupted. I get the same messages for both boards, and it doesn’t matter whether I’m using an SD card with the 2GB or the 4GB image flashed. I even get the same messages when no SD card is inserted at all.
I did say neither board shows a splash screen any more. Originally, one of the boards showed a splash screen and booted correctly, then I must have done something to break it because it started acting like the other board overnight. I don’t know if it was moving things on the board itself, a static shock that damaged the board, or an SD card image that somehow corrupted the bootloader.
Any help in debugging one or both boards would be really appreciated!
Hello @proventusnova , thanks for the response! I don’t know how I can flash the boards using the SDK manager. It doesn’t detect my board when I plug it in, and if I manually select the Jetson Nano series, it has no SDK options available.
There are a couple different situations we need to deal with in this case:
If the board is not being detected by the SDK manager, please first check the following possible causes:
1.1. Check that the board is on recovery mode. You can achieve that by jumping the force recovery button pin to ground and powering on the board. You can verify the board is in recovery mode and detected by the computer with the command lsusb the board should appear as an NVIDIA device.
1.2. If you are sure the boards is in recovery mode and still not showing on the computer, try different cables or USB ports on the computer.
The reason why SDK manager is not showing Jetpacks available for the Jetson Nano is because the Jetson Nano is already EOL and is not longer supported by the latest Jetpack releases. Therefore, SDK manager only shows the resent Jetpack releases.
However, there is way you can try seeing archived version, simply launch SDK manager from the console using this command:
sdkmanager --archivedversions
best regards,
Andrew
Embedded Software Engineer at ProventusNova
I’ve been trying to flash the boards by forcing recovery mode. The boards are correctly identified by the SDK Manager. However, even with archived versions, I’m not able to use my Ubuntu 24.04 installation. I also tried editing files in /etc/ to spoof being on an earlier version, but it didn’t work. I’ve been trying to flash from an Ubuntu 18.04 VM running on VirtualBox on my Ubuntu 24.04 laptop. Here is my process:
Use jumper to bridge the pins labelled FRC on my Jetson Nano
Set up a filter for the USB device so it is recognised by my VM, not the base laptop
Run the SDK Manager from the VM
Plug the Jetson Nano device into my laptop, providing it power. This causes the SDK Manager to prompt me for which Jetson Nano it is, and I select 2GB Developer version.
I tell the Manager to flash the board. It flashes really slowly and gets stuck at 99%. If I unplug the board, it gives me an error log. I’ll attach all the logs below.
This happens for both boards. I also tried removing the jumper once the board had been recognised by SDK manager, but this had no change in behaviour.
I downloaded the archived version of the SDK Manager, but it’s giving me an error at sign-in time. Do you know how to resolve it, please? The error is “TypeError: Cannot read property ‘includes’ of undefined”. It’s in the screenshot below, although I’ve wiped the email and password.
That is weird, I have never seen that error message before.
Flashing without the SDK Manager is also a good approach.
I would suggest you use Jetson Linux Version 32.7.6 which seems to be the latest JP version that would support Jetson Nano.
best regards,
Andrew
Embedded Software Engineer at ProventusNova
It sounds like the SDK manager is out, given the weird sign-in issues. I’ve followed the instructions for flashing the board, told it to begin flashing, and it was going for well over an hour with no sign of actually flashing.
If the board wasn’t plugged in, it failed immediately.
With the board plugged in, it seemed promising, and said it was starting to flash about 2s after starting the process. It then hung there for over an hour. It seems like something is going wrong with the actual flashing of the board; it’s similar behaviour to what happened with the VM.
I can access the UART. I tried the flash while the UART was plugged in, and the log was identical for both boards. The issue seems to be with this message: “Failed to open “sdmmc3_user” for publishing partitions”. I found this thread in the forums: Jetson Nano not responding correctly anymore - #9 by johannes.plapp
It seems to have the same error message and states that the eMMC is broken, meaning the SD card is no longer usable. I interpret this as my boards being dead and in need of recycling. Would you agree?
I would suggest you try with brand new SD cards if possible to rule out a possible SD card issue. Otherwise, it does sounds like you might need to request an RMA.
BTW, just out of curiosity why are you using Nano boards?
I ask because they are already EOL and we would recommend you go with the new Orin lineup.
best regards,
Andrew
Embedded Software Engineer at ProventusNova
I’m afraid I don’t have the proof of purchase, and the behaviour is the same for a fresh SD card. It looks like I’m going to have to recycle these boards and give up on them.
As for why I’m using them, it’s because I already have the boards, and because the robot I’m looking to insert them into doesn’t yet have support for the Orin Nano.
I appreciate all your help debugging this. Thank you!
