This repository was archived by the owner on Dec 23, 2025. It is now read-only.
Raspberry Pi Pico W, Fix build Issues, Configure SD Filesystem, Fix Del key functionality. #1195
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…es/2048/Makefile.common - Added FUZIX_ROOT include path for Pico builds - Moved optimization flag to preserve platform-specific CFLAGS - Prevents missing header errors on rpipico target
…armm0 - The ROOT variable was not defined, causing include/lib/linker paths to fail - Replaced all occurrences of $(ROOT) with $(FUZIX_ROOT) - Ensures absolute paths to Library includes, libs, and linker scripts are correct for all builds
- Move -lgcc to end of linker options in Makefile.common to resolve missing __aeabi_* symbols - Define LINKER_TAIL = -lgcc in Target/rules.armm0 with explanatory comment - Ensures Cortex-M0 runtime helpers are linked for integer division and compiler-generated routines
- Added LINKER_TAIL to include libgcc, libcarmm0, and termcap library - Fixes undefined reference errors for __aeabi_* and __gnu_thumb1_case_* functions - Ensures proper linking order for Cortex-M0+ target applications
… configure del key functionality
Owner
|
Thanks but the project (like all my projects) has moved to codeberg. I do need to go hit the archive button them all to make it more obvious |
Author
|
Well that was a considerable waste of time then.This was the first time I have contributed to a github project so the learning curve was steep to say the least.I tried to create a codeberg account but the verification process fails because my browser generated a strong password but didn’t tell me what it is.I’ll wait a day or two until it times out and I’ll try again.Maybe I’ll be able to resubmit my changes.On 26 Nov 2025, at 9:43 AM, EtchedPixels ***@***.***> wrote:EtchedPixels left a comment (EtchedPixels/FUZIX#1195)
Thanks but the project (like all my projects) has moved to codeberg. I do need to go hit the archive button them all to make it more obvious
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Owner
|
I think I can fish it out from github and apply it on Codeberg. Will see what I can do but currently a bit busy. |
Author
|
What is the URL for Fuxiz on Codeburg.I’ve been chatting with ChatGPT to figure out how I could make the change over to Codeburg without wiping out my changes. It’s literally only a few lines in a couple of files. But it’s the difference between a successful pico compile or not.ThanksDavidSent from my iPadOn 27 Nov 2025, at 9:02 AM, EtchedPixels ***@***.***> wrote:EtchedPixels left a comment (EtchedPixels/FUZIX#1195)
I think I can fish it out from github and apply it on Codeberg. Will see what I can do but currently a bit busy.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Author
|
Don’t worry I found it. I’ll have a go and creating a new pull request.Your time is probably better spent considering if the changes fit correctly into the project. ThanksDavidOn 27 Nov 2025, at 4:46 PM, David Pollard ***@***.***> wrote:What is the URL for Fuxiz on Codeburg.I’ve been chatting with ChatGPT to figure out how I could make the change over to Codeburg without wiping out my changes. It’s literally only a few lines in a couple of files. But it’s the difference between a successful pico compile or not.ThanksDavidSent from my iPadOn 27 Nov 2025, at 9:02 AM, EtchedPixels ***@***.***> wrote:EtchedPixels left a comment (EtchedPixels/FUZIX#1195)
I think I can fish it out from github and apply it on Codeberg. Will see what I can do but currently a bit busy.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR configures the SD filesystem as the new default for the pico. Previously this was set to the NAND Flash storage and this is reportedly flaky or simply not working. I could not get the filesystem to load from flash at all. The SD card worked like a breeze.
There are also several minor changes to the build configuration that was causing the process to fail. These changes allow the build process to complete successfully.
Testing was performed on the Raspberry Pi Pico W with a SD card connected to the default GPIO pins and a terminal (picoterm) connected via the usb port.
The del key now functions correctly from configuration in the added .profile.
These changes are entirely contained within the raspberry pi pico code base and no other platforms are affected.
The existing Pico README.md states that the root filesystem is stored in internal flash.
However, in current builds the flash-based block device no longer mounts reliably.
The SD-card block device mounts successfully and provides a stable root filesystem.
This PR updates the Pico configuration to mount hdb1 as the root device (SD card), which reflects the only storage configuration currently working consistently in testing.
PS including .gitignore is my mistake. I can't figure out how to remove it, please discard it.