<?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: How important is it that the PE FIFO size for K60 SPI peripherals is wrong? in Processor Expert Software</title>
    <link>https://community.nxp.com/t5/Processor-Expert-Software/How-important-is-it-that-the-PE-FIFO-size-for-K60-SPI/m-p/238539#M1284</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 must confirm that this is really bug in latest version of PEx. However I think it should not influence code functionality. You can for example compare generated code when you set buffer size to 1 and to 16, the only difference is in DIS_TXF/DIS_RXF bitfields in MCR register. DIS_TXF/DIS_RXF bit-fields disable/enable FIFO -&amp;gt; size 4 or 16 should not influence driver functionality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We will fix it for next release of PEx.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are sorry for inconvenience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Vojtech Filip&lt;/P&gt;&lt;P&gt;Processor Expert Support Team&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Dec 2013 10:30:41 GMT</pubDate>
    <dc:creator>vfilip</dc:creator>
    <dc:date>2013-12-04T10:30:41Z</dc:date>
    <item>
      <title>How important is it that the PE FIFO size for K60 SPI peripherals is wrong?</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/How-important-is-it-that-the-PE-FIFO-size-for-K60-SPI/m-p/238538#M1283</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am running CW 10.5 Build 130916&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have generated SPI code for the K60DN512VMD10 chip (for SPI2)&lt;/P&gt;&lt;P&gt;In the attribute set list section, it will only accept 1 and 16 for both the HW input buffer size and the HW output buffer size.&lt;/P&gt;&lt;P&gt;This is incorrect (AFAICT), the values should be 1 or 4.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I am not sure this affects any of the generated code at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How important is this error?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Dec 2013 18:01:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/How-important-is-it-that-the-PE-FIFO-size-for-K60-SPI/m-p/238538#M1283</guid>
      <dc:creator>Symbolic</dc:creator>
      <dc:date>2013-12-02T18:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: How important is it that the PE FIFO size for K60 SPI peripherals is wrong?</title>
      <link>https://community.nxp.com/t5/Processor-Expert-Software/How-important-is-it-that-the-PE-FIFO-size-for-K60-SPI/m-p/238539#M1284</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 must confirm that this is really bug in latest version of PEx. However I think it should not influence code functionality. You can for example compare generated code when you set buffer size to 1 and to 16, the only difference is in DIS_TXF/DIS_RXF bitfields in MCR register. DIS_TXF/DIS_RXF bit-fields disable/enable FIFO -&amp;gt; size 4 or 16 should not influence driver functionality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We will fix it for next release of PEx.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are sorry for inconvenience.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Vojtech Filip&lt;/P&gt;&lt;P&gt;Processor Expert Support Team&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Dec 2013 10:30:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Processor-Expert-Software/How-important-is-it-that-the-PE-FIFO-size-for-K60-SPI/m-p/238539#M1284</guid>
      <dc:creator>vfilip</dc:creator>
      <dc:date>2013-12-04T10:30:41Z</dc:date>
    </item>
  </channel>
</rss>

