This issue was fixed in R36.4.3, and according to the information in the post, the effective file is tos_optee_t234.img . Can I use the tos_optee_t234.img from R36.4.3 in R36.4.0? What problems might this cause?
After testing, I found that it can solve the problem, and so far no issues have been found.
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that the question is not directly related to the context, but rather a separate issue regarding a fix in R36.4.3 and its potential application to R36.4.0.
However, I can provide a comprehensive answer based on the information given.
The issue in question is an assertion issue in UEFI during boot on a Jetson AGX Orin device. The fix for this issue is included in the tos_optee_t234.img file, which is part of the R36.4.3 release.
The question is whether it is possible to use the tos_optee_t234.img file from R36.4.3 in R36.4.0, and what potential problems this might cause.
According to the information provided, testing has shown that using the tos_optee_t234.img file from R36.4.3 in R36.4.0 can solve the problem without introducing any new issues.
However, it is essential to note that using a file from a different release version can potentially cause compatibility issues or other problems. Therefore, it is crucial to carefully evaluate the risks and benefits before applying this fix.
In terms of the context provided, there is no direct connection to the peripherals, platforms, or components listed. The issue and fix appear to be specific to the Jetson AGX Orin device and the UEFI boot process.
To build the tos image, it is recommended to follow the steps outlined in the atf_and_optee_README.txt file, which includes setting the UEFI_STMM_PATH environment variable to the correct location before building OP-TEE.
In summary, while using the tos_optee_t234.img file from R36.4.3 in R36.4.0 may solve the assertion issue, it is crucial to carefully evaluate the potential risks and benefits before applying this fix. Additionally, following the recommended steps for building the tos image is essential to ensure compatibility and avoid potential issues.
I think it should work as there should be not many differences in these 2 releases about A/B-secure_os partition, but we’ve not verified for this use case.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.