Hello:
We have been using BSP34 for development and currently have no upgrade plans. Now we want MCU to be the master for pfe acceleration and a53 to be the slave of the accelerator. It is feasible to not consider the impact of uboot on this solution, but when MCU loads A53, uboot will load the firmware once, causing the above solution to fail. As shown in the following figure, BSP39 supports the accelerator slave driver function under uboot, but the uboot we currently use is based on the BSP34 uboot 2020 version, which is too different from the BSP39 uboot 2022 version. The cost of upgrading the project to BSP39 is too high. Is there any way to quickly realize MCU as master and A53 as slave without affecting normal functions?
Hello:
Thank you very much for your answer. We don't have to support the slave driver solution under uboot, we just want to use the M master and A slave functions. How to implement the accelerator M master and A53 slave before BSP39? Should we completely abandon the accelerator driver under uboot to avoid affecting the operation of the M master, or are there other avoidance solutions? Does NXP have any good suggestions?
Thanks
Hello
The slave driver was introduced relatively late, so for customers who have this requirement, we recommend upgrading the corresponding BSP.
In your case, if you really cannot accept the upgrade, according to my personal experience, you need to do a complete backport process to transplant the relevant changes. However, due to the large version span, the time cost of this process may also be relatively large. Whether to upgrade or backport, this may require you to comprehensively evaluate and consider based on your own situation.
BR
Chenyin
In addition, if you want to implement similar BSP39 functions in uboot2020, are there any suggestions or risks to avoid?