now i understand why no pico support in platformio..
Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
11–20 of 38 posts
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#12Seems like PlatformIO wants RPi to PAY them to be officially supported, even though RPi is not even involved in adding this support (someone else did and posted a PR). RPi seems to have correctly replied with what amounts to a "WTF‽". Sure sounds like PlatformIO folks are just being dicks for no reason. This is like person A uploading my code (without permission and blessing from me, but not counter to my license) to…
You left out an important detail: Project C is going to have to _support_ your "free" code in their product. If it breaks, even if not because of anything Project C did, their paying customers are going to demand work from THEM.
if i want the prestige of my code being in their project
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#13A better link to PlatformIo response: https://github.com/platformio/platform-raspberrypi/pull/36#i...
Whilst PlatformIO come across as the villains in this story, adding the RPi support to their core would indicate some kind of support/work from them in future versions (beyond the ‘non production’ support they provide now). It’s upto them if they want to provide this, otherwise it can stay as a patch.
Ultimately this is the never ending saga of the profit/work from open source flowing from easily copyable work of software companies and enthusiasts towards more easily monetisable hardware companies
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#14A bit of background:
I don't believe there's any official support from Raspberry Pi for using the Pico with Arduino. Raspberry Pi provides Micropython and a C/C++ SDK. My guess that professionals in the embedded space probably use the SDK directly (it's nicely documented) and do things themselves, but hobbyists like me would like a package manager so we can install libraries easily. Enter Arduino.
This isn't Arduino's official support for the Pico either. Arduino made a port based on mbed. It doesn't seem to be used much, based on my searches. Not much about it since 2021.
That's because Earle Philhower's "community port," called arduino-pico [1] is nicer. I switched to it to get good USB-Midi support, because it has an option to use Adafruit's fork of the TinyUSB library.
But, as a package manager, Arduino can be confusing and PlatformIO is supposed to be more sane. So, with the patch, you can do that, and the instructions are here [2]. It works fine. The patch isn't merged, but it works.
Somehow this is the unofficial, alternate choice in multiple ways, so it probably looks pretty dubious. But it's the one that seems best for me. Ideally I'd be using a language with a real package manager instead of Arduino or PlatformIO's embedded-only implementations. (I don't even particularly like C++.)
[1] https://github.com/earlephilhower/arduino-pico [2] https://arduino-pico.readthedocs.io/en/latest/platformio.htm...
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#15A better link to PlatformIo response: https://github.com/platformio/platform-raspberrypi/pull/36#i... Whilst PlatformIO come across as the villains in this story, adding the RPi support to their core would indicate some kind of support/work from them in future versions (beyond the ‘non production’ support they provide now). It’s upto them if they want to provide this, otherwise it can stay as a patch. Ultimately this…
> Whilst PlatformIO come across as the villains in this story
I find this to be a bit misleading.
My take is that the RPi foundation wants PlatformIO to do support work for RPi for free.
At no point do I see the RPi foundation saying "Hey, we'll allocate programmers and resources to maintain this code for our chip."
Open source means that you get the code and that's it--open source doesn't mean that you get any say whatsoever over the developers. When did everybody start being so damn entitled that everybody thinks they can tell maintainers what to do?
Don't like it? Shut your piehole and roll up your sleeves. Quit bitching, fork the PlatformIO stuff and do the work yourself. If the fork is sufficiently popular, it will yank enough people away from the original that they'll cave. And if it isn't sufficiently popular, well then that's an answer, too.
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#16A better link to PlatformIo response: https://github.com/platformio/platform-raspberrypi/pull/36#i... Whilst PlatformIO come across as the villains in this story, adding the RPi support to their core would indicate some kind of support/work from them in future versions (beyond the ‘non production’ support they provide now). It’s upto them if they want to provide this, otherwise it can stay as a patch. Ultimately this…
> Whilst PlatformIO come across as the villains in this story I find this to be a bit misleading. My take is that the RPi foundation wants PlatformIO to do support work for RPi for free. At no point do I see the RPi foundation saying "Hey, we'll allocate programmers and resources to maintain this code for our chip." Open source means that you get the code and that's it --open source doesn't mean that you get any say…
> My take is that the RPi foundation wants PlatformIO to do support work for RPi for free.
How did you arrive at this take when the original code and the PR aren’t related to the Raspberry Pi foundation at all? This is a community contribution, not something the Raspberry Pi foundation tried to push throug.
> At no point do I see the RPi foundation saying "Hey, we'll allocate programmers and resources to maintain this code for our chip."
They didn’t write this code, and this isn’t what PlatformIO is asking for. PlatformIO wanted the Raspberry Pi foundation to pay substantial recurring fees so PlatformIO could merge this PR by someone else.
> Don't like it? Shut your piehole and roll up your sleeves. Quit bitching, fork the PlatformIO stuff and do the work yourself.
That’s quite literally what they did. This was developed by someone in a fork. That person didn’t even submit this PR. None of the people involved appear to be related to the Raspberry Pi foundation, but PlatformIO tried to bill Raspberry Pi for it anyway.
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#17A better link to PlatformIo response: https://github.com/platformio/platform-raspberrypi/pull/36#i... Whilst PlatformIO come across as the villains in this story, adding the RPi support to their core would indicate some kind of support/work from them in future versions (beyond the ‘non production’ support they provide now). It’s upto them if they want to provide this, otherwise it can stay as a patch. Ultimately this…
> Whilst PlatformIO come across as the villains in this story I find this to be a bit misleading. My take is that the RPi foundation wants PlatformIO to do support work for RPi for free. At no point do I see the RPi foundation saying "Hey, we'll allocate programmers and resources to maintain this code for our chip." Open source means that you get the code and that's it --open source doesn't mean that you get any say…
>My take is that the RPi foundation wants PlatformIO to do support work for RPi for free.
A third party (the committer - maxgerhardt) wants PlatformIO to do support work (on someone else’s code - Earle Philhower) for people who want to use the Arduino toolset on RPi for free.
I think it’s fine that PlatformIO and RPi don’t want to fund this.
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#18Seems like PlatformIO wants RPi to PAY them to be officially supported, even though RPi is not even involved in adding this support (someone else did and posted a PR). RPi seems to have correctly replied with what amounts to a "WTF‽". Sure sounds like PlatformIO folks are just being dicks for no reason. This is like person A uploading my code (without permission and blessing from me, but not counter to my license) to…
You left out an important detail: Project C is going to have to _support_ your "free" code in their product. If it breaks, even if not because of anything Project C did, their paying customers are going to demand work from THEM. if i want the prestige of my code being in their project LOL yeah that's definitely why this contribution is happening /s
> If it breaks, even if not because of anything Project C did, their paying customers are going to demand work from THEM.
Well... isn't that what their customers are paying them for?
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#19Earlier quoted context omitted.
> Whilst PlatformIO come across as the villains in this story I find this to be a bit misleading. My take is that the RPi foundation wants PlatformIO to do support work for RPi for free. At no point do I see the RPi foundation saying "Hey, we'll allocate programmers and resources to maintain this code for our chip." Open source means that you get the code and that's it --open source doesn't mean that you get any say…
> My take is that the RPi foundation wants PlatformIO to do support work for RPi for free. How did you arrive at this take when the original code and the PR aren’t related to the Raspberry Pi foundation at all? This is a community contribution, not something the Raspberry Pi foundation tried to push throug. > At no point do I see the RPi foundation saying "Hey, we'll allocate programmers and resources to maintain thi…
I take it as the platformio do not have enough employees/throughput to maintain this. So they wanted to make this support semi-official and hire a developer.
Promises from the open-source contributors are just that - promises, life gets in the way of contributing, etc.
Re: Raspberry Pi/PlatformIO conflict blocks support for Pico-Arduino toolchain
#20Seems like PlatformIO wants RPi to PAY them to be officially supported, even though RPi is not even involved in adding this support (someone else did and posted a PR). RPi seems to have correctly replied with what amounts to a "WTF‽". Sure sounds like PlatformIO folks are just being dicks for no reason. This is like person A uploading my code (without permission and blessing from me, but not counter to my license) to…
You left out an important detail: Project C is going to have to _support_ your "free" code in their product. If it breaks, even if not because of anything Project C did, their paying customers are going to demand work from THEM. if i want the prestige of my code being in their project LOL yeah that's definitely why this contribution is happening /s
Then they should take their beef to “person A”, not to me. My example properly captures my noninvolvement. Just like in TFA, RPi was not involved. Someone else made the patch, then PlatformIO demanded money from RPi