printk via RTT will not work, but printf does

[Pamela Keiles]

Hello there,

I have looked through all of the various other related questions, but still cannot resolve this issue. I am trying to use RTT versus a UART for the console. I have confirmed that the printf operation works, but not printk. I have looked at all the various configuration settings and stepped through the code, and the call branches to "log_printk" versus "vprintk". 

I have the following config statements defined in the project file:

CONFIG_CONSOLE=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y

CONFIG_UART_CONSOLE=n

CONFIG_PRINTK=y

CONFIG_LOG_PRINTK=n

However in the output config file, the parameter CONFIG_LOG_PRINTK is always set as "y". Can you tell me why I cannot change this printk log parameter, it appears that this is stopping me from using printk to the RTT console.

Thanks,

Pam

[Pamela Keiles]

I think I have the RTT working now, but only with the Segger RTT Client program. Using the NRF Terminal within Visual Studio doesn't work, but that's okay. It seems like using the Kconfig menu is not a good option most of the time since any changes are erased when a pristine build occurs. In any case, for the moment I have created a custom board for our application and am using the dev board config files as reference. I will submit another case if I have any more issues or questions.

Thanks for all your help and regards,

Pam

[ovrebekk]

Hi Pam

It's good to hear you were able to get this to an acceptable state. 

The CONFIG_THREAD_MONITOR option is documented here.
If you are unable to change it it probably means that one of the configurations listed in the "Symbols that select this symbol" have also been selected, then CONFIG_THREAD_MONITOR will be enabled implicitly, and you are unable to disable it. 

The best of luck with your project

Best regards
Torbjørn