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

Thank you for these files. From the sniffer trace you sent, it seems like the central just stops responding. I think you should be able to get an error code (hexadecimal) on the Windows side. It's very strange that you're not able to see any disconnect reason or connection/pairing failure on that side. 

Best regards,

Simon

[StefiNR]

Where can I get this error code?

 

I trained for almost an hour and found the following:

 

1 / When this line is active (.passkey_confirm = auth_passkey_confirm,),

 immediately after pressing the connect button, the connection is broken. What's going on is in my previous posts.

2 / When the line is off (//.passkey_confirm = auth_passkey_confirm,),

there are two options that I do not know what they depend on.

* In 9 out of 10 cases, after pressing add device, it waits 4 seconds and the connection breaks down. It is not possible to enter the PIN during this short time.

* In 1 out of 10 cases, it waits for the PIN to be entered, and then breaks down.

 

I was filming a short video of what was happening. I apologize for the poor quality, but I hold the phone with one hand, look at two monitors at the same time and look for the mouse on the screen. At the end of the video, it happened to wait for the PIN code to be entered, but it fell apart again. There is no error code anywhere.

 

The clip is MP4, you better download it to your computer and then watch it.

stivi.eu/.../VID_20220127_120125.mp4

[Simonr]

Hi

The link you provided is broken I'm afraid and I'm not able to open it or download the file. Are you able to upload it as a .mp4 file or in a .zip file? I would think you would see the error code pop up once the connection fails, but I guess that's not happening. You should also see the error code in the Device Manager I think though. Under Bluetooth Devices there you could check if you're able to see a device with a warning triangle or similar.

Best regards,

Simon

[StefiNR]

The link works normally, the file is MP4. I tried it on WinXP, Win10, Win11, Firefox, Edge. You either choose to download it or watch it directly in the browser.

I guess you use Linux and it has restrictions on paths and names. Or you have some kind of restriction somewhere. Anyway. The first new link I gave is on the same file, but renamed (the old link also works).

https://stivi.eu/bg1/data/lw1100.mp4

 

The second link in the case where the row is allowed.

.passkey_confirm = auth_passkey_confirm;

There are no errors, a warning triangle or anything like that.

https://stivi.eu/bg1/data/lw1101.mp4