<?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>MQX Software SolutionsのトピックRe: imxsx  flexcan bug report</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/imxsx-flexcan-bug-report/m-p/706910#M17559</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, this is not a bug, but just the expected behaviour. As per the asymmetric multicore design philosophy, M4 is the auxiliary core to perform the low-speed low-performance system tasks when the A9 core sleeps for power saving, but when Linux on the A9 core starts, it takes all the system control on itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, of course, you can manage the A9 and M4 cores interoperability as you want. For example, refer to the Section 2.6 "Remote Processor Messaging" of the attached document.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Artur&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Sep 2017 09:31:23 GMT</pubDate>
    <dc:creator>art</dc:creator>
    <dc:date>2017-09-26T09:31:23Z</dc:date>
    <item>
      <title>imxsx  flexcan bug report</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/imxsx-flexcan-bug-report/m-p/706909#M17558</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;freertos on&amp;nbsp;&amp;nbsp; M4&amp;nbsp; runs perfectly without&amp;nbsp; linux on A9,but linux starts will affect freertos interrupt immediately, I did not change the configure。so&amp;nbsp; i think&amp;nbsp; it is&amp;nbsp; a bug&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Sep 2017 03:45:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/imxsx-flexcan-bug-report/m-p/706909#M17558</guid>
      <dc:creator>bowenzhang</dc:creator>
      <dc:date>2017-09-19T03:45:55Z</dc:date>
    </item>
    <item>
      <title>Re: imxsx  flexcan bug report</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/imxsx-flexcan-bug-report/m-p/706910#M17559</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, this is not a bug, but just the expected behaviour. As per the asymmetric multicore design philosophy, M4 is the auxiliary core to perform the low-speed low-performance system tasks when the A9 core sleeps for power saving, but when Linux on the A9 core starts, it takes all the system control on itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, of course, you can manage the A9 and M4 cores interoperability as you want. For example, refer to the Section 2.6 "Remote Processor Messaging" of the attached document.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Artur&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2017 09:31:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/imxsx-flexcan-bug-report/m-p/706910#M17559</guid>
      <dc:creator>art</dc:creator>
      <dc:date>2017-09-26T09:31:23Z</dc:date>
    </item>
  </channel>
</rss>

