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

Have you checked out the Working with nRF5340 DK guide in the nRFConnect SDK documentation? It describes how to build the APP or NET core of the nRF5340. You generally have to flash the NET and APP core separately unless you merge them yourself. In BLE applications, usually the NET core is flashed with the Bluetooth: HCI RPMsg sample, and the application core is flashed with one of the Bluetooth samples.

Best regards,

Simon

[StefiNR]

Even when it was 1.7.1 (nRF Connect SDK), that's exactly what I did. I opened an example ( from Bluetooth samples ) and generated the project with SEGGER, then I only worked with it. Then I started the NRF Connect Programmer, threw the hex file for the net core and programmed it. I haven't changed it since. I experimented with different examples, they all worked fine (there were old declarations for improvement, but nothing special). I haven't touched the net core.

After that, everything was updated (nRF Connect SDK 1.8.0), and I decided to try a little more seriously what works. And then I tried the laptop, and I saw that nothing was happening. Until then, I only tried with a phone.

========================

The net core I reprogrammed accordingly. this:

developer.nordicsemi.com/.../ug_nrf5340.html

 

No difference, it still can't connect. Same error:

[00:00:09.601,135] [0m<inf> peripheral_uart: Connected 5C:FB:3A:53:9C:3A (public)[0m

[00:00:10.182,373] [0m<inf> peripheral_uart: Passkey for 5C:FB:3A:53:9C:3A (public): 004792[0m

[00:00:10.182,403] [0m<inf> peripheral_uart: Press Button 1 to confirm, Button 2 to reject.[0m

[00:00:18.688,446] [0m<inf> peripheral_uart: Numeric Match, conn 0x20000a60[0m

[00:00:19.965,484] [1;33m<wrn> peripheral_uart: Security failed: 5C:FB:3A:53:9C:3A (public) level 1 err 9[0m

[00:00:19.965,606] [0m<inf> peripheral_uart: Pairing failed conn: 5C:FB:3A:53:9C:3A (public), reason 9[0m

[00:00:19.965,911] [0m<inf> peripheral_uart: Disconnected: 5C:FB:3A:53:9C:3A (public) (reason 8)[0m

 

What is level 1 err 9?