<?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: EzPort timing before configuration has been loaded. in ColdFire/68K Microcontrollers and Processors</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/EzPort-timing-before-configuration-has-been-loaded/m-p/886925#M13731</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The Data Sheet gives the characteristics in "2.5 EzPort Electrical Specifications". The maximum clock rate is Fsys/2. So it depends on what the default power-on frequency of Fsys is for your hardware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Reference Manual Section "16.3.2.1 EZPCK - ExPort Clock" says the same thing, Fsys/2. Except when reading data, and then the maximum is Fsys/8.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd start off really slow and see how fast you can get it before it stops working, but only after you get it working on a slow clock first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Jan 2019 00:07:42 GMT</pubDate>
    <dc:creator>TomE</dc:creator>
    <dc:date>2019-01-24T00:07:42Z</dc:date>
    <item>
      <title>EzPort timing before configuration has been loaded.</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/EzPort-timing-before-configuration-has-been-loaded/m-p/886924#M13730</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to program MCF5213 via EzPort, and I found there is a&amp;nbsp;&amp;nbsp;EzPORT initialization flow as below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EzPORT initialization:&lt;BR /&gt;• EzPORT initialization obey Figure 2.&lt;BR /&gt;• Execute the RDSR command and continue only if the FS flag is cleared, this means the internal&lt;BR /&gt;flash is not secured.&lt;BR /&gt;• Execute WREN command&lt;BR /&gt;• Execute RDSR and see if WEN flag is set&lt;BR /&gt;• Execute WRCR command sending clock configuration&lt;BR /&gt;• Execute RDSR command and wait until the write in progress (WIP) flag is cleared.&lt;BR /&gt;• Execute RDSR command and check the configuration register loaded (CRL) flag is set. Verify&lt;BR /&gt;CRL is the only flag set (no WEP), otherwise there is an error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, how much frequency is propriety for Master to send instruction into Slave via EzPort before I set&amp;nbsp;&lt;SPAN&gt;configuration register ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Jan 2019 03:46:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/EzPort-timing-before-configuration-has-been-loaded/m-p/886924#M13730</guid>
      <dc:creator>jun_chen</dc:creator>
      <dc:date>2019-01-21T03:46:47Z</dc:date>
    </item>
    <item>
      <title>Re: EzPort timing before configuration has been loaded.</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/EzPort-timing-before-configuration-has-been-loaded/m-p/886925#M13731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The Data Sheet gives the characteristics in "2.5 EzPort Electrical Specifications". The maximum clock rate is Fsys/2. So it depends on what the default power-on frequency of Fsys is for your hardware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Reference Manual Section "16.3.2.1 EZPCK - ExPort Clock" says the same thing, Fsys/2. Except when reading data, and then the maximum is Fsys/8.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd start off really slow and see how fast you can get it before it stops working, but only after you get it working on a slow clock first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2019 00:07:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/EzPort-timing-before-configuration-has-been-loaded/m-p/886925#M13731</guid>
      <dc:creator>TomE</dc:creator>
      <dc:date>2019-01-24T00:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: EzPort timing before configuration has been loaded.</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/EzPort-timing-before-configuration-has-been-loaded/m-p/886926#M13732</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See below application note on the Ezport programming:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/docs/en/application-note/AN3897.pdf" title="https://www.nxp.com/docs/en/application-note/AN3897.pdf"&gt;https://www.nxp.com/docs/en/application-note/AN3897.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2019 05:15:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/EzPort-timing-before-configuration-has-been-loaded/m-p/886926#M13732</guid>
      <dc:creator>miduo</dc:creator>
      <dc:date>2019-01-24T05:15:54Z</dc:date>
    </item>
  </channel>
</rss>

