How to view printk output from observer sample project?

[cscase]

Hi all,

I'm sure I must be overlooking something very basic here, but I'm struggling to find a way to view output from printk statements in a sample project I've built and flashed.

I'm using the nrf5340dk evaluation board with SDK 2.2.0 and VSCode.

I've built and flashed the observer sample project to the board. The project I'm referring to is here: https://github.com/nrfconnect/sdk-zephyr/tree/main/samples/bluetooth/observer#id3

This project passively monitors Bluetooth traffic and outputs to printk.

I've connected to each serial port in available on my system with settings n/8/1, 115200 baud, and then reset the 5340dk while watching for serial traffic. I see nothing on any of the available ports. A screenshot below shows, at lower-left, the ports I have visible in VSCode.

I went into my prj.conf and added CONFIG_CONSOLE=y, however when I do that a tooltip says something to the effect of, "Sure, okay, but this was already set in another file so you don't need it here."

I've also poked around in other config/dts files - see my screenshot - and it looks like default console is set to uart0, which I think should be the default. Then, while looking in this file, I see a 20 and 22, so I wondered if maybe this is saying the UART pins are on port 0, pins 20 and 22. So, using an extern USB to serial adapter, I looked on these pins for serial traffic, and again I see nothing.

What am I missing?

Thanks for any help you might be able to offer!

Scott

[Turbo J]

Try one of the other COM ports from the DK itself. One of them is the application, one is hooked to the network core.

You can check the full config and DTS in the build/zephyr subdir.

Careful when resetting the DK Debugger MCU, windows don't like resets on open COM ports much.

[cscase]

Yes, I did try all three of the ports available. These are the three shown in the screenshot: COM5, COM8, COM9 in my case. I am not getting anything on any of those, using the built-in terminal in VSCode, or using TeraTerm. So it sounds like that is indeed where I should expect the output to show up. Just not sure where to look next to determine the cause of the breakdown.

[cscase]

I played with this some more, plugged and unplugged, built again, etc., and I'm not sure what ultimately did the trick but it started working. I found that, at least in my case, the printk output is going to "VCOM2" as shown in the lower-left of the screenshot I posted. Thank you, Turbo.