Connect a Laptop with Windows to Peripheral UART example

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Wed, 16 Feb 2022 07:50:25 GMT

Okay, thank you for clarifying. That is noted, and I have reported this to our documentation team.

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Tue, 15 Feb 2022 11:21:53 GMT

So consistently:

1. I'm not talking about USB at all, I'm not commenting on how the COM ports are presented and in what sequence, after passing through JLINK and being seen in Windows.

2. An example would be for this: peripheral_uart

3. In main.c -> uart_init() , row 238, uart = device_get_binding(CONFIG_BT_NUS_UART_DEV);

CONFIG_BT_NUS_UART_DEV = uart0

from Kconfig -> row 30, config BT_NUS_UART_DEV default "UART_0"

That is, we should use uart0 purely hardware in the processor.

In this file PCA10095_Schematic_And_PCB.pdf

page 2, uart0 does not exist, the count starts from 1. We assume that we are looking for uart1 according to the scheme. This must be P1.00/P1.00 pins.

In page 4, top left UART_1 and VCOM0 are connected to the same U25. This is the first port, according to the count, i.e. so far everything is fine.

P1.00/P1.00 pins are on the P3 terminal.

Here https://infocenter.nordicsemi.com/index.jsp?topic=%2Fstruct_nrf53%2Fstruct%2Fnrf5340.html

nRF5340 DK Hardware -> Virtual COM ports

nRF5340 UART_1 is the same - P1.00/P1.00 pins. (uart0 missing) (OK)

****

However, the data (from uart0 in software) go to P24: P0.20 / 0.22 (uart2). There I connected my logic analyzer to see them. There is nothing on the other pins.

It is this way because in (board folder files) nrf5340_cpuapp_common.dts, rows 142-149, pins are set to 20/22.

It is not clear where the other serial ports should go (must be set) if someone decides to use them. In any case, the signals through the board will pass through other chips, not as described in the wiring diagram.

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Tue, 15 Feb 2022 10:28:17 GMT

Just to make sure, you're talking about USB connector J2 on the nRF5340 DK, correct? By default, the UART connections should go to the Interface MCU and then to the USB connector from P0.19-P0.22 for one UART, and P0.10, P0.11, P1.00 and P1.01 for the other. Both of these should be routed to the interface MCU, but are also routed to pin headers that can be "activated" if required. See section 3.2 in the nRF5340 DK user guide for details. If you disagree, can you describe what pins you mean they're going to by default? If there are any mistakes here we of course want to correct it.

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Mon, 14 Feb 2022 13:20:11 GMT

So much on this topic here. I accept that you have answered everything that interests me. Thank you for your cooperation.

Regarding the COM port of nRF5340DK. The description is wrong. It's not about the USB port to the computer at all. I connected a logic analyzer to monitor the communication between two boards. Good thing it was the Altium project to find out where to connect my analyzer. Accordingly, the signal passes through other switches, etc. According to the wiring diagram and the declaration in the project, uart0 must be connected on other pins. That's why I wrote that if someone makes a board to plug into the kit and expects the pin signals according to the wiring diagram in your documentation, he will be very badly surprised. Adjust it if you want.

So much here.

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Mon, 14 Feb 2022 12:54:08 GMT

Below are my answers to what I picked up as questions from your latest reply. Let me know if I missed some, or if you have further questions. Please note that it's easier to catch them all if you list your specific questions. Also, since this case has moved on from it's initial topic, I would recommend that you create a new DevZone ticket if you have a new issue or require technical support on a different topic.

nRF5340 DK COM ports: COM ports you're seeing are UART0, UART1, and you can choose from the device manager which ones you want to use in I.E. a terminal.

peripheral_uart sample: This sample data received on the RX pin of the UART0 peripheral to the BLE unit. By default, the UART 0 peripheral is gated through the interface MCU to connector J2. To make use of the USB peripheral instead I would suggest checking out the HCI USB sample in Zephyr instead, which is designed to make a USB Bluetooth Dongle from Zephyr.

