You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
about the platform_packages = framework-arduinopico@https://github.com/earlephilhower/arduino-pico.git. I added this when there were the malloc problems with the newlib code and this gave me the latest release from earlephilhower that fixed the problem. Now that this is also published here, does it still make a difference? On average, how much does the platformio release lag behind the quite regular releases of earlephilhower? (maybe more a question for @earlephilhower)
UPDATE: i just switched to the earlephilhower package and the wifi class changes in some places. so i gues with respect to wifi code, its best to keep using the platform_package from earlephilhower to get the latest code
I don't know if it's just me or is the Mbed core dead or at least very very slowly kept up to date.
When comparing the board list on the mbed and earlephilhower give a pretty strong indication.
I know about the whole discussion as I followed it from the start, but at some point, i think it would be best for the community to just switch to the more reliable and better supported core (even if it's not the official)
Are there considerations on replacing the official mbed core with the earlephilhower under https://docs.platformio.org/en/latest/platforms/raspberrypi.html ?
As i found myself looking on quite a lot of different information sources: For somebody finding this searching for Infos, here are the current links I use to find infos and my current build config
i you done use the platform_packages, u will get an pretty old version of the arduino pico core as the last release from max gerhard is over six month. it does not support wifi etc
Merry Christmas,
I was just adding Pico W support to my project and was going over my config
currently, this is how it looks like:
about the
platform_packages = framework-arduinopico@https://github.com/earlephilhower/arduino-pico.git
. I added this when there were the malloc problems with the newlib code and this gave me the latest release from earlephilhower that fixed the problem. Now that this is also published here, does it still make a difference? On average, how much does the platformio release lag behind the quite regular releases of earlephilhower? (maybe more a question for @earlephilhower)UPDATE: i just switched to the earlephilhower package and the wifi class changes in some places. so i gues with respect to wifi code, its best to keep using the platform_package from earlephilhower to get the latest code
another small this: it took me some time to find the board name "rpipicow". i think it would be good to update/extent/create a documentation either on https://docs.platformio.org/ or on https://arduino-pico.readthedocs.io/.
I don't know if it's just me or is the Mbed core dead or at least very very slowly kept up to date.
When comparing the board list on the mbed and earlephilhower give a pretty strong indication.
I know about the whole discussion as I followed it from the start, but at some point, i think it would be best for the community to just switch to the more reliable and better supported core (even if it's not the official)
Are there considerations on replacing the official mbed core with the earlephilhower under https://docs.platformio.org/en/latest/platforms/raspberrypi.html ?
As i found myself looking on quite a lot of different information sources: For somebody finding this searching for Infos, here are the current links I use to find infos and my current build config
The text was updated successfully, but these errors were encountered: