15bd4897c1
Macros that changed: USB_CONFIG_VID -> CONFIG_USB_VID USB_CONFIG_PID -> CONFIG_USB_PID USB_CONFIG_MANUF_STR -> CONFIG_USB_MANUF_STR USB_CONFIG_PRODUCT_STR -> CONFIG_USB_PRODUCT_STR USB_CONFIG_CONFIGURATION_STR -> CONFIG_USB_CONFIGURATION_STR USB_CONFIG_PRODUCT_BCDVERSION -> CONFIG_USB_PRODUCT_BCDVERSION USB_CONFIG_SPEC_BCDVERSION -> CONFIG_USB_SPEC_BCDVERSION USB_CONFIG_SELF_POWERED -> CONFIG_USB_SELF_POWERED USB_CONFIG_MAX_POWER -> CONFIG_USB_MAX_POWER USB_CONFIG_DEFAULT_LANGID -> CONFIG_USB_DEFAULT_LANGID
Expected result
A second USB serial console (ttyACMx) appears when plugging the USB peripheral into a host computer. When opening the serial device it should show the RIOT shell. Basic command interaction must work.
The test should work on Linux, MacOS and Windows. Putty is known to work on Windows.
Changing the baud rate, bit mode and parity mode is accepted by the device and reflected back. However, changing these should not affect shell operation.
Note that when testing with this firmware, the regular USB serial console from the attached debugger is not functional.
Background
This test application can be used to verify the USBUS CDC ACM implementation. Assuming drivers available, the board under test should show up on the host computer as an USB CDC Abstract Control Management device (ttyACMx on Linux). Drivers are available for Linux, macOS and Windows.