Replies: 2 comments
-
you can use
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you!
…On Thu, Feb 22, 2024 at 6:46 AM Ha Thach ***@***.***> wrote:
you can use
- lsusb on linux,macos
- https://www.uwe-sieber.de/usbtreeview_e.html on windows
—
Reply to this email directly, view it on GitHub
<#2465 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALBTS6VFHKMXV6OTA5KUBLYU4VZ7AVCNFSM6AAAAABDFGXW2SVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DKNJVHAZDI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I'm starting development using tinyusb, and using the chrome://usb-internals has been helpful for exploring other USB devices to compare to my own.
Unfortunately I don't seem to be able to interactively "Get Device Descriptor" or "Get Configuration Descriptor" using that tool, though the device does actually appear to be working correctly.
Here is an image of what I see:
I am using a tweaked version of the cdc_msc_freertos example from the pico-sdk library of tinyusb, the usb_descriptors.c file being here (link). Basically it's very vanilla and simple. All I did was remove the functionality for msc.
Anyone have success using the usb-internals tool to examine the device or configuration descriptors? Or know of another tool that does work with tinyusb? Or know of something I might be doing incorrectly to cause this?
Again, I do know my device is being requested the device/configuration descriptors (I log the request) and windows does seem to process it correctly.
I will note that other usb devices (like a logitech mouse, which I expect is working correctly) mostly have the same issue. I've really only found one device (Saleae Logic) which seems to work.
Thanks.
Doug
Beta Was this translation helpful? Give feedback.
All reactions