<?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: MCC timeout after exactly one hour in Vybrid Processors</title>
    <link>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356724#M3652</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/timesyssupport"&gt;timesyssupport&lt;/A&gt; can you attend this case?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 31 Oct 2014 18:43:42 GMT</pubDate>
    <dc:creator>karina_valencia</dc:creator>
    <dc:date>2014-10-31T18:43:42Z</dc:date>
    <item>
      <title>MCC timeout after exactly one hour</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356723#M3651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear freescale team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are using MCC function mcc_send for sample transfer between M4 and A5 on a Vybrid (details of our system see thread 329003). This is running fine on M4, but returning MCC_ERR_TIMEOUT just before an hour has been completed&lt;/P&gt;&lt;P&gt;(we have the timestamp 59:48:xxx or 59:50:xxx on the debug message).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our question: why the timeout just at this time ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help.&lt;/P&gt;&lt;P&gt;Heinz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Oct 2014 07:45:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356723#M3651</guid>
      <dc:creator>heinzroitner</dc:creator>
      <dc:date>2014-10-28T07:45:04Z</dc:date>
    </item>
    <item>
      <title>Re: MCC timeout after exactly one hour</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356724#M3652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/timesyssupport"&gt;timesyssupport&lt;/A&gt; can you attend this case?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 18:43:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356724#M3652</guid>
      <dc:creator>karina_valencia</dc:creator>
      <dc:date>2014-10-31T18:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: MCC timeout after exactly one hour</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356725#M3653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please&amp;nbsp; refer to&amp;nbsp; previous discussion&amp;nbsp; related with this case: &lt;A href="https://community.nxp.com/thread/329003"&gt;Vybrid Strange Memory Overwrite&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 18:51:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356725#M3653</guid>
      <dc:creator>karina_valencia</dc:creator>
      <dc:date>2014-10-31T18:51:57Z</dc:date>
    </item>
    <item>
      <title>Re: MCC timeout after exactly one hour</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356726#M3654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Heinz,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have not yet encountered this issue with MCC. Are you able to reproduce this on a dev kit, and can you share your MQX/Linux source for doing so? This will allow us to reproduce on our end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Timesys Support&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 20:34:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356726#M3654</guid>
      <dc:creator>timesyssupport</dc:creator>
      <dc:date>2014-10-31T20:34:15Z</dc:date>
    </item>
    <item>
      <title>Re: MCC timeout after exactly one hour</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356727#M3655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi support,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have postponed this issue for later. I will start a new thread when we investigate this again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, Heinz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Nov 2014 07:48:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/356727#M3655</guid>
      <dc:creator>heinzroitner</dc:creator>
      <dc:date>2014-11-06T07:48:39Z</dc:date>
    </item>
    <item>
      <title>This an automatic process.  We are marking this post as s...</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/1136190#M6061</link>
      <description>&lt;B&gt;This an automatic process.&lt;/B&gt;&lt;BR /&gt;&lt;BR /&gt;
We are marking this post as solved, due to the either low activity or any reply marked as correct.&lt;BR /&gt;&lt;BR /&gt;
If you have additional questions, please create a new post and reference to this closed post.&lt;BR /&gt;&lt;BR /&gt;
NXP Community!</description>
      <pubDate>Thu, 03 Sep 2020 15:20:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MCC-timeout-after-exactly-one-hour/m-p/1136190#M6061</guid>
      <dc:creator>CommunityBot</dc:creator>
      <dc:date>2020-09-03T15:20:22Z</dc:date>
    </item>
  </channel>
</rss>

