• State Not Answered
  • Replies 5 replies
  • Subscribers 97 subscribers
  • Views 1225 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 301222
Options

Radio_PTX sample code gives error interrupts for ESB_PROTOCOL_ESB protocol

Ajitsj

Hi,

I am software engineer working in Philips. 

I am trying to transmit 21 bytes of our payload data (fixed payload length).

I have the following configurations done for esb_initialize() function.

int esb_initialize(void)
{
    int err;
    /* These are arbitrary default addresses. In end user products
     * different addresses should be used for each set of devices.
     */
    uint8_t base_addr_0[4] = {0x99, 0x44, 0x99, 0x96};
    uint8_t base_addr_1[4] = {0x00, 0x00, 0x00, 0x00};
    uint8_t addr_prefix[8] = {0x96, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

    struct esb_config config = ESB_DEFAULT_CONFIG;

    config.protocol = ESB_PROTOCOL_ESB;
    config.retransmit_delay = 600;
    config.bitrate = ESB_BITRATE_1MBPS;
    config.event_handler = event_handler;
    config.mode = ESB_MODE_PTX;
    config.selective_auto_ack = true;
    config.payload_length = 21;
    err = esb_init(&config);

    if (err) {
        return err;
    }
    err = esb_set_base_address_0(base_addr_0);
    if (err) {
        return err;
    }

    err = esb_set_base_address_1(base_addr_1);
    if (err) {
        return err;
    }

    err = esb_set_prefixes(addr_prefix, ARRAY_SIZE(addr_prefix));
    if (err) {
        return err;
    }

    tx_payload.noack = 1;
    return 0;
}
I am filling up the tx_payload structure with our payload data.
I have created a 1008microseconds timer and in the timer callback function I am transmitting the tx_payload.
void timer_callback(void const *arg)
{

    int err;

if((packet_ready == true)&&(packet_tx_done == false))
{
    esb_flush_tx();

    err = esb_write_payload(&tx_payload);
    if (err) {
        LOG_ERR("Payload write failed, err %d", err);
    }

    esb_flush_tx();
    packet_tx_done = true;

}

}
I also had to update the PCNF0 and PCNF1 registers to remove the "S0", "LF" and "S1" lengths from the packet fit our protocol as shown below.
static void update_rf_payload_format_esb(uint32_t payload_length)
{
#if 0  
    NRF_RADIO->PCNF0 = (1 << RADIO_PCNF0_S0LEN_Pos) |
               (0 << RADIO_PCNF0_LFLEN_Pos) |
               (1 << RADIO_PCNF0_S1LEN_Pos);
#endif
    /*Ajit change*/
    NRF_RADIO->PCNF0 = (0 << RADIO_PCNF0_S0LEN_Pos) |
               (0 << RADIO_PCNF0_LFLEN_Pos) |
               (0 << RADIO_PCNF0_S1LEN_Pos);
    //(" \r\n ** Inside update_rf_payload_format_esb_dpl, NRF_RADIO->PCNF0L: 0x%x ** \r\n",NRF_RADIO->PCNF0);
//Ajit Change
    NRF_RADIO->PCNF1 =
        (RADIO_PCNF1_WHITEEN_Disabled << RADIO_PCNF1_WHITEEN_Pos) |
        (RADIO_PCNF1_ENDIAN_Big << RADIO_PCNF1_ENDIAN_Pos) |
        ((esb_addr.addr_length - 1) << RADIO_PCNF1_BALEN_Pos) |
        (payload_length << RADIO_PCNF1_STATLEN_Pos) |
        (payload_length << RADIO_PCNF1_MAXLEN_Pos);

}
But I getting the error message "TX FAILED EVENT" continuously from the below mentioned interrupt handler.
void event_handler(struct esb_evt const *event)
{
    ready = true;

    switch (event->evt_id) {
    case ESB_EVENT_TX_SUCCESS:
        LOG_DBG("TX SUCCESS EVENT");
        break;
    case ESB_EVENT_TX_FAILED:
        LOG_DBG("TX FAILED EVENT");
        break;
    case ESB_EVENT_RX_RECEIVED:
        printk("RX EVENT \r\n");
        while (esb_read_rx_payload(&rx_payload) == 0) {
            LOG_DBG("Packet received, len %d : "
                "0x%02x, 0x%02x, 0x%02x, 0x%02x, "
                "0x%02x, 0x%02x, 0x%02x, 0x%02x",
                rx_payload.length, rx_payload.data[0],
                rx_payload.data[1], rx_payload.data[2],
                rx_payload.data[3], rx_payload.data[4],
                rx_payload.data[5], rx_payload.data[6],
                rx_payload.data[7]);
        }
        break;
    }
}
However the "ESB_PROTOCOL_ESB_DPL" protocol works when without giving this error interrupt.
But for "ESB_PROTOCOL_ESB_DPL" protocol I had assigned the "PCNF1_STATLEN" and "PCNF1_MAXLEN" values as "21" which is our payload data length.
 
Please could you help me resolve this issue ASAP. We need this program for our application.
Thanks and regards,
Ajit S J
Parents
  • 0

    Hello Kenneth,

    Thanks for your reply. Yes we need to communicate with a legacy patient monitor device. So we need to use this NRF52840 device to send out packets and receive packets as per our legacy device protocol. The ESB protocol has some extra data fields in the packet which would not be compatible with our product. In other posts I was told to use the same ESB sample code for our legacy product.

    I am using the NCS toolchain and library. Can I use the "NRF_ESB_LEGACY" definition in the current "radio_ptx" project "main.c" file? 

    We actually need to modify the "radio_ptx" code to receive data packets at 250ms. But I am facing a lot of issues in getting both tx and rx working together in the same code. I have explained it below.

    I am using separate initialization functions for tx and rx because the transmit payload length is 21 bytes and receive payload length is 9 bytes.


    int esb_initialize_tx(void)
    {
        int err;
        /* These are arbitrary default addresses. In end user products
         * different addresses should be used for each set of devices.
         */
        uint8_t base_addr_0[4] = {0x99, 0x44, 0x99, 0x96};
        uint8_t base_addr_1[4] = {0x00, 0x00, 0x00, 0x00};
        uint8_t addr_prefix[8] = {0x96, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

        struct esb_config config = ESB_DEFAULT_CONFIG;

        config.protocol = ESB_PROTOCOL_ESB;
        config.retransmit_delay = 600;
        config.bitrate = ESB_BITRATE_1MBPS;
        config.event_handler = event_handler;
        config.mode = ESB_MODE_PTX;
        config.selective_auto_ack = true;
        config.payload_length = 21;

        err = esb_init(&config);

        if (err) {
            return err;
        }


        err = esb_set_base_address_0(base_addr_0);
        if (err) {
            return err;
        }

        err = esb_set_base_address_1(base_addr_1);
        if (err) {
            return err;
        }

        err = esb_set_prefixes(addr_prefix, ARRAY_SIZE(addr_prefix));
        if (err) {
            return err;
        }


        tx_payload.noack = 1;
        rx_payload.noack = 1;


        return 0;
    }


    int esb_initialize_rx(void)
    {
        int err;
        /* These are arbitrary default addresses. In end user products
         * different addresses should be used for each set of devices.
         */
        uint8_t base_addr_0[4] = {0x99, 0x44, 0x99, 0x96};
        uint8_t base_addr_1[4] = {0x00, 0x00, 0x00, 0x00};
        uint8_t addr_prefix[8] = {0x96, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};


        struct esb_config config = ESB_DEFAULT_CONFIG;

        config.protocol = ESB_PROTOCOL_ESB;
        config.retransmit_delay = 600;
        config.bitrate = ESB_BITRATE_1MBPS;
        config.event_handler = event_handler;
        config.mode = ESB_MODE_PRX;
        config.selective_auto_ack = true;
        config.payload_length = 9;

        err = esb_init(&config);

        if (err) {
            return err;
        }

        err = esb_set_base_address_0(base_addr_0);
        if (err) {
            return err;
        }

        err = esb_set_base_address_1(base_addr_1);
        if (err) {
            return err;
        }

        err = esb_set_prefixes(addr_prefix, ARRAY_SIZE(addr_prefix));
        if (err) {
            return err;
        }

        tx_payload.noack = 1;
        rx_payload.noack = 1;

        return 0;
    }

    I have created a timer of 1008microseconds which is as per our protocol timing requirements. Then I am calling these initialize functions and tx and rx funtions inside my timer handler function as below. 

    void timer_callback(void const *arg)
    {
    int err;

    esb_set_rf_channel(frequency_hop);

    if((packet_ready == true)&&(packet_tx_done == false))
    {
        esb_stop_rx();  
        esb_initialize_tx();
        esb_flush_tx();

        err = esb_write_payload(&tx_payload);
        if (err) {
            LOG_ERR("Payload write failed, err %d", err);
        }

        esb_flush_tx();
       
        //turn off/on led
        ret = gpio_pin_set(&led_1, led_1.pin, !led_value);
        if (ret) {
            LOG_ERR("LED1 set 0 error: %d", ret);
        }

               
        //printk("\r\n Inside timer handler, after write payload \r\n");
        packet_tx_done = true;
        esb_initialize_rx();
        esb_start_rx();

    }

    }

     

    But either transmit or receive works when I run this program on the nrf52840 development kit. By default the receive works and I get "ESB_EVENT_RX_RECEIVED" event and the below mentioned debug print is displayed on the screen. But the transmit does not work and I do not receive any packet from the nrf52840 onto our legacy product.

        case ESB_EVENT_RX_RECEIVED:
            if (esb_read_rx_payload(&rx_payload) == 0) {
                LOG_DBG("Packet received, len %d : "
                    "0x%02x, 0x%02x, 0x%02x, 0x%02x, "
                    "0x%02x, 0x%02x, 0x%02x, 0x%02x",
                    rx_payload.length, rx_payload.data[0],
                    rx_payload.data[1], rx_payload.data[2],
                    rx_payload.data[3], rx_payload.data[4],
                    rx_payload.data[5], rx_payload.data[6],
                    rx_payload.data[7]);
            }

    However when I enable a print inside the "timer_callback" function the transmit works fine and we see the data that is transmitted from nrf52840 on our legacy product. But the receive does not work and I do not get the prints inside "ESB_EVENT_RX_RECEIVED" event.

    could you please help me out in getting both tx and rx working in the same program? There could be some timing mismatch here as well.

    Thanks and regards

    Ajit S J

  • 0 in reply to Ajitsj

    Hello,

    Looks like you want the very old ShockBurst format of the packet, without the PID field that was introducted in the ESB protocol for dynamic payload length and acknowledge. Unfortunately we don't have any code for this, so you likely need to modify the ESB as you are doing already.

    I can see you have cleared the S0LEN, S1LEN and LFLEN of NRF_RADIO->PCNF0, which should remove the PID field. In that case you will need to always update the STATLEN and MAXLEN of NRF_RADIO->PCNF1 every time before you enter transmit or receive a packet, which I can also see that you are doing. 

    Given your description that you are able to make this "somewhat" work in both directions (but not really at the same time), I think the problem is timing related. I suggest that you get yourself an Nordic PPK II power profiler kit, this will allow you to measure with high accuracy both receive and transmit timing: https://www.nordicsemi.com/Products/Development-hardware/Power-Profiler-Kit-2 

    Best regards,
    Kenneth

  • 0 in reply to Kenneth

    Hi Kenneth,

    Thanks for your reply. Can't we change any register settings or code in the software to make the transmit and receive work together? Why do we need to use another power profiler kit?

    Thanks and regards,

    Ajit S J

  • 0 in reply to Ajitsj

    If you have built your application on the old ShockBurst (SB) protocol, then SB only did tx or rx, and it was up to the application what timing was done if it did switch between the two modes of operation. In this case it is not clear to me what exactly timing you have between the two modes of operation, e.g. what is the receive "window" of the peer if it switch direction. So that is why I suggested getting an PPK, since that allow you to monitor with great detail (in the us range) when the radio is operating in tx and rx (by looking at the peak current consumption), and you could then measure on the old and new implementation and found if one of the timings were off in this case. 

    Best regards,
    Kenneth

Reply
  • 0 in reply to Ajitsj

    If you have built your application on the old ShockBurst (SB) protocol, then SB only did tx or rx, and it was up to the application what timing was done if it did switch between the two modes of operation. In this case it is not clear to me what exactly timing you have between the two modes of operation, e.g. what is the receive "window" of the peer if it switch direction. So that is why I suggested getting an PPK, since that allow you to monitor with great detail (in the us range) when the radio is operating in tx and rx (by looking at the peak current consumption), and you could then measure on the old and new implementation and found if one of the timings were off in this case. 

    Best regards,
    Kenneth

Children
No Data
Related
Terms of service