Open
Description
Is your enhancement proposal related to a problem? Please describe.
Similar to the existent test suites for drivers and shields Bridle should protect the growing variations of the usb-console
reflected to the well known and supported boards.
Describe the solution you'd like
Create a simple build_only
test specification for Twister that holds all supported boards (variations of the usb-console
) as integration_platforms
. The test then configures and builds an empty Zephyr test application. On CMake level, the specific VID and PID for USB have to check.
Describe alternatives you've considered
Maybe there is a proper way to qualify the VID and PID on binary level, not only in CMake configuration.
Additional context
None.