<?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: MQX 4.2 RTCS TCP/IP Crash in MQX Software Solutions</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-RTCS-TCP-IP-Crash/m-p/399067#M13380</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joseph,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what happens here is that if the timeout expires TCP/IP task is removed from ready queue and is sent to Timeout queue, then the scheduler is called to check for other tasks and TCP/IP task will never come back form timeout state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can work around this in different ways. I think a good option is to have another task that is checking the Ethernet link is up. You can do this with the following function:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ipcfg_get_link_active(BSP_DEFAULT_ENET_DEVICE);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then if the link is broken you need to wait until time out expires and if the link is still broken you keep monitoring the link until it is up. Then you can move TCP/IP task to ready state as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;_task_ready(_task_get_td(_task_get_id_from_name("TCP/IP")));&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Carlos&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Sep 2015 21:26:30 GMT</pubDate>
    <dc:creator>Carlos_Musich</dc:creator>
    <dc:date>2015-09-23T21:26:30Z</dc:date>
    <item>
      <title>MQX 4.2 RTCS TCP/IP Crash</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-RTCS-TCP-IP-Crash/m-p/399066#M13379</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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I have found that if I suddenly disconnect the Internet while downloading files through FTP, it will just hang there. If I force to restart my FTP downloading task, TCPIP task will crash in unhandled interrupt. Has anyone encountered the similar issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Joseph Chen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2015 07:02:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-RTCS-TCP-IP-Crash/m-p/399066#M13379</guid>
      <dc:creator>josephchen</dc:creator>
      <dc:date>2015-08-26T07:02:03Z</dc:date>
    </item>
    <item>
      <title>Re: MQX 4.2 RTCS TCP/IP Crash</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-RTCS-TCP-IP-Crash/m-p/399067#M13380</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joseph,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what happens here is that if the timeout expires TCP/IP task is removed from ready queue and is sent to Timeout queue, then the scheduler is called to check for other tasks and TCP/IP task will never come back form timeout state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can work around this in different ways. I think a good option is to have another task that is checking the Ethernet link is up. You can do this with the following function:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ipcfg_get_link_active(BSP_DEFAULT_ENET_DEVICE);&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then if the link is broken you need to wait until time out expires and if the link is still broken you keep monitoring the link until it is up. Then you can move TCP/IP task to ready state as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;_task_ready(_task_get_td(_task_get_id_from_name("TCP/IP")));&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Carlos&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Sep 2015 21:26:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-RTCS-TCP-IP-Crash/m-p/399067#M13380</guid>
      <dc:creator>Carlos_Musich</dc:creator>
      <dc:date>2015-09-23T21:26:30Z</dc:date>
    </item>
  </channel>
</rss>

