<?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: Kinetis Flexbus timing in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175571#M1483</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Helmut, please check my answer in your inbox.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Oct 2012 21:21:33 GMT</pubDate>
    <dc:creator>apanecatl</dc:creator>
    <dc:date>2012-10-22T21:21:33Z</dc:date>
    <item>
      <title>Kinetis Flexbus timing</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175568#M1480</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I'm searching a detailed flexbus timing for the K10...K60/ 100 mask. I'm e.g. missing hold time ALE Low to Address valid and also Data valid from CS going high. Where can I find it?&lt;BR /&gt;The EZPORT timing is given much better within the family datasheets.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;FB&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jun 2012 05:51:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175568#M1480</guid>
      <dc:creator>Burba</dc:creator>
      <dc:date>2012-06-27T05:51:09Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis Flexbus timing</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175569#M1481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Now I know why I even did not get any aswer from freescale. I've done some measurements by myself and found that the adress hold time from ALE going Low is 0 or even little bit negative. That mean that you must use one additional waitstate for ALE for multiplexed flexbus write acces which is a very bad situation and totally waste of performance. With a very fast RAM you waste about 30% of flexbus throughput. I just wonder if the same problem exists on other Cortex M3 devices from other brands.&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Sep 2012 21:08:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175569#M1481</guid>
      <dc:creator>Burba</dc:creator>
      <dc:date>2012-09-03T21:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis Flexbus timing</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175570#M1482</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;try to send Service Request with high priority&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Sep 2012 12:47:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175570#M1482</guid>
      <dc:creator>luke_8</dc:creator>
      <dc:date>2012-09-06T12:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: Kinetis Flexbus timing</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175571#M1483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Helmut, please check my answer in your inbox.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Oct 2012 21:21:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Kinetis-Flexbus-timing/m-p/175571#M1483</guid>
      <dc:creator>apanecatl</dc:creator>
      <dc:date>2012-10-22T21:21:33Z</dc:date>
    </item>
  </channel>
</rss>

