Extended Advertisement with Scan Response

RE: Extended Advertisement with Scan Response

Einar Thorsrud — Thu, 17 Nov 2022 09:08:22 GMT

Hi,

I see you already got an answer from my colleague Edvin in a private case. Copy-pasting the answer here in case it is useful for someone else.

Bluetooth Core Specification Version 5.3 | Vol 4, Part E section 7.8.53: LE Set Extended Advertising Parameters command (page 2450 in the Bluetooth Core Specification Version 5.3):

If extended advertising PDU types are being used (bit 4 = 0) then: The advertisement shall not be both connectable and scannable. High duty cycle directed connectable advertising (≤ 3.75 ms advertising interval) shall not be used (bit 3 = 0).

RE: Extended Advertisement with Scan Response

Vance J Farren — Tue, 15 Nov 2022 22:50:20 GMT

Thank you for your reply. Do you know where this is specified in the core spec? It would be helpful for team closure. I have confirmed in testing that the softdevice will only take extended scan response data if advertising data is omitted.

RE: Extended Advertisement with Scan Response

Einar Thorsrud — Tue, 15 Nov 2022 11:26:17 GMT

Hi,

I was not aware of this myself, but you are not allowed to have both scan response and advertising packets with data using extended advertising. See this post for details.

RE: Extended Advertisement with Scan Response

Vance J Farren — Fri, 11 Nov 2022 13:28:15 GMT

devzone.nordicsemi.com/.../07873.main.cHere is main.c, the only file modified. I've been looking at examples, tweaking input parameters, and googling constraints for a day and a half.

I would like to be able to have an extended advertisement with an extended scan response. Any pointers and explanation of the valid set of input parameters to achieve this is greatly appreciated.

RE: Extended Advertisement with Scan Response

Einar Thorsrud — Fri, 11 Nov 2022 12:51:08 GMT

Hi,

As you get NRF_ERROR_INVALID_PARAM returned from ble_advertising_start() that means that there is a problem with the input parameters to that function call. I do not see enough of your code to say what the problem is though, but that is what you need to look into.

RE: Extended Advertisement with Scan Response

Vance J Farren — Fri, 11 Nov 2022 02:36:45 GMT

<info> app: Running Speed and Cadence example started.
<error> app: ERROR 7 [NRF_ERROR_INVALID_PARAM] at C:\dev\nrf5_sdk_17_copy\nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_rscs\main.c:1061
PC at: 0x0002861D
<error> app: End of error report

        ret_code_t err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);

 (line 1061)       APP_ERROR_CHECK(err_code);