Connect a Laptop with Windows to Peripheral UART example

[StefiNR]

Sure, my question is very stupid, but after one day I found nothing to explain the principle of the situation, I decided to ask.

I have a laptop with built-in Bluetooth 5.2 and Windows 11. It runs a terminal testing program.

I have nRF5340 DK with the example Peripheral UART installed (nRF Connect SDK1.8.0). The board works normally, I tested it with a phone with Android and nRF Connect for Mobile. Everything is working fine. The board is connected to a desktop computer on which a terminal program is running and connected to COM port ( not USB).

Windows (laptop), sees the board. After pressing adding device (on Win), the LED on the board (connected) lights up for 1 second, Windows thinks about 5 seconds, and says try again. I imagine that it will connect to the board, and a window will appear to install a serial port to which I can connect through the terminal program. No PIN display window appears. I tried to quickly press button 1, possibly to confirm, nothing. I can transmit data over the phone without the board being BONDED. Let me just say that I've been doing Nordic for 6 months, and I've learned some things. But here I can't even imagine what should happen. Google didn't help either. Does anything else need to be installed on the board?

In the final version, it should be a remote device to which with any laptop with Bluetooth 5.2, to be able to connect and through a terminal program to exchange data via serial port.

[Simonr]

Hi

There are a lot of dropped log messages here, making it very hard to get something useful from this log...

Best regards,

Simon

[StefiNR]

I've seen it, but I don't know why. I didn't write the software to know. The laptop and the board are on my desk, at a distance of about 70 cm. Here are two more files without the sniffer activated, so as not to affect anything. There is nothing working wirelessly on the table. except my mouse and keyboard, which are certainly not Bluetooth. I have been dealing with the boards for almost 6 months for sure, and in all other cases, when testing different examples, nothing prevents them.

laptopW11_03.zip

[Simonr]

Try increasing the log buffer size by changing a Kconfig variable named CONFIG_LOG_BUFFER_SIZE, also try setting CONFIG_LOG_MODE_IMMEDIATE or CONFIG_LOG_MODE_MINIMAL, as this should fix the dropped log issues.

Best regards,

Simon

[StefiNR]

Without changing the size of the buffer (CONFIG_LOG_BUFFER_SIZE), after starting the board, you can see what I sent the previous time. All these dropped packages. The laptop is not turned on at all and no connection attempts have been made. This is how the software works. The board stands and waits. I experimented with different values, no difference. From some value upwards it is the same. There are written explanations inside the file. Now I don't see any dropped packages. CONFIG_LOG_MODE_IMMEDIATE or CONFIG_LOG_MODE_MINIMAL I haven't used these, I wrote it down before you write these two.

Debug_Terminal.zip