Jetson Nano Module flashing successfully, but stuck at NVIDIA logo

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
,
21

@WayneWWW Is it possible that Avermedia developed this carrier board and created a JetPack 4.3 BSP specifically for an older jetson nano platform? Then NVIDIA updated their Jetson nano platforms and no longer are compatable with that Jetpack 4.3 BSP that Avermedia put together for their custom carrier board?

This PCN document is starting to make me feel like that maybe what has happened.

In which case, would I need to find a different Jetson Nano platform that is a bit older? The one I purchased is brand new.

22

You donā€™t need to guess anythingā€¦

Just wait for the cable and it will tell all the answer.

If you want a quick answer here, my answer is your guess could be wrong.

1 Like
23

Here are the serial logs for the latest Avermedia 4.3 BSP. This one worked in 2023 apparently.

The 2D Barcode of my Jetson Nano module reads this: 1654424241617, 3C6D6618E788, 699-13448-0002-401

Avermedia_rev041823_JetPack4.3_BSP_serial_logs.txt (34.2 KB)

I am looking through it now, but if you have any insights, please let me know!

24

These are the logs for when I got JetPack 4.3 to get to the shell terminal. But that was as far as it got.

Avermedia_rev030820_JetPack4_3_BSP_gotToShell_serial_logs.txt (24.8 KB)

Here is a successful JetPack 4.6.5 flashing serial logs. Just figured that might be helpful as well to potentially compare.

Avermedia_JetPack4_6_5_BSP_successful_flash_serial_logs.txt (29.9 KB)

25

I just regenerated these serial logs with the quiet flag removed. Forgot to remove those previously. Please let me know what you think. Ill keep trying things and seeing if I can get it working.

This is the JetPack 4.3 BSP from Avermedia with the latest updates from them. This gets me just to the NVIDIA logo, but it should be the latest updated working BSP since apparently it worked back in 2023.
Avermedia_rev041823_JetPack4_3_BSP_noquiet_serial_logs.txt (42.0 KB)

This is the successful JetPack 4.6.5 BSP from Avermedia that fully boots in. I just figured it would be handy to have a reference.
Avermedia_JetPack4_6_5_BSP_successful_flash_noquiet_serial_logs.txt (76.7 KB)

26

I donā€™t think this issue is related to PCN update. Looks like the patch has been applied correctly.

But weird part here is your kernel log is less even after you removed the quiet.

BTW, are you using sdkmanager to flash or a custom BSP from vendor?

27

Custom BSP from the vendor.

28

Are you able to make this situation happened again? If you didnā€™t do anything but remove quiet and enable serial console log there, then the situation on the board should be unchanged.

This log shall still happen.

29

yeah sounds like classic dtb mismatch or boot config issue
might be stuck loading kernel or missing rootfs pointer
check extlinux.conf if it even got flashed right
also confirm if the BSP you used is for emmc version not SD version
if UART/serial is available, plug that in to see logs after nvidia logo
sometimes itā€™s just wrong bootargs or missing kernel image in boot partition
also try flashing with --no-systemimg and copy rootfs manually, might help isolate
could be bootloader didnā€™t get replaced, try forcing reflash with clean option
if FLIR gave a custom image, double check their README for any post-flash tweaks
lastly, try known working L4T base image and boot first before mixing in FLIR stuff

30

Yeah, here are the logs for that with quiet removed. This was with an older version of JetPack 4.3 from Avermedia. But it technically is the farthest I have gotten. I also swapped the dtb file from 4.6.5 and added that to this one.

Avermedia_rev030820_JetPack4_3_BSP_gotToShell_noquiet_serial_logs.txt (67.6 KB)

31

Hi @jacob.faile

We are in the right direction now but you still need to fix one thing here.

Please resize your terminal when you dump log.

As you could see each line of your log got truncated, there is a perfect cut hereā€¦

image
image878Ɨ913 132 KB

32

Okay. Ill regenerate that right now with the resized terminal. Sorry about that.

33

I can see the fatal one from this partial log.

Why is the system trying to mount file system from ā€œmmcblk0plā€?

The partition name should be mmcblk0p1. Not ā€œlā€.

34

Ill take a look and see where that is happening at.

35

Okay. It might be working now.

I used the latest version of JetPack 4.3 from Avermedia. I then replaced the /kernal/dtb/tegra210-p3448-0002-p2449-b00.dtb and the /rootfs/boot/tegra210-p3448-0002-p2449-b00.dtb that was in 4.3 and replaced it with the same file in 4.6.5. I also took the /bootloader/tos.img from 4.6.5 and replaced the 4.3 one with this one. That seemed to work and I am now logged into the Jetson with I think 4.3.

I checked dpkg-query --show nvidia-l4t-core and it is popping up with 32.3.1 which is JetPack 4.3.

36

The tricky part now is I need to patch it with software directly from FLIR now, but I at least now have a working base.

Any tips before I start getting into this? The part I am particularly concerned about is the using their .dtb file, because I bet that one might cause some problems.

Jetson Installation Notes:
===================================
	- Be sure to have Jetpack 4.3 (R32.3.1) installed on your Jetson Nano board. 
	It has not been tested on newer or older releases.

BIN file Install
===================================

	Jetson BIN file Install
	===================================
		- Patch Root file system
			Driver will not work properly if lib in the root file system is not patched.
			Please following below steps to replace the lib in your device.

			1. Copy and decompress the file "bin/rootfs/4.9.140-tegra.tgz" in release package to "/lib/modules" in the device.

		- Kernel and dtb 
			1. Two files ā€œImageā€ and ā€œtegra210-p3448-0002-p3449-0000-b00.dtbā€ are included in the release package in the directory "/bin/kernel"
			2. For how to upgrade the kernel image and device tree,
			please refer the document "Tegra Linux Driver Package Development Guide".
			You can find it in the path "nvl4t_docs/" in the installation path of Jetpack.
37

Actually I have no idea what you are talking about here.

If you are using a custom carrier board, then you should use the dtb from the vendor. The dtb provided by us is only for NV devkit.

38

Avermedia (the carrier board manufacturer) has a dtb that now works for JetPack 4.3 after my latest update when I replaced the 4.3 dtb from Avermedia with the 4.6.5 dtb from Avermedia.

However, FLIR (the camera manufacturer) requires that I add a patch to JetPack 4.3 from Avermedia that involves patching thh root file system and upgrading the kernel image and device tree.

I am now just trying to figure out how exactly to do that patch since I am having trouble finding instructions for that. I am also worried the the dtb from FLIR is going to cause everything to fail again.

39

maybe you could file a new topic for that if original issue has been resolved.

40

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.