https://proghq.org/w/index.php?action=history&feed=atom&title=Talk%3AOpen-TL866_Protocol 2026-04-15T04:07:42Z Revision history for this page on the wiki MediaWiki 1.41.1 https://proghq.org/w/index.php?title=Talk:Open-TL866_Protocol&diff=587&oldid=prev 2019-03-13T23:46:39Z

<p>Add talk page for protocol discussion</p> <p><b>New page</b></p><div>== Protocol Improvements ==<br /> <br /> We currently have a CDC/ASCII protocol; having a high-speed bulk transfer/binary protocol would make some programming/read actions quicker. In addition the speed boost would enable some programming tasks whose timing is currently impossible to meet with the ASCII protocol.<br /> <br /> <br /> === Composite Device Proposal ===<br /> Paraphrased from [[User:Elemecca]]. Interface refers to the [http://www.usbmadesimple.co.uk/ums_4.htm USB definition] of interface.<br /> <br /> * Support the CDC and high-speed interfaces in parallel, maybe with an option to reset to a high-speed-exclusive mode.<br /> * Make the interfaces mutually exclusive and boot to the CDC interface by default, but expose the high-speed interface with no endpoints in CDC mode. <br /> ** High-speed clients can check the device status and request reset to high-speed mode without needing to implement the high speed protocol.<br /> <br /> In both cases listed above, control transfers would be used to switch between CDC and high-speed mode. On Windows, the [https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/winusb WinUSB] driver would attach to the high-speed interface (either using a [https://github.com/signal11/m-stack/blob/master/docs/winusb.txt special string descriptor] or an inf file). We also need an inf file for the CDC interface for Windows 8.1 and below.<br /> <br /> == Comments ==<br /> I am on board with either option, with a slight preference for the latter due to being simpler to implement.--[[User:Cr1901|Cr1901]] ([[User talk:Cr1901|talk]]) 23:46, 13 March 2019 (UTC)</div>

Cr1901