error app: Fatal error ?

RE: error app: Fatal error ?

Einar Thorsrud — Fri, 17 Sep 2021 09:58:21 GMT

I am not sure, that depends on the root cause of this issue. Which SDK version are you using?

RE: error app: Fatal error ?

RixtronixLAB — Fri, 17 Sep 2021 09:03:56 GMT

do you think 1024 for RxBuffer ?

RE: error app: Fatal error ?

Einar Thorsrud — Fri, 17 Sep 2021 08:48:13 GMT

Hi,

I do not see that the baud rate is relevant here. Did you try to increase the buffer? There is also a thread here, which may be relevant.

RE: error app: Fatal error ?

RixtronixLAB — Fri, 17 Sep 2021 07:52:58 GMT

[quote userid="7377" url="~/f/nordic-q-a/79559/error-app-fatal-error/329849#329849"]NRF_CLI_LIBUARTE_DEF().[/quote]

I have uint8_t rxBuffer[256];

for libuarte GPS , I try reducing the size but still got the same error, any ideas ?,

How can I handle incoming data faster ? it's connected at 9600 baud, is it too slow ? thanks

    nrf_libuarte_async_config_t nrf_libuarte_async_config1 = {
            .tx_pin     = SER_APP_TX_PIN,
            .rx_pin     = SER_APP_RX_PIN,
            .baudrate   = NRF_UARTE_BAUDRATE_9600,
            .parity     = NRF_UARTE_PARITY_EXCLUDED,
            .hwfc       = NRF_UARTE_HWFC_DISABLED,
            .timeout_us = 1000,
            .int_prio   = APP_IRQ_PRIORITY_LOW

RE: error app: Fatal error ?

Einar Thorsrud — Thu, 16 Sep 2021 12:52:37 GMT

Hi,

Looking at the code line 230 has the APP_ERROR_CHECK_BOOL you see in this snippet:

    case NRF_LIBUARTE_DRV_EVT_RX_BUF_REQ:
    {
        if (p_libuarte->p_ctrl_blk->rx_halted)
        {
            break;
        }

        if (rx_buffer_schedule(p_libuarte) == false)
        {
            if (p_libuarte->p_ctrl_blk->hwfc)
            {
                p_libuarte->p_ctrl_blk->rx_halted = true;
            }
            else
            {
                NRF_LOG_ERROR("(evt) Failed to allocate buffer for RX.");
                APP_ERROR_CHECK_BOOL(false);
            }
        }
        break;

So it seems like you are not handling incoming data fast enough in your application. I suggest you either try to handle incoming data faster, or change the buffer sizes which you configure where you use NRF_CLI_LIBUARTE_DEF().

RE: error app: Fatal error ?

RixtronixLAB — Thu, 16 Sep 2021 12:42:24 GMT

I got this error :

<error> app: ERROR 0 [NRF_SUCCESS] at ..\..\..\..\..\..\..\..\components\librari

\libuarte\nrf_libuarte_async.c:230

at: 0x000390A3

rror> app: End of error report

How can I rectify it ? thanks

RE: error app: Fatal error ?

RixtronixLAB — Thu, 16 Sep 2021 07:18:36 GMT

Thanks Einar, I'm compiling and uploading now, I'll keep posted

RE: error app: Fatal error ?

Einar Thorsrud — Thu, 16 Sep 2021 06:33:17 GMT

With Keil, go to Project -> Options for Target ...., and then select the C/C++ tab. There add "DEBUG" and "DEBUG_NRF" to the preprocessor define list as shown here:

If you want to debug (break in code, inspect with a debugger etc.) it makes sense to also set the optimization level to 0. That is not related to logging, though.

RE: error app: Fatal error ?

RixtronixLAB — Thu, 16 Sep 2021 05:22:09 GMT

I get a clue just now, when the board lost connection with the sensor, ANT HRM sensor, it's giving me

"error app: Fatal error"

If I used Keil, how can set "Debug" build ?

RE: error app: Fatal error ?

Einar Thorsrud — Mon, 13 Sep 2021 06:45:39 GMT

Hi,

[quote user=""]I can't see an error code ?[/quote]

You will get more information (file name, line number and error code) by testing with a debug build. If you use a Segger embedded studio project from the SDK, simply select "Debug" from the build configurations dropdown menu. If using something else, define "DEBUG" and "DEBUG_NRF".

[quote user=""]Is it possible hardware error because voltage surge ? Can capacitor rectify it ?[/quote]

We need to know what the error code was and from where it was returned before we can consider what caused it and how it can be fixed.