Log Message disabled/missing while Kiel debugging secure DFU project

[shay]

Hi

I am trying to see log messages on the kiel debugger window or in the virtual com port window but nothing is not displayed.  printf also are not displayed, nrf logs also disabled because turn on the main log flag cause link problem (no space in execution regions..)

any idea how to get logs?

Thanks

[Einar Thorsrud]

Hi,

I recommend you to use the Logger module (NRF_LOG) which is part of the SDK. This is enabled by default for most SDK examples with the UART backend. You can view the logs in any serial terminal emulator, for example PuTTY. You can also enable the RTT backend and view the logs in J-Link RTT Viewer.

It is not clear to me what is wrong with the Logger module in your case. "No space in execution regions" indicate that something in your application is using a lot of memory so you cannot fit the logger module for some reason. The Logger module itself should not normally require a lot of memory unless you have set large buffer sizes (NRF_LOG_BACKEND_UART_TEMP_BUFFER_SIZE or NRF_LOG_BUFSIZE).

[shay]

Hi

Thanks for your reply

I am trying to use the nrf-log module but when enabling it there is space problem error in link process

I used NRF_LOG_BUFSIZE = 128 and no success. error is:

.\_build\nrf52832_xxaa_s112.axf: Error: L6406E: No space in execution regions with .ANY selector matching pb_decode.o(i.pb_dec_submessage).

my project is on bootloader dfu .

Thanks

[shay]

any update please

[Einar Thorsrud]

How much free flash and RAM do you have before you include logging? You will increase the size of SDK modules if logging is enabled (globally) and for each specific module. Could you try to disable logging for each SDK module in sdk_config.h and set a higher log level and see if you can make it fit that way? You can disable logging from all SDK modules and only use it for your application to conserve as much space as possible.