Starter package building configuration

[MSK]

Hi,

is it possible to know which is the Yocto configuration (manifest release, DISTRO and MACHINE used, other configurations, etc) used to generate the Starter Package of a board?

I think it could be a useful information for everyone. In fact I'm in a situation where the Starter package for STM32MP15 eco 6.0.0 does some operations that fails on an image built using Yocto (Distribution Package) at the same Ecosystem.

Thanks in advance

Mauro

[Olivier GALLIEN · Accepted solution]

Hi @MSK ,

Starter Package for MP15 is generated with DISTRO=st-image-weston MACHINE=stm32mp1

Machine can be tuned to specific board : 

stm32mp1	Machine configuration for STM32MP1 microprocessor device boards
stm32mp13-disco	Example of machine configuration for STM32MP13 discovery board (STM32MP135F-DK   in OP-TEE secure and system services boot mode on SDCard)
stm32mp15-disco	Example of machine configuration for STM32MP1 discovery board (Only STM32MP157F-DK2   in OP-TEE system services only boot mode on SDCard)
stm32mp15-eval	Example of machine configuration for STM32MP1 evaluation board (Only STM32MP157F-EV1   in OP-TEE system services only boot mode on SDCard)

What board are you using and what operation behave differently? 

Did you change DT somehow? 

Thanks

Olivier 

[MSK]

Hi @Olivier GALLIEN ,

Thank you for your answer, that points me to the right direction. More details following.

---

Starter Package for MP15 is generated with DISTRO=st-image-weston MACHINE=stm32mp1

---

I think there is a typo, I suppose you mean st-image-weston is the image and DISTRO is openstlinux-weston, right?

---

What board are you using and what operation behave differently? 

Did you change DT somehow? 

---

I used stm32mp15-disco MACHINE. I didn't change the DT.

Operation behaves differently is using TAs with optee: on Starter Package it works, on my build it doesn't work.

From table in your answer I found that optee is built in different ways depending on machines: "secure and system services" or "system services only". Digging in the (quite cumbersome) wiki I found that these two ways are called "profiles" (here more details), selected in Yocto by "optee" and "optemin" BOOTSCHEME_LABELS.

stm32mp1 MACHINE builds both profiles, but stm32mp15-disco MACHINE builds only "optemin" profile.
Adding BOOTSCHEME_LABELS += "optee" in local.conf allowed me to build a working image.

I would renew the invitation to put in the wiki how Starter Package is built (MACHINE, distro, image, exact repo tag, etc..): this information could be helpful and useful as in my case, and allows customers to build the exact packages provided by ST, validating their Yocto setup.

Thank you, regards
Mauro