Re: Zephyr Low Level BLE Radio question
Chettimada, Vinayak Kariappa
If you are building a Bluetooth Low Energy application using Zephyr, then you should use the public APIs, not call internal subsystem functions unless you know what you are doing.
I think you are looking for the below mentioned options when calling bt_le_ext_adv_create (https://docs.zephyrproject.org/latest/reference/bluetooth/gap.html#c.bt_le_ext_adv_create)
These are for the primary advertising channels, auxiliary PDU channels selection is controller implementation specific.
If you are not using Bluetooth Low Energy stack, then you should refer to nRF52840 product specification for implementing your proprietary radio protocol.
>The low-level bluetooth controller is tragic. I’m sure it’s incredibly useful, but the use of nicknames and acronyms at every corner are not useful. Perhaps if there were comments that could help too
Contributions to improve the code, comments and add new features are always welcome.
From: users@... <users@...> On Behalf Of steven ghekiere via lists.zephyrproject.org
Sent: 15 December 2020 19:48
To: Marciano Preciado <marciano@...>
Subject: Re: [Zephyr-users] Zephyr Low Level BLE Radio question
Thanks for the quick reply!
I’d have to agree on the acronyms and such.
What do you mean that ‘somebody can help us’?
I’d have to agree! The low-level bluetooth controller is tragic. I’m sure it’s incredibly useful, but the use of nicknames and acronyms at every corner are not useful. Perhaps if there were comments that could help too, but there aren’t. 😭
I hope somebody can help us out.