BLE througput reports reason: 0x0e on 52833

RE: BLE througput reports reason: 0x0e on 52833

Hieu — Fri, 21 Apr 2023 20:40:37 GMT

Hi rdim,

Are you certain you are working on an unmodified sample application and an unmodified SDK?

The log of the central device indicates that during Service Discovery. the central device cannot find a Service with the UUID of the Throughput Service.

I cannot reproduce your issue on my end, on NCS v1.9.1, with the Throughput sample application. The baud rate is 115200 as expected, the startup log is very similar to yours, and it works correctly.

[quote user="rdim"]Where can I read anything how to get such a trace? Actually as because of my typo with error code maybe sniffer is not very actual at a moment anymore?[/quote]

From your update, a sniffer trace is not necessary yet. If you wish to learn about the sniffer trace, please check out Nordic's free online course titled Bluetooth Low Energe Fundamental. Lesson 6 is about the nRF Sniffer, which is a free solution that runs on a nRF Development Kit.

[quote user="rdim"]nRF Connect SDK v1.9.1 - to keep all the other SW in line[/quote]

Depends on the stage of your project, I suggest moving to newer versions such as nRF Connect SDK v2.3.0 as soon as possible. The move from version 1.x to 2.x is not trivial. The more built up your project is, the more costly it will be. If you have just started your project, I recommend just restart development on a newer SDK version.

RE: BLE througput reports reason: 0x0e on 52833

rdim — Thu, 20 Apr 2023 21:52:39 GMT

Hi Hieu,

Many thanks for your answer!

First of all, I'd like to ask for excuse for my typo in error code that I'm getting: instead of 0x0e I receive 0x3e (BT_HCI_ERR_CONN_FAIL_TO_ESTAB) - that's why I had an idea that a connection is not completely(?) established.

Let me add two logs: first from the device running this time in advertising mode, and then from the log from nrf52840dk board that plays a role of BLE Central:

First log:

*** Booting Zephyr OS build v2.7.99-ncs1-1 ***
Starting Bluetooth Throughput example
I: SoftDevice Controller build revision:
I: 0e e7 c5 66 67 18 3c ac |...fg.<.
I: b3 d2 cc 81 a3 dc f1 c0 |........
I: c0 36 02 22 |.6."

: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 14.50663 Build 1008232 294
I: Identity: FA:D8:8D:7B:FB:2E (random)
I: HCI: version 5.2 (0x0b) revision 0x12fe, manufacturer 0x0059
I: LMP: version 5.2 (0x0b) subver 0x12fe
Bluetooth initialized

Press button 1 on the master board.
Press button 2 on the slave board.

Slave role. Starting advertising
32muart:~$ Connected as peripheral
Conn. interval is 320 units
Disconnected (reason 0x3e)
Connected as peripheral
Conn. interval is 320 units
Disconnected (reason 0x3e)
Connected as peripheral
Conn. interval is 320 units
Disconnected (reason 0x3e)
Connected as peripheral
Conn. interval is 320 units
Disconnected (reason 0x3e)

Second log

** Booting Zephyr OS build v2.7.99-ncs1-1 ***
Starting Bluetooth Throughput example
I: SoftDevice Controller build revision:
I: 0e e7 c5 66 67 18 3c ac |...fg.<.
I: b3 d2 cc 81 a3 dc f1 c0 |........
I: c0 36 02 22 |.6."
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 14.50663 Build 1008232294
I: Identity: FF:84:4B:5E:95:A8 (random)
I: HCI: version 5.2 (0x0b) revision 0x12fe, manufacturer 0x0059
I: LMP: version 5.2 (0x0b) subver 0x12fe
Bluetooth initialized

Press button 1 on the master board.
Press button 2 on the slave board.

Master role. Starting scanning
Filter not match. Address: 51:8A:DE:57:B4:86 (random) connectable: 1
Filter not match. Address: 68:A0:1F:E1:C1:7A (random) connectable: 1
Filter not match. Address: B4:60:77:B6:F8:6A (public) connectable: 1
Filter not match. Address: E3:7A:B3:EE:14:3F (random) connectable: 0
Filters matched. Address: FA:D8:8D:7B:FB:2E (random) connectable: 1
Filter not match. Address: 68:A0:1F:E1:C1:7A (random) connectable: 1
Filter not match. Address: B4:60:77:B6:F8:6A (public) connectable: 1
Connected as central
Conn. interval is 320 units
Service not found
Disconnected (reason 0x3e)
Filter not match. Address: 51:8A:DE:57:B4:86 (random) connectable: 1
Filter not match. Address: 68:A0:1F:E1:C1:7A (random) connectable: 1
Filter not match. Address: E4:9D:63:D8:78:76 (random) connectable: 0
Filter not match. Address: 51:8A:DE:57:B4:86 (random) connectable: 1

