<?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: Modular programming in CodeWarrior for MCU</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Modular-programming/m-p/127201#M479</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;You might be able to do it but you'd have to manage your loading/programming pretty well.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;First off, you'd have to had your core 'detect' the libraries and handle the fact that they might not be where expected.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Then you'd have to make sure your libraries had 'jump tables' or at least well defined entry points common to any change or enhancement you might make down the road.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Then you'd have to manage placement.&amp;nbsp; Not only to insure that the libraries each sat on an erase block boundary to start, but also how then ended with the next snippet of code.&amp;nbsp; And provide for a 'buffer' space to grow, as your replacements and/or upgrades may not be exactly the same.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Finally, you'd have to make sure your S-record updater and/or programmer was smart enough to know to only erase the sector/block that was referenced in an s-record, and to leave everything else alone.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Mike&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Feb 2006 21:05:55 GMT</pubDate>
    <dc:creator>mke_et</dc:creator>
    <dc:date>2006-02-24T21:05:55Z</dc:date>
    <item>
      <title>Modular programming</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Modular-programming/m-p/127200#M478</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using the MC9S12DP256B and I have a question about modular programming.&lt;/P&gt;&lt;P&gt;I would like to know if it is possible to update only certains parts of an application already burn in the MCU.&lt;/P&gt;&lt;P&gt;Let say&amp;nbsp;my project contains 3 librairies and I decided to change one of them. Is is possible to send&amp;nbsp;(burn) only the new code&amp;nbsp;of this library.&lt;/P&gt;&lt;P&gt;Do I have the burn 4 separate .s28 files ? (3 libraires and a&amp;nbsp;small "core" applicaiton) ?&lt;/P&gt;&lt;P&gt;Is there any type of dynamic library in embedded ?&lt;/P&gt;&lt;P&gt;Would it be possible with PIC code (position independant code) ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Feb 2006 13:19:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Modular-programming/m-p/127200#M478</guid>
      <dc:creator>desroc01</dc:creator>
      <dc:date>2006-02-24T13:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Modular programming</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Modular-programming/m-p/127201#M479</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;You might be able to do it but you'd have to manage your loading/programming pretty well.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;First off, you'd have to had your core 'detect' the libraries and handle the fact that they might not be where expected.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Then you'd have to make sure your libraries had 'jump tables' or at least well defined entry points common to any change or enhancement you might make down the road.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Then you'd have to manage placement.&amp;nbsp; Not only to insure that the libraries each sat on an erase block boundary to start, but also how then ended with the next snippet of code.&amp;nbsp; And provide for a 'buffer' space to grow, as your replacements and/or upgrades may not be exactly the same.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Finally, you'd have to make sure your S-record updater and/or programmer was smart enough to know to only erase the sector/block that was referenced in an s-record, and to leave everything else alone.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Mike&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Feb 2006 21:05:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Modular-programming/m-p/127201#M479</guid>
      <dc:creator>mke_et</dc:creator>
      <dc:date>2006-02-24T21:05:55Z</dc:date>
    </item>
  </channel>
</rss>

