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 Stefan

From your latest log files there are two specific lines that stick out:

[00:01:15.743,469] <dbg> bt_hci_core.le_phy_update_complete: PHY updated: status: 0x00, tx: 2, rx: 2
...
[00:01:25.407,653] <dbg> bt_hci_core.hci_disconn_complete_prio: status 0x00 handle 15 reason 0x08

Reason 0x08 is a connection timeout, so the connection seems to time out shortly after switching to the 2MBPS PHY. Maybe Windows 11 (or the laptop's Bluetooth controller) doesn't like the PHY changing during the pairing process. Please try disabling the PHY update by setting CONFIG_BT_PHY_UPDATE=n. You can also try increasing the supervision by setting CONFIG_BT_PERIPHERAL_PREF_TIMEOUT to a larger value.

Best regards,

Simon

[StefiNR]

Connects !, I tried several times, all successful. Only the CONFIG_BT_PHY_UPDATE=n option is enough.

But there is no Serial Port anywhere. It does not appear anywhere when the device is added. I tried tot add, through advanced Bluetooth settings, there it does not appear as a device to which to add a serial port. I also tried through the properties of the device, services, there is an empty field.
I have a feeling that because windows add it as "Category: Heart Rate Monitor", that's why he doesn't want to add a serial port.