<?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のトピックInvalid LPC-LINK2 USB interface descriptor number sequence</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Invalid-LPC-LINK2-USB-interface-descriptor-number-sequence/m-p/1056466#M40909</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The USB 2.0 standard specifies &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;bInterfaceNumber&lt;/SPAN&gt; as "Number of this interface. Zero-based value identifying the index in the array of concurrent interfaces supported by this configuration." in section 9.6.5 (page 268)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, the LPC-LINK2 CMSIS-DAP V5.224 firmware declares interface descriptors with the following sequence of &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;bInterfaceNumber&lt;/SPAN&gt; values: 0, 4, 1, 2, 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This causes Google's gousb library (&lt;A href="https://github.com/google/gousb"&gt;https://github.com/google/gousb&lt;/A&gt;) to fail when an LPC Link 2 device is present on&amp;nbsp;any USB bus, with:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;config 1 interface at index 1 has number 4, USB standard states they should be identical&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also see &lt;A href="https://github.com/google/gousb/issues/65"&gt;https://github.com/google/gousb/issues/65&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can this behavior of the LPC-LINK2 CMSIS-DAP firmware be corrected ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ivo.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Apr 2020 14:30:49 GMT</pubDate>
    <dc:creator>IvoBCD</dc:creator>
    <dc:date>2020-04-20T14:30:49Z</dc:date>
    <item>
      <title>Invalid LPC-LINK2 USB interface descriptor number sequence</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Invalid-LPC-LINK2-USB-interface-descriptor-number-sequence/m-p/1056466#M40909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The USB 2.0 standard specifies &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;bInterfaceNumber&lt;/SPAN&gt; as "Number of this interface. Zero-based value identifying the index in the array of concurrent interfaces supported by this configuration." in section 9.6.5 (page 268)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, the LPC-LINK2 CMSIS-DAP V5.224 firmware declares interface descriptors with the following sequence of &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;bInterfaceNumber&lt;/SPAN&gt; values: 0, 4, 1, 2, 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This causes Google's gousb library (&lt;A href="https://github.com/google/gousb"&gt;https://github.com/google/gousb&lt;/A&gt;) to fail when an LPC Link 2 device is present on&amp;nbsp;any USB bus, with:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;config 1 interface at index 1 has number 4, USB standard states they should be identical&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also see &lt;A href="https://github.com/google/gousb/issues/65"&gt;https://github.com/google/gousb/issues/65&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can this behavior of the LPC-LINK2 CMSIS-DAP firmware be corrected ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ivo.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Apr 2020 14:30:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Invalid-LPC-LINK2-USB-interface-descriptor-number-sequence/m-p/1056466#M40909</guid>
      <dc:creator>IvoBCD</dc:creator>
      <dc:date>2020-04-20T14:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid LPC-LINK2 USB interface descriptor number sequence</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Invalid-LPC-LINK2-USB-interface-descriptor-number-sequence/m-p/1056467#M40910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp; &lt;A _jive_internal="true" data-content-finding="Community" data-userid="356079" data-username="ivo@bcdevices.com" href="https://community.nxp.com/people/ivo@bcdevices.com"&gt;Ivo Clarysse&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thank you for your interest in NXP Semiconductor products and &lt;BR /&gt;for the opportunity to serve you.&lt;BR /&gt;1) Can this behavior of the LPC-LINK2 CMSIS-DAP firmware be corrected?&lt;BR /&gt;-- No, I'm afraid not, and the composite USB device is able to be enumerated with the following sequence of bInterfaceNumber values: 0, 4, 1, 2, 3.&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Ping&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Apr 2020 02:28:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Invalid-LPC-LINK2-USB-interface-descriptor-number-sequence/m-p/1056467#M40910</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2020-04-21T02:28:03Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid LPC-LINK2 USB interface descriptor number sequence</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Invalid-LPC-LINK2-USB-interface-descriptor-number-sequence/m-p/1396027#M47562</link>
      <description>&lt;P&gt;The fact that the device enumerates is only because most USB host platforms gracefully support devices that violate the USB standard with respect to interface enumeration.&lt;/P&gt;&lt;P&gt;gousb library has since also been updated to deal with broken USB implementations such as NXP's LPC-Link2.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 08:04:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Invalid-LPC-LINK2-USB-interface-descriptor-number-sequence/m-p/1396027#M47562</guid>
      <dc:creator>IvoBCD</dc:creator>
      <dc:date>2022-01-07T08:04:31Z</dc:date>
    </item>
  </channel>
</rss>

