NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

[yoyou]

Hello,

NCS1.9.0 or NCS1.9.1,  Windows10 X64,VS Code,periodic_adv.default codes

with nRF52840-DK work fine.

but nRF5340-DK got error,as folow logs

"Failed to create advertising set (err -5)"

*** Booting Zephyr OS build v2.7.99-ncs1  ***
Starting Periodic Advertising Demo
Failed to create advertising set (err -5)
[00:00:00.283,355] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.283,355] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.283,386] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 14.50663 Build 1008232294
[00:00:00.286,712] <inf> bt_hci_core: Identity: C7:71:77:EB:8D:C1 (random)
[00:00:00.286,712] <inf> bt_hci_core: HCI: version 5.2 (0x0b) revision 0x22fe, manufacturer 0x0059
[00:00:00.286,712] <inf> bt_hci_core: LMP: version 5.2 (0x0b) subver 0x22fe
[00:00:00.289,093] <wrn> bt_hci_core: opcode 0x2036 status 0x01

  

thanks

Best Regards

[yoyou]

Hi,

thank you very much,

avoid packet loss  is most important to me.

I can try to figure out if there is an easier way to detect duplicate packets on the receive side, so you don't have to do this manually. 

that is great!

If you send a 200 byte payload every 50ms you should get 4 kByte/s easily. 

it is so good!

but when i add CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=202 two side or only adv side prj.conf bese on your project.   sync side can't recv data,maybe I'm missing something?

   

Best Regards

[ovrebekk]

Hi 

yoyou said:

I can try to figure out if there is an easier way to detect duplicate packets on the receive side, so you don't have to do this manually. 

that is great!

I checked with the team, and it seems the SoftDevice controller doesn't support this feature unfortunately. In other words it is necessary to check this manually, like I do in the example I sent. 

yoyou said:

but when i add CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=202 two side or only adv side prj.conf bese on your project.   sync side can't recv data,maybe I'm missing something?

You only have to add this to the advertiser, the scanner will already be set up to support reception of long packets. 

Do you see any error messages in the advertiser or scanner that could explain why you don't receive anything?

Best regards
Torbjørn

[yoyou]

Hi,

thanks for reply,  you work carefully!

i delete it and rebuild,it work fine,can recv 202 byte,good!

now,

First question:

i want 

Create a non-connectable non-scannable DIRECTED advertising set

Only some devices can receive data.

how to do it?

if Peer address set to not NULL, periodic_sync will can't recv.

maybe periodic_sync  side also need set Peer address?

        

Second question:

how to set max TX power and max GIAN  for long rang  (without nRF21540) ?

              

thanks

Best regards

[ovrebekk]

Hi 

yoyou said:

Create a non-connectable non-scannable DIRECTED advertising set

Only some devices can receive data.

how to do it?

This is not supported in the Bluetooth specification unfortunately. Periodic advertising can not be directed. 

yoyou said:

how to set max TX power and max GIAN  for long rang  (without nRF21540) ?

Do you need to set the power statically or dynamically?

There is a sample in Zephyr showing how you can set the TX power for Bluetooth applications:
https://docs.zephyrproject.org/2.6.0/samples/bluetooth/hci_pwr_ctrl/README.html

Best regards
Torbjørn

[yoyou]

Hi,

thanks for reply,

Do you need to set the power statically or dynamically? 

i want to set maximum statically only.

   

Best regards