Unable to print using printf or nrf_log_info

[fatimatayyab71]

I am using nrf5 sdk 17.1.0, segger embedded studio v6.40 and nrf52832-dk, when running the spi example, i do able to see the log only after the build, and when i reset the device no log is shown on the Jlink-RTT viewer. When running the uart example provided in nrf5 sdk i was unable to see any anything on the terminal also. Can you please let me know what might be the potential reason?

[Edvin]

Hello,

The printk() usually prints to the UART, and not the RTT log. If you want to print something to the RTT Log, make sure that RTT logging is enabled in your sdk_config.h. 

If you try the ble_app_uart example, in nRF5 SDK 17.1.0, you can see that printk() will print to the UART terminal (use something like Putty or Termite), but logging, which uses NRF_LOG_INFO(), will be printed to the RTT log.

Best regards,

Edvin

[fatimatayyab71]

I have used UART terminal of nrf connect for desktop and putty but nothing prints there, and for nrf_log_info() i have used RTT log of Jlink RTT viewr separately but nothing shows.

[Edvin]

What application are you testing on? And what HW are you using? A standard Nordic nRF52832 DK? 

Best regards,

Edvin

[fatimatayyab71]

I have performed the factory reset and then able to print on the terminal using the above code on nordic connect sdk, but when again implement this below example on nrf5 sdk nothing prints. 

Edvin said:

If you try the ble_app_uart example, in nRF5 SDK 17.1.0, you can see that printk() will print to the UART terminal (use something like Putty or Termite), but logging, which uses NRF_LOG_INFO(), will be printed to the RTT log.

Yes, I am using standard nrf52832-DK.

[fatimatayyab71]

I have tested the ble_app_uart, on ses version 6.40 but it was not printing anything, but when i tried on version 4.52 it prints on the terminal.

[Edvin]

Ah, yes.

Sorry for not noticing, but it has been a while since I saw this issue. 

If you look in the release notes, you can see what SES version this SDK is tested with. It says 5.42a, which means we don't maintain it for versions newer than this.

I think it was SES v6.0 or something that introduced a breaking change regarding logging, meaning it will not work out of the box. So the easiest way to get this working without any hassle is to use v5.42a.

Best regards,

Edvin