RE: How does the nRF52833 reply back to nRF24L01+ with user data automatically?

JackLan — Fri, 05 Jul 2024 09:11:30 GMT
Thanks.
The following codeblock works.
/**
 * Copyright (c) 2014 - 2021, Nordic Semiconductor ASA
 *
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without modification,
 * are permitted provided that the following conditions are met:
 *
 * 1. Redistributions of source code must retain the above copyright notice, this
 *    list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form, except as embedded into a Nordic
 *    Semiconductor ASA integrated circuit in a product or a software update for
 *    such product, must reproduce the above copyright notice, this list of
 *    conditions and the following disclaimer in the documentation and/or other
 *    materials provided with the distribution.
 *
 * 3. Neither the name of Nordic Semiconductor ASA nor the names of its
 *    contributors may be used to endorse or promote products derived from this
 *    software without specific prior written permission.
 *
 * 4. This software, with or without modification, must only be used with a
 *    Nordic Semiconductor ASA integrated circuit.
 *
 * 5. Any software provided in binary form under this license must not be reverse
 *    engineered, decompiled, modified and/or disassembled.
 *
 * THIS SOFTWARE IS PROVIDED BY NORDIC SEMICONDUCTOR ASA "AS IS" AND ANY EXPRESS
 * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
 * OF MERCHANTABILITY, NONINFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE ARE
 * DISCLAIMED. IN NO EVENT SHALL NORDIC SEMICONDUCTOR ASA OR CONTRIBUTORS BE
 * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
 * GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
 * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 *
 */
#include "nrf_esb.h"

#include <stdbool.h>
#include <stdint.h>
#include "sdk_common.h"
#include "nrf.h"
#include "nrf_esb_error_codes.h"
#include "nrf_delay.h"
#include "nrf_gpio.h"
#include "nrf_error.h"
#include "boards.h"


#include "nrf_log.h"
#include "nrf_log_ctrl.h"
#include "nrf_log_default_backends.h"

uint8_t led_nr;

nrf_esb_payload_t rx_payload;
static nrf_esb_payload_t tx_payload = NRF_ESB_CREATE_PAYLOAD(0, 0x00, 0x00, 0x00, 0x00, 0x11, 0x00, 0x00, 0x00);	

/*lint -save -esym(40, BUTTON_1) -esym(40, BUTTON_2) -esym(40, BUTTON_3) -esym(40, BUTTON_4) -esym(40, LED_1) -esym(40, LED_2) -esym(40, LED_3) -esym(40, LED_4) */
volatile static uint16_t recvCount = 0, countBak = 0, count;

void nrf_esb_event_handler(nrf_esb_evt_t const * p_event)
{
		//
    switch (p_event->evt_id)
    {
        case NRF_ESB_EVENT_TX_SUCCESS:
            //NRF_LOG_DEBUG("TX SUCCESS EVENT");
            break;
        case NRF_ESB_EVENT_TX_FAILED:
            //NRF_LOG_DEBUG("TX FAILED EVENT");
            break;
        case NRF_ESB_EVENT_RX_RECEIVED:
            //NRF_LOG_DEBUG("RX RECEIVED EVENT");

            if (nrf_esb_read_rx_payload(&rx_payload) == NRF_SUCCESS)
            {
								recvCount = *((uint16_t*)rx_payload.data);
								count++;
								//if(countBak != recvCount)
								{
						      nrf_gpio_pin_write(LED_1, recvCount % 2);
									nrf_gpio_pin_write(LED_2, recvCount % 2);
									nrf_gpio_pin_write(LED_3, recvCount % 2);
									nrf_gpio_pin_write(LED_4, recvCount % 2);																			
									//NRF_LOG_DEBUG("%d, %d", recvCount, recvCount);									
								}
                // Set LEDs identical to the ones on the PTX.
/*
                nrf_gpio_pin_write(LED_1, !(rx_payload.data[1]%8>0 && rx_payload.data[1]%8<=4));
                nrf_gpio_pin_write(LED_2, !(rx_payload.data[1]%8>1 && rx_payload.data[1]%8<=5));
                nrf_gpio_pin_write(LED_3, !(rx_payload.data[1]%8>2 && rx_payload.data[1]%8<=6));
                nrf_gpio_pin_write(LED_4, !(rx_payload.data[1]%8>3));
*/
								
								nrf_esb_write_payload(&tx_payload);

								//APP_ERROR_CHECK(err_code);
                //NRF_LOG_DEBUG("Receiving packet: Length == %d, rssi == %d", rx_payload.length, rx_payload.rssi);
            }
            break;
    }
}


