<?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>CodeWarrior Development Tools中的主题 Re: Problem with SPI simulation on CW4.7 and 5.2 in FCS</title>
    <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Problem-with-SPI-simulation-on-CW4-7-and-5-2-in-FCS/m-p/994993#M7994</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have checked it and SPI does not work. The SPTEF is never set so it looks like a bug or "feature". I is strange because UART is setting TC flag and you are able to simulate.&lt;/P&gt;&lt;P&gt;I do not know whether there is any workaround but setting SPTEF manually does not work.&lt;/P&gt;&lt;P&gt;I believe you will find there is much more limitations and it is useful for core simulation mainly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Ladislav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Dec 2019 15:37:44 GMT</pubDate>
    <dc:creator>lama</dc:creator>
    <dc:date>2019-12-05T15:37:44Z</dc:date>
    <item>
      <title>Problem with SPI simulation on CW4.7 and 5.2 in FCS</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Problem-with-SPI-simulation-on-CW4-7-and-5-2-in-FCS/m-p/994991#M7992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello to the whole group. Question: is there anyone who has happened that the SPI does not work in the simulation? I have CW4.7 and CW5.2, none works. It does not generate the interruption.&lt;/P&gt;&lt;P&gt;Tank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Dec 2019 16:51:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Problem-with-SPI-simulation-on-CW4-7-and-5-2-in-FCS/m-p/994991#M7992</guid>
      <dc:creator>Leojunin</dc:creator>
      <dc:date>2019-12-02T16:51:27Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with SPI simulation on CW4.7 and 5.2 in FCS</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Problem-with-SPI-simulation-on-CW4-7-and-5-2-in-FCS/m-p/994992#M7993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I forgot to tell you the chip: s12xs&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Dec 2019 17:08:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Problem-with-SPI-simulation-on-CW4-7-and-5-2-in-FCS/m-p/994992#M7993</guid>
      <dc:creator>Leojunin</dc:creator>
      <dc:date>2019-12-02T17:08:28Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with SPI simulation on CW4.7 and 5.2 in FCS</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Problem-with-SPI-simulation-on-CW4-7-and-5-2-in-FCS/m-p/994993#M7994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have checked it and SPI does not work. The SPTEF is never set so it looks like a bug or "feature". I is strange because UART is setting TC flag and you are able to simulate.&lt;/P&gt;&lt;P&gt;I do not know whether there is any workaround but setting SPTEF manually does not work.&lt;/P&gt;&lt;P&gt;I believe you will find there is much more limitations and it is useful for core simulation mainly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Ladislav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Dec 2019 15:37:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/Problem-with-SPI-simulation-on-CW4-7-and-5-2-in-FCS/m-p/994993#M7994</guid>
      <dc:creator>lama</dc:creator>
      <dc:date>2019-12-05T15:37:44Z</dc:date>
    </item>
  </channel>
</rss>

