I am trying to get a Jetson Nano flashed , but am running into some issues. I am using an Avermedia EN715 carrier board and have tried multiple BSPs. The Jetson module I have is this one: https://www.arrow.com/en/products/900-13448-0020-000/nvidia4
I have looked around on the forums and most issues like this are using a SD card boot and not a eMMc boot. The other ones seem pretty different or say to speak to the manufacturer of the carrier board. I have been working with the manufacturer for a while, but they are still not sure what is going wrong and have recommended I reach out to the NVIDIA forums.
The main problem is that it is just sitting at the NVIDIA logo screen after successfully flashing. This persists after a full reboot as well. Power off → unplug → replug → wait for bootup. Picture below:
I am unable to use an F1, ESC keys to enter any sort of BIOS as well.
My board does have an SD card in its slot (though I believe this is not used for flashing to an eMMc chip). I have tried flashing with and without the SD card inserted in case that was needed.
Since the version required is Jetpack 4.3 (R32.3.1), I am using a physical Ubuntu 18.04 machine (no VM).
I attached two logs that used two different flashes and had the same results. Avermedia (the carrier board manufacturer) has its own BSP and instructions, and FLIR (the camera manufacturer that requires this custom carrier board) has its own image I have tried to clone onto the eMMc. They both lead to a successful flashing, but being stuck at the NVIDIA logo.
Here is a link to the EN715 carrier board and the BSP for Nano can also be found at that link.
That method’s results can be found in avermedia_flash_log.log avermedia_flash_log.log (310.4 KB)
It looks like it might be a version issue. I flashed it with a Jetpack 4.6.5 BSP and that one worked fine. I am working with the carrier board manufacter and FLIR to see if that Jetpack version will work.
Does anyone know if some Jetson Modules are not compatible with earlier versions of Jetpack like 4.3? And how would I know if mine is not compatible?
And would this work for Jetson Nano with Jetpack 4.3 (R32.3.1)? It seems to say it is for R32.7.5 or R32.7.6 and there are no other options for the Jetson Nano.
Ill give this a shot and see if I can get the patch to apply. I am new to patching, so hopefully I can figure it out. If you have any instructions on applying patches, let me know. But Ill see what I can find if you dont.
After attempting to patch JetPack 4.3 with the R32.7.5 overlay, I am still getting some errors. However, it did get past the NVIDIA logo and into some kind of limited shell environment. It outputted these errors:
imx219 30-0010: reset-gpios not found
imx219 30-0010: tegra camera driver registration failed
imx219 30-0010: reset-gpios not found
imx219 30-0010: tegra camera driver registration failed
tegra-asoc: sound: Can’t retrieve clk ahub
imx219 30-0010: imx219_board_setup: error during i2c read probe (-121)
imx219 30-0010: board setup failed
imx219 30-0010: imx219_board_setup: error during i2c read probe (-121)
imx219 30-0010: board setup failed
bash:cannot set terminal process group (-1): Inappropriate IOCtl for device
bash: no job control in this shell
bash-4.3#_
A reminder first. All the things we could provide here is to debug the NV devkit. We don’t know whether your custom carrier board from other vendor has the same interface in use or not.
For NV devkit, we have below method to use usb ttl cable to capture all the logs since the bootloader.
No matter what situation, this method would dump out some logs.
It does not look like this carrier board has the connectors outlined in that tutorial. Can I grab these logs using the micro-b connector for recovery mode?
Ill need to order the cable to see if I can get that working.
In the meantime, do you have any thoughts on the why JetPack 4.6.5 works fine and JetPack 4.3 does not? 4.6.5 has no problem flashing to the eMMc and booting up.
4.3 just holds at the NVIDIA logo screen. Do you think the problem is the overlay or could it be something else? I am just trying to figure out where to focus my efforts.
I have been talking with the carrier board manufacturers, but they seem to be at a loss as well.
Do this in the meantime when you are trying to get the cable.
Go to your BSP directly.
Then cd to rootfs/boot/extlinux
Modify the extlinux.conf and remove the “quiet” in it. This will enable more logs. But it will not help for now because your monitor size won’t be sufficient for all the logs.
This will only help dump out the final log from the debug serial.
