<?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>LPCXpresso IDEのトピックRe: LPCXpresso Debugger Peripheral Views</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPCXpresso-Debugger-Peripheral-Views/m-p/580092#M24441</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lpcxpresso-support on Mon Feb 02 07:35:11 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;The format and delivery of our peripheral descriptions has a lot of history behind it, some of which would perhaps no longer be relevant if we were starting again from scratch. But reexamining&amp;nbsp; our peripherals infrastructure is something we do want to do at some point, and I'll log your comments for consideration when we do.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;With regards to your comment about USB host registers, I'll take a look into this.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;LPCXpresso Support&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Jun 2016 02:34:50 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-16T02:34:50Z</dc:date>
    <item>
      <title>LPCXpresso Debugger Peripheral Views</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPCXpresso-Debugger-Peripheral-Views/m-p/580091#M24440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by MikeSimmonds on Sat Jan 31 21:56:07 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;As far as I can see, the layout and content etc. of the various debugger peripheral views are defined in files with an&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;extension of '.xme'. I am guessing that these are encrypted xml files.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there any good reason for the secrecy (given that the register descriptions etc. are plainly stated in the various&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;user manuals)?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In the case of mistakes, the knowledgeable users have no posibility of correcting the errors.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Some peripheral blocks are not covered at all. E.g the USB host register block (for LPC1778 at least).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It would be useful to supply un-encrypted files (and a brief format description) so that&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;(a) Errors and ommisions can be corrected without having to wait an unspecified amount of time for an update.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(b) A peripheral view could be tailored for a particular user's preference/way of working. [E.g. to group related&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PIO registers by port rather than all ports for each register, or to put the most important (to the user) registers&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;at the top.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(c) [Given that a peripheral register is 'just a memory address'] Create user/project specific views of user data&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;structures. E.g. my UART control blocks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If un-encrypted files are not to be forth comming, could you at least allow for user created 'extensions' to be handled&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;by the debugger.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards, Mike&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jun 2016 02:34:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LPCXpresso-Debugger-Peripheral-Views/m-p/580091#M24440</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-16T02:34:49Z</dc:date>
    </item>
    <item>
      <title>Re: LPCXpresso Debugger Peripheral Views</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPCXpresso-Debugger-Peripheral-Views/m-p/580092#M24441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lpcxpresso-support on Mon Feb 02 07:35:11 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;The format and delivery of our peripheral descriptions has a lot of history behind it, some of which would perhaps no longer be relevant if we were starting again from scratch. But reexamining&amp;nbsp; our peripherals infrastructure is something we do want to do at some point, and I'll log your comments for consideration when we do.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;With regards to your comment about USB host registers, I'll take a look into this.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;LPCXpresso Support&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jun 2016 02:34:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LPCXpresso-Debugger-Peripheral-Views/m-p/580092#M24441</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-16T02:34:50Z</dc:date>
    </item>
    <item>
      <title>Re: LPCXpresso Debugger Peripheral Views</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPCXpresso-Debugger-Peripheral-Views/m-p/580093#M24442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by MikeSimmonds on Mon Feb 02 14:17:44 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jun 2016 02:34:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LPCXpresso-Debugger-Peripheral-Views/m-p/580093#M24442</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-16T02:34:50Z</dc:date>
    </item>
  </channel>
</rss>

