Academy course: Bluetooth Low Energy Fundamentals, no UART log

RE: Academy course: Bluetooth Low Energy Fundamentals, no UART log

keithauhk — Mon, 18 Aug 2025 02:09:52 GMT

Hi Benjamin,

I just reviewed this and found I have wrongly chosen "nrf52kbd/nrf52832" as Board target.

I changed it to "nrf52dk/nrf52832" and now works.

Thanks for your help!

RE: Academy course: Bluetooth Low Energy Fundamentals, no UART log

Benjamin — Tue, 17 Jun 2025 07:49:45 GMT

Hi,
Your settings looks correct to me. I went through the build steps now with the same DK that you are using and everything works without changing anything.

Have you changed any other file or setting?

Also, make sure you have the latest software installed. I recommend going though the installation steps in the fundamentals course.

Best regards,
Benjamin

RE: Academy course: Bluetooth Low Energy Fundamentals, no UART log

keithauhk — Mon, 16 Jun 2025 01:06:38 GMT

Hi Benjamin,

Thanks for your reply.

I can get UART output normally with other sample codes from NCS v3.0.1. So, the problem should not be caused by Windows setup.

For those BLE Fundamentals examples, the settings that I am using is "Board target" -> "nrf52dk/nrf52832" and "Base configuration files" -> prj.conf. Would there anything that I have missed?

Thank you!

Regards,

Keith

RE: Academy course: Bluetooth Low Energy Fundamentals, no UART log

Benjamin — Fri, 13 Jun 2025 11:59:54 GMT

Hi Keith,

Thanks for reaching out!

Which operating system are you using? Does this issue occur with one specific exercise or across all of them? And have you tried building and flashing the exercise solution? In the BLE Fundamentals course, you shouldn't need to modify the prj.conf file to enable logging, as it's already set up for you.

UART logs are sent to the serial terminal. By default, UART0 appears as a COM port on Windows or a ttyACM device on Linux or macOS. Make sure you're connected to the correct serial terminal (usually VCOM0). This is done by selecting the plug icon on VCOM0 in the Connected Devices menu. You should see the output logs directly in VS Code.

You can also use another terminal program if you prefer, as long as it's pointed to the correct port or device.

Be sure the baud rate is set to 115200. Also, there could be issues if you have multiple instances opened of a port/device. If you read from the port/device in you normal terminal you will not see output in the VSCode terminal.

If not done already, also check out Lesson 4 of the NCS Fundamentals course as this explain logging and printing over UART step by step.

Best Regards,
Benjamin