Skip to content

Ci rp2 riscv ghactions membrowse - #159

Open
tobiaguiar08 wants to merge 4 commits into
ventZl:masterfrom
tobiaguiar08:ci_rp2_riscv_ghactions_membrowse
Open

Ci rp2 riscv ghactions membrowse#159
tobiaguiar08 wants to merge 4 commits into
ventZl:masterfrom
tobiaguiar08:ci_rp2_riscv_ghactions_membrowse

Conversation

@tobiaguiar08

Copy link
Copy Markdown
Contributor

Summary

Add GitHub Actions CI workflow and MemBrowse configuration for RP2350 RISC-V builds, mirroring the existing ARM platform support (rp2040, stm32g4/h7).

Changes

1. New build workflow (.github/workflows/rp2350-riscv-build.yml)

  • Automated build of the RP2350 RISC-V integration test project
  • Uses RISC-V toolchain from pico-sdk-tools (v2.3.0-1)
  • Configures for Hazard3 core and RP2350 memory layout
  • Includes inline MemBrowse analysis with real RP2350 memory regions (2MB flash @ 0x10000000, 512KB RAM @ 0x20000000)
  • Triggers on push to master and pull_request (same as rp2040)

2. MemBrowse matrix entry (.github/membrowse-targets.json)

  • Registers rp2350-riscv target for manual MemBrowse analysis via workflow_dispatch
  • Artifact paths match the primary build workflow
  • Build command includes same configure flags and memory region generation

3. Updated onboard workflow (.github/workflows/membrowse-onboard.yml)

  • Narrows ARM toolchain condition to exclude rp2350-riscv
  • Adds RISC-V toolchain installation step (curl, extract, PATH setup)
  • Makes Pico SDK checkout path matrix-driven so each target checks out to correct location
    • rp2040 → _integ/rp2040-pico-sdk/pico-sdk
    • rp2350-riscv → _integ/rp2350-pico-sdk-riscv/pico-sdk

4. README CI badge

  • Adds RP2350 RISC-V build-status badge alongside existing platform badges

@ventZl

ventZl commented Aug 20, 2026

Copy link
Copy Markdown
Owner

It seems that rp2350-riscv job needs to pass toolchain path as CMake argument. That should do the job and fix the failure.

Creates a GitHub Actions workflow for automated building of the RP2350
RISC-V integration test project, mirroring the rp2040 workflow but using
the RISC-V toolchain from pico-sdk-tools and configuring for the Hazard3
core.

Assisted-by: Claude
Signed-off-by: Tobias Aguiar <tobi.aguiar01@gmail.com>
Register the RP2350 RISC-V target in membrowse-targets.json so it can be
invoked manually via the membrowse-onboard workflow. Includes build
command with the RISC-V configure flags, memory region generation, and
artifact paths matching the primary build workflow.

Assisted-by: Claude
Signed-off-by: Tobias Aguiar <tobi.aguiar01@gmail.com>
Extend the MemBrowse dispatcher workflow to handle RP2350 RISC-V builds:
- Narrow ARM toolchain condition to exclude rp2350-riscv
- Add new RISC-V toolchain installation step (curl v2.3.0-1, extract to
PATH)
- Gate Pico SDK checkout to rp2040 and rp2350-riscv, with matrix-driven
path so each target checks out to the correct integration project
directory

Assisted-by: Claude
Signed-off-by: Tobias Aguiar <tobi.aguiar01@gmail.com>
Add a build-status badge for the rp2350-riscv workflow to the top-level
README, consistent with existing build badges for other platforms
(rp2040, stm32g4, stm32h7, linux). Give users and developers visibility
into the RISC-V port's CI status.

Assisted-by: Claude
Signed-off-by: Tobias Aguiar <tobi.aguiar01@gmail.com>
@tobiaguiar08
tobiaguiar08 force-pushed the ci_rp2_riscv_ghactions_membrowse branch from b1214c3 to ccae332 Compare August 21, 2026 05:40
@tobiaguiar08

Copy link
Copy Markdown
Contributor Author

It seems that rp2350-riscv job needs to pass toolchain path as CMake argument. That should do the job and fix the failure.

Done, not sure I added in the correct places though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants