Remove redundant pre-processor symbol MCUBOOT_TARGET_CONFIG

[jespertragardh]

Describe the set-up

• STM32CubeIDE 1.18.0

Describe the bug
Projects/*/Applications/ROT/OEMiROT_Boot

All the IDE-configs seem to add '-DMCUBOOT_TARGET_CONFIG=<flash_layout.h>' to the build command line.
I have only tested with STM32CubeIDE but it is present in EWARM/Project.ewp and MDK-ARM/Project.uvprojx too.

This preprocessor symbol is redundant. No code tests for it.

In the upstream mcuboot 1.7.2 it is used in boot/zephyr/include/target.h but this file is not present in Middlewares/Third_Party/mcuboot/ in this git. There is no Zephyr support in this git. And to my understanding (which I admit is limited), if you want to boot Zephyr using mcuboot, you build mcuboot as part of Zephyr. OEMiROT_Boot cannot be used for this purpose.

Suggested fix
Remove '-DMCUBOOT_TARGET_CONFIG=<flash_layout.h>' from the project configs for EWARM, MDK-ARM and STM32CubeIDE.

[ALABSTM]

See also #27

[KRASTM]

Hello @jespertragardh,

Regarding this ticket, are you saying that you have encountered an issue related to the macro -DMCUBOOT_TARGET_CONFIG=<flash_layout.h> in the preprocessor symbol?

With regards,

[jespertragardh]

Regarding this ticket, are you saying that you have encountered an issue related to the macro -DMCUBOOT_TARGET_CONFIG=<flash_layout.h> in the preprocessor symbol?

Well, yes it is not needed and causing confusion for the customers.

I guess is a left-over from some other project's code that was transformed into OEMiROT_Boot for STM32H5. Maybe it has been added to OEMiROT_Boot for other MCUs too - I haven't checked.
It is not breaking anything at the moment but it would be good to clean it up when time permits.

Best regards, Jesper

[KRASTM]

Hello @jespertragardh,

Thank you for your feedback. I will share it with our team.
Since it is related to the same application and was addressed in #27, I propose closing the other ticket and keeping track of this one.

With regards,

[KRASTM]

ST Internal Reference: 223461