Hi,
We have a project where we would like to have the opportunity to compile it for using a bootloader version and compile it for a version without bootloader. For that I am using the compile in debug mode or in release mode, changing the code accordingly with #if DEBUG and #endif . But to totally accomplish it, we would like to change the PROGRAM_FLASH as well , setting it to 0xf000 for the bootloader and 0 for the debug version .
I am trying to find a way to do so but the MCUxpresso Properties->MCU settings are not defined by the compile mode, therefore I always have to change the PROGRAM_FLASH address every time I want to change the mode.
Is there a way to link the address to the compile mode so that the transition is just linked with the compilation mode?
Thank you for the help
Regards
Solved! Go to Solution.
See my article on this topic at https://mcuoneclipse.com/2019/10/06/linking-bootloader-applications-with-eclipse-and-freemarker-scri...
As you noted, the memory map/MCU settings do not support build configurations. I have filed a feature request on this, so I hope this could be available in a future version. Until then, the above approach with freemarker scripts works very well for me: I can build the booloader app or the standalone app. As long as the device stays the same with its overall memory map. Which is usually the case.
I hope this helps,
Erich
See my article on this topic at https://mcuoneclipse.com/2019/10/06/linking-bootloader-applications-with-eclipse-and-freemarker-scri...
As you noted, the memory map/MCU settings do not support build configurations. I have filed a feature request on this, so I hope this could be available in a future version. Until then, the above approach with freemarker scripts works very well for me: I can build the booloader app or the standalone app. As long as the device stays the same with its overall memory map. Which is usually the case.
I hope this helps,
Erich
Hi @ErichStyger ,
Thank you very much for the reply and help.
I am glad to hear that you have already filed a feature request on this , so I look forward to see it implemented on the next versions of the MCUxpresso, as it would help a lot.
Thank you also for the link on a way to work around this issue. I will try to implement it for sure.
Regards