Errors with extended advertising while trying to configure coded phy on a nrf5340 custom board

I am getting an error trying to get coded phy working with a sysbuild configuration for a nrf5340 custom board:

<wrn> bt_hci_core: opcode 0x203a status 0x01 
<wrn> bt_hci_core: Controller does not support 'LE_READ_MAX_ADV_DATA_LEN'. Assuming maximum length is 31 bytes.
<inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
<inf> bt_hci_core: HW Variant: nRF53x (0x0003)
<inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 252.16862 Build 1121034987
<inf> bt_hci_core: HCI transport: IPC
<inf> bt_hci_core: Identity: CD:BA:8D:27:07:4E (random)
<inf> bt_hci_core: HCI: version 6.1 (0x0f) revision 0x2069, manufacturer 0x0059
<inf> bt_hci_core: LMP: version 6.1 (0x0f) subver 0x2069
<wrn> bt_hci_core: opcode 0x2036 status 0x01 
<err> ble_manager: Advertising failed to start (err -5)

I am trying to follow the Bluetooth: Peripheral Heart Rate Monitor with Coded PHY example for how they enabled it by adding these settings:

CONFIG_BT_CTLR_PHY_CODED=y
CONFIG_BT_CTLR_ADV_EXT=y

CONFIG_BT_EXT_ADV=y
CONFIG_BT_EXT_ADV_CODING_SELECTION=y
CONFIG_BT_USER_PHY_UPDATE=y

When I add extended advertising it seems to fail.

Parents Reply
  • lcj said:
    Shouldn't at least the extended advertising work?

    Yes, without coded PHY. So did you get the "opcode 0x2036 status 0x01" message while CONFIG_BT_EXT_ADV=y
    and CONFIG_BT_CTLR_ADV_EXT=y was supposed to be enabled on the controller? If so, it seems like the configurations were not applied to the controller build. You can confirm this by checking the generated config file build/ipc_radio/zephyr/.config

    lcj said:
    Also I created peripheral_hr_coded to test if I could get extended advertising working and flashed a nrf5340dk with it. It seems to run based on the log but I cannot see it in the nrfConnect app for iOS.

    This is expected as iOS does not support Coded PHY

Children
No Data
Related