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

It should be sufficient to set CONFIG_BT_DEBUG_LOG=y in the prj.conf file of your project. 

Best regards,

Simon

[StefiNR]

At least I don't see any more information. I think there is a timeout that is running out.

[00:00:00.512,329] <inf> fs_nvs: 2 Sectors of 4096 bytes
[00:00:00.512,329] <inf> fs_nvs: alloc wra: 0, f70
[00:00:00.512,359] <inf> fs_nvs: data wra: 0, dc
[00:00:00.534,667] <inf> bt_hci_core: No ID address. App must call settings_load()
[00:00:00.534,698] <inf> peripheral_uart: Bluetooth initialized
[00:01:13.407,714] <inf> peripheral_uart: Connected 5C:FB:3A:53:9C:3A (public)
[00:01:14.162,231] <inf> peripheral_uart: Passkey for 5C:FB:3A:53:9C:3A (public): 426108
[00:01:14.162,231] <inf> peripheral_uart: Press Button 1 to confirm, Button 2 to reject.
[00:01:24.005,706] <wrn> peripheral_uart: Security failed: 5C:FB:3A:53:9C:3A (public) level 1 err 9
[00:01:24.005,828] <inf> peripheral_uart: Pairing failed conn: 5C:FB:3A:53:9C:3A (public), reason 9
[00:01:24.006,011] <inf> peripheral_uart: Disconnected: 5C:FB:3A:53:9C:3A (public) (reason 8)
[00:01:34.948,791] <inf> peripheral_uart: Connected 5C:FB:3A:53:9C:3A (public)
[00:01:35.463,623] <inf> peripheral_uart: Passkey for 5C:FB:3A:53:9C:3A (public): 051090
[00:01:35.463,623] <inf> peripheral_uart: Press Button 1 to confirm, Button 2 to reject.
[00:01:38.374,816] <inf> peripheral_uart: Numeric Match, conn 0x20000a60
[00:01:45.307,098] <wrn> peripheral_uart: Security failed: 5C:FB:3A:53:9C:3A (public) level 1 err 9
[00:01:45.307,220] <inf> peripheral_uart: Pairing failed conn: 5C:FB:3A:53:9C:3A (public), reason 9
[00:01:45.307,403] <inf> peripheral_uart: Disconnected: 5C:FB:3A:53:9C:3A (public) (reason 8)