Code flashing successful but not working!

[siltvm]

Hello,

I am creating a new project that uses the nRF52810 as my controller, and during the development stage, I am using the PCA10040 nRF52832 development board. (I read somewhere that we can flash the nRF52810 code into the nRF52832 PCA10040 development board). My requirement is a simple LED indicator based on delay commands from an APK that uses the Nordic UART service to send and receive data. I added the timer peripheral to the ble_app_uart example project from the directory nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_app_uart\pca10040e\s112\ses and flashed the code onto the PCA10040 nRF52832 development board to test it. The code works perfectly.

Then I took an nRF52810 custom PCB and connected the JTAG. The board is able to detect and erase the chip. When I flash the code onto the board, the IDE shows "flash successful," but the board is not working. Are there any other conditions for flashing the code into the nRF52810 custom board? Your response is valuable.

SDK version: 17.0.2
SEGGER Embedded Studio version: 5.42a

[billtsai]

Hi,

If your custom board do not have external 32K crystal, you can try to modify these parameters in sdk_config.h

// <o> NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source.
 
// <0=> NRF_CLOCK_LF_SRC_RC 
// <1=> NRF_CLOCK_LF_SRC_XTAL 
// <2=> NRF_CLOCK_LF_SRC_SYNTH 

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

// <o> NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. 
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#endif

// <o> NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. 
// <i> How often (in number of calibration intervals) the RC oscillator shall be calibrated
// <i>  if the temperature has not changed.

#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#endif

// <o> NRF_SDH_CLOCK_LF_ACCURACY  - External clock accuracy used in the LL to compute timing.
 
// <0=> NRF_CLOCK_LF_ACCURACY_250_PPM 
// <1=> NRF_CLOCK_LF_ACCURACY_500_PPM 
// <2=> NRF_CLOCK_LF_ACCURACY_150_PPM 
// <3=> NRF_CLOCK_LF_ACCURACY_100_PPM 
// <4=> NRF_CLOCK_LF_ACCURACY_75_PPM 
// <5=> NRF_CLOCK_LF_ACCURACY_50_PPM 
// <6=> NRF_CLOCK_LF_ACCURACY_30_PPM 
// <7=> NRF_CLOCK_LF_ACCURACY_20_PPM 
// <8=> NRF_CLOCK_LF_ACCURACY_10_PPM 
// <9=> NRF_CLOCK_LF_ACCURACY_5_PPM 
// <10=> NRF_CLOCK_LF_ACCURACY_2_PPM 
// <11=> NRF_CLOCK_LF_ACCURACY_1_PPM 

#ifndef NRF_SDH_CLOCK_LF_ACCURACY
#define NRF_SDH_CLOCK_LF_ACCURACY 1
#endif

[siltvm]

hi billtsai ,

I modified the sdk_config file as per the given instructions. Now I am able to debug through RTT Viewer, but the issue still persists. I am still getting a fatal error, Are there any other memory constraints while flashing the code onto the nRF52810 ?.

[billtsai]

One possible reason is that the uart rx pin is low in nRF52810.

This will cause APP_UART_COMMUNICATION_ERROR in application code.

You can set uart rx pin as pull high to avoid this error.

[Jared]

 siltvm  

siltvm said:

As per your suggestion, I checked the ERRORSRC register while debugging the code. I will attach an image of the ERRORSRC register values on my custom PCB with the nRF52810.

Based on this, I would suggest checking Bill Tsai suggestion. Check if the UART pin is pulled low.

regards

Jared 

[siltvm]

hi Jared  billtsai ,

As per your suggestion, I have modified the `apply_config()` function in the `nrfx_uart.c` and `nrfx_uarte.c` files. I pulled up the RX pin like this in both drivers:

 if (p_config->pselrxd != NRF_UART_PSEL_DISCONNECTED)
    {
        nrf_gpio_cfg_input(p_config->pselrxd, NRF_GPIO_PIN_PULLUP);
    }

 

Now the nRF52810 custom PCB advertises its name, but after a few seconds, the board turns off. I debugged the code and observed that the issue still persists. I am sharing my debug console output for better understanding. You can see the ERRORSRC register values in the picture. Your response is very valuable..

[billtsai]

You can consider using app_timer one single shot mode instead of nrf_delay_ms.

nrf_delay_ms will occupy mcu resource and may disturb ble stack and interrupt handler.

[siltvm]

