printk via RTT will not work, but printf does

RE: printk via RTT will not work, but printf does

ovrebekk — Fri, 06 May 2022 08:12:04 GMT

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

RE: printk via RTT will not work, but printf does

Pamela Keiles — Thu, 05 May 2022 04:48:18 GMT

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

RE: printk via RTT will not work, but printf does

Pamela Keiles — Wed, 04 May 2022 17:20:05 GMT

Also, I'm thinking the issue with the RTT as the console output might be because I am using the NRF52DK development board and the CONFIG_UART_CONSOLE is set to "y" in the default board configuration file. I just need to over-ride that since I am using the UART on that board another way.

RE: printk via RTT will not work, but printf does

Pamela Keiles — Wed, 04 May 2022 16:41:16 GMT

Hi Torbjørn,

Yes I've gone through all the tutorials and videos, unfortunately they don't help with some of the details for working with all these config items. I will check them again though to be sure, unless you have a specific one to recommend on this subject.

As for using the "Save to file" option, I didn't see a difference in the zephyr .config file outcome. I just get an error message in the lower corner of Visual Studio stating "No changes to save". So I have no idea where the changes are being saved when I use this editor and why they are not "sticking". Currently I am just trying to change the "thread awareness support" under "Debugging Options", I was trying to get the CONFIG_THREAD_MONITOR define to not be grayed out so I could turn it off, I'm guessing these 2 options are related?

Thanks and regards,

Pam

RE: printk via RTT will not work, but printf does

ovrebekk — Wed, 04 May 2022 10:46:52 GMT

Hi Pam

[quote user="pkeiles"]For example, I changed a bunch of settings in the Kconfig Actions menu, but then when I do a pristine build they are reset back to their original settings. I even try to over-ride some of these settings within the prj.conf file and it doesn't effect the outcome for some of the settings[/quote]

Could you try to use the "Save to file" option in the Kconfig configurator rather than the "Save" option?

Then the changes you make should be stored in the prj.conf file, which means they will be added permanently to the project configuration, and will remain even if you do a pristine build. The other advantage is that you see immediately how the changes in the GUI get represented in the config file.

[quote user="pkeiles"]I find it is hard to get anything done with this system, any way I can get this mess to work with IAR tools?[/quote]

The nRF Connect SDK is not supported in IAR unfortunately. It does work with Segger Embedded Studio, which provides a more IAR like experience, but the main focus going forward is the VSCode integration and that is what we recommend.

[quote user="pkeiles"]I am currently playing around with trying to get optimization setting changed, but it won't "stick", any suggestions on how to get these config settings to work correctly would be greatly appreciated.[/quote]

Which option have you set? Could you try the 'Save to file' option like I mentioned earlier?

As a general tip to help you get started with the nRF Connect SDK and the associated tools I would recommend going through the nRF Connect SDK tutorial series, and the newly released nRF Connect SDK Fundamentals course on the Nordic Academy.

Best regards
Torbjørn

RE: printk via RTT will not work, but printf does

Pamela Keiles — Tue, 03 May 2022 21:12:48 GMT

Hi Torbjørn,

It seems like the whole behavior is inconsistent. I'm sure part of it is due to me learning the IDE and SDK design, but it also seems to be due to the nature of the configuration control and generation. I am using the latest Windows 11 Pro, and the Segger JLink version 7.58b.

For example, I changed a bunch of settings in the Kconfig Actions menu, but then when I do a pristine build they are reset back to their original settings. I even try to over-ride some of these settings within the prj.conf file and it doesn't effect the outcome for some of the settings. As a firmware developer with over 30 years of experience, this approach is way too complicated and very difficult to use. I find it is hard to get anything done with this system, any way I can get this mess to work with IAR tools?

I am currently playing around with trying to get optimization setting changed, but it won't "stick", any suggestions on how to get these config settings to work correctly would be greatly appreciated.

Thanks,

Pam

RE: printk via RTT will not work, but printf does

ovrebekk — Fri, 29 Apr 2022 08:23:26 GMT

Hi Pam

I must admit I don't have a lot of experience using the RTT interface in the nRF Terminal or Ozone, but I was able to get it working without obvious issues.

I made a small modification to one of the Bluetooth examples to print to the RTT log every second, and can see it appear consistently.

Which operating system and version are you running on your PC?

Do you know which version of the JLink DLL you are using?

Best regards
Torbjørn

RE: printk via RTT will not work, but printf does

Pamela Keiles — Wed, 27 Apr 2022 17:19:14 GMT

Hello Torbjørn,

I see what part of the issue might be. I am able to see all the printk statements (as well as log statements I believe) using the Segger RTT Client program. But they are not showing consistently in either the NRF Terminal window within Visual Studio, or the Terminal window within the Ozone debugger. I was occasionally able to see some statements, then nothing. Resetting the processor within the debugger doesn't help, nor does exiting and re-downloading the image. It appears to be very random when it works in those terminal windows, which is rarely.

Thanks,

Pam

RE: printk via RTT will not work, but printf does

ovrebekk — Wed, 27 Apr 2022 13:14:40 GMT

Hi Pam

Is there any particular reason you need to set CONFIG_LOG_PRINTK=n ?

I was able to route the printk message to RTT in the peripheral_uart sample by adding the following configurations only:

CONFIG_UART_RTT=y
CONFIG_RTT_CONSOLE=y

Best regards
Torbjørn

RE: printk via RTT will not work, but printf does

Pamela Keiles — Tue, 26 Apr 2022 16:51:48 GMT

Hi Torbjørn,

Unfortunately that didn't help. I'm thinking the problem might be related to not being able to set CONFIG_LOG_PRINTK=n. I am getting a build error when I try to set it to "n" in the prj.conf file. Also, I think I am not allowed to set it within the Kconfig menu, the option is greyed out. Here is the build error I am seeing:

warning: LOG_PRINTK (defined at c:\Soberlink\soberlink_sfw\trunk_NordicBLE\peripheral_uart\build\subsys\logging\Kconfig.processing:8) was assigned the value 'n' but
got the value 'y'. See docs.zephyrproject.org/.../CONFIG_LOG_PRINTK.html
and/or look up LOG_PRINTK in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

The reason I think the issue might be related to this logging feature is that when I single step through the printk() routine, the code then branches to the routine log_printk() versus vprintk().

Thanks,

Pam

RE: printk via RTT will not work, but printf does

ovrebekk — Tue, 26 Apr 2022 10:33:28 GMT

Hi Pam

Could you try to add the following config as well?

CONFIG_UART_RTT=y

This should fix the issue.

Best regards
Torbjørn