RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
250f6fdfa3
RIOT/examples/usbus_minimal
History
chrysn 250f6fdfa3 usb: Warn on test-ID usage in a unified location 
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
2020-06-30 10:51:36 +02:00
..
main.c usbus_minimal: Adapt example to auto_init 2019-06-05 16:17:01 +02:00
Makefile usb: Warn on test-ID usage in a unified location 2020-06-30 10:51:36 +02:00
README.md usb: Move configuration macros to 'CONFIG_' namespace 2020-01-14 10:34:53 +01:00

README.md

usbus_minimal example

This is a minimalistic example for RIOT's USB stack. The application will initialize and start the USB stack. The stack is started without any USB handlers, it should show up as an empty USB device on the host.

RIOT doesn't own any USB vendor and product ID. To compile this example, add your own vendor and product ID to the makefile:

CFLAGS += -DCONFIG_USB_VID=0xYOURVID -DCONFIG_USB_PID=0xYOURPID

The example demonstrates basic USB communication between a host and a RIOT based USB peripheral. Tools such as lsusb should display the device and detailed information about the device such as descriptor strings.