init of one UARTE OK but subsequent UARTE failing in slightly modified example in .../examples/libuarte/main.c

RE: init of one UARTE OK but subsequent UARTE failing in slightly modified example in .../examples/libuarte/main.c

Edvin — Fri, 14 Jan 2022 10:44:55 GMT

It looks like the libuarte library is really not made to handle two instances at once efficiently, because they require one timer and one rtc each.

This worked for me:

NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte2, 1, 1, 2, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 255, 3);

It means that libuarte1 is using UARTE instance nr. 0, timer 0 and RTC0,

then libuarte2 is using UARTE instance nr.1, timer1 and RTC2.

I tried to set it up with RTC1, but since app_timer is enabled in the libuarte project, it wouldn't let me.use RTC1 as this is used by the app_timer.

Remember to enable TIMER1 and RTC2 in sdk_config.h.

Now again, do you really need to use libuarte? The other UART implementations require less resources. If you intend to use the softdevice and app_timer in your application, then this will not work, because you don't have two spare RTCs. The softdevice uses RTC0 and the app_timer uses RTC1, leaving you with RTC2.

In case you just used libuarte because it was the first thing you came across, I suggest you look into the UART implementation from ble_app_uart, and try to get that up and running with two instances.

Best regards,

Edvin

RE: init of one UARTE OK but subsequent UARTE failing in slightly modified example in .../examples/libuarte/main.c

William Wiese — Wed, 12 Jan 2022 21:55:11 GMT

Hi Edvin..

Update...

With config as
...
NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 4);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte2, 1, 0, 1, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 4);
...

or even
...
NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 0, 0, 0, n1, 128, 4);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte2, 1, 0, 1, n2, 128, 4);

where n=0, 2 etc and same or different....

We also need necessary elevating of config structure's .int_prio field to APP_IRQ_PRIORITY_MID (i.e,,. > ..._LOW).

So we are now progressing thru codeflow to

nrf_libuarte_async_init(...) lines 530-533
| |
+---> nrf_libuarte_drv_init(...) lines 493-496, with NRF_ERR_INTERNAL via call to nrfx_timer_init(&p_libuarte->timer, &tmr_config, tmr_evt_handler);

Helping me understand basic config in the ..._DEFINE setup for two UARTEs without conflict of associated elements/assets/timers
might be helpful

Thx
Bill

RE: init of one UARTE OK but subsequent UARTE failing in slightly modified example in .../examples/libuarte/main.c

William Wiese — Wed, 12 Jan 2022 19:05:54 GMT

Edvin,
Slight changes to declarations

NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 3);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte2, 1, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 3);

result in err_code on 2nd ...init() call being 3 instead of 7.

err_code == 3 : NRF_ERROR_INTERNAL (??)

err_code == 7: NRF_ERROR_INVALID_PARAM

My bet is that my parameter setups in NRF...DEFINE are conflicting/screwed up.

RE: init of one UARTE OK but subsequent UARTE failing in slightly modified example in .../examples/libuarte/main.c

William Wiese — Wed, 12 Jan 2022 18:31:01 GMT

Edvin,

I quickly got RTTView setup - still have to bring up Ozone. The err_code value for the second 'init' call
we're discussing:

err_code = nrf_libuarte_async_init(&libuarte2,
&nrf_libuarte_async_config[1],
uart_event_handler2,
(void *)&libuarte2);

is 7 and then Fatal Error (see below).

Again, this call works fine if the first call to ...init(....) is not made and both UARTE0 and 1 work fine separately (if indeed the indexing is working OK in the ...DEFINE macro.

BTW, are the parameters of my config at top of code OK for NRF_LIBUARTE_ASYNC_DEFINE(...) ??

NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 3);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte2, 1, 0, 1, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 3);

Thanks
Bill

RTTView Output:

00> Here Start
00> Here 0
00> err_code = 0...
00> Here 1
00> err_code = 7...
00> <error> app: Fatal error
00>

RE: init of one UARTE OK but subsequent UARTE failing in slightly modified example in .../examples/libuarte/main.c

William Wiese — Wed, 12 Jan 2022 18:30:20 GMT

Edvin,
I quickly got RTTView setup - still have to bring up Ozone. The err_code value for the second 'open' call
we are discussing:

err_code = nrf_libuarte_async_init(&libuarte2, &nrf_libuarte_async_config[1], uart_event_handler2, (void *)&libuarte2);

is 7 and then Fatal Error.

BTW, are the parameters of my config at top of code OK for NRF_LIBUARTE_ASYNC_DEFINE(...) ??

NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 3);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte2, 1, 0, 1, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 3);

When I use

NRF_LIBUARTE_ASYNC_DEFINE(libuarte1, 0, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 3);
NRF_LIBUARTE_ASYNC_DEFINE(libuarte2, 1, 0, 0, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 128, 3);

the err_code on the 2nd init call is 3 instead and then fatal error.

Thanks
Bill

RTTView Output:

00> Here Start
00> Here 0
00> err_code = 0...
00> Here 1
00> err_code = 7...
00> <error> app: Fatal error
00>

RE: init of one UARTE OK but subsequent UARTE failing in slightly modified example in .../examples/libuarte/main.c

Edvin — Wed, 12 Jan 2022 14:32:01 GMT

Hello,

What does

err_code = nrf_libuarte_async_init(&libuarte2, &nrf_libuarte_async_config[1], uart_event_handler2, (void *)&libuarte2);

return?

If you haven't connected the debugger yet (which I suggests you do for help during development), try to print err_code instead of passing it into APP_ERROR_CHECK(err_code);

Best regards,

Edvin

RE: init of one UARTE OK but subsequent UARTE failing in slightly modified example in .../examples/libuarte/main.c

William Wiese — Wed, 12 Jan 2022 02:51:08 GMT

(BTW, SDK 17.0.2)