ESB applications compatibility developed with SDK and Connect SDK

We have developed a sensor application using ESB protocol with the nRF SDK (nRF52832 on Tx side and nRF52840 on Rx side).

We would like to redevelop now the receiver under nRF connect SDK to take advantage of the functions of an RTOS.

We note that the ESB applications developed under SDK seem incompatible with those developed under Connect SDK.

We have checked with the basic examples provided: esb_ptx (SDK) and nrf / samples / esb / prx (Connect SDK) and it does not work?

Is there a way to make them compatible?

thanks in advance.

Parents
  • Hi,

     

    We note that the ESB applications developed under SDK seem incompatible with those developed under Connect SDK.

    Yes, this is true, the API is slightly changed, and porting is required to make it compatible.

    We have checked with the basic examples provided: esb_ptx (SDK) and nrf / samples / esb / prx (Connect SDK) and it does not work?

    Here is the default configuration set for the ncs sample:

    https://github.com/nrfconnect/sdk-nrf/blob/v1.8.0/include/esb.h#L46

    As well as the default addr/crc configuration (unless manually configured):

    https://github.com/nrfconnect/sdk-nrf/blob/v1.8.0/subsys/esb/esb.c#L163-L171

     

    Your implementation in esb (in ncs) should match your wanted configuration on the esb-ptx side.

    I quickly tested the PRX (in nRF5 SDK) communicating with the PTX (from NCS v1.8.0) and it worked here:

    *** Booting Zephyr OS build v2.7.0-ncs1  ***
    I: Enhanced ShockBurst prx sample
    D: HF clock started
    I: Initialization complete
    I: Setting up for packet receiption
    D: Packet received, len 8 : 0x01, 0xb8, 0x00, 0x00, 0x11, 0x00, 0x00, 0x00
    D: TX SUCCESS EVENT
    D: Packet received, len 8 : 0x01, 0xb9, 0x00, 0x00, 0x11, 0x00, 0x00, 0x00
    ....

     

    Kind regards,

    Håkon

Reply
  • Hi,

     

    We note that the ESB applications developed under SDK seem incompatible with those developed under Connect SDK.

    Yes, this is true, the API is slightly changed, and porting is required to make it compatible.

    We have checked with the basic examples provided: esb_ptx (SDK) and nrf / samples / esb / prx (Connect SDK) and it does not work?

    Here is the default configuration set for the ncs sample:

    https://github.com/nrfconnect/sdk-nrf/blob/v1.8.0/include/esb.h#L46

    As well as the default addr/crc configuration (unless manually configured):

    https://github.com/nrfconnect/sdk-nrf/blob/v1.8.0/subsys/esb/esb.c#L163-L171

     

    Your implementation in esb (in ncs) should match your wanted configuration on the esb-ptx side.

    I quickly tested the PRX (in nRF5 SDK) communicating with the PTX (from NCS v1.8.0) and it worked here:

    *** Booting Zephyr OS build v2.7.0-ncs1  ***
    I: Enhanced ShockBurst prx sample
    D: HF clock started
    I: Initialization complete
    I: Setting up for packet receiption
    D: Packet received, len 8 : 0x01, 0xb8, 0x00, 0x00, 0x11, 0x00, 0x00, 0x00
    D: TX SUCCESS EVENT
    D: Packet received, len 8 : 0x01, 0xb9, 0x00, 0x00, 0x11, 0x00, 0x00, 0x00
    ....

     

    Kind regards,

    Håkon

Children
Related