<?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 USB_Error_Event parameter explanation/ request for ROM symbols for debugging in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/USB-Error-Event-parameter-explanation-request-for-ROM-symbols/m-p/523490#M6126</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by twiddle on Mon Jun 15 06:51:13 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;So I've managed to cobble together a USBD/Rom-based implementation for my custom LPC11u35-based development board.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Both hw-&amp;gt;Init and hid-&amp;gt;Init, as well as hw-&amp;gt;connect, appear to work fine, but my device apparently still doesn't respond properly to a device descriptor request. USB_Error_Event gets called, with a value of 0x8 for its parameter. The documentation indicates that this is 'device interrupt status register' value, but I'm having a hard time interpreting how to respond to this. If I interpret correctly, looking at the UM for my part, 0x8 corresponds to the EP1_IN interrupt register being set, but I'm at a loss for what I should be doing. Given that this is inside my *error* handler, am I supposed to interpret this as saying there was an error while responding to the EP1_IN request? I'd have expected these codes to be a little bit more helpful with isolating the issue, if that is the case.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;On these lines, is there any chance I could get the debug symbols for the ROM API, like TI gives with their chips that have the API? It would make debugging my own code much easier if I could at least have some idea of what the ROM libraries are doing. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In any event, I've attached my project. Any pointers would be appreciated. &lt;/SPAN&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-338100"&gt;HIDPrototype.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 16:44:27 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T16:44:27Z</dc:date>
    <item>
      <title>USB_Error_Event parameter explanation/ request for ROM symbols for debugging</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/USB-Error-Event-parameter-explanation-request-for-ROM-symbols/m-p/523490#M6126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by twiddle on Mon Jun 15 06:51:13 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;So I've managed to cobble together a USBD/Rom-based implementation for my custom LPC11u35-based development board.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Both hw-&amp;gt;Init and hid-&amp;gt;Init, as well as hw-&amp;gt;connect, appear to work fine, but my device apparently still doesn't respond properly to a device descriptor request. USB_Error_Event gets called, with a value of 0x8 for its parameter. The documentation indicates that this is 'device interrupt status register' value, but I'm having a hard time interpreting how to respond to this. If I interpret correctly, looking at the UM for my part, 0x8 corresponds to the EP1_IN interrupt register being set, but I'm at a loss for what I should be doing. Given that this is inside my *error* handler, am I supposed to interpret this as saying there was an error while responding to the EP1_IN request? I'd have expected these codes to be a little bit more helpful with isolating the issue, if that is the case.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;On these lines, is there any chance I could get the debug symbols for the ROM API, like TI gives with their chips that have the API? It would make debugging my own code much easier if I could at least have some idea of what the ROM libraries are doing. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In any event, I've attached my project. Any pointers would be appreciated. &lt;/SPAN&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-338100"&gt;HIDPrototype.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 16:44:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/USB-Error-Event-parameter-explanation-request-for-ROM-symbols/m-p/523490#M6126</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T16:44:27Z</dc:date>
    </item>
  </channel>
</rss>

