Logging functions disabled for nRF52 DK board

RE: Logging functions disabled for nRF52 DK board

Burt — Tue, 21 Nov 2023 20:38:41 GMT

My bad. Actually __CDT_PARSER__ is defined by nRF Connect for VS Code to calm down Intellisense from trying to parse complicated logging macros (which Intellisense is not capable of doing) from the C/C++ VS Code extension, but it is only used by Intellisense. It has no bearing on the actual build--only what you THINK the build is based on Intellisense and hovering over __CDT_PARSER__ in a file. It does not affect logging, therefore.

RE: Logging functions disabled for nRF52 DK board

Raoul — Mon, 20 Nov 2023 22:01:36 GMT

Noted!

Best regards,

Raoul

RE: Logging functions disabled for nRF52 DK board

Timothy — Mon, 20 Nov 2023 19:04:30 GMT

this can be closed

RE: Logging functions disabled for nRF52 DK board

Raoul — Fri, 17 Nov 2023 00:28:44 GMT

Hi,

Sorry Timothy, my last reply was a bit nonsensical - I missed the printf on the very last line, and so got the impression that logging was partially working.

Burt is right in that looking at a lot of the underlying code won't always make sense as Zephyr makes heavy use of macros and compile time configuration of the implementation files. So if your editor thinks __CDT_PARSER__ is defined, I wouldn't worry too much about it.

I would still recommend you to consult the Dev Academy to get some basic printing and logging set up over uart/rtt. I wasn't able to spot any issues with the config you shared.

Best regards,

Raoul

RE: Logging functions disabled for nRF52 DK board

Burt — Tue, 14 Nov 2023 03:07:52 GMT

Tim,

I don't know what gave you the idea that __CDT_PARSER__ is defined. You are not using Eclipse so that explains why you cannot find it defined. The nRF Connect SDK documentation describes every sample application in the SDK and shows you how to get a logging console for the sample you are working with. There is a lot of Zephyr code included in the logging subsystem; apparently the printf function which is a C library function bypasses all that and goes directly to UART. All we have to know is that there is a bunch of logging subsystem code--the easiest way to deal with that is to simply follow the directions in the sample in which case we never have to know anything much about that logging subsystem. Maybe it helps to know that it has separate "backends" for UART and for RTT. Definitely for you and I who have come from a nRF9160 background it is unexpected that printf and LOG messages go to different places, but it is what it is!

Burt

10/23/2025: please see my correction further down!

RE: Logging functions disabled for nRF52 DK board

Timothy — Mon, 13 Nov 2023 18:38:21 GMT

the LOG_INF is NOT printing. my printf statement is printing. none of the LOG_XXX are printing as I show above. I am using VS Code for all development. the __CDT_PARSER__ is defined somewhere which cause all of the logging statement to be NULL (0). I have no idea where that is defined and why it is blocking things.

this is my code shown below.

printf("V %d.%02d %s%s\r\n",VERSION_MAJOR, VERSION_MINOR, VERSION_DATE,VERSION_DATE_EXT);

LOG_INF("Bluetooth initialized INF");

LOG_WRN("Bluetooth initialized WRN");

LOG_ERR("Bluetooth initialized ERR");

printf("Bluetooth initialized\r\n");

RE: Logging functions disabled for nRF52 DK board

Raoul — Mon, 13 Nov 2023 18:32:45 GMT

Hi again,

Which IDE are you using? Are you actually using CLion? Or just VS Code with our extension?

[quote user="tjm1"]

this is what is printed

V 0.01 Temp/Humidity BLE Sensor 11/11/23 (Bd 1.0 DK)
Bluetooth initialized

[/quote]

Thanks for sharing. It looks to me like your LOG_INF statement is actually printing, so that's a good sign.

But just to be clear, is it cutting off the "INF" at the end of that log statement? And is it not printing the other two statements? Or did you just give me an excerpt?

I need to understand exactly what issue you are seeing.

Also, have you tried logging with UART? Or do you have to use RTT?

Best regards,

Raoul

RE: Logging functions disabled for nRF52 DK board

Timothy — Mon, 13 Nov 2023 15:21:40 GMT

Raoul

thanks for the quick reply. I am not new to NCS. I have been using NCS with the V1.7.0 and nRF9160 for several years.

I am new to nrf52 and V2.5.0. I have the following in my prj.conf file. I have details below. what am I doing wrong.

# Config logger
CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n
#CONFIG_LOG_PRINTK=n
CONFIG_LOG_PRINTK=y

I have the following in my code

printf("V %d.%02d %s%s\r\n",VERSION_MAJOR, VERSION_MINOR, VERSION_DATE,VERSION_DATE_EXT);

LOG_INF("Bluetooth initialized INF");

LOG_WRN("Bluetooth initialized WRN");

LOG_ERR("Bluetooth initialized ERR");

printf("Bluetooth initialized\r\n");

this is what is printed

V 0.01 Temp/Humidity BLE Sensor 11/11/23 (Bd 1.0 DK)
Bluetooth initialized

RE: Logging functions disabled for nRF52 DK board

Raoul — Mon, 13 Nov 2023 10:04:05 GMT

Hi Timothy,

In the nRF Connect SDK, Logging is enabled and configured through the appropriate Kconfig options.

For example to enable logging, you add

CONFIG_LOG=y

to your prj.conf.

I assume you're new to NCS. I would therefore strongly recommend you to start with the NCS fundamentals course on our Developer Academy:

https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/

It covers logging as well, if you want to skip straight to that:

https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-3-printing-messages-to-console-and-logging/topic/exercise-2-4/

Best regards,

Raoul