Your use case: I understand it as the "remotes" you mention will be nRF5340 devices, correct? And you want to transmit data from these devices over BLE to the computers, which will forward that data to a USB device, correct? Forgive me if I misunderstand anything. The transmission speed (throughput) you mention might be an issue, depending on how many bytes you plan on transmitting at a time. As explained in this blog post, the maximum throughput we're able to achieve with BLE 5 will be ~1400.56 Kbits/s, but that will also depend on the BLE module on the computer's side. If that is sufficient in your case, I don't see any issue this wouldn't be possible. Will the device connected to the computer also be an nRF device? If so you can communicate directly with the nRF instead of having to go through the computer first.

Encryption should not be an issue either. The nRF53 series use the Bluetooth LE bond module for managing BLE peers and bonds. The computer generally handles this by "choosing" pairing when you connect to a device I believe.

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Sun, 13 Feb 2022 10:38:24 GMT

This idea with HID is good, but for some next stage eventually. It cannot be used at the moment.

The Dongle idea also has bread in it, but I don't understand something here. I will think about something on the topic in the future. From a consumer point of view, this will be a board with a Nordic chip that has a USB port that is connected to the USB port on the board. It doesn't matter who the manufacturer is. And nRF52840 Dongle happens, or something like that (I don't see the point in putting a powerful processor for a simple USB converter > Bluetooth / Virtual COM for Windows). Why the two examples are not compatible with it (central/peripheral uart). It is clear to me that there is no J-Link on the board, and the development environment (VSC/SEGGER) cannot recognize it (and here there is one but), but there is a nRF Programmer (he recognizes it). Yes, I know, bootloader 1, bootloader 2, etc. Even I did not understand what was happening. Why you can't compile and program with it. I think this is the main application of this board, apart from the sniffer. Simply put on a computer / desktop for example / to provide LBE for tests and experiments with other LBE boards. If necessary, make two special examples of this type of board, which can be programmed only through the programmer.

On nRF5340DK there is some confusion with com ports. It is not clear how they are counted, and from how much they start, from 0 or from 1. There is some other counting in the documentation. The software usually uses Uart0, which if the first of the possible and should be on P1.00 / 1.01. But in reality, the data that come out through the USB port(J-Link) appear on P0.20 / 0.22 (Uart2 from PCA10095_Schematic_And_PCB.pdf). If someone makes a board that plugs into the kit, will be quite unpleasantly surprised without checking all the signals where they are output.

Out of pure curiosity, I decided to compile for the USB port, which is directly to the SOC. After 6 hours of fighting and experimenting with punctuation I gave up, there is some mistake somewhere. (\SDK\ncs\v1.8.0\nrf\samples\bluetooth\peripheral_uart)

VSC:

Configuration -> prj_cdc.conf

Extra CMake arguments -> -DDTC_OVERLAY_FILE="usb.overlay"

The file is attached.

I wondered what I would see on the computer after plugging in the cable.

Otherwise, at the moment the situation is as follows, I wrote it in my other topic. There is service software that connects through a serial port to our electronics. The software is very complex and large, probably generating 400-500 different commands through the serial port. It is installed on a laptop. We are currently working with USB> RS485 converter. My colleagues travel all over the country and work at different sites. He goes to the place, takes off the equipment, connects the USB cable to the machine and works. Usually 10-20 meters from the machine. This thing can happen several times a day. Currently, a 4-port hub is glued to each laptop. When one port breaks down mechanically, it goes to the other. So, after about 6 months, the hub changes because all its ports are broken (the cable itself is a separate thing).

Everything is set up in real time, the setting is done while the machine is running, this is how our electronics are made. The commands are up to 40 bytes long (that's the size of the buffers). Usually, one command is 2-3 ms long. After about 100-150 microseconds, the other board starts to respond. That is, this is the time between the last byte of the command and the first byte of the response. The interval between each two commands is 3 ms. Some commands have no response. Over time, the information that is transmitted increases, and now the RS-485 is slow. I expected to speed up at least a little with Bluetooth. I saw that the minimum times for Bluetooth are 7.5 ms in one direction. And to remove the mechanical connection to the USB.

This is about the connection between the laptop and the machine.

It is now planned to offer wireless remote control to customers to control the machine. WIFI doesn't work here because it consumes a lot of electricity. The connection must be encrypted, separately inside there is a second encryption in the packets themselves. The PIN code must be fixed and saved in advance, not visible anywhere (but programmed by my colleague on site at the client.). Separately, after an internal command check, the connection may be disconnected, if the device is not recognized.

The commands run constantly, they are looped, the times inside the machine are the same.

A second processor will receive all the internal data, extract the necessary data, and transmit it via Bluetooth to the remote control. About 1-1.5k bytes in the worst case, 5-10 times per second. This is necessary for everything to be smooth. For example, an operator to move the joystick and see the movements in the machine, at the same time there must be feedback/status with indications of what is happening, among other things.

The colleague with the laptop must connect with the laptop, both to the machine and the remote and set them up in real time. At the moment, all this will work with the RS-485, but it is inconvenient to work. (without remote it works right now.)

CANBUS is not used because it has many problems and is unusable in our case. But that's another topic.

And it is planned that everything will go to LAN in the machine. The connection to the laptop will be WIFI or Bluetooth, but the remote-machine remains on Bluetooth for sure. The remote may have an E-Ink display with a second processor.

But this process is smooth, and we need to keep the maintenance of the old electronics and our customers.

In general, the task is interesting. 🙂

devzone.nordicsemi.com/.../err.txt

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Fri, 11 Feb 2022 14:47:22 GMT

It might be worth looking into the HID profile. It won't give you a direct connection to a serial console, but you can connect directly to the computer and provide various services. For starters the HIDS mouse or HIDS keyboard sample projects might be worth looking at. Or do you specifically need the serial console?

If you share some information on what the end goal of your application is, that might help us find out what service would be best to use to communicate with the computer as you wish.

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Fri, 11 Feb 2022 10:54:02 GMT

Bad very bad. It was the idea of everything to connect the laptop to the device via Bluetooth. But I don't know in what language software should be written to connect to the device that was added to Windows. This device is currently unusable in Windows. The most important thing was not to plug anything into the ports of the laptop, because in a few months they die purely mechanically from turning on and off USB devices. I need to seriously rethink the whole strategy.

Thank you for your cooperation and time.

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Fri, 11 Feb 2022 10:00:30 GMT

I see, that would be the Bluetooth Classic profile Serial Port Profile (SPP). This is not supported in BLE unfortunately, so this won't be possible with nRF5x series devices, which only support BLE. You will need some sort of Dongle that is connected serially to the computer to get up a serial port on the PC.

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Thu, 10 Feb 2022 09:30:01 GMT

Are you expecting to see a serial port on the PC side when the device is connected over BLE.

Exactly!

Until now, when I used Bluetooth modules, older versions, when I connect/add to them, a serial port appears in Windows. Once this device is added, Windows remembers it. From the software I use, just select opening port (COM XXX) and Windows connects to this device. It doesn't matter for the software whether this port is Bluetooth, a physical port, or an adapter cable (USB to XX converter).

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Thu, 10 Feb 2022 07:06:19 GMT

Glad to hear you're able to connect now Stefan!

Regarding the serial port. Are you expecting to see a serial port on the PC side when the device is connected over BLE, or is it also connected to the PC serially and you don't see any logging?

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Wed, 09 Feb 2022 10:30:03 GMT

Connects !, I tried several times, all successful. Only the CONFIG_BT_PHY_UPDATE=n option is enough.

But there is no Serial Port anywhere. It does not appear anywhere when the device is added. I tried tot add, through advanced Bluetooth settings, there it does not appear as a device to which to add a serial port. I also tried through the properties of the device, services, there is an empty field.
I have a feeling that because windows add it as "Category: Heart Rate Monitor", that's why he doesn't want to add a serial port.

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Wed, 09 Feb 2022 08:27:21 GMT

Hi Stefan

From your latest log files there are two specific lines that stick out:

[00:01:15.743,469] <dbg> bt_hci_core.le_phy_update_complete: PHY updated: status: 0x00, tx: 2, rx: 2
...
[00:01:25.407,653] <dbg> bt_hci_core.hci_disconn_complete_prio: status 0x00 handle 15 reason 0x08

Reason 0x08 is a connection timeout, so the connection seems to time out shortly after switching to the 2MBPS PHY. Maybe Windows 11 (or the laptop's Bluetooth controller) doesn't like the PHY changing during the pairing process. Please try disabling the PHY update by setting CONFIG_BT_PHY_UPDATE=n. You can also try increasing the supervision by setting CONFIG_BT_PERIPHERAL_PREF_TIMEOUT to a larger value.

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Tue, 08 Feb 2022 10:59:42 GMT

Without changing the size of the buffer (CONFIG_LOG_BUFFER_SIZE), after starting the board, you can see what I sent the previous time. All these dropped packages. The laptop is not turned on at all and no connection attempts have been made. This is how the software works. The board stands and waits. I experimented with different values, no difference. From some value upwards it is the same. There are written explanations inside the file. Now I don't see any dropped packages. CONFIG_LOG_MODE_IMMEDIATE or CONFIG_LOG_MODE_MINIMAL I haven't used these, I wrote it down before you write these two.

devzone.nordicsemi.com/.../Debug_5F00_Terminal.zip

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Tue, 08 Feb 2022 07:43:30 GMT

Try increasing the log buffer size by changing a Kconfig variable named CONFIG_LOG_BUFFER_SIZE, also try setting CONFIG_LOG_MODE_IMMEDIATE or CONFIG_LOG_MODE_MINIMAL, as this should fix the dropped log issues.

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Mon, 07 Feb 2022 14:00:01 GMT

I've seen it, but I don't know why. I didn't write the software to know. The laptop and the board are on my desk, at a distance of about 70 cm. Here are two more files without the sniffer activated, so as not to affect anything. There is nothing working wirelessly on the table. except my mouse and keyboard, which are certainly not Bluetooth. I have been dealing with the boards for almost 6 months for sure, and in all other cases, when testing different examples, nothing prevents them.

devzone.nordicsemi.com/.../laptopW11_5F00_03.zip

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Mon, 07 Feb 2022 12:44:03 GMT

There are a lot of dropped log messages here, making it very hard to get something useful from this log...

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Fri, 04 Feb 2022 12:55:22 GMT

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.

devzone.nordicsemi.com/.../laptopW11_5F00_002.zip

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Fri, 04 Feb 2022 11:18:06 GMT

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

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Thu, 03 Feb 2022 08:02:27 GMT

[00:00:00.448,089] [0m<inf> fs_nvs: 2 Sectors of 4096 bytes[0m
[00:00:00.448,089] [0m<inf> fs_nvs: alloc wra: 0, f70[0m
[00:00:00.448,089] [0m<inf> fs_nvs: data wra: 0, dc[0m
[00:00:00.469,238] [0m<inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)[0m
[00:00:00.469,238] [0m<inf> bt_hci_core: HW Variant: nRF53x (0x0003)[0m
[00:00:00.469,238] [0m<inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 223.20160 Build 1719410646[0m
[00:00:00.470,153] [0m<dbg> bt_smp.bt_smp_init: LE SC enabled[0m
[00:00:00.470,489] [0m<inf> bt_hci_core: No ID address. App must call settings_load()[0m
[00:00:00.470,489] [0m<inf> peripheral_uart: Bluetooth initialized[0m
[00:00:00.473,022] [0m<inf> bt_hci_core: Identity: DF:1C:CC:6F:45:96 (random)[0m
[00:00:00.473,052] [0m<inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x22b0, manufacturer 0x0059[0m
[00:00:00.473,052] [0m<inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0x22b0[0m
[00:00:00.718,994] [0m<dbg> bt_smp.bt_smp_pkey_ready: [0m
[00:00:44.320,068] [0m<dbg> bt_smp.bt_smp_accept: conn 0x20000a60 handle 15[0m
[00:00:44.320,098] [0m<dbg> bt_smp.bt_smp_connected: chan 0x20001010 cid 0x0006[0m
[00:00:44.320,220] [0m<inf> peripheral_uart: Connected 5C:FB:3A:53:9C:3A (public)[0m
[00:00:44.597,351] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x01 len 6[0m
[00:00:44.597,351] [0m<dbg> bt_smp.smp_pairing_req: [0m
[00:00:44.598,876] [0m<dbg> bt_smp.smp_init: prnd 92f9c4cda9547020542d544580fd9eae[0m
[00:00:44.719,696] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x0c len 64[0m
[00:00:44.719,696] [0m<dbg> bt_smp.smp_public_key: [0m
[00:00:44.719,818] [0m<dbg> bt_smp.smp_f4: u f966c0cd4ab920a2644d57fac6f892acdd844bd7a9bd20758f62ab6cc463cb54[0m
[00:00:44.719,848] [0m<dbg> bt_smp.smp_f4: v 9ba09d2dce8da508ed1dec35545e25cdad6b9144b303a2b2b57e606e4685df93[0m
[00:00:44.719,879] [0m<dbg> bt_smp.smp_f4: x 92f9c4cda9547020542d544580fd9eae z 0x0[0m
[00:00:44.721,008] [0m<dbg> bt_smp.smp_f4: res c05fe9716a9ecd30ccee3eb0db664a61[0m
[00:00:44.898,468] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x04 len 16[0m
[00:00:44.898,468] [0m<dbg> bt_smp.smp_pairing_random: [0m
[00:00:44.898,498] [0m<dbg> bt_smp.smp_g2: u 9ba09d2dce8da508ed1dec35545e25cdad6b9144b303a2b2b57e606e4685df93[0m
[00:00:44.898,529] [0m<dbg> bt_smp.smp_g2: v f966c0cd4ab920a2644d57fac6f892acdd844bd7a9bd20758f62ab6cc463cb54[0m
[00:00:44.898,559] [0m<dbg> bt_smp.smp_g2: x bbb90de01a71ce7fc6d360b880ea22ee[0m
[00:00:44.898,559] [0m<dbg> bt_smp.smp_g2: y 92f9c4cda9547020542d544580fd9eae[0m
[00:00:44.899,719] [0m<dbg> bt_smp.smp_g2: res 3e7647b4529c77b74a6971e267d877b9[0m
[00:00:44.899,749] [0m<dbg> bt_smp.smp_g2: passkey 239673[0m
[00:00:44.899,871] [0m<inf> peripheral_uart: Passkey for 5C:FB:3A:53:9C:3A (public): 239673[0m
[00:00:44.899,871] [0m<inf> peripheral_uart: Press Button 1 to confirm, Button 2 to reject.[0m
[00:00:44.969,177] [0m<dbg> bt_smp.bt_smp_dhkey_ready: 0x20006d7f[0m
[00:00:47.987,152] [0m<inf> peripheral_uart: Numeric Match, conn 0x20000a60[0m
[00:00:54.683,074] [0m<dbg> bt_smp.bt_smp_disconnected: chan 0x20001010 cid 0x0006[0m
[00:00:54.683,105] [0m<dbg> bt_smp.smp_pairing_complete: status 0x8[0m
[00:00:54.683,105] [0m<dbg> bt_smp.bt_smp_encrypt_change: chan 0x20001010 conn 0x20000a60 handle 15 encrypt 0x00 hci status 0x1f[0m
[00:00:54.683,227] [1;33m<wrn> peripheral_uart: Security failed: 5C:FB:3A:53:9C:3A (public) level 1 err 9[0m
[00:00:54.683,349] [0m<inf> peripheral_uart: Pairing failed conn: 5C:FB:3A:53:9C:3A (public), reason 9[0m
[00:00:54.683,532] [0m<inf> peripheral_uart: Disconnected: 5C:FB:3A:53:9C:3A (public) (reason 8)[0m
[00:01:04.271,759] [0m<dbg> bt_smp.bt_smp_accept: conn 0x20000a60 handle 15[0m
[00:01:04.271,789] [0m<dbg> bt_smp.bt_smp_connected: chan 0x20001010 cid 0x0006[0m
[00:01:04.271,911] [0m<inf> peripheral_uart: Connected 5C:FB:3A:53:9C:3A (public)[0m
[00:01:04.543,762] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x01 len 6[0m
[00:01:04.543,762] [0m<dbg> bt_smp.smp_pairing_req: [0m
[00:01:04.545,318] [0m<dbg> bt_smp.smp_init: prnd e16181486351fbbb429949be5a679a84[0m
[00:01:04.666,076] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x0c len 64[0m
[00:01:04.666,076] [0m<dbg> bt_smp.smp_public_key: [0m
[00:01:04.666,198] [0m<dbg> bt_smp.smp_f4: u f966c0cd4ab920a2644d57fac6f892acdd844bd7a9bd20758f62ab6cc463cb54[0m
[00:01:04.666,229] [0m<dbg> bt_smp.smp_f4: v 9e24905bf10a70a9a10ea523872d25ed65fa69a2e15e267b68fd9aa4ce785dbf[0m
[00:01:04.666,259] [0m<dbg> bt_smp.smp_f4: x e16181486351fbbb429949be5a679a84 z 0x0[0m
[00:01:04.667,419] [0m<dbg> bt_smp.smp_f4: res ebdd52513e772cea9cb31253b5030c88[0m
[00:01:04.844,909] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x04 len 16[0m
[00:01:04.844,940] [0m<dbg> bt_smp.smp_pairing_random: [0m
[00:01:04.844,970] [0m<dbg> bt_smp.smp_g2: u 9e24905bf10a70a9a10ea523872d25ed65fa69a2e15e267b68fd9aa4ce785dbf[0m
[00:01:04.845,001] [0m<dbg> bt_smp.smp_g2: v f966c0cd4ab920a2644d57fac6f892acdd844bd7a9bd20758f62ab6cc463cb54[0m
[00:01:04.845,001] [0m<dbg> bt_smp.smp_g2: x fe2e72d3dc6e7968f8e6b538bda89b14[0m
[00:01:04.845,031] [0m<dbg> bt_smp.smp_g2: y e16181486351fbbb429949be5a679a84[0m
[00:01:04.846,221] [0m<dbg> bt_smp.smp_g2: res 159fb5e98b20313ecd4c29356eb350e9[0m
[00:01:04.846,252] [0m<dbg> bt_smp.smp_g2: passkey 245417[0m
[00:01:04.846,374] [0m<inf> peripheral_uart: Passkey for 5C:FB:3A:53:9C:3A (public): 245417[0m
[00:01:04.846,374] [0m<inf> peripheral_uart: Press Button 1 to confirm, Button 2 to reject.[0m
[00:01:04.915,740] [0m<dbg> bt_smp.bt_smp_dhkey_ready: 0x20006d7f[0m
[00:01:06.340,301] [0m<inf> peripheral_uart: Numeric Match, conn 0x20000a60[0m
[00:01:14.569,458] [0m<dbg> bt_smp.bt_smp_disconnected: chan 0x20001010 cid 0x0006[0m
[00:01:14.569,488] [0m<dbg> bt_smp.smp_pairing_complete: status 0x8[0m
[00:01:14.569,519] [0m<dbg> bt_smp.bt_smp_encrypt_change: chan 0x20001010 conn 0x20000a60 handle 15 encrypt 0x00 hci status 0x1f[0m
[00:01:14.569,641] [1;33m<wrn> peripheral_uart: Security failed: 5C:FB:3A:53:9C:3A (public) level 1 err 9[0m
[00:01:14.569,732] [0m<inf> peripheral_uart: Pairing failed conn: 5C:FB:3A:53:9C:3A (public), reason 9[0m
[00:01:14.569,915] [0m<inf> peripheral_uart: Disconnected: 5C:FB:3A:53:9C:3A (public) (reason 8)[0m
[00:01:21.716,705] [0m<dbg> bt_smp.bt_smp_accept: conn 0x20000a60 handle 15[0m
[00:01:21.716,735] [0m<dbg> bt_smp.bt_smp_connected: chan 0x20001010 cid 0x0006[0m
[00:01:21.716,857] [0m<inf> peripheral_uart: Connected 5C:FB:3A:53:9C:3A (public)[0m
[00:01:21.992,614] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x01 len 6[0m
[00:01:21.992,645] [0m<dbg> bt_smp.smp_pairing_req: [0m
[00:01:21.994,171] [0m<dbg> bt_smp.smp_init: prnd f336db04b25935564e557ea799e4592a[0m
[00:01:22.114,959] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x0c len 64[0m
[00:01:22.114,959] [0m<dbg> bt_smp.smp_public_key: [0m
[00:01:22.115,081] [0m<dbg> bt_smp.smp_f4: u f966c0cd4ab920a2644d57fac6f892acdd844bd7a9bd20758f62ab6cc463cb54[0m
[00:01:22.115,112] [0m<dbg> bt_smp.smp_f4: v 145991bbb068fcaa11495cb1a38f1460cbabf32f1ca76f13958389befa99d56f[0m
[00:01:22.115,142] [0m<dbg> bt_smp.smp_f4: x f336db04b25935564e557ea799e4592a z 0x0[0m
[00:01:22.116,302] [0m<dbg> bt_smp.smp_f4: res a43326b1a05e7a2411d14de6c394224a[0m
[00:01:22.293,731] [0m<dbg> bt_smp.bt_smp_recv: Received SMP code 0x04 len 16[0m
[00:01:22.293,762] [0m<dbg> bt_smp.smp_pairing_random: [0m
[00:01:22.293,792] [0m<dbg> bt_smp.smp_g2: u 145991bbb068fcaa11495cb1a38f1460cbabf32f1ca76f13958389befa99d56f[0m
[00:01:22.293,823] [0m<dbg> bt_smp.smp_g2: v f966c0cd4ab920a2644d57fac6f892acdd844bd7a9bd20758f62ab6cc463cb54[0m
[00:01:22.293,823] [0m<dbg> bt_smp.smp_g2: x 9c0a1983151bbb373f05d6fd0d18e14f[0m
[00:01:22.293,853] [0m<dbg> bt_smp.smp_g2: y f336db04b25935564e557ea799e4592a[0m
[00:01:22.295,013] [0m<dbg> bt_smp.smp_g2: res 29e16266206bca04111c8730fb3720d8[0m
[00:01:22.295,013] [0m<dbg> bt_smp.smp_g2: passkey 694104[0m
[00:01:22.295,135] [0m<inf> peripheral_uart: Passkey for 5C:FB:3A:53:9C:3A (public): 694104[0m
[00:01:22.295,135] [0m<inf> peripheral_uart: Press Button 1 to confirm, Button 2 to reject.[0m
[00:01:22.364,501] [0m<dbg> bt_smp.bt_smp_dhkey_ready: 0x20006d7f[0m
[00:01:24.381,927] [0m<inf> peripheral_uart: Numeric Match, conn 0x20000a60[0m
[00:01:32.138,336] [0m<dbg> bt_smp.bt_smp_disconnected: chan 0x20001010 cid 0x0006[0m
[00:01:32.138,366] [0m<dbg> bt_smp.smp_pairing_complete: status 0x8[0m
[00:01:32.138,397] [0m<dbg> bt_smp.bt_smp_encrypt_change: chan 0x20001010 conn 0x20000a60 handle 15 encrypt 0x00 hci status 0x1f[0m
[00:01:32.138,519] [1;33m<wrn> peripheral_uart: Security failed: 5C:FB:3A:53:9C:3A (public) level 1 err 9[0m
[00:01:32.138,641] [0m<inf> peripheral_uart: Pairing failed conn: 5C:FB:3A:53:9C:3A (public), reason 9[0m
[00:01:32.138,793] [0m<inf> peripheral_uart: Disconnected: 5C:FB:3A:53:9C:3A (public) (reason 8)[0m

I tried to press the button on the board first, then on the laptop, it doesn't matter. Three attempts, in the first and third, first on the laptop, then on the board.

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Thu, 03 Feb 2022 06:37:27 GMT

Sorry, there might have been a misunderstanding here. I meant that you need to set both CONFIG_BT_DEBUG_LOG and CONFIG_BT_DEBUG_SMP to Y in your prj.conf file to get more information in the log.

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Wed, 02 Feb 2022 14:33:46 GMT

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

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

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Wed, 02 Feb 2022 14:16:08 GMT

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

Best regards,

Simon

RE: Connect a Laptop with Windows to Peripheral UART example

StefiNR — Wed, 02 Feb 2022 09:31:41 GMT

How do I enable this option? (Do I need to reprogram and Net core?)

On the example \SDK\ncs\v1.8.0\nrf\samples\bluetooth\peripheral_uart , I put it in prj.conf, last row CONFIG_BT_DEBUG_SMP=y.

There is no effect in the SEGGER, no more rows appear at the time of connection.

This thing appears in the VSC and it is still useless.

Bluetooth Security Manager Protocol (SMP) debug

Type: bool

Value: n

This option enables debug support for the Bluetooth Security Manager Protocol (SMP). WARNING: This option prints out private security keys such as the Long Term Key. Use of this feature in production is strongly discouraged.

Value has changed in the build

CONFIG_BT_DEBUG_SMP was assigned the value y, but got the value n. Missing dependencies:

(BT_HCI_HOST && BT_SMP && BT_DEBUG && BT_RPC_STACK) || (BT_HCI_HOST && BT_SMP && BT_DEBUG && BT_HCI && BT)

In the file smp.c, the word UNSPECIFIED occurs 81 times, how exactly will I find out what to do?

The sniffer is unusable for devices other than Nordic. In order to be able to trace the connection of two devices, I need to determine which device is the peripheral and broadcast. Unfortunately, in the field: Device(Wireshark), there are only addresses without names and I do not know what to connect to. I tried to search by ADDRESS, which is in the phone for Bluetooth, such does not exist. I tried all the addresses in sequence, nothing. I can upload a video of how the connection works, but nothing special. The PIN window appears, confirm it, and connect.

At the beginning of the topic I wrote that I cannot scan the connection of two devices so I can look for differences.

RE: Connect a Laptop with Windows to Peripheral UART example

Simonr — Wed, 02 Feb 2022 06:34:00 GMT

Hi Stefan

Can you also add logging in SMP as well? You can do this by enabling BT_DEBUG_SMP, as this should give us more info on this "UNSPECIFIED" error code you're seeing. I would look in zephyr/subsys/bluetooth/host/smp.c for the UNSPECIFIED error and see in which cases the host might return that. You could also enable debugging for SMP (CONFIG_BT_DEBUG_SMP).

If possible, can we also get a sniffer log of a Bluetooth device that is able to connect to the laptop for comparison?

Best regards,

Simon