Region Size of FLASH changes when CONFIG_DEBUG is set to 'y'

[Stefan Schmidt]

Dear Support-Team,

I noticed that the displayed region size changes when I enable CONFIG_DEBUG. Here an example with the asset_tracker_v2 in nrf Connect SDK v2.5.0:

Building the asset_tracker_v2 unmodified with

west build -p -b nrf9160dk_nrf9160_ns

gives

Memory region         Used Size  Region Size  %age Used
           FLASH:      262652 B       736 KB     34.85%
             RAM:      132596 B     211608 B     62.66%
            IDT_LIST:          0 GB         2 KB      0.00%

Setting CONFIG_DEBUG=y in the prj.conf file and build with

west build -p -b nrf9160dk_nrf9160_ns

gives

Memory region Used Size Region Size %age Used
         FLASH: 367252 B 704 KB 50.94%
         RAM: 132588 B 211608 B 62.66%
         IDT_LIST: 0 GB 2 KB 0.00%

I understand that the code size changes, but I do not understand why the region size is different...

[Sigurd]

Hi!

Let's use the Memory report to look at this.

In the non-debug build, we can see these Partitions:

In the debug build, we see these Partitions:

We see that enabling CONFIG_DEBUG, the size of the TFM partition went up, both the size itself and the Region. As a results of this, the app partitions region was reduced with the same size.

[Stefan Schmidt]

Hi Sigurd,

 thank you for the information!

Best

Stefan