Coded PHY Advertising on nRF Connect SDK

RE: Coded PHY Advertising on nRF Connect SDK

Blue King — Wed, 21 Oct 2020 07:22:05 GMT

the problem is, Zehpyr can't see the NRFxlib

I followed this tutorial to install NRFx with zephyr with no luck

https://jimmywongiot.com/2019/12/18/step-by-step-on-nordic-connect-sdk-for-development/

tried also to copy the nrfxlib and import the kconfig file into my zephyr enviroment.

https://github.com/nrfconnect/sdk-nrfxlib

actually, I find nowhere in any file on nrfx library this text "LL_NRFXLIB"

tried also to include CONFIG_SOFTDEVICE_CONTROLLER_S140 with no luck.

so, What do i miss?

I always get

prj.conf:9: warning: attempt to assign the value 'y' to the undefined symbol BT_LL_NRFXLIB_DEFAULT

same for CONFIG_BT_LL_NRFXLIB_VS_INCLUDE

this is my prj.conf

CONFIG_BT=y
CONFIG_BT_BROADCASTER=y
CONFIG_BT_OBSERVER=y
CONFIG_BOARD_NRF52840DONGLE_NRF52840=y

# Link Layer
#NRF
#CONFIG_SOFTDEVICE_CONTROLLER_S140=y
CONFIG_BT_LL_NRFXLIB_DEFAULT=y
#NRF
CONFIG_BT_EXT_ADV=y
CONFIG_BT_CTLR_PHY_CODED=y
CONFIG_GPIO=y

CONFIG_USB=y
CONFIG_USB_DEVICE_STACK=y
CONFIG_USB_DEVICE_PRODUCT="Qoudra BLE"
CONFIG_USB_UART_CONSOLE=y

CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_LINE_CTRL=y
CONFIG_UART_CONSOLE_ON_DEV_NAME="CDC_ACM_0"

RE: Coded PHY Advertising on nRF Connect SDK

Jared — Mon, 10 Aug 2020 23:29:46 GMT

After a long while, I took another look at this. I got some nRF52840-PDK boards working with updated nRF5284s. I was then able to get a nRF9160+nRF52840 and a separate nRF52840 working over PHY CODED.

For some reason the connect_if_match parameter for scanning does not work for PHY CODED. I implemented my own connect in the filter match callback. Seems to be connecting well!

RE: Coded PHY Advertising on nRF Connect SDK

Jared — Mon, 22 Jun 2020 14:43:54 GMT

Got it. Thank you 😎

RE: Coded PHY Advertising on nRF Connect SDK

Susheel Nuguru — Mon, 22 Jun 2020 07:39:59 GMT

Hi Jared,
The guys replying to you in the Zephyr forum are the guys I would have contacted internally too. cuficarles and vinayak are the experts in this. Lets hope they have time reply in the zephyr forum.

RE: Coded PHY Advertising on nRF Connect SDK

Jared — Sat, 20 Jun 2020 03:17:02 GMT

I was instructed to try doing everything manually with the tests/bluetooth/shell example. My attempt looked like this:

bt init
bt adv-create conn-scan ext-adv coded
bt adv-select 0
bt adv-start

I had to use the adv- commands as they're specific for the new extended API. Unfortunately seems some type of kernel issue with the scheduler. Exactly sure what's going on there.

Advertiser[0] 0x20003944 set started
uart:~$ ASSERTION FAIL [!arch_is_in_isr()] @ ../../../../kernel/include/ksched.h:267

I only added a few Lins to the prj.conf:

CONFIG_BT_LL_NRFXLIB_VS_INCLUDE=y
CONFIG_BT_LL_NRFXLIB_DEFAULT=y
CONFIG_BT_MAX_CONN=2

Building with this:

west build -b nrf52840dk_nrf52840

RE: Coded PHY Advertising on nRF Connect SDK

Jared — Fri, 19 Jun 2020 20:16:52 GMT

Hi Susheel Nuguru

I didn't have much luck moving forward.

Some Nordic engineers on the Zephyr repo are convinced I should be able to use it with the Nordic LL. Any way to get more information?

Thanks!

RE: Coded PHY Advertising on nRF Connect SDK

Jared — Wed, 17 Jun 2020 12:34:52 GMT

Hi Susheel Nuguru

It appears that connectable advertising for CODED PHY is not implemented on Zephyr. I don't think there are any work arounds until this is implemented unfortunately. More updates in the Github issue.

RE: Coded PHY Advertising on nRF Connect SDK

Susheel Nuguru — Wed, 17 Jun 2020 06:37:33 GMT

I have not played with CODED PHY in Zephyr, but you seems to have a good progress on this. Jared, please keep us updated with this so that fellow developers gain from your experience.

RE: Coded PHY Advertising on nRF Connect SDK

Jared — Wed, 17 Jun 2020 03:55:24 GMT

Update:

Adding these guys

# Link Layer
CONFIG_BT_LL_NRFXLIB_VS_INCLUDE=y
CONFIG_BT_LL_NRFXLIB_DEFAULT=y
CONFIG_BT_EXT_ADV=y
CONFIG_BT_CTLR_PHY_CODED=y

Seemed to have done the trick.

Now, I've set my device connectable using this block:

struct bt_le_ext_adv *adv;
struct bt_le_adv_param *adv_param =
BT_LE_ADV_PARAM(BT_LE_ADV_OPT_CONNECTABLE | BT_LE_ADV_OPT_ONE_TIME | BT_LE_ADV_OPT_CODED | BT_LE_ADV_OPT_EXT_ADV,
BT_GAP_ADV_FAST_INT_MIN_2,
BT_GAP_ADV_FAST_INT_MAX_2,
NULL);

But on the central device it always shows up as not connectable. I'm getting that info from the scan_filter_match callback.

static void scan_filter_match(struct bt_scan_device_info *device_info,
struct bt_scan_filter_match *filter_match,
bool connectable)
{
// int err;

LOG_INF("Filters matched. Connectable: %s",
connectable ? "yes" : "no");

If I try to auto-connect, the bt_conn_cb callback returns with an error of 2 which means a timeout. I'll fiddle with it more tomorrow..

RE: Coded PHY Advertising on nRF Connect SDK

Jared — Wed, 17 Jun 2020 00:52:39 GMT

This is also nice news! www.zephyrproject.org/.../

RE: Coded PHY Advertising on nRF Connect SDK

Jared — Tue, 16 Jun 2020 18:28:56 GMT

The Zephyr link layer does not support extended advertising. Whereas the Nordic one does. Enabling these two in my prj.conf seems to fix the errors. I've yet been able to scan/connect though..

# Link Layer

CONFIG_BT_LL_NRFXLIB_VS_INCLUDE=y

CONFIG_BT_LL_NRFXLIB_DEFAULT=y