I’m using a Jetpack 4.5 image for the Jetbot, which should be compatible with boards that have and do not have the updated firmware flashed on them.
I have not tried using the SDK Manager to flash the boards yet. This is for a customer order, in which they claimed to have an out-of-the-box problem. After several attempts at some basic troubleshooting on their end, we got their boards back and eventually found this discrepency in the bootloarder messages of their boards.
I’ve tried powering the all the boards both through the micro-USB connector (5V/3.5A wall adapter) and the barrel jack with a variable power supply (set at 5V@4.5A).
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0
However, now none of the bootloader messages get passed through the serial console. I restarted the Jetson several times, waiting a few minutes longer each time. I’ve also tried this on another of the boards with the same issue.
Though, I am pretty sure I saw part of the kernel log was in the text files that I linked in my previous responses.
Yup, one of the jumper wires was loose… go figure. These are the bootloader messages, with the /boot/extlinux/extlinux.conf file modified (as previously discussed): extlinux-modified.txt (24.0 KB)
I keep a working 4GB Jetson board for dev. testing and building custom images for our jetbot kits that I keep at my desk.
I was given four boards that the customer sent back. However, I was told that ~8 boards in total were experiencing an issue. I believe two had power issues (seperate topic - green LED would come one breifly and then turn off) and six were getting stuck on the splash screen. (I’ll have to double check with the customer service team to get the exact numbers.) Of the four boards that I have, one had the power issue and three are hanging on the splash screen.
Are you sure that the image on the SD card is the problem? I can double check again, but I am pretty sure that I am using this 4GB image.
I’ll redo the test, but that image worked on the 4GB Jetson Nano (v3) that I normally use. I would assume if I was using a 2GB Jetson image, that it wouldn’t work for either of the 4GB Jetson Nano (v3) boards (working and not working).
Let’s validate this in another way. From the NG board, please do not erase it. Just move the sdcard out from the board. Put it to your host. Check what is inside /boot and /boot/dtb folder on this sdcard. And share me the result.
You can also try the same method on every of the board you hit issue. Share me all the log of these boards so that we can see if they all have same situation.
This is the boot folder from the SD card. I just plugged the SD into another computer with Ubuntu on it, mounted it as a drive, and copied the folder from the SD card.
Unfortunately, I am trying to keep my working Jetson Nano in a state where the new firmware hasn’t been flashed, in order to support our legacy custom images for customers. I’ll see if someone at the office has an older v2 board that I can use to check the uboot version.