<?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 Re: Timeouts in LPUART with FreeRTOS in MCUXpresso General</title>
    <link>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875297#M1582</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Erich,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for this, and sorry for the delay of my reply; I'll take a look.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am thinking, in any case, that I'll have to modify the MCUXpresso API, but I was hoping that NXP would consider modifying the standard API.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Feb 2019 07:56:26 GMT</pubDate>
    <dc:creator>andrew_walsh</dc:creator>
    <dc:date>2019-02-11T07:56:26Z</dc:date>
    <item>
      <title>Timeouts in LPUART with FreeRTOS</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875295#M1580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently planning to use the LPUART FreeRTOS driver (fsl_lpuart_freertos.*) from the&amp;nbsp;MCUXpresso SDK, but I've noticed that it is not possible to specify a timeout. This appears to be the case in 2.5.0, which I think is the latest (dated 11th Jan 2019).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, inside the function&amp;nbsp;LPUART_RTOS_Send(), there is a call to&amp;nbsp;LPUART_TransferSendNonBlocking(), followed by a call to the FreeRTOS&amp;nbsp;xEventGroupWaitBits(), which is as I might expect. The problem, however, is that a hardcoded value, portMAX_DELAY is passed for the parameter&amp;nbsp;xTicksToWait, which I think means it will wait forever.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would NXP consider modifying the SDK, providing an extra parameter to&amp;nbsp;LPUART_RTOS_Send() which would allow this wait time to be specified? If &lt;SPAN&gt;xEventGroupWaitBits() then&amp;nbsp;&lt;/SPAN&gt;returns with no event bits set, &lt;SPAN&gt;LPUART_RTOS_Send()&lt;/SPAN&gt; would call&amp;nbsp;LPUART_TransferAbortSend(), perhaps?&lt;/P&gt;&lt;P&gt;If this change was made, I think similar modifications would also be needed in&amp;nbsp;LPUART_RTOS_Receive().&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2019 09:05:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875295#M1580</guid>
      <dc:creator>andrew_walsh</dc:creator>
      <dc:date>2019-01-31T09:05:08Z</dc:date>
    </item>
    <item>
      <title>Re: Timeouts in LPUART with FreeRTOS</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875296#M1581</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andrew,&lt;/P&gt;&lt;P&gt;you might have a look at the files in &lt;A class="link-titled" href="https://github.com/ErichStyger/mcuoneclipse/blob/master/Examples/MCUXpresso/i.MX%20RT1064_EVK/MIMXRT1064_FreeRTOS/source/uart.c" title="https://github.com/ErichStyger/mcuoneclipse/blob/master/Examples/MCUXpresso/i.MX%20RT1064_EVK/MIMXRT1064_FreeRTOS/source/uart.c"&gt;mcuoneclipse/uart.c at master&amp;nbsp; · GitHub&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;where it implements a simple non-blocking UART driver with FreeRTOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2019 17:58:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875296#M1581</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2019-01-31T17:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: Timeouts in LPUART with FreeRTOS</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875297#M1582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Erich,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for this, and sorry for the delay of my reply; I'll take a look.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am thinking, in any case, that I'll have to modify the MCUXpresso API, but I was hoping that NXP would consider modifying the standard API.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Feb 2019 07:56:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875297#M1582</guid>
      <dc:creator>andrew_walsh</dc:creator>
      <dc:date>2019-02-11T07:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: Timeouts in LPUART with FreeRTOS</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875298#M1583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Andrew:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your good suggestion, I will issue a feature request to the develop team.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Feb 2019 15:09:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/875298#M1583</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2019-02-18T15:09:11Z</dc:date>
    </item>
    <item>
      <title>Re: Timeouts in LPUART with FreeRTOS</title>
      <link>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/1248859#M4123</link>
      <description>&lt;P&gt;Hiii I tried your code&amp;nbsp;&lt;A href="https://github.com/ErichStyger/mcuoneclipse/blob/f2a1361e8a49cc0a2428618796fde21d559cc304/Examples/MCUXpresso/i.MX%20RT1064_EVK/MIMXRT1064_FreeRTOS/source/uart.c" target="_self"&gt;https://github.com/ErichStyger/mcuoneclipse/blob/f2a1361e8a49cc0a2428618796fde21d559cc304/Examples/MCUXpresso/i.MX%20RT1064_EVK/MIMXRT1064_FreeRTOS/source/uart.c&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;void UART_Init(void) {
  MSG_Init();
  if (xTaskCreate(UartTask,      /* pointer to the task                      */
          "UartTask",            /* task name for kernel awareness debugging */
          500/sizeof(portSTACK_TYPE),  /* task stack size                          */
          NULL,                      /* optional task startup argument           */
          tskIDLE_PRIORITY+1,       /* initial priority                         */
          NULL /* optional task handle to create           */
          ) != pdPASS)
  {
      for(;;) {}
  }
  MSG_SendStringTxQueue("AT\r");
  MSG_SendStringTxQueue("AT+CSQ\r");
}&lt;/LI-CODE&gt;&lt;P&gt;Then it transmits both the string together("AT\rAT+CSQ\r"). I checked here&amp;nbsp;&lt;STRONG&gt;MSG_GetStringTxQueue(localBuf, sizeof(localBuf));&lt;/STRONG&gt; and gives response of first string.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Mar 2021 10:32:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-General/Timeouts-in-LPUART-with-FreeRTOS/m-p/1248859#M4123</guid>
      <dc:creator>Meera_123</dc:creator>
      <dc:date>2021-03-19T10:32:32Z</dc:date>
    </item>
  </channel>
</rss>

