ARM, RISC-V контроллеры

Вы абсолютно правы. Вот ответ от FTDI. A1. FTDI have defined our own device class. So FTDI devices return a 0 for the bDeviceClass (Vendor class). The class cannot be configured by the designer. Our chips do not return the correct USB device descriptors to be USB HID class or USB Mass Storage class. It may be possible to write a filter driver that will make our chip appear to be a HID or mass storage class device, but to do this would involve a lot of work. A2. Our devcie are all USB client devices and as such cannot be used as a USB host.