nRF52840 DK can not advertising extension when using zephyr nRF Connect SDK v1.6.1

[yuyin]

HW : nRF52840DK

SW :  nRF3.7.0 desktop tool

          nRF Connect SDK v1.6.1

IDE: SES

Project: periodic_sync or periodic_adv

Operation:

1. build -> rebuild the solution,  success;

2. Target -> Download zephyr/zephyr.elf,  success;

result: 

nRF52840DK LED1 blink , no any advertising packet can be received.

 

Anyone can help me why the extend adv pkt can not received, and how should I do correctly?

[Amanda Hsieh]

Hi, 

Have a look at the response Sigurd provided in this post.

I add CONFIG_BT_LL_SW_SPLIT=y into prj.conf of periodic_sync and periodic_adv. One DK runs periodic_adv and get the log like this: 

*** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***

Starting Periodic Advertising Demo

[00:00:00.276,367] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)

[00:00:00.276,367] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)

[00:00:00.276,397] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0                                                                                                                                                             x00) Version 2.6 Build 0

[00:00:00.276,947] <inf> bt_hci_core: Identity: FA:B0:6E:34:31:BE (random)

[00:00:00.276,947] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, m                                                                                                                                                             anufacturer 0x05f1

[00:00:00.276,947] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff

Set Periodic Advertising Data...done.

Set Periodic Advertising Data...done.

Set Periodic Advertising Data...done.

Set Periodic Advertising Data...done.

Set Periodic Advertising Data...done.

Set Periodic Advertising Data...done.

Set Periodic Advertising Data...done.

Set Periodic Advertising Data...done.

Another DK runs periodic_sync and get the log like this

*** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***

Starting Periodic Advertising Synchronization Demo

Checking LED device...done.

Configuring GPIO pin...done.

Scan callbacks register...success.

Periodic Advertising callbacks register...Success.

Start scanning...success.

Start blinking LED...

Waiting for periodic advertising...

[00:00:00.258,514] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)

[00:00:00.258,514] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)

[00:00:00.258,514] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.6 Build 0

[00:00:00.259,094] <inf> bt_hci_core: Identity: DA:20:CF:24:38:05 (random)

[00:00:00.259,094] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1

[00:00:00.259,094] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0xffff

[DEVICE]: 59:67:CB:E2:45:60 (random), AD evt type 2, Tx Pwr: 127, RSSI -78  C:0 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 59:67:CB:E2:45:60 (random), AD evt type 4, Tx Pwr: 127, RSSI -78  C:0 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 98:D6:BB:23:D7:AF (public), AD evt type 0, Tx Pwr: 127, RSSI -81  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 0F:26:07:0C:5A:31 (random), AD evt type 5, Tx Pwr: 127, RSSI -38 Test Periodic Advertising C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0

Found periodic advertising.

Creating Periodic Advertising Sync...success.

Waiting for periodic sync...

[DEVICE]: 5D:07:B0:F2:BC:39 (random), AD evt type 3, Tx Pwr: 127, RSSI -36  C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

PER_ADV_SYNC[0]: [DEVICE]: 0F:26:07:0C:5A:31 (random) synced, Interval 0x0780 (2400 ms), PHY LE 2M

Periodic sync established.

Stop blinking LED.

Waiting for periodic sync lost...

[DEVICE]: A4:30:7A:67:32:2C (public), AD evt type 0, Tx Pwr: 127, RSSI -85  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

PER_ADV_SYNC[0]: [DEVICE]: 0F:26:07:0C:5A:31 (random), tx_power 127, RSSI -38, CTE 1, data length 5, data: 04ffffffb0

[DEVICE]: 74:15:A4:DD:73:86 (random), AD evt type 4, Tx Pwr: 127, RSSI -81  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 59:67:CB:E2:45:60 (random), AD evt type 4, Tx Pwr: 127, RSSI -80  C:0 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

PER_ADV_SYNC[0]: [DEVICE]: 0F:26:07:0C:5A:31 (random), tx_power 127, RSSI -39, CTE 1, data length 5, data: 04ffffffb3

[DEVICE]: 6C:4A:85:5A:95:F5 (public), AD evt type 0, Tx Pwr: 127, RSSI -82  C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

[DEVICE]: 6C:4A:85:5A:95:F5 (public), AD evt type 4, Tx Pwr: 127, RSSI -82  C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

PER_ADV_SYNC[0]: [DEVICE]: 0F:26:07:0C:5A:31 (random), tx_power 127, RSSI -40, CTE 1, data length 5, data: 04ffffffb5

If you still have the issue, please provide the logs. Thanks. 

-Amanda H.

[Ashishsult]

Hi Amanda, have you tested it for long packet size such as 50 bytes? 

[Amanda Hsieh]

Hi, 

Not sure what you want to ask. If it's related to throughput, please see this sample Bluetooth: Throughput.  

I would suggest you create a new case for your own issue. 

-Amanda