<?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: Flashing Bootloader &amp; Image in a single .s19 file in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215378#M18668</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;It depends on how you have setup your bootloader and application.&lt;BR /&gt;&lt;BR /&gt;If your bootloader does not alter the application in any way (e.g., relocation of vectors, decryption, etc.), it's straight-forward.&amp;nbsp; &lt;B&gt;Simply concatenate the two S19 files into one.&lt;/B&gt;&amp;nbsp; &lt;I&gt;You may have to remove duplicate S9 records, if your tool complains.&lt;/I&gt;&lt;BR /&gt;&lt;BR /&gt;If your bootloader relocates vectors, you'll have to add a conditional to prepare the app with vectors in their final position, so they don't overwrite the bootloader's ones.&lt;BR /&gt;&lt;BR /&gt;If you use encryption, you'll have to add a conditional to prepare the app unencrypted.&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;Message Edited by tonyp on &lt;SPAN class="date_text"&gt;2009-01-12&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;02:17 PM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 12 Jan 2009 20:06:49 GMT</pubDate>
    <dc:creator>tonyp</dc:creator>
    <dc:date>2009-01-12T20:06:49Z</dc:date>
    <item>
      <title>Flashing Bootloader &amp; Image in a single .s19 file</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215377#M18667</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi All,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Currently I'm Flashing the UART Bootloader onto&amp;nbsp;the JM32 MCU with the USB Multilink and after that using the bootloader application to load the Firmware image.&lt;/DIV&gt;&lt;DIV&gt;During production, I would like to Flash both the Bootloader and the Image in a single file onto the JM32.&lt;/DIV&gt;&lt;DIV&gt;How do I modify the s19 file to contain both the bootloader and the user application?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Help is greatly appreciated.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;SBD&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Jan 2009 19:54:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215377#M18667</guid>
      <dc:creator>S_B_D</dc:creator>
      <dc:date>2009-01-12T19:54:57Z</dc:date>
    </item>
    <item>
      <title>Re: Flashing Bootloader &amp; Image in a single .s19 file</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215378#M18668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;It depends on how you have setup your bootloader and application.&lt;BR /&gt;&lt;BR /&gt;If your bootloader does not alter the application in any way (e.g., relocation of vectors, decryption, etc.), it's straight-forward.&amp;nbsp; &lt;B&gt;Simply concatenate the two S19 files into one.&lt;/B&gt;&amp;nbsp; &lt;I&gt;You may have to remove duplicate S9 records, if your tool complains.&lt;/I&gt;&lt;BR /&gt;&lt;BR /&gt;If your bootloader relocates vectors, you'll have to add a conditional to prepare the app with vectors in their final position, so they don't overwrite the bootloader's ones.&lt;BR /&gt;&lt;BR /&gt;If you use encryption, you'll have to add a conditional to prepare the app unencrypted.&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;Message Edited by tonyp on &lt;SPAN class="date_text"&gt;2009-01-12&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;02:17 PM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Jan 2009 20:06:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215378#M18668</guid>
      <dc:creator>tonyp</dc:creator>
      <dc:date>2009-01-12T20:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: Flashing Bootloader &amp; Image in a single .s19 file</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215379#M18669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Tonyp,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;WOW..that was fast.&lt;/DIV&gt;&lt;DIV&gt;To tell the truth, I just took the UART Bootloader for the JM32&amp;nbsp;"as is" from AN2295. I really don't know if the interrupt vector is remapped. My application uses varius interrupt sources so I guess it has to. No encryption is used.&lt;/DIV&gt;&lt;DIV&gt;How do I check if the AN2295 bootloader remaps the interupt vector?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;SBD&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Jan 2009 20:24:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215379#M18669</guid>
      <dc:creator>S_B_D</dc:creator>
      <dc:date>2009-01-12T20:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: Flashing Bootloader &amp; Image in a single .s19 file</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215380#M18670</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;OK, from a quick overview of the app you mention, it uses relocation by means of JMP table, which implies each vector takes three bytes, not two.&lt;BR /&gt;&lt;BR /&gt;Anyway, you'll have to set up the JMP table inside your code (this part should be conditionally enabled only for when you want to concatenate the resulting S19 with the bootloader S19).&lt;BR /&gt;&lt;BR /&gt;It seems the address of the JMP table itself is part of the communication protocol, so I guess you have an option to define that in the PC portion of the bootloader.&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Jan 2009 20:39:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Flashing-Bootloader-Image-in-a-single-s19-file/m-p/215380#M18670</guid>
      <dc:creator>tonyp</dc:creator>
      <dc:date>2009-01-12T20:39:34Z</dc:date>
    </item>
  </channel>
</rss>

