<?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 uTasker and LPC2xxx/LPC17xx in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/uTasker-and-LPC2xxx-LPC17xx/m-p/563394#M16663</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just realised that now that NXP has eaten Freescale the uTasker project in fact allows NXP Coldfire, NXP Kinetis and NXP LPC2xxx/LPC17xx chips to be used almost transparently, where an application can basically be developed on one part (like an LPC2XXX) and moved to another family (like Kinetis) with little effort; rather than having to learn a completely new library and incompatible tools. Although the LPC2xxx range is maybe legacy there could still be some cases where this capability would be of value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.utasker.com%2Findex.html" rel="nofollow" target="_blank"&gt;http://www.utasker.com/index.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Aug 2016 17:38:54 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2016-08-02T17:38:54Z</dc:date>
    <item>
      <title>uTasker and LPC2xxx/LPC17xx</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/uTasker-and-LPC2xxx-LPC17xx/m-p/563394#M16663</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just realised that now that NXP has eaten Freescale the uTasker project in fact allows NXP Coldfire, NXP Kinetis and NXP LPC2xxx/LPC17xx chips to be used almost transparently, where an application can basically be developed on one part (like an LPC2XXX) and moved to another family (like Kinetis) with little effort; rather than having to learn a completely new library and incompatible tools. Although the LPC2xxx range is maybe legacy there could still be some cases where this capability would be of value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.utasker.com%2Findex.html" rel="nofollow" target="_blank"&gt;http://www.utasker.com/index.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2016 17:38:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/uTasker-and-LPC2xxx-LPC17xx/m-p/563394#M16663</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2016-08-02T17:38:54Z</dc:date>
    </item>
  </channel>
</rss>

