Dear TF-M maintainers,
I am currently developing an application using the STM board b_u585i-iot02a (target: b_u585i_iot02a/stm32u585xx/ns). As mentioned in this issuehttps://github.com/zephyrproject-rtos/zephyr/issues/92670, , the provisioning data is currently statically programmed.
Instead of changing this hardcoded data directly, I created a jinja2 template and a generation script based on the original file. This follows the same pattern used in trusted-firmware-m/platform/ext/common/provisioning_bundle/CMakeLists.txt.
This approach works well locally, but I would like some feedback to ensure it meets the project's standards before opening a PR.
First, what are your thoughts on this method? Should this feature be made available for all STM boards, or is it better to restrict it to the b_u585i-iot02a for now?
Additionally, I am currently passing variables such as huk, iak, and boot_seed from my local project's CMakeLists.txt. If they are not provided, the script simply falls back to the default hardcoded values.
Thank you in advance for your time and guidance.
Best regards,
———
Benjamin Grolleau benjamin.grolleau@outlook.com