<?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>ColdFire/68K Microcontrollers and Processors中的主题 Re: MCF5445x running code from internal SRAM</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5445x-running-code-from-internal-SRAM/m-p/200885#M9220</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;So far I've learnt that there is an error in the manual regarding the internal SRAM but I have not found out what the solution is.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I believe it is only possible to have either code or data in the SRAM but not both when connected directly to the core.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;It's about time a new manual was released for this processor since there are so many errors in the existing one (Rev 2) or at the very least an updated list of errata.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Apr 2008 15:31:13 GMT</pubDate>
    <dc:creator>M_H_</dc:creator>
    <dc:date>2008-04-15T15:31:13Z</dc:date>
    <item>
      <title>MCF5445x running code from internal SRAM</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5445x-running-code-from-internal-SRAM/m-p/200884#M9219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Has anyone been able to run code in the internal SRAM of the MCF5445x processor without enabling back-door access? If you have, how did you do it?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I can run code if the back-door is enabled but according to the device errata you shouldn't enable back-door and core access at the same time. When I only enable the back-door my code runs about 40% slower which I assume is because back-door access is slower than core access and my stack is in the SRAM. If I don't enable back-door access then the processor resets as soon as a function is called that sits in the SRAM. I can read and write data (and the stack) when only core access is enabled but can't run code.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Malcolm&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Mar 2008 19:01:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5445x-running-code-from-internal-SRAM/m-p/200884#M9219</guid>
      <dc:creator>M_H_</dc:creator>
      <dc:date>2008-03-07T19:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: MCF5445x running code from internal SRAM</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5445x-running-code-from-internal-SRAM/m-p/200885#M9220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;So far I've learnt that there is an error in the manual regarding the internal SRAM but I have not found out what the solution is.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I believe it is only possible to have either code or data in the SRAM but not both when connected directly to the core.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;It's about time a new manual was released for this processor since there are so many errors in the existing one (Rev 2) or at the very least an updated list of errata.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Apr 2008 15:31:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF5445x-running-code-from-internal-SRAM/m-p/200885#M9220</guid>
      <dc:creator>M_H_</dc:creator>
      <dc:date>2008-04-15T15:31:13Z</dc:date>
    </item>
  </channel>
</rss>

