Skip to content

Rpi 5 BCM2712 & Heltec HC01P Support#46

Open
andrewsuggs465 wants to merge 9 commits into
OpenMANET:24.10from
andrewsuggs465:rpi5-support
Open

Rpi 5 BCM2712 & Heltec HC01P Support#46
andrewsuggs465 wants to merge 9 commits into
OpenMANET:24.10from
andrewsuggs465:rpi5-support

Conversation

@andrewsuggs465

Copy link
Copy Markdown

No description provided.

@andrewsuggs465
andrewsuggs465 force-pushed the rpi5-support branch 2 times, most recently from 7ce55d3 to 2dd0c60 Compare April 2, 2026 22:32
@andrewsuggs465 andrewsuggs465 changed the title rpi5 support Rpi 5 Support: BCM2712 & Heltec HC01P Support Apr 2, 2026
@andrewsuggs465 andrewsuggs465 changed the title Rpi 5 Support: BCM2712 & Heltec HC01P Support Rpi 5 BCM2712 & Heltec HC01P Support Apr 2, 2026
@andrewsuggs465

Copy link
Copy Markdown
Author

I forked the repo and the build worked. The previous build, there was an issue with the .patch file I wrote. I've also added Heltec HC01P support.

@coreywagehoft
coreywagehoft self-requested a review April 3, 2026 22:46
@coreywagehoft

Copy link
Copy Markdown
Collaborator

@andrewsuggs465 do you also have a Seeed Studio board and Pi hat?

An unknown here is if your changes to the linux patches would break the existing support for the Seeed Studio board and the Pi4

@andrewsuggs465
andrewsuggs465 force-pushed the rpi5-support branch 2 times, most recently from 12733e1 to dc23da4 Compare April 9, 2026 00:17
andrewsuggs465 and others added 9 commits July 23, 2026 20:31
- Add package/utils/persistent-vars-storage-bcm2712 for RPi5 EEPROM
  storage (mirrors bcm2711 variant with @TARGET_bcm27xx_bcm2712 guard)
- Fix boards/ekh-bcm2712/target_diffconfig: use bcm2712 package instead
  of bcm2711 which has a hard @TARGET_bcm27xx_bcm2711 dependency
- Add .github/workflows/build-pr-bcm2712.yml to CI-validate the new
  board on every PR touching boards/ekh-bcm2712/ or target/linux/bcm27xx/
The openwrt/actions-shared-workflows formal.yml requires pull-requests: write
to post check summaries as PR comments. Without this the caller workflow
fails at startup when triggered from a fork PR.
- Add build-ekh-bcm2712 job using cpu_arch aarch64_cortex-a76
- Add ekh-bcm2712 to needs arrays in publish-packages and release jobs
  so RPi5 firmware is included in official releases
Superseded by build-release.yml which handles the same v* tag trigger
but also builds all firmware, publishes packages, and creates a proper
release with artifacts. Having both caused duplicate competing draft
releases on every tag push.
BCM2712 does not use the VPU start.elf/fixup.dat boot model; the
EEPROM bootloader loads the kernel directly. Copying start4*.elf and
fixup4*.dat into the RPi5 boot partition is unnecessary and diverges
from the stock Device/rpi-5 recipe (boot-common | sdcard-img).
Remove Build/boot-2712 and use boot-common | boot-rpi5-morse instead.
The firmware overlay loader fails the entire overlay if any fragment
target label is unresolvable. Mixing RP1 fragments (&rp1_mmc0,
&rp1_spi0, &rp1_gpio) into the shared mm_wlan/mm610x-spi/mm810x-spi
overlays would therefore break overlay application on Pi 3/4 and
Seeed boards, which lack those labels.

- Restore 991-0001 and 991-0003 to their upstream (Pi 1-4 only) form
- Add 991-0008 creating mm_wlan-pi5, mm610x-spi-pi5, mm810x-spi-pi5
  overlays with the RP1 fragments
- Register the -pi5 dtbos in the overlays Makefile patch
- Point the rpi5 distroconfig files at the -pi5 overlay names and add
  missing trailing newlines (boot-rpi5-morse concatenates these files;
  a missing final newline merged two config lines into one)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants