testing with nrF52 dev kit board - using libuarte - SDK 16.0
See NRF_UARTE_EVENT_ERROR - what error/condition triggers this ?
Using 115200 baud,
testing with nrF52 dev kit board - using libuarte - SDK 16.0
See NRF_UARTE_EVENT_ERROR - what error/condition triggers this ?
Using 115200 baud,
If you look into the product spec you can find this:
35.5 Error conditions
An ERROR event, in the form of a framing error, will be generated if a valid stop bit is not detected in a
frame. Another ERROR event, in the form of a break condition, will be generated if the RXD line is held
active low for longer than the length of a data frame. Effectively, a framing error is always generated before a
break condition occurs.
An ERROR event will not stop reception. If the error was a parity error, the received byte will still be
transferred into Data RAM, and so will following incoming bytes. If there was a framing error (wrong stop bit),
that specific byte will NOT be stored into Data RAM, but following incoming bytes will
Please try to debug using a logic analyzer.
If you look into the product spec you can find this:
35.5 Error conditions
An ERROR event, in the form of a framing error, will be generated if a valid stop bit is not detected in a
frame. Another ERROR event, in the form of a break condition, will be generated if the RXD line is held
active low for longer than the length of a data frame. Effectively, a framing error is always generated before a
break condition occurs.
An ERROR event will not stop reception. If the error was a parity error, the received byte will still be
transferred into Data RAM, and so will following incoming bytes. If there was a framing error (wrong stop bit),
that specific byte will NOT be stored into Data RAM, but following incoming bytes will
Please try to debug using a logic analyzer.
Hello Hung,
Thanks for the feedback/information on error/operation.
Regards