topic USB controller hardware version / ISO OUT (RX) transfers and DQH MULT in LPC Microcontrollers https://community.nxp.com/t5/LPC-Microcontrollers/USB-controller-hardware-version-ISO-OUT-RX-transfers-and-DQH/m-p/562769#M16539 <HTML><HEAD></HEAD><BODY><STRONG>Content originally posted in LPCWare by apriori on Wed Mar 16 11:47:30 MST 2016</STRONG><BR /><SPAN>We have implemented our own replacement for the USB ROM API that uses the USB peripheral of the LPC4337 directly.</SPAN><BR /><SPAN>The manual (UM10503, 25.10.9) says</SPAN><BR /><BR /><HR /><SPAN style="color: #0000ff;"><STRONG>Quote: </STRONG><BR />Remark: Exit criteria only valid in hardware version 2.3 or later. Previous to hardware<BR />version 2.3, any PID sequence that did not match the MULT field exactly would be<BR />flagged as a transaction error due to PID mismatch or fulfillment error.</SPAN><HR /><BR /><BR /><SPAN>So to be precise, hardware version &lt;2.3 does not allow an endpoint whose DQH was initialized with MULT=3</SPAN><BR /><SPAN>to receive</SPAN><BR /><BR /><STRONG>DATA0</STRONG><BR /><BR /><SPAN>and</SPAN><BR /><BR /><STRONG>MDATA DATA1</STRONG><BR /><BR /><SPAN>(i.e. 1 or 2 transactions per microframe)</SPAN><BR /><BR /><SPAN>I think we're having trouble with this. How can we determine the hardware version we're using?</SPAN><BR /><SPAN>Is this a licensed IP core?</SPAN></BODY></HTML> Wed, 15 Jun 2016 18:47:07 GMT lpcware 2016-06-15T18:47:07Z USB controller hardware version / ISO OUT (RX) transfers and DQH MULT https://community.nxp.com/t5/LPC-Microcontrollers/USB-controller-hardware-version-ISO-OUT-RX-transfers-and-DQH/m-p/562769#M16539 <HTML><HEAD></HEAD><BODY><STRONG>Content originally posted in LPCWare by apriori on Wed Mar 16 11:47:30 MST 2016</STRONG><BR /><SPAN>We have implemented our own replacement for the USB ROM API that uses the USB peripheral of the LPC4337 directly.</SPAN><BR /><SPAN>The manual (UM10503, 25.10.9) says</SPAN><BR /><BR /><HR /><SPAN style="color: #0000ff;"><STRONG>Quote: </STRONG><BR />Remark: Exit criteria only valid in hardware version 2.3 or later. Previous to hardware<BR />version 2.3, any PID sequence that did not match the MULT field exactly would be<BR />flagged as a transaction error due to PID mismatch or fulfillment error.</SPAN><HR /><BR /><BR /><SPAN>So to be precise, hardware version &lt;2.3 does not allow an endpoint whose DQH was initialized with MULT=3</SPAN><BR /><SPAN>to receive</SPAN><BR /><BR /><STRONG>DATA0</STRONG><BR /><BR /><SPAN>and</SPAN><BR /><BR /><STRONG>MDATA DATA1</STRONG><BR /><BR /><SPAN>(i.e. 1 or 2 transactions per microframe)</SPAN><BR /><BR /><SPAN>I think we're having trouble with this. How can we determine the hardware version we're using?</SPAN><BR /><SPAN>Is this a licensed IP core?</SPAN></BODY></HTML> Wed, 15 Jun 2016 18:47:07 GMT https://community.nxp.com/t5/LPC-Microcontrollers/USB-controller-hardware-version-ISO-OUT-RX-transfers-and-DQH/m-p/562769#M16539 lpcware 2016-06-15T18:47:07Z Re: USB controller hardware version / ISO OUT (RX) transfers and DQH MULT https://community.nxp.com/t5/LPC-Microcontrollers/USB-controller-hardware-version-ISO-OUT-RX-transfers-and-DQH/m-p/562770#M16540 <HTML><HEAD></HEAD><BODY><SPAN>bump</SPAN></BODY></HTML> Sun, 19 Jun 2016 01:05:24 GMT https://community.nxp.com/t5/LPC-Microcontrollers/USB-controller-hardware-version-ISO-OUT-RX-transfers-and-DQH/m-p/562770#M16540 lpcware 2016-06-19T01:05:24Z