-
Notifications
You must be signed in to change notification settings - Fork 30
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
Raspberry Pi Pico W #109
Comments
Issue closed: Pico W not supported in PlatformIOYou have reminded me that I need to update my issue template here and clarify that a potential target MUST be supported in both the Arduino IDE and PlatformIO. The Pico W, IIRC uses Earle Philhower's Arduino Pico package, of which is not supported by PlatformIO at this time. I highly recommend you make some noise in this Issue over on PlatformIO's repository, because I simply cannot add more Pico-based development boards beyond what is simultaneously supported in the Arduino IDE and PlatformIO. |
It's not officially supported by PlatformIO but it is quite trivial to make it work by changing two lines of |
The focus is to add boards that are officially supported in the Arduino IDE (either by Arduino themselves or through third party board packages via the I simply will not add boards with unofficial support in both the Arduino IDE or PlatformIO to CRSF for Arduino's Compatibility Table. If the board-in-question is officially supported in both the Arduno IDE and PlatformIO, then I will add it to the Compatibility Table. Adding boards with unofficial support, or adding boards that are supported in one IDE and not the other creates a level of uncertainty and inconsistency with CRSF for Arduino that I am not willing to take on. The juice is not worth the squeeze.
I understand that it's easy to implement your request. Be that as it may, simplicity versus complexity does not guarantee your request will be fulfilled, especially when there is a valid reason as to why it cannot be fulfilled.
I sympathise greatly with folks that are using RP2040-based development boards and their inability to use them with PlatformIO beyond the two boards that are officially supported. I would add support for every RP2040-based target in a heartbeat if they were officially supported in PlatformIO. However, at this time (and for the forseeable future), they are not; and this is something that is beyond my control. Therefore it is not my call to make. Rest assured, as soon as PlatformIO officially supports most RP2040-based targets, they will be added to the Compatibility Table here in CRSF for Arduino. My decision is final, and this is not up for debate. |
Issue re-opened: Pico and Pico W support can be added after allHi @britannio I was reading through this section of Earle Philhower's Arduino-Pico package, and it turns out I was wrong. My information on why the vast majority of RP2040-based targets couldn't be added to CRSF for Arduino's Compatibility Table was outdated. So, I have re-opened this issue and removed the "I'm not doing this" label and replaced it with the "In progress" label. As I am writing this comment, I am currently checking out the Arduino-Pico package, and I am conducting some internal tests in a private branch, to ensure everything is all a-okay. Once the build succeeds, I will publish the branch and attach a Pull Request to it, and go from there. Update 1723 Hrs NZSTI successfully installed Max Gerhaldt's PlatformIO integration of Earle Philhower's Arduino-Pico package, and did a build test on my local branch. You're in luck, 'cause look... 👇 Also, this 👇 was highlighted in my Compatibility Table... ConclusionYour request has been added to my development pipeline, and it will make it into the upcoming release of Version 1.1.0. |
:) |
Minimum requirements
What development board would you like me to add?
It seems like this is the only change to make: britannio@d699599
The text was updated successfully, but these errors were encountered: