feature(esp_tinyusb): Added tusb_teardown() call while tinyusb_driver_uninstall()

[roma-jam]

Requirements

• To uninstall tinyusb driver, a teardown tinyusb stack should be called.
• tud_deinit() feature was implemented in upstream, starting with version v0.17.0.

Description

• Added tusb_teardown() call while tinyusb_driver_uninstall()
• Added test app to verify teardown feature

Testing

Added test_app teardown_device for CDC Device Class. The logic of the test:

1. Installs the tinyUSB driver via esp-tinyusb wrapper with 1xCDC class device
2. Expects the 'teardown' string from the Host
3. Echoes the 'teardown' string to the Host
4. Teardowns the tinyUSB driver via esp-tinyusb wrapper
5. Repeats the steps from the step.1 10 times
6. Verify amount of attempts and memory leakage

Related issues

• Original espressif/tinyusb PR: feature(usbd): Added tud_teardown() tinyusb#27 (closed, because of synchronizing with upstream v0.17)
• Requires tusb_teardown() API: feature(tusb): Added tusb_teardown() tinyusb#44
• Resolve esp32s3, restarting cdc software serial doesn't work (IDFGH-12813) esp-idf#13788

[roma-jam]

@tore-espressif , @peter-marcisovsky
This changes unlock the possibility to run usb device tests one by one (espressif/tinyusb#27 should be merged first, though).

I posted two questions for both of you, because it seems that we can make it better and we can use it.

I need that for enumeration driver testing (but maybe I will eliminate esp_tinyusb component from the chain, but anyway), so feel free to check it out when possible.

Meanwhile, I will go and cover the Enum Driver as much as I can.

[peter-marcisovsky]

Left some observations from using the test app

[finger563]

Is there a timeline for this feature to be finalized?

[roma-jam]

Hi @finger563 ,

This feature allows the re-configure the driver with these changes: espressif/tinyusb#27
But as far as the same changes are already in the upstream, so we will rebase these changes after updating version to v0.17.0.
For current feature there is no available timeline for now, but the one thing for sure: the update to v0.17.0 will be done first.

Meanwhile, this feature should be available in the upstream of TinyUSB, if anything it is possible to use it.

Sorry for the inconvenience.

[roma-jam]

@tore-espressif @peter-marcisovsky
This is the enabling of teardown feature via tinyusb_driver_uninstall() call from esp_tinyusb wrapper.

To enable the CI (I am expecting the teardown_device test to fail), it is required to release espressif/tinyusb component with changes from here: espressif/tinyusb#44

Feel free to review the changes in current PR and I will relaunch CI after the tinyusb release (Which I planned on 22th of December, but will do that next Monday, 16th).

UPD: we are running only cdc test, not all of them, so there is not problem with CI