search

ARM-software / tf-issues

Issue tracking for the ARM Trusted Firmware project
37 stars 16 forks source link

Changing MPU model among STM32MP1* family #700

Closed ghost closed 3 months ago

ghost commented 5 years ago

I'm working on a custom Yocto image based upon the Distribution Package from ST. First, I built a working image for STM32MP157C-DK2 evaluation board. Now I need to change the target MPU to STM32MP151A. About TF-A, is there something I need to tweak inside the Yocto environment?

ssg-bot commented 5 years ago

Hello @Mark-81!

Thank you for raising an issue for Trusted Firmware-A.

The TF-A project has now migrated to www.trustedfirmware.org. This issue tracker will still remain accessible for some time, but only for historical reasons. From now on you should raise any new issues on trustedfirmware.org.

How do I raise issues for TF-A?

Please use our new issue tracking board. For this you just need to login with your existing GitHub account. We also have a guide to help you raise the issue with the appropriate labels and tags. This way it will be easier for both you and us to track and address the issue most effectively.

What if I face any problems?

You can send us an email in the public TF-A mailing list. Here you can also find all the mailing lists for all the projects hosted under trustedfirmware.org.

We are looking forward to seeing you in trustedfirmware.org!

The Trusted Firmware-A team

Yann-lms commented 3 months ago

AFAIK, there is nothing to change in yocto for TF-A in this case. The management of SoC version is done through device tree. In your board device tree, you have to #include "stm32mp151.dtsi", instead of stm32mp157.dtsi".