Hi there,

Thanks for your interest in wolfBoot on AURIX!

This is due to compatibility with one of the demo examples for wolfHSM on the AURIX platform. If you are just using wolfBoot without wolfHSM, then you can feel free to modify how wolfBoot utilizes the address space however you wish, as long as you also update the appropriate wolfBoot configuration preprocessor macros accordingly (ARCH_FLASH_OFFSET, WOLFBOOT_PARTITION_BOOT_ADDRESS, WOLFBOOT_PARTITION_UPDATE_ADDRESS, etc.). Note that this is done for the fixed demo project addresses by the AURIX helper script (tools/scripts/tc3xx/wbaurixtool.sh) when invoked with the "target" sub-command.

- For more information on wolfHSM see: https://www.wolfssl.com/products/wolfhsm/
- For more information on how wolfBoot integrates with wolfHSM, see: https://github.com/wolfSSL/wolfBoot/blo … wolfHSM.md and the wolfHSM integration section of the README you are referencing.
- Further information about the HSM subsystem on AURIX is restricted by Infineon NDA. Please reach out to your Infineon sales representative.

You don't need winIDEA specifically to edit the UCBs, you just need to be able to program those flash sectors. This can be done using the Infineon provided memtool and the onboard "mini wiggler DAP", an external programmer like a Lauterbach device, or even from source code running on the device.

Note that the wolfBoot documentation does assume a general understanding of how the AURIX platform works, including how to program and configure the device. The AURIX platform is quite complex and the UCBs are a fundamental aspect of the system configuration, so I would urge you to consult the reference manual for the device to learn more. I would also recommend reach out to your Infineon sales or support contact for more information and training material.

Best,
Brett