USB2ANY: USB-CDC protocol

Danilo,

USB2ANY enumerates as an HID, less because of the actual device class and more because the MSP430 had some existing HID library support developed which made USB2ANY development faster. Using a custom DLL we pack relevant commands and payload into the control transfer's 64 bytes. Keep in mind, USB2ANY was designed to work with TI EVMs, and most of those EVMs have relatively simple needs - basic SPI/I2C, basic UART, exposing a few on-board peripherals at low bandwidth, etc. There's a lot of capabilities USB2ANY never needed to support, such as real-time I/O.

We do provide some documentation of the DLL and its exposed APIs on other posts: https://e2e.ti.com/support/clock-timing-group/clock-and-timing/f/clock-timing-forum/1025934/lmx2594evm-serial-control-through-python shows some example code, while https://e2e.ti.com/support/clock-timing-group/clock-and-timing/f/clock-timing-forum/1028162/lmk01000eval-usb2any-sdk-download has a more recent SDK link. If this is the same application as the previous question, USB2ANY could conceivably be used with its UART APIs, but there would be some significant limitations due to the control transfer payload size and the latency between the full-speed control transfer (fastest I've ever seen is around 5ms between transfers). You're welcome to experiment with it, but I suspect you'll need a different solution.

Regards,

Derek Payne