<?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 Re: USB CDC example has flaws in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/USB-CDC-example-has-flaws/m-p/578558#M19853</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by abonent on Wed Dec 30 13:25:54 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;This looks familiar to me &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=https%3A%2F%2Fwww.lpcware.com%2Fcontent%2Fforum%2Fplease-help-me-understand-lpcopen-cdc-example" rel="nofollow" target="_blank"&gt;https://www.lpcware.com/content/forum/please-help-me-understand-lpcopen-cdc-example&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 20:20:05 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T20:20:05Z</dc:date>
    <item>
      <title>USB CDC example has flaws</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/USB-CDC-example-has-flaws/m-p/578557#M19852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by rjm on Thu Oct 15 07:25:26 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;today, I tested "usbd_rom_cdc" Example for LPC1549.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The code works well, demonstrating echoing characters that are typed in a terminal emulator that connects to the target via a CDC-ACM virtual COM-port.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, when I send a file from the terminal emulator, data loss occurs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It has been found out that the design of the buffer structure, where data is buffered into an interrupt routine and unbuffered into a function loop at the main loop level is not OK. It would have been better when the buffer structure was designed à la fifo, in order to ensure no data loss. Under such circumstances, the code could be reused in own applications without pain.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In the situation "as is", the appropriate code segments aren't readable well, and the small portions of interrupt disable aren't necessary, too, when the buffer structure would have been implemented well.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 20:20:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/USB-CDC-example-has-flaws/m-p/578557#M19852</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T20:20:03Z</dc:date>
    </item>
    <item>
      <title>Re: USB CDC example has flaws</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/USB-CDC-example-has-flaws/m-p/578558#M19853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by abonent on Wed Dec 30 13:25:54 MST 2015&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;This looks familiar to me &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=https%3A%2F%2Fwww.lpcware.com%2Fcontent%2Fforum%2Fplease-help-me-understand-lpcopen-cdc-example" rel="nofollow" target="_blank"&gt;https://www.lpcware.com/content/forum/please-help-me-understand-lpcopen-cdc-example&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 20:20:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/USB-CDC-example-has-flaws/m-p/578558#M19853</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T20:20:05Z</dc:date>
    </item>
  </channel>
</rss>

