<?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 S32K144 interrupt based UART: STATUS_UART_NOISE_ERROR in Model-Based Design Toolbox (MBDT)</title>
    <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K144-interrupt-based-UART-STATUS-UART-NOISE-ERROR/m-p/870865#M2903</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a interrupt driven UART inplementation (SDK version is 2.0.0 and I'm using regular lpuart driver, not pal or flexio) in which I need to look at each received byte, as they arrive. Thus, I use:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/* Get last transfer status */&lt;BR /&gt; result = LPUART_DRV_GetReceiveStatus(INST_UART, NULL);&lt;BR /&gt; if (STATUS_SUCCESS == result)&lt;BR /&gt; {&lt;BR /&gt; /* Execute send non-blocking */&lt;BR /&gt; LPUART_DRV_ReceiveData(INST_UART, inst_datum, 1U);&lt;BR /&gt; }&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...where "inst_datum" is a one-byte buffer.&lt;/P&gt;&lt;P&gt;Also, I have a Rx callback installed which retrieves the content o inst_datum and calls the Rx code above for next byte reception.&lt;/P&gt;&lt;P&gt;It works, as far as the bytes arrival rate is not too high. If bytes arrival gets too fast, lpuart triggers a&amp;nbsp;STATUS_UART_NOISE_ERROR interrupt.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any hints?&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Joao&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Mar 2019 20:26:24 GMT</pubDate>
    <dc:creator>Joao_Roscoe</dc:creator>
    <dc:date>2019-03-19T20:26:24Z</dc:date>
    <item>
      <title>S32K144 interrupt based UART: STATUS_UART_NOISE_ERROR</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K144-interrupt-based-UART-STATUS-UART-NOISE-ERROR/m-p/870865#M2903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a interrupt driven UART inplementation (SDK version is 2.0.0 and I'm using regular lpuart driver, not pal or flexio) in which I need to look at each received byte, as they arrive. Thus, I use:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/* Get last transfer status */&lt;BR /&gt; result = LPUART_DRV_GetReceiveStatus(INST_UART, NULL);&lt;BR /&gt; if (STATUS_SUCCESS == result)&lt;BR /&gt; {&lt;BR /&gt; /* Execute send non-blocking */&lt;BR /&gt; LPUART_DRV_ReceiveData(INST_UART, inst_datum, 1U);&lt;BR /&gt; }&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...where "inst_datum" is a one-byte buffer.&lt;/P&gt;&lt;P&gt;Also, I have a Rx callback installed which retrieves the content o inst_datum and calls the Rx code above for next byte reception.&lt;/P&gt;&lt;P&gt;It works, as far as the bytes arrival rate is not too high. If bytes arrival gets too fast, lpuart triggers a&amp;nbsp;STATUS_UART_NOISE_ERROR interrupt.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any hints?&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Joao&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Mar 2019 20:26:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K144-interrupt-based-UART-STATUS-UART-NOISE-ERROR/m-p/870865#M2903</guid>
      <dc:creator>Joao_Roscoe</dc:creator>
      <dc:date>2019-03-19T20:26:24Z</dc:date>
    </item>
    <item>
      <title>Re: S32K144 interrupt based UART: STATUS_UART_NOISE_ERROR</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K144-interrupt-based-UART-STATUS-UART-NOISE-ERROR/m-p/870866#M2904</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/t_62835@cpqd.com.br"&gt;t_62835@cpqd.com.br&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On this community we handle questions regarding MATLAB/Simulink and our toolboxes - this question would be more appropriate for&amp;nbsp;&lt;A href="https://community.nxp.com/space/11492"&gt;S32K&lt;/A&gt;&amp;nbsp;community.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My thoughts - check if the clock that you are using is suitable for your baud rate. Check if the clock is stable for said baudrate. Check what OSR (over-sampling ratio) you are using. You can get more details in the&amp;nbsp;&lt;STRONG&gt;Data sampling technique&amp;nbsp;&lt;/STRONG&gt;and&lt;STRONG&gt;&amp;nbsp;&lt;STRONG&gt;Baud rate generation&lt;/STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;chapters (from LPUART Functional Description). You'll get more help on the S32K community (previously linked).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S.: it's always recommended that you are using the latest SDK version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Razvan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2019 09:07:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K144-interrupt-based-UART-STATUS-UART-NOISE-ERROR/m-p/870866#M2904</guid>
      <dc:creator>constantinrazva</dc:creator>
      <dc:date>2019-03-20T09:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: S32K144 interrupt based UART: STATUS_UART_NOISE_ERROR</title>
      <link>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K144-interrupt-based-UART-STATUS-UART-NOISE-ERROR/m-p/870867#M2905</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for posting off topic, and thank you for your time, your hints are welcome, anyway.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Joao&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Mar 2019 12:38:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/S32K144-interrupt-based-UART-STATUS-UART-NOISE-ERROR/m-p/870867#M2905</guid>
      <dc:creator>Joao_Roscoe</dc:creator>
      <dc:date>2019-03-20T12:38:48Z</dc:date>
    </item>
  </channel>
</rss>

