<?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: MCF51 - CodeSourcery - Checking Application Flash CRC in ColdFire/68K Microcontrollers and Processors</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51-CodeSourcery-Checking-Application-Flash-CRC/m-p/174996#M6739</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I treat the 'bootloader' and 'application' processes as completely independent processes.&amp;nbsp; They are built independently, and each area has its own CRC.&amp;nbsp; The bootloader has routines to download &amp;amp; program S records in the application area.&amp;nbsp; This is all largely controlled (and CRC is calculated) by prm-file entries.&amp;nbsp; When operating the debugger, each job has been set up to protect (reprogram) the FLASH area of the other.&amp;nbsp; I manually combine the .s19 files to create a 'whole' image for production programming.&amp;nbsp; I will note that my world is S08, but I expect the MCF51 processor has similar hooks for FLASH protection and vector redirection.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Apr 2010 01:13:22 GMT</pubDate>
    <dc:creator>egoodii</dc:creator>
    <dc:date>2010-04-07T01:13:22Z</dc:date>
    <item>
      <title>MCF51 - CodeSourcery - Checking Application Flash CRC</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51-CodeSourcery-Checking-Application-Flash-CRC/m-p/174994#M6737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using MCF51AC256, and I need to verify flash memory CRC&amp;nbsp;as described in AN3257.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need a simple method that does not interfer when compiling a new software release.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My code is build with 2 parts :&lt;/P&gt;&lt;P&gt;- Fisrt a Bootloader system. (here I will verify flash CRC before starting the application)&lt;/P&gt;&lt;P&gt;- Then&amp;nbsp;the application.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Bootloader is flashed only once time and is flash protected.&lt;/P&gt;&lt;P&gt;The application is flashed by final user when he need to change firmware.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The computation as explained in AN3257 is&amp;nbsp;under control&amp;nbsp;(I use a CRC method&amp;nbsp;using hardware CRC engine in the coldfire instead of the XOR method described in the AN3257.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The C routine to realize the CRC compute on the flash should be implement without trouble.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;The main matter is :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;How should I manage the "original" CRC as simple as possible with minimal impact when compiling a new application release ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All yours ideas are welcome, thanks.&lt;/P&gt;&lt;P&gt;Julien&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Feb 2010 17:08:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51-CodeSourcery-Checking-Application-Flash-CRC/m-p/174994#M6737</guid>
      <dc:creator>SoJulien</dc:creator>
      <dc:date>2010-02-11T17:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: MCF51 - CodeSourcery - Checking Application Flash CRC</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51-CodeSourcery-Checking-Application-Flash-CRC/m-p/174995#M6738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Julien,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not sure what the problem is specifically. If you want to append a CRC to a compiled/linked image, you can use srec_cat from the SRecord package. I pointed to that program in the other thread that you started.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;- mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Feb 2010 20:02:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51-CodeSourcery-Checking-Application-Flash-CRC/m-p/174995#M6738</guid>
      <dc:creator>scifi</dc:creator>
      <dc:date>2010-02-11T20:02:50Z</dc:date>
    </item>
    <item>
      <title>Re: MCF51 - CodeSourcery - Checking Application Flash CRC</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51-CodeSourcery-Checking-Application-Flash-CRC/m-p/174996#M6739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I treat the 'bootloader' and 'application' processes as completely independent processes.&amp;nbsp; They are built independently, and each area has its own CRC.&amp;nbsp; The bootloader has routines to download &amp;amp; program S records in the application area.&amp;nbsp; This is all largely controlled (and CRC is calculated) by prm-file entries.&amp;nbsp; When operating the debugger, each job has been set up to protect (reprogram) the FLASH area of the other.&amp;nbsp; I manually combine the .s19 files to create a 'whole' image for production programming.&amp;nbsp; I will note that my world is S08, but I expect the MCF51 processor has similar hooks for FLASH protection and vector redirection.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Apr 2010 01:13:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/MCF51-CodeSourcery-Checking-Application-Flash-CRC/m-p/174996#M6739</guid>
      <dc:creator>egoodii</dc:creator>
      <dc:date>2010-04-07T01:13:22Z</dc:date>
    </item>
  </channel>
</rss>

