-
Notifications
You must be signed in to change notification settings - Fork 531
CI: Tidyup and combine MicroPython builds. #737
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
Conversation
f5582b1
to
0e8dae4
Compare
0e8dae4
to
d697976
Compare
Set the PICO_BOARD_HEADER_DIRS environment variable as per https://github.com/raspberrypi/pico-sdk/blob/master/src/boards/generic_board.cmake Add our local search path alongside the existing Pico SDK boards dir.
3dd98e3
to
1fcde4c
Compare
Move out of the USER_C_MODULES .cmake file.
1fcde4c
to
cce02fe
Compare
be27c84
to
3a35013
Compare
This is getting... somewhere. I couldn't help but come back for another crack at this. The TLDR is- our build setup wasn't exactly robust and up to date, and this should - with any luck - give us a more rational set of steps that aren't against the grain and hard to debug. Mostly-
Given my recent tweaks to C++ code to avoid init RAM allocation (and on-init RAM initialisation I guess) I need to re-benchmark the Pico W startup time for Enviro to see if it's still necessary to include a full wakeup GPIO patch, or if we can move to the leaner, overclock-only version we use for Badger 2040. If it's the latter, the overclock-only patch can just be applied to all builds for the very small, early speedup that it gives prior to proper clock configuration. This hack/patch was originally contrived because MicroPython's Additionally I learned that C++ |
15c1ab2
to
3a35013
Compare
This might be better left until we've removed Cosmic, Galactic and Inky frame builds to their own repositories.
Most of the fixups can probably be replaced with
-DMICROPY_BOARD_DIR
, too. As per - https://github.com/pimoroni/badger2040/blob/main/.github/workflows/micropython.yml