topic Re: IMXRT LPUART non-blocking transfer API makes error handling difficult in i.MX RT Crossover MCUs

IMXRT LPUART non-blocking transfer API makes error handling difficult

nxp16 — Mon, 13 Jul 2026 11:53:08 GMT

Hi,

I've been looking at the "transfer" API for LPUART, for interrupt-based non-blocking transfers. It seems to do a decent job of wrapping all the "happy case" handling of LPUART interrupts, etc, and providing a good high level API for just receiving data when it's ready (i.e. handling IDLE, RX ready, TX complete, etc). However, it makes handling UART errors very difficult.

There is no error handling inside the LPUART_TransferHandleIRQ function, and just after that function in fsl_lpuart.c is a bogus empty LPUART_TransferHandleErrorIRQ containing a comment "To be implemented by the user". This looks completely half-baked.

The only way to actually handle UART errors seems to be to override the default LPUARTx_IRQHandler functions so that instead of calling LPUARTx_RX_DriverIRQHandler (or TX), you'd have to call your own function that handles errors and passes on "happy case" interrupts to the original LPUARTx_RX/TX_DriverIRQHandler so it can call into LPUART_TransferHandleErrorIRQ.

In addition you'd have to enable those error interrupts yourself outside the transfer API by calling LPUART_EnableInterrupts, and in your error handling also call LPUART_DisableInterrupts and deal with clearing them, etc.

This seems like a lot of extra hassle to handle errors. Why is this not baked into the transfer API itself?

-m

Re: IMXRT LPUART non-blocking transfer API makes error handling difficult

Habib_MS — Mon, 13 Jul 2026 21:57:17 GMT

Hello @nxp16,

Thank you for the detailed feedback. I understand that the SDK could be a little ambiguous since these are intended to provide a common use cases for each peripheral functionality. We are constantly working to improve our APIs thanks also of recommendations like this. Thank you for the recommendations, and we hope that LPUART's error handling will be implemented in future releases.
On the other hand, could you please let me know which specific error conditions you are interested in handling and which device you are using? With that information, I can suggest documentation related to those error conditions that may help with your implementation.

BR
Habib

Re: IMXRT LPUART non-blocking transfer API makes error handling difficult

nxp16 — Tue, 14 Jul 2026 11:44:04 GMT

All possible errors. This applies to pretty much all peripherals (SPI, I2C, etc) that have a transfer API but no error handling. LPUART on IMXRT1172 specifically has framing, parity, and noise errors that aren't handled. Unfortunately right now all these peripherals require some hacking to handle errors when using the transfer API. I had to override the actual default IRQ handlers to check for errors before calling the SDK handler.

Thanks,

-m

Re: IMXRT LPUART non-blocking transfer API makes error handling difficult

Habib_MS — Tue, 14 Jul 2026 21:04:27 GMT

Hello @nxp16,

I understand that this may require additional development time, sorry for that, we continuing working to improve our SDKs. As a reference, you may review the following structure of the SDK (version 26.6) function called "LPUART_TransferHandleIRQ" and implement a similar recovery flow as your application requires.

BR
Habib

Re: IMXRT LPUART non-blocking transfer API makes error handling difficult

nxp16 — Wed, 15 Jul 2026 11:56:56 GMT

Yes, I've already implemented something similar. Thanks for sending that.

Re: IMXRT LPUART non-blocking transfer API makes error handling difficult

Habib_MS — Wed, 15 Jul 2026 21:50:28 GMT

Hello @nxp16,

Please let me know if you have any further questions.
BR
Habib