move to tinyusb 0.9.0 - switch to using their examples directly rather than copied versions #99
Conversation
| add_tinyusb_device_example(cdc_msc) | ||
| # todo gate with freertos lib | ||
| #add_tinyusb_device_example(cdc_msc_freertos) | ||
| add_tinyusb_device_example(dfu_runtime) |
There was a problem hiding this comment.
Is this relevant, given that we recommend flashing via UF2? 🤷
There was a problem hiding this comment.
what do you mean?
There was a problem hiding this comment.
DFU = Device Firmware Upgrade, typically used to write the flash on a microcontroller (which is what we use UF2 for). But I've just checked https://github.com/hathach/tinyusb/blob/master/examples/device/dfu_runtime/src/main.c and see that it says:
Since this example is minimal, it doesn't actually go into DFU mode but rather change the LED blinking pattern to fast rate as indicator.
So apologies for the irrelevant comment! 😆
|
I guess the CI tests here won't pass until after raspberrypi/pico-sdk#321 has been merged. |
correct; would be nice if there is a way to handle this sort of dependency case without too much effort |
I think you might be able to fix that by editing the |
|
P.S. Should this PR be targeting the |
replace copied tinyusb examples with use of examples directly from tinyusb repo.
this avoids us having to fix up examples ourselves if the upstream API changes, though for now we still have a hard-coded list of examples, and we are using a GLOB (within an SDK provide add_tinyusb_device/host_example method) to generate build targets for them.
this works currently, though is not ideal. to fix it we need the cmake structure within TinyUSB example to be more friendly towards the use case of including their exmaples'
CMakeLists.txts in this way