Receiving data from UART via a peripheral device

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Tue, 10 Dec 2019 12:52:45 GMT

Hi Thomas,

I am happy to hear that it works 🙂

RE: Receiving data from UART via a peripheral device

Thomas — Tue, 10 Dec 2019 10:10:01 GMT

Hi Einar,

Thanks for the help, I've gotten my solution to work now, Just wanted to thank you for the support it really helped a lot.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 15:00:09 GMT

Ok I'll have a detailed look through. But, I've stepped through the code when the error is thrown and I can not identify why it occurs. It goes from this:

m_event_handler(&app_uart_event);

to this:

app_error_fault_handler(NRF_FAULT_ID_SDK_ERROR, 0, (uint32_t)(&error_info));

This then runs to NRF_BREAKPOINT_COND

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Fri, 06 Dec 2019 14:30:42 GMT

Yes, that is correct. If you test the debug build you should see a sensible message in the log, and if there is problems with the logging you can inspect the info struct yourself. I think you will find An introduction to error handling in nRF5 projects useful.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 14:23:26 GMT

#define NRF_FAULT_ID_SDK_ERROR       (NRF_FAULT_ID_SDK_RANGE_START + 1) /**< An error stemming from a call to @ref APP_ERROR_CHECK or @ref APP_ERROR_CHECK_BOOL. The info parameter is a pointer to an @ref error_info_t variable. */

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 14:21:22 GMT

0x0000000000004001.

Also how does it tell me what the error is? I don't have an error code lookup table.

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Fri, 06 Dec 2019 14:20:45 GMT

What was the error code? That usually tells you what the problem was.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 14:16:33 GMT

It runs from

err_code = sd_ble_gap_adv_stop(m_adv_handle);
    APP_ERROR_CHECK(err_code);

and sometimes from :

err_code = sd_ble_gap_adv_start(m_adv_handle, APP_BLE_CONN_CFG_TAG);
    APP_ERROR_CHECK(err_code);

Both of which are within my ad mod code.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 14:11:18 GMT

I do have another issue. After a short while I do get Fatal error. Was after 27 seconds of reading fine. Any idea what could cause this? Or how to implement a restart feature

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 13:39:50 GMT

FIXED IT

I forgot to start the add before moding it.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 13:36:28 GMT

I get NRF_FAULT_ID_SDK_ERROR 0x0000000000004001.

This comes from NRF_DRV_UART_EVT_TX_DONE: within the app_uart_fifo.c.

When it runs the m_event_handler

This runs from the line of code:

err_code = ble_advdata_encode(&advdata, m_adv_data.adv_data.p_data, &m_adv_data.adv_data.len);
    APP_ERROR_CHECK(err_code);

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Fri, 06 Dec 2019 13:32:28 GMT

I see. Generally, you need to debug and see what the fatal error is. If you enable debug builds (Select Debug instead of release from the build target configuration dropdown) and have RTT logging enabled, you will get the error code and location printed in the log. Most of the times this will imediately tell you what the problem is.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 13:28:10 GMT

Ok I've merged them and get a fatal error. Here is my RTT+ beacon code(main) This works when i remove the line advertising_mod:

int main(void)
{
    uint32_t err_code;
    char string[MAX_TEST_DATA_BYTES];
    char c;
    int pos;
    
    T1_data_1 = 0;T1_data_2 = 0;T2_data_1 = 0;T2_data_2 = 0;T3_data_1 = 0;
    T3_data_2 = 0;P1_data_1 = 0;P1_data_2 = 0;P2_data_1 = 0;P2_data_2 = 0;
    // Initialize.
    timers_init();
    leds_init();
    power_management_init();
    ble_stack_init();
    advertising_init();
    //hfxo_enable();

    log_init();

    NRF_LOG_INFO("UART example started.");

    bsp_board_init(BSP_INIT_LEDS);

    const app_uart_comm_params_t comm_params =
      {
          RX_PIN_NUMBER,
          TX_PIN_NUMBER,
          RTS_PIN_NUMBER,
          CTS_PIN_NUMBER,
          UART_HWFC,
          false,
#if defined (UART_PRESENT)
          NRF_UART_BAUDRATE_115200
#else
          NRF_UARTE_BAUDRATE_115200
#endif
      };
    APP_UART_FIFO_INIT(&comm_params,
                         UART_RX_BUF_SIZE,
                         UART_TX_BUF_SIZE,
                         uart_error_handle,
                         APP_IRQ_PRIORITY_LOWEST,
                         err_code);

    APP_ERROR_CHECK(err_code);
    pos = 0;
    //UART get code RTT RX code
    while (true)
    {
        // Get next gyte from FIFO
        while (app_uart_get(&c) != NRF_SUCCESS);
        string[pos] = c;
        // Assume that all strings end with \n. If end, print and start over.
        if (string[pos] == '\n')
        {
            string[pos+1] = '\0';
            NRF_LOG_INFO("Received string: \"%s\"", string);
            pos = 0;
        }
        else
        {
            pos++;
        }
       
        //nrf_delay_ms(1000);//Delay 1 second
        counter++;
        idle_state_handle();
        data_changed = true;
        if(data_changed==true)
        {
          advertising_mod(counter,T1_data_1,T1_data_2,T2_data_1,T2_data_2,00,00,70,80,70,80);//Only have two temperature sensors
          data_changed = false;
        }
    }
}

