-
Notifications
You must be signed in to change notification settings - Fork 52
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
Can no longer resolve dependencies (Error: VCS: Could not process command ...) #26
Comments
I've gotten two errors about filenames being too long some log entries before the fatal errors happened, I'm not sure if they are related:
|
After finding hathach/tinyusb#1939 it seems like this repo needs to update the tinyusb submodule. @maxgerhardt would that be doable? |
No. The repo points at Arduino-Pico. That the points at the stable Pico-SDK. That points to a TinyUSB version that still has all the submodules.The change will only trickle through after a new Pico-SDK version is released that points to new TinyUSB version and Arduino-Pico repoints at the new Pico-SDK. There's nothing we can do in this repo.
|
Oh right I kind of messed up which repo we are on. Until raspberry updates tinyusb and earlephilhower updates the tinyusb submodule the framework won't be useable I gueses. Hm. Will try to implement the changes on a fork so I can work with it for the time being. |
Given the issues from PlatformIO to accept the PR is there a workaround on this? I have the same issue |
Dependency downloading is completely unrelated to the PR. It doesn't matter a single bit if they accept the PR in platform-raspberry or not here. The depenency downloads should work fine. If you're on Windows, make sure that you have enough space (TinyUSB takes up lots of space, have at least 3, if not better 5 GB free!) and make sure you followed https://arduino-pico.readthedocs.io/en/latest/platformio.html#important-steps-for-windows-users-before-installing |
I have this platform referenced via
When opening the project, PIO starts cloning submodules for around 10 minutes. After the submodule pyserial, it gives me an error.
I have tried re-installing PIO, deleting the .platformio folder, re-installing VSC etc. multiple times without any success. This behavior was replicatable by other people. When executing the exact command via the cmd, everything clones fine without any errors. First I thought this is because I am using a fork of this repository but I tried using this instead and the issue still existed. This started happening after updating to the newest state of the master branch of this repo. Before, I was using a ~2 months behind fork that worked without any issues. What's also mentionable is that the error comes after the pyserial submodule, which is actually the last module which I found out when cloning the repo manually.
The text was updated successfully, but these errors were encountered: