<?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>Kinetis Software Development KitのトピックRe: Regard to the cdc endpoint in usb composite ( cdc + msd )</title>
    <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011839#M8007</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jim,&lt;/P&gt;&lt;P&gt;Please see the USB 2.0 specification. In section 5.3.1.2, it shows&lt;/P&gt;&lt;P&gt;"Functions can have additional endpoints as required for their implementation. Low-speed functions are&lt;BR /&gt;limited to two optional endpoints beyond the two required to implement the Default Control Pipe. Fullspeed&lt;BR /&gt;devices can have additional endpoints only limited by the protocol definition (i.e., a maximum of 15&lt;BR /&gt;additional input endpoints and 15 additional output endpoints)."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Nov 2019 07:08:43 GMT</pubDate>
    <dc:creator>jingpan</dc:creator>
    <dc:date>2019-11-21T07:08:43Z</dc:date>
    <item>
      <title>Regard to the cdc endpoint in usb composite ( cdc + msd )</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011838#M8006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I create the usb composite cdc msc project, and I'm going&amp;nbsp; to see usb_device_descriptor.c/.h, I don't understand that Bulk IN and Bulk OUT endpoint number is same in the endpoint descriptor of Data Interface descriptor (below picture : Green wire).&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_4.bmp"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/94722i6D30DF9AFBB91AC0/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_4.bmp" alt="pastedImage_4.bmp" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_3.bmp"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/94678i843F4FA20C0A6D41/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_3.bmp" alt="pastedImage_3.bmp" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I try to change Bulk OUT number 3 to number 5, This change&amp;nbsp;will&amp;nbsp;cause cdc to don't work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.bmp"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/94601iB9502F21ECED011C/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.bmp" alt="pastedImage_1.bmp" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I think it is related to the driver(INF), but not very sure.&lt;/P&gt;&lt;P&gt;Why the&amp;nbsp;&lt;SPAN&gt;Bulk IN and Bulk OUT endpoint number is same?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Nov 2019 02:01:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011838#M8006</guid>
      <dc:creator>jimhuang2</dc:creator>
      <dc:date>2019-11-20T02:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: Regard to the cdc endpoint in usb composite ( cdc + msd )</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011839#M8007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jim,&lt;/P&gt;&lt;P&gt;Please see the USB 2.0 specification. In section 5.3.1.2, it shows&lt;/P&gt;&lt;P&gt;"Functions can have additional endpoints as required for their implementation. Low-speed functions are&lt;BR /&gt;limited to two optional endpoints beyond the two required to implement the Default Control Pipe. Fullspeed&lt;BR /&gt;devices can have additional endpoints only limited by the protocol definition (i.e., a maximum of 15&lt;BR /&gt;additional input endpoints and 15 additional output endpoints)."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Nov 2019 07:08:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011839#M8007</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2019-11-21T07:08:43Z</dc:date>
    </item>
    <item>
      <title>Re: Regard to the cdc endpoint in usb composite ( cdc + msd )</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011840#M8008</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Hi Jing,&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;I am going to see&amp;nbsp;5.3.1.2 Non-endpoint Zero Requirements, but the next chapter "5.3.2. Stream Pipes" have describe&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Stream pipes deliver data in the data packet portion of bus transactions with no USB-required structure on&lt;BR /&gt;the data content. Data flows in at one end of a stream pipe and out the other end in the same order. Stream&lt;BR /&gt;pipes are&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;always uni-directional&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in their communication flow.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;A stream pipe to a device is bound to a single device endpoint number in the appropriate direction (i.e.,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;corresponding to an IN or OUT token as defined by the protocol layer). The device endpoint number for the&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG style="border: 0px; font-weight: bold;"&gt;opposite direction can be used for some other stream pipe to the device.&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;Stream pipes support bulk, isochronous, and interrupt transfer types, which are explained in later sections.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;So, I think an&amp;nbsp;&lt;SPAN style="border: 0px; font-weight: inherit;"&gt;endpoints number&amp;nbsp;&lt;/SPAN&gt;only set&amp;nbsp;one transmission direction.&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: inherit;"&gt;Best Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="color: #51626f; background-color: #ffffff; border: 0px;"&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff; border: 0px; font-weight: inherit;"&gt;Jim&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Nov 2019 09:15:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011840#M8008</guid>
      <dc:creator>jimhuang2</dc:creator>
      <dc:date>2019-11-21T09:15:57Z</dc:date>
    </item>
    <item>
      <title>Re: Regard to the cdc endpoint in usb composite ( cdc + msd )</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011841#M8009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your reply, I tested that IN and OUT endpoint number is same to work.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Nov 2019 01:30:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011841#M8009</guid>
      <dc:creator>jimhuang2</dc:creator>
      <dc:date>2019-11-22T01:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: Regard to the cdc endpoint in usb composite ( cdc + msd )</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011842#M8010</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;No. For example, the pipe on endpoint 1 out and endpoint 1 in is different pipe, they are different endpoint.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;jing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Nov 2019 06:03:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Regard-to-the-cdc-endpoint-in-usb-composite-cdc-msd/m-p/1011842#M8010</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2019-11-25T06:03:22Z</dc:date>
    </item>
  </channel>
</rss>

