<?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>8-bit MicrocontrollersのトピックRe: Updating firmware via CAN</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144609#M6895</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;I had looked at AN2295, but it seems that they send a “certain character at a certain time”, such as XX m/us after reset. I would like to update the firmware "anytime", which is different than a 'boot'loader (though maybe only a semantic issue).&lt;BR /&gt;&lt;BR /&gt;Are your CAN routines part of your bootloader?&lt;BR /&gt;&lt;BR /&gt;I am thinking of putting my CAN routines in a 'protected' area and, when the command is received, erase and fill the old (non-protected) code area with the new code then jump to the new code once it has been loaded. Do you see any problems doing it this way? Is this more of a headache than doing it as a bootloader (eg AN2295)?&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Feb 2007 09:27:41 GMT</pubDate>
    <dc:creator>mayfly</dc:creator>
    <dc:date>2007-02-08T09:27:41Z</dc:date>
    <item>
      <title>Updating firmware via CAN</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144607#M6893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does anyone know of (or can think of) a way to update the firmware for an HC(S)08 over CAN? It would be nice to upgrade the firmware of multiple micro-controllers on a CAN network without having to BDM/MON08 upgrade each of them individually. Any ideas how to do this?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;yoroshiku&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Feb 2007 17:02:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144607#M6893</guid>
      <dc:creator>mayfly</dc:creator>
      <dc:date>2007-02-06T17:02:10Z</dc:date>
    </item>
    <item>
      <title>Re: Updating firmware via CAN</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144608#M6894</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;You can write your own bootloader based on AN2295, you need to write data send/receive over MSCAN08 routines(for AZ &amp;amp; GZ family), and write something for the gateway between RS232 (host PC) an CAN bus.&lt;BR /&gt;I did that with multiple 908GZ60 boards and a MCF5213 board.&lt;BR /&gt;If you want to keep the system simple, you have to upgrade boards one by one.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Emmanuel,&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Feb 2007 21:44:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144608#M6894</guid>
      <dc:creator>Nouchi</dc:creator>
      <dc:date>2007-02-06T21:44:51Z</dc:date>
    </item>
    <item>
      <title>Re: Updating firmware via CAN</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144609#M6895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;I had looked at AN2295, but it seems that they send a “certain character at a certain time”, such as XX m/us after reset. I would like to update the firmware "anytime", which is different than a 'boot'loader (though maybe only a semantic issue).&lt;BR /&gt;&lt;BR /&gt;Are your CAN routines part of your bootloader?&lt;BR /&gt;&lt;BR /&gt;I am thinking of putting my CAN routines in a 'protected' area and, when the command is received, erase and fill the old (non-protected) code area with the new code then jump to the new code once it has been loaded. Do you see any problems doing it this way? Is this more of a headache than doing it as a bootloader (eg AN2295)?&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2007 09:27:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144609#M6895</guid>
      <dc:creator>mayfly</dc:creator>
      <dc:date>2007-02-08T09:27:41Z</dc:date>
    </item>
    <item>
      <title>Re: Updating firmware via CAN</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144610#M6896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I did some minor changes, like, the bootloader is only called when IRQ is low (with jumper), I suppressed clock calibration (using 8Mhz crystal), I had to increase protected space to 1024 bytes to fit CAN send/receive simplified routines in polled mode, and works fine for few month now. The application program use its owns CAN routines with interrupts management.&lt;BR /&gt;If you like headache, you can build your own bootloader from scratch, but IMHO doing a work based on AN2295 will be more efficient because the main part of the job is done.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Emmanuel&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2007 16:04:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Updating-firmware-via-CAN/m-p/144610#M6896</guid>
      <dc:creator>Nouchi</dc:creator>
      <dc:date>2007-02-08T16:04:42Z</dc:date>
    </item>
  </channel>
</rss>

