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

Multiple devs have reviewed your logs, and there are just a few reasons the error you're seeing BT_SMP_ERR_UNSPECIFIED after a pairing request have been received should be trigged, so we've narrowed it down somewhat at least.

Can you also add HCI logging so we can get a look there as well. The following configs in prj.conf should do it

CONFIG_BT_DEBUG_HCI_CORE=y

CONFIG_BT_DEBUG_HCI_DRIVER=y

Can you also confirm that the Windows 11 device has removed previous bonds before trying to bond to this device, and that the DK isn't already paired. As we thought we were able to reproduce it for a moment here, but it was fixed by erasing previous bonding information on the two devices.

Best regards,

Simon

[StefiNR]

Everything I wrote on the topic is based on the standard example:

/SDK/ncs/v1.8.0/nrf/samples/bluetooth/peripheral_uart  (/build_nrf5340dk_nrf5340_cpuapp).

I only added, already 4, debug lines. I am attaching the file, they are finally written.

In Windows I removed all Bluetooth devices, there is nothing.

The kit was programmed before the tests with another example, i.e. there should be nothing left.

( I am currently thinking about how to speed up the transmission speeds. How to declare and change: ATT_MTU size, PHY, LE Data Length, LE Connection interval. It was programmed with: Bluetooth: Throughput. After reading the whole forum and other information on the net, I came to the conclusion that it is not clear at all. The standard example (uart) works with intervals of about 100+ ms, 20-bytes packet, string format. I changed everything, now it works with binary transfer, interval about 40ms, 40-bytes packet. BUT that's another question, so I'm not asking anything.

I will post another question in the forum after clarifying some more things.)

 

I don't see any movement in the debug window at the time of connection. I made three attempts.

laptopW11_002.zip