hi , billtsai Jared I just modified it as per your suggestion. When I am debugging the code, I am getting the same error situation as before. Can you check the flash and RAM memory configuration of the section placement macros?

 ‘s112_nrf52_7.2.0_softdevice.hex’    - size 98.7kb.

  ‘ble_app_uart_pca10040e_s112.elf’     - size 31.7kb

section placement macros in linker . 

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x30000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x6000

FLASH_START=0x19000

FLASH_SIZE=0x17000

RAM_START=0x200022c8

RAM_SIZE=0x3d38

is this configuration is correct ?

each response is valuble . 

[billtsai]

I think the settings is ok. Because you can see the advertising of your device.

Call stack contents shows the error is from uart_event_handler.

Can you use break point to check the error is from case APP_UART_DATA_READY or other case?

[siltvm]

hi , Jared ,billtsai , Sorry for the late response. When debugging the code, I am checking the error code before a fatal error. The log indicates error code 4. Is it related to a memory issue? How can I solve this?

[billtsai]

Hi,

Yes, it's no memory error code. But there are many functions will return this error code.

You should put the break points in the uart_event_handler and find which function returns this error code.

[siltvm]

hi billtsai ,Jared ,

I am having trouble debugging the code. Sometimes it gets stuck for a while. i think this function app_fifo_put(), which returns NRF_ERROR_NO_MEM. What is the reason for this function returning 'no memory'?

     static void uart_event_handler(nrf_drv_uart_event_t * p_event, void* p_context)
{
    app_uart_evt_t app_uart_event;
    uint32_t err_code;
    NRF_LOG_INFO(" UART EVENT HANDLER \n");
    switch (p_event->type)
    {
        case NRF_DRV_UART_EVT_RX_DONE:
            // If 0, then this is a RXTO event with no new bytes.
            if(p_event->data.rxtx.bytes == 0)
            {
               // A new start RX is needed to continue to receive data
               (void)nrf_drv_uart_rx(&app_uart_inst, rx_buffer, 1);
               break;
            }

            // Write received byte to FIFO.
            err_code = app_fifo_put(&m_rx_fifo, p_event->data.rxtx.p_data[0]);
            NRF_LOG_INFO(" app_fifo_put : %d\n",err_code);
            if (err_code != NRF_SUCCESS)
            {
                
                app_uart_event.evt_type          = APP_UART_FIFO_ERROR;
                app_uart_event.data.error_code   = err_code;
                m_event_handler(&app_uart_event);
            }
            // Notify that there are data available.
            else if (FIFO_LENGTH(m_rx_fifo) != 0)
            {
                app_uart_event.evt_type = APP_UART_DATA_READY;
                m_event_handler(&app_uart_event);
            }

            // Start new RX if size in buffer.
            if (FIFO_LENGTH(m_rx_fifo) <= m_rx_fifo.buf_size_mask)
            {
                (void)nrf_drv_uart_rx(&app_uart_inst, rx_buffer, 1);
            }
            else
            {
                // Overflow in RX FIFO.
                m_rx_ovf = true;
            }

            break;

        case NRF_DRV_UART_EVT_ERROR:
            NRF_LOG_INFO("  NRF_DRV_UART_EVT_ERROR \n");
            app_uart_event.evt_type                 = APP_UART_COMMUNICATION_ERROR;
            app_uart_event.data.error_communication = p_event->data.error.error_mask;
            (void)nrf_drv_uart_rx(&app_uart_inst, rx_buffer, 1);
            m_event_handler(&app_uart_event);
            break;

        case NRF_DRV_UART_EVT_TX_DONE:
            // Get next byte from FIFO.
            if (app_fifo_get(&m_tx_fifo, tx_buffer) == NRF_SUCCESS)
            {
                (void)nrf_drv_uart_tx(&app_uart_inst, tx_buffer, 1);
            }
            else
            {
                NRF_LOG_INFO(" else NRF_DRV_UART_EVT_TX_DONE \n");
                // Last byte from FIFO transmitted, notify the application.
                app_uart_event.evt_type = APP_UART_TX_EMPTY;
                m_event_handler(&app_uart_event);
            }
            break;

        default:
            break;
    }
}

//________________________________________________________________//

uint32_t app_fifo_put(app_fifo_t * p_fifo, uint8_t byte)
{
    if (FIFO_LENGTH() <= p_fifo->buf_size_mask)
    {
        fifo_put(p_fifo, byte);
        return NRF_SUCCESS;
    }

    return NRF_ERROR_NO_MEM;
}