About esb_ptx_ble & esb_prx_ble.

Can I copy the ESB code from SDK v3.3.0-preview3 into SDK v2.9.0, and then get the functionality in esb_ptx_ble & esb_prx_ble?

 

Is there any way to achieve it quickly?

Parents
  • Hello Leo,

    Just an update. R&D has started looking into this now, but I don't have an answer for you yet. 

    FYI I did try some workarounds when I looked into this back when your ticket was assigned to me, but all of them triggerd asserts, so I guess the MPSL wasn't too happy with the application doing direct changes to the PPI channels. Therefore I suspect that this requires changes to the MPSL library, and hence would require a new SDK release. But let us see what the MPSL team figures out before concluding this.

    Best regards,

    Edvin

  • Hello,

    We have a suggested workaround:

    https://github.com/maje-emb/sdk-nrf/commits/esb_ppi_ch_leak/

    It is not yet part of the SDK, and I can't guarantee when it will be merged and included in an NCS release, but perhaps you can test it on your end. 

    Both the author and I have tested this workaround for a while, and so far it shows up without leaking any PPI channels (which was quite quick to reproduce before the workaround). 

    Can you test it on your application and let me know if you still see the same issue, or if this resolves it?

    Note that this is not yet officially tested from Nordic's side, but from my point of view, it behaves better with this workaround than without.

    Best regards,

    Edvin

Reply
  • Hello,

    We have a suggested workaround:

    https://github.com/maje-emb/sdk-nrf/commits/esb_ppi_ch_leak/

    It is not yet part of the SDK, and I can't guarantee when it will be merged and included in an NCS release, but perhaps you can test it on your end. 

    Both the author and I have tested this workaround for a while, and so far it shows up without leaking any PPI channels (which was quite quick to reproduce before the workaround). 

    Can you test it on your application and let me know if you still see the same issue, or if this resolves it?

    Note that this is not yet officially tested from Nordic's side, but from my point of view, it behaves better with this workaround than without.

    Best regards,

    Edvin

Children
No Data
Related