SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

Simonr — Mon, 18 Dec 2023 06:40:12 GMT

Hi Larry

That makes sense. Sorry I didn't think to ask of that on my end either, but I'm glad to hear you figured it out eventually!

Best regards,

Simon

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Fri, 15 Dec 2023 16:17:09 GMT

Hi Simon, OK, mega mea culpa from this BT and Wireshark Newbie, I thought I'd check the Wireshark preferences and settings and found this little jewel:

extcap._dev_cu_usbmodem14101_4_0.coded, and change from false to true

Voila, can now see Prim=CODED packets and the Sec=CODED Aux packets.

Sorry, to waste your time, but I certainly learned several things. Many thanks for your patience and support!

Humbly typed, Larry

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Fri, 15 Dec 2023 15:25:19 GMT

Hi Simon,

The _rscs example works fine, as-is, as I'd expect, Pri=1M/Sec=2M. I change Sec=CODED and that works, but when I change Pri=CODED there is once again no packets from my -DK showing in Wireshark BLE sniffer. I stepped thru the code in ble_advertising_init() and ble_advertising_start(), and all looks correct before and after the S140 calls for sd_ble_gap_adv_set_configure() and sd_gap_adv_start(). This is with AdvMode = _FAST. I'll try AdvMode = _SLOW and see if that makes a difference, perhaps the default interval is too fast for Pri=CODED?

Larry

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Thu, 14 Dec 2023 16:50:29 GMT

