<?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>LPC MicrocontrollersのトピックRe: LPCOpen 1.01</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPCOpen-1-01/m-p/594663#M22677</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by rgledhill on Mon Apr 08 07:12:38 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Does this mean the standard LPCWare CMSIS distribution will no longer be developed?&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Richard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 19:21:16 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T19:21:16Z</dc:date>
    <item>
      <title>LPCOpen 1.01</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPCOpen-1-01/m-p/594661#M22675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by khfreiberg on Mon Mar 18 11:43:04 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am still confused which platform I should use for code. I thought that LPCOpen is a better approach than Keil, since it was newer and seems to be better maintained. But now I am looking to your new 1.01 and find all files renamed, subroutines renamed, .h and .c files merged.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;May be I got a little rigid since I am normally working on class-c. But I do not understand why braking code for a useless prefix 'Chip_'. Should I keep what I have or will 1.02 be more stable?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:21:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPCOpen-1-01/m-p/594661#M22675</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:21:15Z</dc:date>
    </item>
    <item>
      <title>Re: LPCOpen 1.01</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPCOpen-1-01/m-p/594662#M22676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by wellsk on Wed Mar 20 17:06:00 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;The structure (drivers, API calls, projects, etc.) of LPCOpen and other existing packages are very different. I'm not familiar with the approach Keil uses - is this the lpc43xx Keil CMSIS code bundle?. LPCOpen and the Keil CMSIS code bundle are really different things.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you are happy with your current package and it works for you or deep into development of a product with it, I wouldn't switch. If you are just starting development or starting a new design with new code, I would start with LPCOpen.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For stability, are you asking about stability of the function APIs? These are mostly stable, but some drivers are in the process of being re-designed (from scratch) to use less memory and generally do things more efficiently with more flexibility. Unfortunately, the APIs for some drivers will change as they are re-written, but they will tend to be limited in scope (so maybe one peripheral in a release).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can get a list of the v1.02 changes and upcoming features at the links below:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.lpcware.com%2Fcontent%2Fpage%2Flpcopen-releases-and-versioning-information" rel="nofollow" target="_blank"&gt;http://www.lpcware.com/content/page/lpcopen-releases-and-versioning-information&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.lpcware.com%2Fcontent%2Fproject%2Flpcopen-platform-nxp-lpc-microcontrollers%2Flpcopen-upcoming-releases" rel="nofollow" target="_blank"&gt;http://www.lpcware.com/content/project/lpcopen-platform-nxp-lpc-microcontrollers/lpcopen-upcoming-releases&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I hope this helps!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:21:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPCOpen-1-01/m-p/594662#M22676</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: LPCOpen 1.01</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPCOpen-1-01/m-p/594663#M22677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by rgledhill on Mon Apr 08 07:12:38 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Does this mean the standard LPCWare CMSIS distribution will no longer be developed?&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;BR /&gt;&lt;P&gt;Richard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:21:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPCOpen-1-01/m-p/594663#M22677</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:21:16Z</dc:date>
    </item>
  </channel>
</rss>

