使用R35.3.1版本SDK,自定义载板,现在出现部分模组下载固件失败的情况,报错如下图:
查阅相关问题,说可能是emmc大小不同导致,应用PCN补丁后已将emmc的num_sectors由原来的“124321792”替换为“124190720”,仍会出现该问题,麻烦帮忙分析下是什么原因?
使用R35.3.1版本SDK,自定义载板,现在出现部分模组下载固件失败的情况,报错如下图:
查阅相关问题,说可能是emmc大小不同导致,应用PCN补丁后已将emmc的num_sectors由原来的“124321792”替换为“124190720”,仍会出现该问题,麻烦帮忙分析下是什么原因?
*** Please note that this reply is generated by LLM automatically ***
The provided information is related to the NVIDIA Jetson Linux Developer Guide, specifically the Jetson Orin Series, which includes the Jetson AGX Orin, Jetson Orin NX, and Jetson Orin Nano Series.
However, the question seems to be related to a specific configuration or setting for the Jetson AGX Orin module, specifically the R3531SDK version.
The provided configuration string appears to be related to the eMMC (embedded MultiMediaCard) settings for the Jetson AGX Orin module. Here’s a breakdown of the configuration string:
emmcPCN: This likely refers to the eMMC partition configuration.emmcnumsectors: This specifies the number of sectors on the eMMC device.124321792: This is the total number of sectors on the eMMC device.124190720: This is likely the number of sectors allocated for a specific partition or configuration.Unfortunately, without more context or information about the specific requirements or goals of the configuration, it’s difficult to provide a more detailed answer.
However, I can suggest that the configuration string is likely related to the eMMC settings for the Jetson AGX Orin module, and the numbers provided specify the total number of sectors on the eMMC device and the number of sectors allocated for a specific partition or configuration.
If you’re looking to configure the eMMC settings for your Jetson AGX Orin module, I recommend referring to the NVIDIA Jetson Linux Developer Guide and the Jetson Orin Series documentation for more information on the available configuration options and settings.
Additionally, you may want to compare the provided configuration string with other available configurations or settings for the Jetson AGX Orin module to determine the best approach for your specific use case.
Here are some potential next steps:
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Hi 1472619047,
Could you share the full flash log for further check?
Please also verify with the latest R35.6.2 so that you don’t need to apply the PCN overlay manually.
下面是完整的flash日志:
flash_3-4.1_0_20251209-094859.log (7.5 KB)
R35.3.1这个版本已经是在客户现场用的比较稳定的一个版本了,所以希望能在这个版本上解决这个问题。
顺带问一下,我记得当时是在https://developer.nvidia.com/embedded/jetson-linux-r3531这个页面最后看到并下载了补丁包Overlay_PCN210361_PCN210100_r35.3.1.tbz2,但是现在去看为什么没有了呢,是补丁包存在什么问题吗?
I just want to clarify the issue and know if r35.6.2 can work w/o any modification.
Do you have the devkit to verify? If so, you can simply put the current module on it and flash Jetpack 5.1.5(r35.6.2) through SDK manager.
We’ve moved all PCN packages and related information to Jetson PCN Center in Jetson Download Center.
Which PCN module are you using currently?
没有
当时下载的时候只有这一个Overlay_PCN210361_PCN210100_r35.3.1.tbz2,没有应用这个补丁之前,下载固件会卡在引导阶段
Do you mean the device can be flashed successfully after applying this PCN overlay(i.e. PCN210361 and PCN210100)?
应用补丁之前是我们手上有的所有设备都下载失败,卡在引导阶段,应用补丁后至少不会卡在引导阶段,部分设备能下载了,emmc num_sectors为124321792的下载失败,emmc num_sectors为124190720的能下载成功,num_sectors的更改是不是最终会应用到secureflash.xml中,我在打包出来的固件中查看了secureflash.xml,mmc对应的num_sectors就已经更改之后的124190720了,如下图
使用r35.6.2版本已测试过,可以正常下载
Do you mean it could work after you apply the overlay package from r35.6.2?
If so, do you have further question about this topic.
Please just confirm the sector_size(512)* number_sectors(124190720) <= physical size of eMMC of your module if you have eMMC size related issue.
我的意思是我直接使用r35.6.2版本的SDK编译生成固件,可以正常下载,但是R35.3.1版本的SDK还是不行,我需要使用r35.3.1这个版本
emmc大小我已经确定过了,number_sectors和实际的是一样的