250f6fdfa3
This
* renames DEFAULT_xID to USB_xID_TESTING as it is not really a default
(if anyting, the 7D00 is, and it's not that)
* moves the check into Makefile
* generalizes the check to all test PID/VID pairs
* in doing so, fixes the "or" (which would have ruled out warning-free
use of an allocated pid.codes number), and compares to the actual
testing PID rather than the RIOT-peripheral PID
* removes all occurrences of duplicated checks in examples or tests,
leaving definitions only where they are needed
* moves the Kconfig defaults of the usbus_minimal example into the main
Kconfig, as these are good defaults for all cases when USB is enabled
manually
Closes: https://github.com/RIOT-OS/RIOT/issues/12273
|
||
|---|---|---|
| .. | ||
| main.c | ||
| Makefile | ||
| Makefile.ci | ||
| README.md | ||
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.