[skipped]

Filter not match. Address: CF:44:AB:F8:E6:3A (random) connectable: 0
Filter not match. Address: B4:60:77:B6:F8:6A (public) connectable: 1
Filters matched. Address: FA:D8:8D:7B:FB:2E (random) connectable: 1
Filter not match. Address: 68:A0:1F:E1:C1:7A (random) connectable: 1
Filter not match. Address: 51:8A:DE:57:B4:86 (random) connectable: 1
Connected as central
Conn. interval is 320 units
Service not found
Disconnected (reason 0x3e)
Filter not match. Address: 51:8A:DE:57:B4:86 (random) connectable: 1
Filter not match. Address: B4:60:77:B6:F8:6A (public) connectable: 1
Filter not match. Address: 68:A0:1F:E1:C1:7A (random) connectable: 1
Filter not match. Address: 51:8A:DE:57:B4:86 (random) connectable: 1
Filter not match. Address: C3:D4:F2:E3:59:53 (random) connectable: 0

[skipped]

Filter not match. Address: C8:B2:1E:C5:8B:10 (public) connectable: 1
Filter not match. Address: 68:A0:1F:E1:C1:7A (random) connectable: 1
Filter not match. Address: 51:8A:DE:57:B4:86 (random) connectable: 1
Filter not match. Address: 68:A0:1F:E1:C1:7A (random) connectable: 1
Filter not match. Address: 51:8A:DE:57:B4:86 (random) connectable: 1
Filters matched. Address: FA:D8:8D:7B:FB:2E (random) connectable: 1
Filter not match. Address: 68:A0:1F:E1:C1:7A (random) connectable: 1
Connected as central
Conn. interval is 320 units

Next, I will answer the rest of your questions:

Which device is connecting with your custom board? - nrf52840dk in this example; I've got the same result with nrf52833dk board
Which device is giving disconnect reason 0x0E? - that I can not say for sure, but looking at message "Service not found" at the log from Central I can presume that disconnection is initiated by the Central (nrf52840dk) side.
Are you building with debug options enabled? - yes
We are talking about this sample on the nRF Connect SDK, correct? - Yes, correct
What version of the SDK are you using? - nRF Connect SDK v1.9.1 - to keep all the other SW in line

If you can get a sniffer trace of the disconnection, that would also be great. - Unfortunately I don't know how to get it.. Where can I read anything how to get such a trace? Actually as because of my typo with error code maybe sniffer is not very actual at a moment anymore?

I don't have any nRF52833 DKs to test this at the moment. When I get to office later this week, I will try the Throughput sample on one of those DK to see if I encounter your issue.

This is not a big deal, nrf52840dk gives the same result, although two strange things happens for 52840:

1. After building in spite of serial port speed was not changed from 115200 52840 drops the serial speed down to 19200

2. Start-up log is different for 52840 and 52833

Could these two give any idea why these two work differently?

Many thanks for your help again!

RE: BLE througput reports reason: 0x0e on 52833

Hieu — Tue, 18 Apr 2023 20:26:58 GMT

Hi rdim,

Error code 0x0E is Connection Rejected Due To Security Reasons, and can be looked up in-code here: https://github.com/nrfconnect/sdk-zephyr/blob/v3.2.99-ncs2/include/zephyr/bluetooth/hci_err.h#L32.

It is really strange that your custom board has this issue, because the throughput sample should not rely on any pairing/bonding.

[quote user=""]For sure it is related somehow to somewhat that is different in 833 compare to 840 and 5340, but how to catch this critical difference..? :)[/quote]

Another really strange thing is, as far as this sample go, there should be no difference between those SoCs.

Could you please give more details about your setup?

The full log leading up to the disconnection (to give more context)
Which device is connecting with your custom board?
Which device is giving disconnect reason 0x0E?
Are you building with debug options enabled?
We are talking about this sample on the nRF Connect SDK, correct?
What version of the SDK are you using?

If you can get a sniffer trace of the disconnection, that would also be great.

I don't have any nRF52833 DKs to test this at the moment. When I get to office later this week, I will try the Throughput sample on one of those DK to see if I encounter your issue.

Hieu

RE: BLE througput reports reason: 0x0e on 52833

Hieu — Tue, 18 Apr 2023 13:12:31 GMT

Hi rdim,

Please be informed that I will support you with this question shortly.

Hieu