Logging functions disabled for nRF52 DK board

[Timothy]

I have the nRF52 DK board and I am loading the peripheral_uart example. All works fine I can compile and flash and connect to iPhone. There is no problem with the application. I just want to be able to turn on logging. there is a line in log.h as shown below that shows _CDT_PARSER_ as "#define _CDT_PARSER_ 1". I do not see how or where this is set and how I undefine or disable it.

if _CDT_PARSER_ is defined as a 1 then all logging functions will be 0. What am I doing wrong? I am new to nRF52 DK tools so I am sure it is operator error.

/*

 * Eclipse CDT or JetBrains Clion parser is sometimes confused by logging API

 * code and freezes the whole IDE. Following lines hides LOG_x macros from them.

 */

#if defined(__CDT_PARSER__) || defined(__JETBRAINS_IDE__)

#undef LOG_ERR

#undef LOG_WRN

#undef LOG_INF

#undef LOG_DBG

#undef LOG_HEXDUMP_ERR

#undef LOG_HEXDUMP_WRN

#undef LOG_HEXDUMP_INF

#undef LOG_HEXDUMP_DBG

#define LOG_ERR(...) (void) 0

#define LOG_WRN(...) (void) 0

#define LOG_DBG(...) (void) 0

#define LOG_INF(...) (void) 0

#define LOG_HEXDUMP_ERR(...) (void) 0

#define LOG_HEXDUMP_WRN(...) (void) 0

#define LOG_HEXDUMP_DBG(...) (void) 0

#define LOG_HEXDUMP_INF(...) (void) 0

#endif

[Raoul]

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

[Timothy]

this can be closed

[Raoul]

Noted!

Best regards,

Raoul

[Burt]

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.