LOG written in FLASH : use memory in Release build

[ValentinL]

Hello,

I have issue with my application size which is too big to success DFU.

So i checked the memory content with nrfjprog --memrd 0x0001C000 --n 0x5C000.

I see that my prints are present in flash and consume the memory ! even if i build in release. see below an exemple.
I have that with "SEGGER_RTT_printf" and "__LOG" prints.
This looks really not normal in "release". It is not what I want.

0x00043410: 4C415620 54414449 21204445 32000A21 | VALIDATED !!..2|
0x00043420: 4F542064 20484355 65746564 64657463 |d TOUCH detected|
0x00043430: 0A212120 20643200 43554F54 41562048 | !!..2d TOUCH VA|
0x00043440: 4144494C 20444554 000A2121 54206433 |LIDATED !!..3d T|
0x00043450: 64205041 63657465 20646574 000A2121 |AP detected !!..|

Here is how I build and the configuration : 
Name="Release"
arm_use_builtins="Yes"
build_intermediate_directory="build/$(ProjectName)_$(Configuration)/obj"
build_output_directory="build/$(ProjectName)_$(Configuration)"
gcc_debugging_level="None"
gcc_entry_point="Reset_Handler"
gcc_omit_frame_pointer="Yes"
gcc_optimization_level="Optimize For Size" />

in sdk_config.h file : 
#define NRF_LOG_ENABLED 0

How can I still use this log in "debug" environment and disable in release to NOT write in FLASH which is precious.

Thank you for your help, I didn't find help on the forum.

Valentin

[Vidar Berg]

Hello,

LOG messages will not end up in your binary if you have disabled NRF_LOG_ENABLED and are using the NRF_LOG_* macros. Is there a reason for using the SEGGER_RTT_printf() function instead of the LOG macros? 

Best regards,

Vidar

[ValentinL]

Hi. Thank you.

I already tried to use only logs like : __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "----- test -----\n");

I still have my logs in flash with NRF_LOG_ENABLED = 0 ... it's not normal ?

I was thinking that would resolve but it looks not.

Any other idea ?

[Vidar Berg]

Yes, you need to use the public NRF_LOG_* macros, not the internal logger macros. 

[ValentinL]

Ok if I want to use the NRF_LOG_ENABLED flag, I need to use NRF_LOG_ macros.

But is this the good way to print my application and disable prints writing in flash ?
I would like to use __LOG and that logs do not write in flash.

If I user NRF_LOG, I still need to compile specifically with NRF_LOG_ENABLE 0 in release.
I will not change my sdk_config.h always when i flash for release ...

Sry i try to understand what the best I can do.
Thx :)

[Vidar Berg]

Hi,

Are you using the nRF5 SDK for Mesh by any chance? I assumed you were using the regular nRF5 SDK which does not expose the __LOG() macro. If so, I will need to have a look at that SDK to see if what can be done.

[ValentinL]

Hello,

Yes sorry I am using the nRF5 SDK for Mesh yes.
nrf5_SDK_for_Mesh_v4.0.0.

so, waiting for your answer, thx!

[Vidar Berg]

Hello,

No worries. I should have realized this sooner. Anyway, thanks for confirming. It looks like setting NRF_MESH_LOG_ENABLE to '0' in nr_mesh_config_core.h should do the trick.

[ValentinL]

Thx ! Yes it do the trick. I placed the flag in preprocessor options for debug and release :)

It works!