<?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 CDC ROM Driver Bug for SetLineCoding in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/CDC-ROM-Driver-Bug-for-SetLineCoding/m-p/576608#M19468</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Hansi on Fri Dec 05 06:01:50 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm experiencing problems with an LPC11U34/421 chip. When I use the ROM USB and DCD drivers, the "line_coding" parameter of the "SetLineCode" function only contains 0xFF (7 bytes with this value). I checked with an USB data sniffer that the transmitted data is ok.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When linking against usbd_11uxx_lib, the values of the "line_coding" parameter are ok too.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Could you please point me to the proper workaround for the ROM drivers to get this working?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Background information: I've instantiated two CDC interfaces (appearing as /dev/ttyACM0 and /dev/ttyACM1) as well as a custom EP0 handler using RegisterClassHandler(). When I comment out the custom EP0 handler, the problem persists.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; Hansi&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 20:16:53 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T20:16:53Z</dc:date>
    <item>
      <title>CDC ROM Driver Bug for SetLineCoding</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/CDC-ROM-Driver-Bug-for-SetLineCoding/m-p/576608#M19468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Hansi on Fri Dec 05 06:01:50 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm experiencing problems with an LPC11U34/421 chip. When I use the ROM USB and DCD drivers, the "line_coding" parameter of the "SetLineCode" function only contains 0xFF (7 bytes with this value). I checked with an USB data sniffer that the transmitted data is ok.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When linking against usbd_11uxx_lib, the values of the "line_coding" parameter are ok too.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Could you please point me to the proper workaround for the ROM drivers to get this working?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Background information: I've instantiated two CDC interfaces (appearing as /dev/ttyACM0 and /dev/ttyACM1) as well as a custom EP0 handler using RegisterClassHandler(). When I comment out the custom EP0 handler, the problem persists.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; Hansi&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 20:16:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/CDC-ROM-Driver-Bug-for-SetLineCoding/m-p/576608#M19468</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T20:16:53Z</dc:date>
    </item>
  </channel>
</rss>

