How to see LOG_INF, LOG_WRN messages, preferably in real time

[DiBosco]

Al over these example programs there are all these messages like

LOG_INF("Filters matched. Address: %s connectable: %d",

addr, connectable);

How do you actually *see* them? The best bet would be have them spit out over the USB

connection that's

used for the built in debugger. I've seen some pages suggesting this might be true,

but I just can't

understand what any of them are saying.

I've seen this for example:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.4.99-dev1/kconfig/CONFIG_LOG_DEFAULT_LEVEL.html

And it casually says things like this:

At <nRF>/samples/Kconfig:33

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:9 → <BuildDir>/Kconfig/Kconfig.modules:1 → <nRF>/Kconfig.nrf:24

Menu path: (Top) → Modules → Nordic nRF Connect

I have absolutely no idea what this is saying.

Are there some explicit instructions somewhere that says:

You need open this menu up from this part of VSC, click here, go to sub

menus X, Y & Z to this line and change it say

DEBUGGING_OUT_OF_JLINK=y

Or whatever it should be.

All I want to see is what these messages are saying in real time. With any normal

debugging system

I'd set a breakpoint and single step though looking at registers to see

what's going on. Or in extreme cases use

a UART to spit out some info, but I'm already using the UART to

[try to] send info in and out over BLE.

Thanks

[Sigurd]

Hi!

The nRF52840 has 2 UARTE instances, so you can use one for logging and the other your application.

[DiBosco]

Thanks, but that doesn't really help in terms of how you'd assign it, set it up, point the debugging info/LOG messages etc to the different UART  and it doesn't address whether it's possible with minimal effort with the segger interface.

[Sigurd]

How do you actually *see* them?

If you are already using a sample that uses LOG messages, and looking for a tool that sees the logs, then I suggest either:

1) If you are using VS Code, we have the nRF terminal:

https://marketplace.visualstudio.com/items?itemName=nordic-semiconductor.nrf-terminal

2) You could also use our Serial Terminal app:

https://docs.nordicsemi.com/bundle/nrf-connect-serial-terminal/page/index.html

[DiBosco]

I do have the extension pack installed, but there's no nrf terminal available. There's nrf  serial  terminal and nrf debug.

[DiBosco]

Sorry to mither, but any chance of a reply on this please?

[Sigurd]

easiest way to open COM port in VS code, is to do it from the Connected device view:

https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/reference/ui_sidebar_connected_devices.html#view-actions

https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/bd_work_with_boards.html#how-to-connect-using-serial-port

[DiBosco]

Hi, Sorry to be a pain, but this isn't helping me at all.

I can see those connected devices, but what do I do with them? How do I get things like this:

LOG_ERR("could not start the discovery procedure, error "

"code: %d", err);

LOG_INF("MTU exchange done");

LOG_WRN("MTU exchange failed (err %" PRIu8 ")", err);

Appearing somewhere? I am guessing they get stored in a log
file somewhere? Where? And even better can I make them appear,
in real time, in some kind of debug window, whether it be a
standard serial terminal like Cutecom, or in VSC?

If it is possible what are the exact steps needed to make this
happen?

I did manage after hours of trying one thing and another to get

stuff coming out of /dev/ttyACM0 in a termninal window on VSC, but

it just shoves out exactly

what comes out of the standard UART.

[DiBosco]

I think I finally might have got somewhere with  this. Found a third party article that explains it a bit more clearly. Am finally getting some stuff spat out to Terminal in  VSC.