Slow and large installation due to unnecessary TinyUSB components

[Liftyee]

When installing the pico-sdk, the installation takes much longer than it should because many unnecessary drivers from the TinyUSB repo are cloned individually due to the references. https://github.com/hathach/tinyusb/tree/86c416d4c0fb38432460b3e11b08b9de76941bf5/hw/mcu Example
folder that is slowing down the installation - surely all the infineon, wch, etc. drivers are not needed?

The pico-sdk could be made much smaller and quicker to install if only the required parts of TinyUSB were included.

[dhalbert]

TinyUSB recently removed submodules. See hathach/tinyusb#1947 and hathach/tinyusb#1961. So maybe this problem will go away when TinyUSB is updated?

Tagging @hathach for interest.

[Liftyee]

Looks like hathach/tinyusb#1947 will improve install times, although hopefully the python script won't break anything.

Leaving issue open until that PR is merged.

[lurch]

See also raspberrypi/pico-sdk#1044

You only get these "unnecessary drivers" if you do a recursive clone, which isn't what https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf says to do (for precisely this reason 😉 ). I'm curious which instructions you were following which means you are pulling down all the submodules?

[Liftyee]

Perhaps the problem lies in my development workflow. I am using the Earle Philhower Arduino core via PlatformIO in Visual Studio Code, and something along the chain (I think it is PlatformIO) is doing a recursive clone on the pico-sdk repo. I'm not manually installing the SDK, so I haven't followed those instructions. It seems to occur when the Earle Philhower core is cloned recursively by PlatformIO, which works in reasonable time for other linked repos but has the aforementioned issues with this one.

[aallan]

Raspberry Pi only directly supports our official C SDK and the MicroPython environment. Unfortunately, PlatformIO isn't an officially supported environment.