Hi team,
I'm testing the rpi-pico-blink example using the latest Swift 6.1.2 toolchain on macOS. The compilation works and the .uf2 gets flashed correctly to the Pico, and the program runs as expected after copying the .uf2.
However, once I press the RESET button, the program is no longer running. I have to re-copy the .uf2 file to run it again. It seems like the program is not being stored or executed properly from flash after a reset.
Reproduction steps:
- Build
rpi-pico-blink using the provided Makefile and toolset.
- Copy the generated
.uf2 file to the Pico's storage.
- Observe the program running correctly.
- Press RESET on the board.
- Observe that the program does not run anymore.
Expected behavior:
After RESET, the program should persist and run from flash, like typical firmware does.
Environment:
- Swift: 6.1.2 snapshot toolchain
- Platform: macOS 13.x
- Target: Raspberry Pi Pico (RP2040)
- Toolset: pico.json from the official repo
Notes:
- The issue might be related to how the vector table or entry point is defined.
vmaddr values seem to point to RAM regions (e.g., 0x10000000) instead of flash (0x20000000).
- This could be a misconfiguration in the linker or a section mapping issue.
Let me know if you need logs or a reproducible test case. Thanks for this amazing project!
Best,
Asiel Cabrera
Hi team,
I'm testing the
rpi-pico-blinkexample using the latest Swift 6.1.2 toolchain on macOS. The compilation works and the.uf2gets flashed correctly to the Pico, and the program runs as expected after copying the.uf2.However, once I press the RESET button, the program is no longer running. I have to re-copy the
.uf2file to run it again. It seems like the program is not being stored or executed properly from flash after a reset.Reproduction steps:
rpi-pico-blinkusing the provided Makefile and toolset..uf2file to the Pico's storage.Expected behavior:
After RESET, the program should persist and run from flash, like typical firmware does.
Environment:
Notes:
vmaddrvalues seem to point to RAM regions (e.g.,0x10000000) instead of flash (0x20000000).Let me know if you need logs or a reproducible test case. Thanks for this amazing project!
Best,
Asiel Cabrera