nRF52840 BLE 3-Wire PTA for Wi-Fi

RE: nRF52840 BLE 3-Wire PTA for Wi-Fi

Amanda Hsieh — Fri, 12 Jul 2024 13:58:43 GMT

I only found this https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrfxlib/mpsl/doc/api.html#c.mpsl_cx_prio_t which has the same content as you provided.

RE: nRF52840 BLE 3-Wire PTA for Wi-Fi

Jayant Tang — Fri, 12 Jul 2024 07:22:26 GMT

Hello Amanda,

That works for me. Thank you very much.

But I have a further question:

In `nrf/subsys/mpsl/cx/thread/mpsl_cx_thread.c:130`.

We can see in the `request()` function that it will activate the PRIORITY pin only if the priority>127.

The priority is a numerical value. Do we have any document about the value meaning?

/**
 * @brief Priority of given radio operation.
 *
 * This numerical value is translated by given PTA interface driver to appropriate signal.
 * The straightforward translation would be <= UINT8_MAX/2 is low priority, while > UINT8_MAX/2
 * is high priority. More complicated PTAs support more than 2 priority levels and valid matching
 * must be implemented for such devices.
 *
 * Priority values must be aligned between all users of this API in given system. When multiple
 * radio protocols are enabled (like Bluetooth LE and IEEE 802.15.4), all protocols must use
 * aligned values (Bluetooth low priority operations must use numerically lower value than
 * IEEE 802.15.4 high priority operations).
 */
typedef uint8_t mpsl_cx_prio_t;

Best regards,

Jayant

RE: nRF52840 BLE 3-Wire PTA for Wi-Fi

Amanda Hsieh — Thu, 11 Jul 2024 13:36:57 GMT

Hi,

For now, you can use the following workaround:

Add CONFIG_BT_LL_SOFTDEVICE_MULTIROLE=y to prj.conf - this is required as coex is not included in the peripheral library, and currently this is not correctly getting selected automatically when coex is enabled.
Remove the line depends on !BT as the customer has already done, and use CONFIG_MPSL_CX_THREAD=y

The developer has tested this locally and it works on our side, note enabling the multirole library is required for coex to work. This will not build as-is on NCS latest due to a regression, but is fine on 2.5.3. Will be fixed soon and will be part of NCS 2.8.

-Amanda H.

RE: nRF52840 BLE 3-Wire PTA for Wi-Fi

Jayant Tang — Thu, 11 Jul 2024 09:36:06 GMT

I have some updates.

1. I find out that the MPSL does not call the `register_callback` function. So, my code didn't get the callback function.

2. I tried a different way to enable 3-wire PTA in MPSL. I referred to nrf/subsys/mpsl/cx/bluetooth/mpsl_cx_1w_bluetooth.c

It doesn't work, too.

You can replace the same name file in my project (previously provided) with this file.

devzone.nordicsemi.com/.../mpsl_5F00_cx_5F00_3w_5F00_bluetooth.c

RE: nRF52840 BLE 3-Wire PTA for Wi-Fi

Jayant Tang — Thu, 11 Jul 2024 03:35:45 GMT

Hi Amanda,

This config CONFIG_MPSL_CX_THREAD=y does not work.

By default, it can't be enabled in BLE samples, because the nrf/subsys/mpsl/cx/Kconfig says this Kconfig `depends on !BT`. So, I deleted the line `depends on !BT`.

The REQUEST pin and PRIORITY pin still not change state. And I can't connect to the DK with my nRF Connect App. The BLE advertising stopped just after startup.

Best regards,

Jayant

RE: nRF52840 BLE 3-Wire PTA for Wi-Fi

Amanda Hsieh — Wed, 10 Jul 2024 16:41:45 GMT

Hi,

The generic three-wire coex implementation (CONFIG_MPSL_CX_THREAD), despite the confusing name, also supports BLE as it implements the MPSL generic coex API (https://docs.nordicsemi.com/bundle/ncs-2.5.3/page/nrf/device_guides/wifi_coex.html#ug-radio-coex-mpsl-cx-based)

Try to enable CONFIG_MPSL_CX_THREAD=y in prj.conf instead to see if this protocol works for your requirements.

Regards,
Amanda H.