-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a new USB device which does not fit into the included classes. #150
Comments
This is working for any device class |
Hi Chegewara. That is the code I've started with and made some good progress with it. However in order to get the device descriptors below changed from what they would be (shown below): Device Descriptor: To what I need them to be: Device Descriptor: I've amended, for the time being, the code below found in the "usb_descriptors.cpp" file. Which isn't ideal as this will be overridden at the next update of the library.
I'd like to be able to set these values within the project as opposed to relying on the source files. I'm still looking at where the configuration descriptors below are set, and obviously would like to configure these within the project as opposed to the source files: Configuration Descriptor: Any help/advice/pointers you can put my way would be gratefully received. Regards |
It is arduino library, which means it was meant to use by newb-ish users. My suggestion is to fork library and to add options you need, or just change values you mentioned. |
我也在尝试使用esp32s3,让它被计算机识别成打印机,通过USB进行连接,期待作者支持 |
I am looking at creating a IoT device which will have it's own vendor and product ID, but who's description does not fit in with the included defined device classes. Basically I want to fool another device into thinking that it has a USB printer attached to it.
Where do I start?
I could have a defined class in a CPP and H files in the same directory as the project (coding in Arduino IDE), but couldn't find a good example of how the vendor and product ID are defined.
Any help would be gratefully received. Thanks
The text was updated successfully, but these errors were encountered: