Skip to content

pico-sdk installed size #1330

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
robaol opened this issue Mar 27, 2023 · 3 comments
Closed

pico-sdk installed size #1330

robaol opened this issue Mar 27, 2023 · 3 comments

Comments

@robaol
Copy link

robaol commented Mar 27, 2023

Thank you for your effort to bring the pico to the arduino environment.

I installed as per the README by adding the url to the Additional Boards Manager and then did as suggested in Current state of development to build for the pico from within vscode+pio.
I have found that the framework-arduinopico is 2.6GB out of 3.5GB for the whole of my .platformio. Looking at the folder breakdown, attached, it appears to be driven by tinyusb/.../hw (~1.5GB) and the corresponding .git/modules/pico-sdk/modules (~0.7GB).
This seems excessive for a usb library and appears to be due to linked/submoduled tinyusb including hw support for many other mcus. I know "disk is cheap" but I don't want to use the space I have unnecessarily.

Have I done something wrong?
Is this something that you have no control over as it comes with the pico-sdk? Or has it perhaps been addressed in later pico-sdks that you can reference? Or is it a question for raspberrypi pico-sdk?

Screenshot 2023-03-11 141747 tinyusb disk usage

@earlephilhower
Copy link
Owner

Sorry, that's just the way Platform.IO is. It does a deep recursive clone and can't be changed AFAIK when using a git source.

You can use the released platform package, not the git, which only has the needed files and not the sub-submodules, if you're really short of disk space. (i.e. it follows the README https://github.com/earlephilhower/arduino-pico#installing-via-git )

@maxgerhardt
Copy link
Contributor

The next release of Pico-SDK will have that fixed given that it'll be using the next stable version of TinyUSB, since all submodules were removed and replaced by a download script that should only pull what you need, see discussion at hathach/tinyusb#1939. So the change will slowly trickle through all layers.

@robaol
Copy link
Author

robaol commented Mar 31, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants