<?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: Using I2C bus to download code in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Using-I2C-bus-to-download-code/m-p/139727#M5428</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Thank you for the response.&lt;/DIV&gt;&lt;DIV&gt;Yes, my application is already using I2C bus, that's why I want to use I2C for the reprogramming.&lt;/DIV&gt;&lt;DIV&gt;I got answer from Freescale technical support, they are saying this is basically a boot loader issue. They don't have a boot loader using I2C, but they have one using SCI ports. According to them, it's possible to modify upon this boot loader.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Dec 2006 05:56:06 GMT</pubDate>
    <dc:creator>Fan</dc:creator>
    <dc:date>2006-12-13T05:56:06Z</dc:date>
    <item>
      <title>Using I2C bus to download code</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Using-I2C-bus-to-download-code/m-p/139725#M5426</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;Instead of using a debugger, can I use I2C bus to download code to the microcontroller? I know this is a very special case: basically a running code on the MCU has to be able to overwrite itself.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I am using HCS08 microcontroller.&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks for any information.&lt;/DIV&gt;&lt;DIV&gt;Fan&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Dec 2006 01:11:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Using-I2C-bus-to-download-code/m-p/139725#M5426</guid>
      <dc:creator>Fan</dc:creator>
      <dc:date>2006-12-13T01:11:44Z</dc:date>
    </item>
    <item>
      <title>Re: Using I2C bus to download code</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Using-I2C-bus-to-download-code/m-p/139726#M5427</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I'm wondering why you feel using the I2C interface would make it simpler to solve the problem of overwriting itself? No matter what, the issues will remain the same.&lt;BR /&gt;&lt;BR /&gt;EXCEPT where the interface hardware is concerned.&lt;BR /&gt;&lt;BR /&gt;By that I mean if you write a polled serial handler and a polled I2C handler, then there's not much difference in the issues involved. But if you mean an interrupt driven serial handler (with vectors in flash) as opposed to a polled I2C handler, yes, there is a difference. In either case though, the safest thing to do is to disable interrupts and use a scheme where you place everything in RAM, including code, to do the erase and reprogram.&lt;BR /&gt;&lt;BR /&gt;Then again, if you mean using 'existing packaged debug tools' over the serial link vs writing your own I2C interface handler...&lt;BR /&gt;&lt;BR /&gt;On the other hand... If you had an application that had to use I2C and you didn't want to interface to the serial port, but instead share usage of the I2C, then right there is a very logical reason to use the I2C. But you still have all the same issues that you would have with a serial port doing a 'live interactive update' of the code.&lt;P&gt;Message Edited by mke_et on &lt;SPAN class="date_text"&gt;2006-12-12&lt;/SPAN&gt;&lt;SPAN class="time_text"&gt;04:38 PM&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Dec 2006 05:33:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Using-I2C-bus-to-download-code/m-p/139726#M5427</guid>
      <dc:creator>mke_et</dc:creator>
      <dc:date>2006-12-13T05:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: Using I2C bus to download code</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Using-I2C-bus-to-download-code/m-p/139727#M5428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Thank you for the response.&lt;/DIV&gt;&lt;DIV&gt;Yes, my application is already using I2C bus, that's why I want to use I2C for the reprogramming.&lt;/DIV&gt;&lt;DIV&gt;I got answer from Freescale technical support, they are saying this is basically a boot loader issue. They don't have a boot loader using I2C, but they have one using SCI ports. According to them, it's possible to modify upon this boot loader.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Dec 2006 05:56:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Using-I2C-bus-to-download-code/m-p/139727#M5428</guid>
      <dc:creator>Fan</dc:creator>
      <dc:date>2006-12-13T05:56:06Z</dc:date>
    </item>
  </channel>
</rss>

