https://devzone.nordicsemi.com/f/nordic-q-a/95506/how-to-view-printk-output-from-observer-sample-projectHi all, I&#39;m sure I must be overlooking something very basic here, but I&#39;m struggling to find a way to view output from printk statements in a sample project I&#39;ve built and flashed. I&#39;m using the nrf5340dk evaluation board with SDK 2.2.0 and VSCodeen-USTelligent Community 13Tue, 10 Jan 2023 19:27:17 GMThttps://devzone.nordicsemi.com/thread/404189?ContentTypeID=1Tue, 10 Jan 2023 19:27:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e7b44b9c-3fdc-4b71-ace2-78287b0a4924cscase<p>I played with this some more, plugged and unplugged, built again, etc., and I&#39;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 &quot;VCOM2&quot; as shown in the lower-left of the screenshot I posted. Thank you, Turbo.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/403941?ContentTypeID=1Mon, 09 Jan 2023 22:06:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0ae7e3b5-2e98-404c-91dd-ffbcdf41f452cscase<p>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.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/403940?ContentTypeID=1Mon, 09 Jan 2023 21:42:25 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e9feeb87-4d05-454b-ad32-6dbce312341aTurbo J<p>Try one of the other COM ports from the DK itself. One of them is the application, one is hooked to the network core.</p> <p>You can check the full config and DTS in the build/zephyr subdir.</p> <p>Careful when resetting the DK Debugger MCU, windows don&#39;t like resets on open COM ports much.</p><div style="clear:both;"></div>