Assertions in uarte driver due to framing and parity errors can't be overridden.

[TomKeddie]

Hi,

I'm seeing frequent assertions the uarte driver (sdk/components/libraries/experimental_libuarte/nrf_libuarte_async.c) due to framing and parity errors.  These are expected since the pin is not always connected so I need to be able to handle them gracefully.  At the moment they hit the default condition in uart_evt_handler() and assert, there needs to be a user callback available so they can be handled gracefullly.

I'm using S132 and SDK 15.2 on an nrf52832.

Thanks,
Tom

[Edvin]

Hello,

Is the assert that you speak of the APP_UART_COMMUNICATION_ERROR in uart_event_handle() in main.c?

If so, as you say, they are expected if you have some floating pins. What you can do is to not pass the p_event->data.error_communication into the APP_ERROR_HANDLER().

If it is something else, can you please describe what sort of default condition you are speaking of?

Best regards,

Edvin

[TomKeddie]

Hi Edvin,

It's in nrf_libuarte_async.c in uart_evt_handler() at line 158.  The callback handles all the event types except NRF_LIBUARTE_EVT_ERROR.  I see framing errors assert here.

Thanks,

Tom

[Edvin]

As you say, this is an experimental library. The error handler is currently what is causing the resets, because the APP_ERROR_BOOL_CHECK(value) will reset the device if "value" is not 1.

I am not sure what changes our developers will do to this file, but as of now, I suggest you just add the error event that I described in the previous reply. Alternatively, you can change the callback function in nrf_libuarte_async_init()

And point it to a function in main.c, or wherever you like it.

Either way, if you don't want it to reset at this point in time, your only option is to do some modifications in this file.

Best regards,

Edvin

[TomKeddie]

Edvin,

Please provide this feedback to the developers.  I sure you understand it's not sustainable for developers to update local copies each time an SDK is released.

Thanks,
Tom

[Edvin]

Thank you Tom, I have.

But as you probably understood, with the current release, you must do these changes if you want to disable the resets when unplugging and plugging the uart.

BR,

Edvin

[TomKeddie]

*bump*

This is still broken in 15.3.

Thanks,

Tom

[Edvin]

Thanks for the reminder, Tom.

I bumped the internal ticket.