Kinetis MicrocontrollersのトピックRe: MKE14F: Where's UART Error interrupt

MKE14F: Where's UART Error interrupt

michaelheidinge — Mon, 10 Jul 2017 16:21:11 GMT

Is it right, that there's no interrupt source assigned in the MKE14F to the UART1 communication error?

Re: MKE14F: Where's UART Error interrupt

egoodii — Mon, 10 Jul 2017 19:26:38 GMT

Which is to say there are no errors that are not directly associated with receiving a character (RDRF set), so it is necessary and sufficient to read LPUARTx_STAT prior to LPUARTx_DATA to ascertain 'error' associated with the RX interrupt.

Re: MKE14F: Where's UART Error interrupt

kerryzhou — Tue, 11 Jul 2017 06:16:53 GMT

Hello Michael Heidinger,

About the LPUART1 error interrupt, you can check the reference manual, LPCUART control register, there have these errors interrupt:

Noise Error Interrupt Enable

Framing Error Interrupt Enable

Parity Error Interrupt Enable

Overrun Interrupt Enable

Wish it helps you!

Have a great day,
Kerry

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: MKE14F: Where's UART Error interrupt

michaelheidinge — Tue, 15 Aug 2017 16:13:11 GMT

But NVIC is missing interrupt error, or do i see it wrong?

Re: MKE14F: Where's UART Error interrupt

egoodii — Tue, 15 Aug 2017 17:21:47 GMT

I see your point, in that while the LPUART has the 'error interrupt enable' bits, there is no independent vector for them --- but, as before, every error is again directly associated with an RDF indication --- all I can suppose is that the 'error interrupt' could give you an RX interrupt while your watermark has not yet been hit.

Since every error indication still involves reading from the DATA register, what are you hoping to gain from an independent interrupt vector (as opposed to just checking for any 'error indications' prior to data-register-offload in the RX interrupt handler)?