-
Notifications
You must be signed in to change notification settings - Fork 31
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
Interested in adding other RP2040 boards? #2
Comments
Hello ! I am very honored that this firmware has been integrated into Blinka for the CircuitPython. Adafruit products are very good and you make DIY electronics progress a lot with your github repositories. Although the pico is very flexible in terms of pin mapping, I wanted to freeze them and match them to the PCB that I made at the same time. It was for simplicity but I think it was a mistake. This infinite loop problem is very strange. For my part, I am developing on a debian 10 which provides gcc-arm-none-eabi in version "15:7-2018-q2-6". If I have a chance to upgrade gcc, I will try to find the problem, thanks for the information! |
May have fixed the weird compiler issue - or at least tweaked the code to get things working. See: |
Fix compiler warnings and make pico-sdk a submodule.
Thanks for your pull request. I also added the UART1 interface because I saw that the QT Py card was wired to UART1 and not UART0. So there may be a modification in Blinka in order to handle both uart (as you made it for SPI and I2C). |
woot! thanks! |
Hey @execuc , this isn't an issue.
First, thanks for writing this cool firmware. I did the work to add the additional support needed to allow using the Pico w/ u2if firmware from a PC via the Blinka library:
https://learn.adafruit.com/circuitpython-libraries-on-any-computer-with-raspberry-pi-pico
It all worked really well!
I've also done some simple modifications to allow adding other RP2040 based boards:
adafruit#1
which generally came down to a pin re-mapping. Would you be interested in a pull request to add that capability here?
Also - curious what build environment you used for your release artifacts? I was originally using
gcc-arm-none-eabi-10-2020-q4-major
to build for the PR linked above and had issues with it creating an infinite loop insideStreamedInterface::streamRxRead
. Eventually tried just switching togcc-arm-none-eabi-7-2018-q2-update
which worked as expected. Really weird issue.The text was updated successfully, but these errors were encountered: