<?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: LPC54608:  artf44835 ROM USB stack workaround in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54608-artf44835-ROM-USB-stack-workaround/m-p/842894#M33542</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bob,&lt;/P&gt;&lt;P&gt;Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.&lt;BR /&gt;1) Yes, it means the logical endpoint.&lt;BR /&gt;2) I think all ROM USB demo should add the corresponding workaround for artf44835 ROM driver bug, I'll contact the SDK library team for confirming, and inform you ASAP after I get some clarifications.&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&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>Thu, 11 Oct 2018 03:31:05 GMT</pubDate>
    <dc:creator>jeremyzhou</dc:creator>
    <dc:date>2018-10-11T03:31:05Z</dc:date>
    <item>
      <title>LPC54608:  artf44835 ROM USB stack workaround</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54608-artf44835-ROM-USB-stack-workaround/m-p/842893#M33541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using SDK 2.4.1.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;rom_dev_hid_generic_bm\hid_main.c\#147 reads:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;/*&amp;nbsp;&amp;nbsp;&amp;nbsp; WORKAROUND for artf44835 ROM driver BUG:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Code clearing STALL bits in endpoint reset routine corrupts memory area&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; next to the endpoint control data. For example When EP0, EP1_IN, EP1_OUT,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; EP2_IN are used we need to specify 3 here. But as a workaround for this&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; issue specify 4. So that extra EPs control structure acts as padding buffer&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; to avoid data corruption. Corruption of padding memory doesn’t affect the&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; stack/program behaviour.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; */&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; usb_param.max_num_ep = 2 + 1;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; usb_param.mem_base = (uint32_t)&amp;amp;g_memUsbStack;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; usb_param.mem_size = USB_STACK_MEM_SIZE;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have 3 questions:&lt;/P&gt;&lt;P&gt;1)&lt;/P&gt;&lt;P&gt;I read “&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;&lt;EM&gt;For example When EP0, EP1_IN, EP1_OUT, EP2_IN are used we need to specify 3 here&lt;/EM&gt;&lt;/SPAN&gt;” as the value 3 referring to the number of Logical endpoints and NOT physical endpoints. Is this correct?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;assuming that the workaround refers to logical endpoints this explains that “2 + 1” because of &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;EP0&lt;/SPAN&gt; and &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;EP1_IN&lt;/SPAN&gt; (HID).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2)&lt;/P&gt;&lt;P&gt;why is this workaround missing from other ROM USB Stack based examples ?&lt;/P&gt;&lt;P&gt;For example, rom_dev_audio_bm\sources\audio_main.c\#99 reads:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;usb_param.max_num_ep = 2;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2.a) this does not mention WORKAROUND for artf44835?&lt;/P&gt;&lt;P&gt;2.b) The example is using &lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;EP0,EP1_IN,EP1_OUT;&lt;/SPAN&gt;so shouldn't this be 2+1 as well to address artf44835?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With the discrepancy mentioned above in [2.a], is artf44835 still relevant to LPC546xx or should it be dismissed?&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Oct 2018 22:19:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54608-artf44835-ROM-USB-stack-workaround/m-p/842893#M33541</guid>
      <dc:creator>belmontbob59</dc:creator>
      <dc:date>2018-10-09T22:19:50Z</dc:date>
    </item>
    <item>
      <title>Re: LPC54608:  artf44835 ROM USB stack workaround</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54608-artf44835-ROM-USB-stack-workaround/m-p/842894#M33542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bob,&lt;/P&gt;&lt;P&gt;Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.&lt;BR /&gt;1) Yes, it means the logical endpoint.&lt;BR /&gt;2) I think all ROM USB demo should add the corresponding workaround for artf44835 ROM driver bug, I'll contact the SDK library team for confirming, and inform you ASAP after I get some clarifications.&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&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>Thu, 11 Oct 2018 03:31:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC54608-artf44835-ROM-USB-stack-workaround/m-p/842894#M33542</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2018-10-11T03:31:05Z</dc:date>
    </item>
  </channel>
</rss>

