<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic LPUART_UART_IP_STATUS_RX_OVERRUN Issue When Sending More Than 14 Characters in S32K</title>
    <link>https://community.nxp.com/t5/S32K/LPUART-UART-IP-STATUS-RX-OVERRUN-Issue-When-Sending-More-Than-14/m-p/2051036#M46233</link>
    <description>&lt;P&gt;I am working with UART communication using LPUART on S32K322 and encountering an issue when receiving more than 14 characters. Specifically, when calling&amp;nbsp;Lpuart_Uart_Ip_GetReceiveStatus&amp;nbsp;&lt;FONT color="#000000"&gt;I get the error&amp;nbsp;LPUART_UART_IP_STATUS_RX_OVERRUN&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Could you please provide insights into:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The possible reasons for this overrun error?&lt;/LI&gt;&lt;LI&gt;Any known limitations on the receive buffer size for LPUART?&lt;/LI&gt;&lt;LI&gt;Recommended configurations or workarounds to prevent RX overruns (e.g., increasing buffer size, adjusting FIFO settings,)?&lt;/LI&gt;&lt;LI&gt;Any specific SDK settings or driver modifications that might help resolve this?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Any guidance related to this issue would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Feb 2025 17:56:47 GMT</pubDate>
    <dc:creator>pramodvittal09</dc:creator>
    <dc:date>2025-02-25T17:56:47Z</dc:date>
    <item>
      <title>LPUART_UART_IP_STATUS_RX_OVERRUN Issue When Sending More Than 14 Characters</title>
      <link>https://community.nxp.com/t5/S32K/LPUART-UART-IP-STATUS-RX-OVERRUN-Issue-When-Sending-More-Than-14/m-p/2051036#M46233</link>
      <description>&lt;P&gt;I am working with UART communication using LPUART on S32K322 and encountering an issue when receiving more than 14 characters. Specifically, when calling&amp;nbsp;Lpuart_Uart_Ip_GetReceiveStatus&amp;nbsp;&lt;FONT color="#000000"&gt;I get the error&amp;nbsp;LPUART_UART_IP_STATUS_RX_OVERRUN&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Could you please provide insights into:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The possible reasons for this overrun error?&lt;/LI&gt;&lt;LI&gt;Any known limitations on the receive buffer size for LPUART?&lt;/LI&gt;&lt;LI&gt;Recommended configurations or workarounds to prevent RX overruns (e.g., increasing buffer size, adjusting FIFO settings,)?&lt;/LI&gt;&lt;LI&gt;Any specific SDK settings or driver modifications that might help resolve this?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Any guidance related to this issue would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Feb 2025 17:56:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/LPUART-UART-IP-STATUS-RX-OVERRUN-Issue-When-Sending-More-Than-14/m-p/2051036#M46233</guid>
      <dc:creator>pramodvittal09</dc:creator>
      <dc:date>2025-02-25T17:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: LPUART_UART_IP_STATUS_RX_OVERRUN Issue When Sending More Than 14 Characters</title>
      <link>https://community.nxp.com/t5/S32K/LPUART-UART-IP-STATUS-RX-OVERRUN-Issue-When-Sending-More-Than-14/m-p/2051436#M46251</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;The driver changes UartState-&amp;gt;ReceiveStatus to LPUART_UART_IP_STATUS_RX_OVERRUN if the flag OR = 1 in the STAT register.&lt;BR /&gt;Refer to Lpuart_Uart_Ip_ErrIrqHandler() in Lpuart_Uart_Ip.c&lt;BR /&gt;This flag is set when STAT[RDRF] = 1, and the driver fails to read the data before another byte is received, the data register overflows.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I don't know how many bytes you sent and what argument you pass as the RxSize parameter in Lpuart_Uart_Ip_AsyncReceive().&lt;BR /&gt;If you send more bytes than what was passed to the AsyncReceive() function, the overrun can be avoided by using this API of the Uart_Ip driver: Lpuart_Uart_Ip_SetRxBuffer()&lt;BR /&gt;Refer to this example:&amp;nbsp;&lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/Lpuart-Ip-Set-Tx-Buffer-Example-S32K344-S32DS35-RTD400-P24/ta-p/1909776" target="_self"&gt;Lpuart_Ip_Set_Tx_Buffer_Example_S32K344_S32DS35_RTD400_P24&lt;/A&gt;&lt;BR /&gt;In the callback, check for LPUART_UART_IP_EVENT_RX_FULL and update the buffer using Lpuart_Uart_Ip_SetRxBuffer().&lt;BR /&gt;If you use the interrupt mode, I would recommend using a higher priority for the RX interrupt so that the core can read the LPUART RX FIFO in time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If the length of data to be received is not fixed and varies time to time, then it is recommended to refer to &lt;A href="https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/S32K/36096/1/Uart_Idle_S32K344_LLD_RTD400.zip" target="_self"&gt;Uart_Idle_S32K344_LLD_RTD400.zip&lt;/A&gt; attached in &lt;A href="https://community.nxp.com/t5/S32K/DMA-UART-IDLE/td-p/1875524" target="_self"&gt;DMA UART IDLE&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Robin&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 07:21:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/LPUART-UART-IP-STATUS-RX-OVERRUN-Issue-When-Sending-More-Than-14/m-p/2051436#M46251</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2025-02-26T07:21:43Z</dc:date>
    </item>
  </channel>
</rss>