Simon, thanks for the quick response. I believe the example I was using may have been derived from another, and it did not use the newer helper components (e.g. ble_advertising), but the direct API interfaces. (It may be derived from SDK-15.2, but moving to 17.1, I didn't migrate my baseline example. So, the "extras" are from the original baseline). Thanks for the extra review and recommendations. I will also re-baseline on the rscs example.

Regards, Larry

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

Simonr — Thu, 14 Dec 2023 12:50:01 GMT

Hi Larry

I took another look at your main file, and realized you don't have the extended advertisements enabled in your advertising intitialization. Please try adding the following in your advertising_init() function. I thought "m_adv_params.properties.type" took care of this, but that does not seem to be the case I'm afraid. You can see the ble_app_rscs example project for reference.

init.config.ble_adv_extended_enabled = true;

Also, I see that you have quite a few other things added in advertising_init() that I'm not sure should be there in the first place. Can you explain what the if loop is doing exactly and why it should be in the init function? I also see that you don't have a ble_advertising_init() call in advertising_init() like most other examples in the nRF5 SDKs have.

Best regards,

Simon

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Wed, 13 Dec 2023 19:23:10 GMT

Hi Simon, still struggling with this, getting PriPHY as CODED. Do you know if there is S140-7.2.0 BT5 LongRange Adv example on the forums or examples that is known to work, to help me save trial and error time?

Appreciate it, Larry

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Mon, 11 Dec 2023 21:59:22 GMT

Simon, no worries. Thanks for the info, I'll work on recreating the HardFault trace and getting the context. I will also try SCANNABLE. My concern with the new S140 version is our ultimate intent on using the Adafruit board and effort to update to the newer version on that env. Regardless, we need to show it working properly on a known config before 'back-porting'.

Thanks

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

Simonr — Mon, 11 Dec 2023 07:11:27 GMT

Sorry about the late reply, but I had to discuss this with a colleague before getting back to you.

The error 0xA60 that you see from your debugging screenshot is a SoftDevice hardfault handler. This usually gets forwarded to the app fault handler that should get us more information on the fault context. Please try seeing what the app fault handler is returning here so we can get some more information that way.

I'm not able to spot what the issue is from looking at your main application, and the only thing I can think of is trying to support scan response data by using BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_SCANNABLE_UNDIRECTED instead of BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED in your application, but I think we need the information from the app fault handler to get anywhere here.

For your last reply, all revisions of the nRF52840 should support Bluetooth 5.0 and Coded PHY, so I don't think there's a reason to look at the IC revision, however the SDK and SoftDevice version should indeed match your HW revision (SDK 17.1.0 and SoftDevice 7.2.0 is what I'd recommend).

Best regards,

Simon

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Mon, 11 Dec 2023 03:19:53 GMT

Simon, one more check... I assume if I bought my 52840-DK board this year (has a version of 3.0.1 and date stamp of 2023.14 on the label), that it has a newer HW version of the SOC that supports BT5 extended adv:

https://docs.nordicsemi.com/bundle/comp_matrix_nrf52840/page/COMP/nrf52840/nRF52840_ic_revision_overview.html

https://docs.nordicsemi.com/bundle/comp_matrix_nrf52840/page/COMP/nrf52840/nRF52840_ic_rev_sdk_sd_comp_matrix.html

and then, do I need to confirm my SOC HW version with the compatible SDK and S140 versions?

Thanks.

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Sun, 10 Dec 2023 00:16:28 GMT

Simon, FYI, I did try loading both the DEBUG and RELEASE binaries via Segger from the attached SDK15.2 zip uart-peripheral, and had no extended advertising visible from the 58240-DK via Wireshark BT sniffer. Moving back to the SDK17.1 peripheral example, but not having any success there either. Attached my latest main.c from this effort, if you could review adv init and start setup.

devzone.nordicsemi.com/.../main_5F00_sdk17.1.beacon.c

Thanks

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Fri, 08 Dec 2023 04:26:43 GMT

(Reference the previous post) when I try using the SDK-17.1 and S140-7.2.0 periph-beacon example, similar results, no packets in Wireshark, and I get the following HardFault FORCED in the debugger after running for a while. Assume the call stack is in the S140 firmware?

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Fri, 08 Dec 2023 04:11:04 GMT

Hi Simon,

Thanks for the feedback. Sorry, yes using BT LE sniffer firmware on an Adafruit ItsyBitsy 52840 at version 4.0.10, and have seen EXT_ADV (PriPhy=1MBPS) and AUX_ADV (SecPhy=CODED with S8) from both the Nordic-DK52840/SDK15.3 modified periph beacon example, and also with a similar example for Adafruit Feather Express 52840, but have not got EXT_ADV(PriPhy = CODED) to work. Have just started to try the 15.2 UART example from the attached .zip and modifying to use .flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE (per the original post), but having issues with the re-build.

So, I am going to try doing similar mods to the SDK17.1 Beacon example (S140-7.2.0), and see if I can get Pri=CODED and Sec=CODED to work there.

I'll need to talk to our project engineer about extended MTU and the packet size limitation. We were hoping to get the extended/larger packets to work for our application... OpenDroneID BT advertising where the OpenDrone messages are sent individually in Legacy BT and they can all be theoretically packed in the larger message frame of BT5 extd'd (255 bytes).

Sorry, I inadvertently selected 'Answered' and now have reverted this case.

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

Simonr — Thu, 07 Dec 2023 08:39:17 GMT

Just to make sure, are you using the Bluetooth LE sniffer firmware for Wireshark to sniff advertising packets? Note that only from v4.0.0 does the nRF Sniffer support Coded PHY. What phone do you use for scanning on the nRF Connect app? Not all phones support Coded PHY, usually only the flagship models for the last 3 years of so does so.

From your settings it seems correct, and the only thing I can think of is that if your application uses extended MTU, the Coded PHY does not support larger data packets than 27 bytes. Note that S2 is not supported by the nRF5 SDK, so you'll have to make do with S8 (should be the default setting).

Best regards,

Simon

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

clb62 — Mon, 04 Dec 2023 19:49:38 GMT

Hi Simon, thanks for the response.

So, I do think I'm at a point of needing some assistance. Following Vidar's example, I am applying his example settings to the 15.3-s140-6.1.1 low-level Periph-Beacon example. I am not using a central to test, but Wireshark and/or nRF Connect on my phone.

Legacy (not EXTended, NONconn, NONscan, and UNdir) works fine for Primary Phy. My next setup is EXTended, NONconnectable, NONscannable, and UNdirected. The first attempt has Primary as 1MBPS and 2ndary as CODED. I am using Wireshark on my laptop to confirm advertising packets. For this config, packets look as expected; reference this Wireshark image, filtered to just show my BT device (52840-DK, ec:8a:0e:d1:3e:82). Notice PHY is 1MBPS, 2ndary is CODED (not shown).

but when I change Primary Phy to CODED then I get no EXT adv packets from the -DK

Here are the settings for EXT ADV params, note 'include appearance" is false:

    //flags = BLE_GAP_ADV_FLAG_BR_EDR_NOT_SUPPORTED;
    flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

    // Build and set advertising data.
    memset(&advdata, 0, sizeof(advdata));

    //advdata.name_type             = BLE_ADVDATA_NO_NAME;
    advdata.name_type             = BLE_ADVDATA_FULL_NAME;
    advdata.flags                 = flags;
    advdata.p_manuf_specific_data = &manuf_specific_data;
    //advdata.include_appearance    = true;

    // Initialize advertising parameters (used when starting advertising).
    memset(&m_adv_params, 0, sizeof(m_adv_params));

    //m_adv_params.properties.type = BLE_GAP_ADV_TYPE_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;
    m_adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_NONCONNECTABLE_NONSCANNABLE_UNDIRECTED;
    m_adv_params.p_peer_addr     = NULL;    // Undirected advertisement.
    m_adv_params.filter_policy   = BLE_GAP_ADV_FP_ANY;
    m_adv_params.interval        = NON_CONNECTABLE_ADV_INTERVAL;
    m_adv_params.duration        = 0;       // Never time out.
    //m_adv_params.primary_phy     = BLE_GAP_PHY_1MBPS;
    m_adv_params.primary_phy     = BLE_GAP_PHY_CODED;
    m_adv_params.secondary_phy   = BLE_GAP_PHY_CODED;

    err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
    APP_ERROR_CHECK(err_code);

    err_code = sd_ble_gap_adv_set_configure(&m_adv_handle, &m_adv_data, &m_adv_params);
    APP_ERROR_CHECK(err_code);

I also tried changing .include_appearance to true, but that did not have any effect. Thoughts?

[Also, I've noticed that when I make a software change, rebuild, and download, that I need to actually power reset the board, vs just soft reset and re-download via Segger/JLink.]

Thanks, Larry

RE: SDK-15.3 + S140 6.1.1 for Ext Adv + Coded Phy on 52840-DK then Adafruit

Simonr — Mon, 04 Dec 2023 13:34:20 GMT

Do you need help with anything in particular here? I think going through the advertising params in Vidar's example project should be sufficient to use Coded PHY as the primary advertising PHY as well. Does the central you're using for scanning support scanning on the Coded PHY as well?

Best regards,

Simon