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

From what I can find through googling, there seems to be some issues with BLE not working properly on Windows 11, so that might be it. I'm currently in my home office without a laptop with BLE available, but I can test this on my end when I go to the office on Monday. 

In the meantime, can you try downloading and opening the J-Link RTT viewer so we can get a better picture of why the nRF53 DK is disconnected when Windows returns this "try again" message, as it should provide debug logging/information in the peripheral_uart example.

Alternatively, if you have a spare nRF52DK or Dongle, you could check out the nRF Sniffer and take a sniffer trace of the connection so we can see what goes on on the air between the two devices.

Best regards,

Simon

[StefiNR]

Twice attempt to add device to each file. Row 435 LTK key ?? I don't even know what that means. And why he repeats the commands twice is also strange to me.I tried to record how the laptop connects to the phone, but the sniffer doesn't detect it at all. I tried several times.

LaptopW11.zip

[Simonr]

Disconnect reason 19 (0x13) indicates that the remote user terminated the connection (defined in ble_hci.h). This means that if you're seeing it on the central side, the peripheral is disconnecting for some reason. What does the device not reporting the 19 (0x13) reason return when the disconnect occurs?

We have some common sniffing actions that describes how to for example follow a device into a connection and captura the data sent between them. You should also check out the nRFSniffer User Guide for detailed information on how to set it up. Are you able to sniff advertising data at all or are you struggling to get the sniffer up and running at all?

Best regards,

Simon

[StefiNR]

I do not understand exactly what you are asking me. The file I uploaded in the previous post is exactly a recording of the process of connecting between the laptop and the board. The sniffer works normally. I have uploaded only one file in the zip file, because all records are the same. It is pointless to attach several files with the same record. I recorded for about an hour (about 50 attempts) and I tried to see some difference between them, there is no difference, the commands are the same. I wrote down how the phone connects (I didn't apply it), but there the commands are different. The laptop connects to everything else, but not to the board.

In nRFSniffer User Guide nothing special is written, I read it too.

As I wrote in the beginning, my first post on the subject, the laptop connects briefly, the LED lights up, and then disconnects. I don't know why this is happening.

The board is also programmed and works normally, because when I connect the phone to it, I can stay connected indefinitely, even without using Nordic software.

[Simonr]

Yes, it's a recording of the connection from the board' s point of view, correct? The disconnect message points to the disconnect being caused by the remote user (the computer in your case). Does the computer not report any reason what so ever as to why it disconnects from the nRF?

Again, from your description this sounds like the issues reported for BLE not working as intended on Windows 11. Can you upload the sniffer log as well. To "follow" a peripheral into a connection it should be sufficient to select the board from the device list in Wireshark during advertiisng, and then connect the central to that same peripheral.

Best regards,

Simon