rp2350-riscv: add RISC-V integration test and CI build - #1
Conversation
CMRX now has a working RISC-V port for the RP2350's Hazard3 cores, but this repo has no way to verify it keeps building. Add rp2350-pico-sdk-riscv/, a build-only project mirroring the existing rp2040-pico-sdk layout: a minimal hello_world application and a Pico SDK-based timing provider for CMRX's scheduler. Assisted-by: Claude Signed-off-by: Tobias Aguiar <tobi.aguiar01@gmail.com>
Wire rp2350-pico-sdk-riscv into GitHub Actions so it gets a build-only check on every push, alongside the existing stm32h7 job. There's no ready-made GitHub Action for the RISC-V toolchain this target needs, so the workflow fetches it directly from its official release. Assisted-by: Claude Signed-off-by: Tobias Aguiar <tobi.aguiar01@gmail.com>
|
Test project looks good. Just the correct place for the GitHub action is the main repository. That's the easiest way to launch CI always with newest kernel when commit to kernel master branch is made. I must have forgot to remove this H7 action from this repository. Actions there are a bit more complicated as now they also involve MemBrowse workflow |
I see, I thought I would need to add a PR here first so then I could open a PR for the actions changes in cmrx. I have its changes locally ready, will open a PR there. |
|
PR open : ventZl/cmrx#159 |
|
I'll remove actions later so nobody will be confused by their presence. |
2 participants
CMRX now has a working RISC-V port for the RP2350's Hazard3 cores, but
this repo has no way to verify it keeps building. This adds a build-only
integration test for it, alongside the existing stm32h7 and rp2040
platforms.
rp2350-pico-sdk-riscv/: a minimal hello_world application and a Pico
SDK-based timing provider for CMRX's scheduler, mirroring the existing
rp2040-pico-sdk layout.
.github/workflows/integration-build-riscv.yml: builds it on every push,
next to the existing stm32h7 job. There's no ready-made GitHub Action
for the RISC-V toolchain this target needs, so the workflow fetches it
directly from its official raspberrypi/pico-sdk-tools release.
Like the stm32h7 job, the build step is non-gating (continue-on-error)
while the RISC-V port is still stabilizing.