Here is my other beacon code. This outputs a ble_advert and increments a counter. This can be seen using nrf connect.

int main(void)
{
   
    bool erase_bonds;

    T1_data_1 = 0;T1_data_2 = 0;T2_data_1 = 0;T2_data_2 = 0;T3_data_1 = 0;
    T3_data_2 = 0;P1_data_1 = 0;P1_data_2 = 0;P2_data_1 = 0;P2_data_2 = 0;
    
    // Initialize.
    uart_init();
    log_init();
    timers_init();
    buttons_leds_init(&erase_bonds);
    power_management_init();
    ble_stack_init();
    gap_params_init();
    gatt_init();
    services_init();
    advertising_init();
    conn_params_init();
    bsp_board_led_invert(2);
    // Start execution.
    //printf("\r\nUART started.\r\n");
    
    NRF_LOG_INFO("Debug logging for UART over RTT started.");
    advertising_start();
    advertising_mod(counter,00,00,00,00,00,00,70,80,70,80);//Only have two temperature sensors
    // Enter main loop.
    for (;;)
    {
        nrf_delay_ms(1000);
        //printf("Test\n\r");//Works if the uart board is disconnected
        //printf("Test");//Works if the uart board is disconnecte
        counter ++;
        idle_state_handle();
        data_changed = true;
        if(data_changed==true)
        {
          printf("data changed value is: %d\r\n",data_changed);
          advertising_mod(counter,T1_data_1,T1_data_2,T2_data_1,T2_data_2,00,00,70,80,70,80);//Only have two temperature sensors
          data_changed = false;
          printf("data changed value is: %d\r\n",data_changed);
        }
    }
}

I need to figure a way to merge them and have them both run.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 13:06:23 GMT

Ok thanks, that seemed to work. Now I'll try merging my ble_Advert code with it

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Fri, 06 Dec 2019 12:32:00 GMT

Hi,

I checked your application, and the problem is that you don't process logs in your main loop, so, therefore, you should set NRF_LOG_DEFERRED to 0 in your projects sdk_config.h. With that in place, the RTT log is output correctly.

(I also noticed that you added include paths for specific files rather than for the whole project. Instead of modifying the options for app_uart_fifo.c and main.c, you should instead have added it to the project-wide include path (from Project -> Options...). Not that it really matters, but that is cleaner and easier than adding it for specific files, and is what is done in all our example projects.)

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 12:16:21 GMT

devzone.nordicsemi.com/.../ble_5F00_app_5F00_beacon_5F00_not_5F00_working_5F00_rtt.zip

That is the code I am using inside the ble_peripheral folder

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Fri, 06 Dec 2019 12:14:08 GMT

There are a few other potential issues as well, for instance if you have enabled deferred logging in sdk_config.h, but do not process those. Can you send me your project, including the main.c file and sdk_config.h som that I can see? Also, do you get an errors or warnings when building? Any interesting things when you debug?

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 12:06:33 GMT

Ok I've gone through the entire sdk_config.h for the RTT and compared it to the ble_app_beacon. Changed a few differences where i found them but, the RTT view still does not have anything inside of it.

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Fri, 06 Dec 2019 12:02:00 GMT

Yes, that is also expected. UART logging is default in most BLE examples, and you cannot use the same UART instance for two things at the same time. I should have remembered to mention that as well, but generally, the thing is that there is som many small details that the sensible way of doing this is testing and fixing until it works. And then it does not take much time since every single issue is usually easy to understand from the error (being compile-time, link-time or runtime).

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 11:56:00 GMT

fatal error is gone when i change NRF_LOG_BACKEND_UART_ENABLED from 1 to 0. As this is what it is in the RTT RX sdk_config

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 11:53:45 GMT

Yeah changed those, i get app fatal error to the rtt

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Fri, 06 Dec 2019 11:50:49 GMT

Have you enabled RTT logging in the sdk_config.h file? You need to make sure NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED are both set to 1, and should also set NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED to 0.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 11:44:47 GMT

I've still got a setup / configuration issue. If i remove all the code from the ble_app_beacon example and paste in the RTT RX code.

It does not output data to the RTT but the RTT code (in the peripheral folder does).

But the ble_beacon code complies

RE: Receiving data from UART via a peripheral device

Einar Thorsrud — Fri, 06 Dec 2019 11:34:24 GMT

Hi,

Yes, I forgot to mention that you cannot enable the HFCO the way I did it in the UART example when you have the SoftDevice. Then you need to use the SoftDevice API, or the clock driver which does it for you. Then you enable the clock by a call to nrf_drv_clock_hfclk_request(). Alternatively, you can just remove that part of the code (i.e. not start the HFXO) if that is OK for the UART communication.

Note that if current consumption is an issue, you should only enable the HFXO when there is a UART transaction. That is a bit hidden when you use app_uart_fifo, since all happens in the library. So if you stick with that approach you can implement it in the library.

RE: Receiving data from UART via a peripheral device

Thomas — Fri, 06 Dec 2019 10:54:53 GMT

The error i think comes from hfxo_enable.

One issue is though if I use your RTT RX code, it crashes when I debug and try stepping through. So I presume when I merge the projects I won't be able to debug it via the debugger.