Multi-image build with selective optimization level

[rw_w]

Hello,

when creating a multi-image build is it possible to select the optimization level for each image individually?

Below is an example of the issue I am facing currently:

• I have a mutli-image build that builds mcuboot, TFM and my application.
• I also use a pm_static.yml file with optimized flash partition size for the TFM image.
• When I create a new configuration (VS Code with nRF extension)  and select "Optimize for debugging (-Og)" in the "Optimization level" drop-down, the image size of TFM increases by around 35% and as a result it does not fit anymore in the partition defined with the pm_static.yml file.
• I actually don't need the debug optimization in TFM, only in my application.
• Is it possible to configure the build somehow, so only my application is build with debug optimization but TFM (and mcuboot) with another optimization level (e.g. size)?

Thanks and best regards,

rw

[Håkon Alseth]

Hi,

 

Unfortunately, the configuration set in your project will be inherited into the tf-m child image.

What is possible is to set the configuration to optimize for size, then re-configure only the application project to use debug optimizations (CONFIG_DEBUG_OPTIMIZATIONS=y) for the specific generated build only:

 RE: Using CONFIG_DEBUG_OPTIMIZATIONS with Thingy:91 and Asset Tracker v2 

 

This will leave other images (tf-m/mcuboot) with the original optimization level.

 

Kind regards,

Håkon

[rw_w]

Hello Hakon,

thanks for the response.

Changing the optimization level only for the application using the .config file in the build folder solves the issue on my end.

Too bad I didn't see the other topic before creating this issue.

Thanks and best regards

rw

[Håkon Alseth]

Hi rw,

 

Glad to hear you got things running as expected.

I hope you have a wonderful day!

 

Kind regards,

Håkon