We are currently facing an issue with multiple Jetson Nano modules from the same batch. While the flashing process completes successfully, the devices fail to boot after the flash process is finished. The issue has been observed across several units from the same batch.
I’m probably the wrong guy to answer this, but you need to provide the specific model and the L4T release you are using. One very important part is that if this is using a third party carrier board, then the flash software which is required will change versus a developer’s kit. Is this really the older Nano, or is it one of the newer Nanos (e.g., it might be Xavier Nano or Orin Nano)? Is this using a third party carrier board, and thus it has eMMC? L4T release can be found in “/etc/nv_tegra_release”, or from the host PC used for flashing, the “Linux_for_Tegra/rootfs/etc/nv_tegra_release”. For this case I’d also say you need to post a copy of the “/etc/nv_boot_control.conf”.
Note: One of the reasons why the exact release might matter is if there is a particular version of memory, then there might be a requirement to use a slightly more recent L4T release for that board revision.
We are using a third-party carrier board with the BSP from the manufacturer. The module is an older Jetson Nano. I’ve tested the same Nano module on a different carrier board, and the issue persists.
nv_tegra_release:
***# R32 (release), REVISION: 6.1, GCID: 27863751, BOARD: t210ref, EABI: aarch64, DATE: Mon Jul 26 19:20:30 UTC 2021***
nv_boot_control.conf
TNSPEC 3448-402-0002-B.0-1-0-jetson-nano-emmc-mmcblk0p1
TEGRA_CHIPID 0x21
TEGRA_OTA_BOOT_DEVICE /dev/mmcblk0boot0
TEGRA_OTA_GPT_DEVICE /dev/mmcblk0boot1
I won’t be able to answer for a third party carrier board, but I’ll add some notes.
Flash itself using a third party carrier board implies the need to follow the third party carrier board manufacturer’s instructions since firmware might differ. If the carrier board has the same exact electrical layout, then the manufacturer might say to just use the NVIDIA flash software directly. If not an exact match, then either there will be a patch from that vendor to apply to the NVIDIA software, or they will provide rebranded flash software (which basically is a patched firmware version of NVIDIA’s software).
It is possible that a certain batch of Jetson modules will have a different hardware revision. For example, one might use a different brand or specification for some memory component. If the problem is a result of this, then it might be that whatever flash is being used requires naming the specs for the newer revision. I don’t know. However, the flash software itself should provide a log of the flash failure which you can post.
What does the manufacturer of the carrier board say to do for flash? What specific instructions apply to flash from that carrier board vendor? This in combination with the flash log will likely offer a clue. It might be as simple as using a more updated flash release for a different module revision. Or it might be a case of using some updated firmware patch.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.