nRF52833 Coded PHY

RE: nRF52833 Coded PHY

Simonr — Wed, 17 Aug 2022 14:10:11 GMT

I'm sorry, but I don't see what's missing here. This should run on Coded PHY from what I can see. Can you try doing a Diff between the nRF52833 main file and the Coded PHY main file I uploaded?

Best regards,

Simon

RE: nRF52833 Coded PHY

Louw — Wed, 17 Aug 2022 07:15:33 GMT

The NRF_BLE_SCAN_BUFFER is set to 255

ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST); returns error code 0

Stepping through the ble_advertising_start function:
line 547: p_advertising->initialized == true
552: p_advertising->adv_mode_current is set to 0x03

The if statement on line 556 is false

572: p_advertising->adv_mode_current is set to 0x03

The if statement on line 574 is false, else on line 584 is used
p_advertising->whitelist_reply_expected is set to 0x00

595: if statement is valid, p_advertising->adv_params.primary_phy is set to 0x04
604: if statement is valid, p_advertising->adv_params.secondary_phy is set to 0x04

616: p_advertising->adv_params.filter_policy is set to 0x00

switch statement on line 619 value is BLE_ADV_MODE_FAST

645: if(p_advertising->adv_mode_current != BLE_ADV_MODE_IDLE) is true
649: if(ret != NRF_SUCCESS) is false
655: if(ret != NRF_SUCCESS) is false
661: if (p_advertising->evt_handler != NULL) is true

RE: nRF52833 Coded PHY

Simonr — Thu, 11 Aug 2022 09:11:02 GMT

Can you show me what your ble_advertising_start function does though? Please also make sure that the NRF_BLE_SCAN_BUFFER is equal to BLE_GAP_SCAN_BUFFER_EXTENDED_MIN (255)?

Best regards,

Simon

RE: nRF52833 Coded PHY

Louw — Wed, 10 Aug 2022 14:04:15 GMT

There is no more logging after "Debug logging for UART over RTT started". When debugging the code, I'm able to step through everything without any errors.

If I comment out (lines 629 - 631 in my code):
// init.config.ble_adv_primary_phy = BLE_GAP_PHY_CODED;
// init.config.ble_adv_secondary_phy = BLE_GAP_PHY_CODED;
// init.config.ble_adv_extended_enabled = true;
The code works fine again, immediately connects.

00> <info> app_timer: RTC: initialized.
00>
00> <info> app: Debug logging for UART over RTT started.
00>
00> <debug> nrf_ble_gatt: Requesting to update ATT MTU to 247 bytes on connection 0x0.
00>
00> <debug> nrf_ble_gatt: Updating data length to 251 on connection 0x0.
00>
00> <info> app: Connected
00>
00> <debug> nrf_ble_gatt: Peer on connection 0x0 requested an ATT MTU of 247 bytes.
00>
00> <debug> nrf_ble_gatt: Updating ATT MTU to 247 bytes (desired: 247) on connection 0x0.
00>
00> <debug> nrf_ble_gatt: ATT MTU updated to 247 bytes on connection

I don't think the advertising_start function is changing anything
static void advertising_start(void)
{
uint32_t err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);
APP_ERROR_CHECK(err_code);
}

RE: nRF52833 Coded PHY

Simonr — Wed, 10 Aug 2022 12:43:49 GMT

Is there no more logging after the "Debug logging for UART over RTT started" line? Does the peripheral application start advertising at all? And can you check that the ble_advertising_start() function (wherever it is defined) does not change the advertising settings that you set in advertising_init()?

Best regards,

Simon

RE: nRF52833 Coded PHY

Louw — Wed, 10 Aug 2022 08:54:13 GMT

I still can't get the two devices to connect. I've attached my code, could you please have a look at it.

I get the following output from RTT Viewer:

Central
00> <info> app_timer: RTC: initialized.
00>
00> <debug> ble_scan: Added filter on UUID 1
00>
00> <info> app: BLE UART central example started.
00>
00> <debug> ble_scan: Scanning
00>

Peripheral
00> <info> app_timer: RTC: initialized.
00>
00> <info> app: Debug logging for UART over RTT started.
00>

devzone.nordicsemi.com/.../Coded_5F00_PHY_5F00_Examle.zip

RE: nRF52833 Coded PHY

Simonr — Tue, 09 Aug 2022 06:15:42 GMT

Indeed, only advertising/scan initialization should be necessary to add Coded PHY. Most importantly are the following inits (in advertising):

init.advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

init.config.ble_adv_primary_phy = BLE_GAP_PHY_CODED;

init.config.ble_adv_secondary_phy = BLE_GAP_PHY_CODED;

init.config.ble_adv_extended_enabled = true;

And these for scan_init:

scan_params.filter_policy = BLE_GAP_SCAN_FP_ACCEPT_ALL;

scan_params.scan_phys = BLE_GAP_PHY_CODED;

scan_params.extended = true;

Best regards,

Simon

RE: nRF52833 Coded PHY

Louw — Mon, 08 Aug 2022 14:42:19 GMT

Thank you for the quick response.

I have tried to copy the code from your project to a fresh example from the SDK, since I need to use the pca10100 example and your code is from pca10056. The central and peripheral won't connect to each other.

From what I've seen, your only changes to the code was
to advertising_init() on the central
and to scan_init() on the peripheral
Is this correct?

Do you have any further advice?

Thanks for the extra advice of setting
sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_ADV, m_advertising.adv_handle, 8);
and
sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_SCAN_INIT, 0, 8);
on the devices, I'll use that when I've managed to get the two devices connected

RE: nRF52833 Coded PHY

Simonr — Mon, 08 Aug 2022 12:25:19 GMT

We don't have an official sample project in the nRF5 SDK for using Coded PHY, but here you have an unofficial modified version of the ble_app_uart project running with Coded PHY. The main changes are to the PHY used. Extended advertising being enabled, as well as the advertising flags are set to GENERAL_DISC. If your application also uses extended MTU for example, Coded PHY does not support larger data packets than 27 bytes.

Please note that S2 is not supported by the nRF5 SDK, so you'll have to make do with S8.

Long_range_15.2.zip