void clocks_start( void )
{
    NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
    NRF_CLOCK->TASKS_HFCLKSTART = 1;

    while (NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);
}


void gpio_init( void )
{
    bsp_board_init(BSP_INIT_LEDS);
}


uint32_t esb_init( void )
{
    uint32_t err_code;
    /*
    uint8_t base_addr_0[4] = {0x43,0x10,0x10,0x01};
    uint8_t base_addr_1[4] = {0x43,0x10,0x10,0x01};
    uint8_t addr_prefix[8] = {0x34, 0x34, 0xC3, 0xC4, 0xC5, 0xC6, 0xC7, 0xC8 };
    */
    uint8_t base_addr_0[4] = {0xA0, 0xD3, 0xCA, 0x41};
    uint8_t base_addr_1[4] = {0xA0, 0xD3, 0xCA, 0x41};
    uint8_t addr_prefix[8] = {0x6A, 0x6A, 0xC3, 0xC4, 0xC5, 0xC6, 0xC7, 0xC8 };
    nrf_esb_config_t nrf_esb_config         = NRF_ESB_LEGACY_CONFIG;
    nrf_esb_config.payload_length           = 32;
    nrf_esb_config.protocol                 = NRF_ESB_PROTOCOL_ESB_DPL;
    nrf_esb_config.bitrate                  = NRF_ESB_BITRATE_2MBPS;
    nrf_esb_config.mode                     = NRF_ESB_MODE_PRX;
    nrf_esb_config.event_handler            = nrf_esb_event_handler;
    nrf_esb_config.selective_auto_ack       = true;

    err_code = nrf_esb_init(&nrf_esb_config);
    VERIFY_SUCCESS(err_code);

    err_code = nrf_esb_set_base_address_0(base_addr_0);
    VERIFY_SUCCESS(err_code);

    err_code = nrf_esb_set_base_address_1(base_addr_1);
    VERIFY_SUCCESS(err_code);

    err_code = nrf_esb_set_prefixes(addr_prefix, 8);
    VERIFY_SUCCESS(err_code);

    
    err_code = nrf_esb_set_rf_channel(12);
    VERIFY_SUCCESS(err_code);

    return err_code;
}


int main(void)
{
    uint32_t err_code;
    gpio_init();

    err_code = NRF_LOG_INIT(NULL);
    APP_ERROR_CHECK(err_code);

    NRF_LOG_DEFAULT_BACKENDS_INIT();

    clocks_start();

    err_code = esb_init();
    APP_ERROR_CHECK(err_code);

    NRF_LOG_DEBUG("Enhanced ShockBurst Receiver Example started.");

	tx_payload.noack = true;
	tx_payload.length = 2;
	tx_payload.pipe = 0;
	tx_payload.data[0] = 0x12;
	tx_payload.data[1] = 0x23;

	
    err_code = nrf_esb_start_rx();
    APP_ERROR_CHECK(err_code);

    while (true)
    {
				nrf_delay_ms(1000);
				NRF_LOG_DEBUG("%d PS, %d", count - countBak, recvCount);
				countBak = count;			
        //if (NRF_LOG_PROCESS() == false)
        {
        //    __WFE();
        }
    }
}
/*lint -restore */
RE: How does the nRF52833 reply back to nRF24L01+ with user data automatically?

Sigurd — Fri, 05 Jul 2024 08:55:24 GMT
Hi!
See this guide here: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/esb_users_guide.html?cp=9_1_5_3
RE: How does the nRF52833 reply back to nRF24L01+ with user data automatically?

JackLan — Fri, 05 Jul 2024 08:54:20 GMT
Take the following case as example:
Once the nRF52833(PRX) received the data from nRF24L01+ (PTX).
The nRF52833(PRX) send back the [0x01, 0x02, 0x03, 0x04, 0x05, 0x06] data to nRF24L01+ (PTX).