-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Update Code for Class Vendor_Host #1097
Comments
yes, vendor host is lacking behind the migration/upgrade and currently I don't have plan/time to work on it. |
What needs to be done in order to migrate/upgrade this? I want to communicate with a ft232r with the rp2040's USB. |
Any news ? |
@jmark1m did you manage to get the vendor specific host to work? |
See #2488. |
I guess I did manage to get usb host to work just using the tinyusb submodule that comes with the pico 2040 sdk. For my project it was known what devices were going to be plugged in to it so I assigned them fixed end points and didn't go through all of the things a host should do to assign endpoints. But eventually I just sent data from my host to the device with this simple function. Good luck.
|
@jmark1m thanks for your reply. |
No news since 2021 ? |
The type definitions for pipe_handle_t were removed in #449 for all class drivers except for class Vendor_Host (/class/vendor_host.h and /class/vendor_host.c).
The Class Vendor_Device also does not use the type pipe_handle_t so it seems Vendor_Host should follow a similar pattern.
I want to simply define,
#define CFG_TUH_VENDOR 1
and then simply be able to use these functions for bulk data transfer.
tusb_error_t tusbh_custom_read(uint8_t dev_addr, uint16_t vendor_id, uint16_t product_id, void * p_buffer, uint16_t length);
tusb_error_t tusbh_custom_write(uint8_t dev_addr, uint16_t vendor_id, uint16_t product_id, void const * p_data, uint16_t length);
I can't compile currently because
/class/vendor/vendor_host.h:37:3: error: pipe_handle_t does not name a type (pipe_handle_t pipe_in)
The text was updated successfully, but these errors were encountered: