Need information on customising webusb_serial example #1465
Replies: 3 comments 2 replies
-
OK solved the "invalid configuration descriptor" issue, but still the device fails to enumerate as WinUSB device and WinUSB.sys is not loaded. Below are my changes:
}; //#define CONFIG_TOTAL_LEN (TUD_CONFIG_DESC_LEN + TUD_CDC_DESC_LEN + TUD_VENDOR_DESC_LEN) // Interface number, string index, EP notification address and size, EP data address (out, in) and size. // Interface number, string index, EP Out & IN address, EP size Thanks, |
Beta Was this translation helpful? Give feedback.
-
are you runnning webusb_serial example as it is (un-modified) with makefile. If not then, please try with makefile before doing any ports to prevent similar issue regarding porting with cdc_msc example previously. |
Beta Was this translation helpful? Give feedback.
-
I eventually have managed to remove the CDC from the WebUSB_Serial example application and modified it to only have Vendor class device, coming up as a WinUSB device with read and write working. I had to change the endpoints used for vendor class interface. This is all working good on the custom platform. However I couldn't get the WebUSB example to work on STM32F723E discovery board even after changing the Vendor device interface endpoints. Below is what I had to do get the Vendor class come up as WinUSB device on the custom board.
to get the write functionality working, I had to synchronising the application to wait for DATA-In to signal that previous write was successfully completed. I did this by defining the tud_vendor_tx_cb() function and used a binary semaphore to synchronise with the tud_vendor_n_write() function. Thanks, |
Beta Was this translation helpful? Give feedback.
-
Hello,
I have the tinyUSB ported to a custom board that has the same USB controller (synopsys) as in SM32F723E discovery board. I had the cdc_msc example working and I'm now working on the webusb_serial example. My goal is to create a Vendor specific device class that enumerates on Windows 10 as a winusb device. My plan is to remove the CDC part from the configuration descriptor of this example. Then remove the webusb part from the BOS descriptor of this example and only retain the winusb part. Then use the read and write functions of the Vendor class to communicate with the device using a Windows application through WinUSB interface.
I'm currently facing these two issue and need help to solve them:
Please advice.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions