Skip to content

Register the Heltec RC32, RC52, and RCC6 in the device registry - #130

Merged
rcarteraz merged 3 commits into
masterfrom
device-registry/heltec-rc32-rc52-rcc6
Aug 27, 2026
Merged

Register the Heltec RC32, RC52, and RCC6 in the device registry#130
rcarteraz merged 3 commits into
masterfrom
device-registry/heltec-rc32-rc52-rcc6

Conversation

@rcarteraz

@rcarteraz rcarteraz commented Aug 22, 2026

Copy link
Copy Markdown
Member

Adds deviceHardware entries for three Heltec boards, filling the 141-143 gap
between MESHNOLOGY_W10 and SEEED_WIO_TRACKER_L1_PRO_1W.

hwModel Slug platformioTarget Architecture Firmware PR
141 HELTEC_RC32 heltec-rc32 esp32-s3 meshtastic/firmware#10876
142 HELTEC_RC52 heltec-rc52 nrf52840 meshtastic/firmware#11249
143 HELTEC_RCC6 heltec-rcc6 esp32-c6 meshtastic/firmware#11041

Field values come from each variant's custom_meshtastic_* block in the
firmware repo. The hwModels and slugs match the reserved HardwareModel enum
values in protobufs master.

Also maps the RC52's SoftDevice variant in bootloaderOtaQuirks.json as
6.1.1, per the s140 / sd_version 6.1.1 its firmware board definition
declares.

🤖 Generated with Claude Code

Adds deviceHardware entries for the three Heltec boards whose hardware
models are already reserved in the protobufs HardwareModel enum but which
have no registry entry yet, so 141-143 were a gap between MESHNOLOGY_W10
and SEEED_WIO_TRACKER_L1_PRO_1W.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 22, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 034b94a7-dab8-4754-8a0c-0fa572211728

📥 Commits

Reviewing files that changed from the base of the PR and between 69772f5 and dd88dac.

📒 Files selected for processing (1)
  • src/lib/resource.ts

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

Added unsupported Heltec RC32, RC52, and RCC6 entries to deviceHardwareList. The entries define hardware platforms, architectures, display metadata, images, DFU requirements, partition schemes, and support levels.

Changes

Heltec hardware support metadata

Layer / File(s) Summary
Add Heltec hardware entries
src/lib/resource.ts
Adds metadata for RC32, RC52, and RCC6. The entries specify platform targets, architectures, display details, images, DFU requirements, partition schemes, and unsupported support level 1.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to dd88d

This additive registry change is merge-ready after normal checks and review; no actionable merge-blocking risk remains.

Suggested reviewers: thebentern, caveman99, copilot

Poem

A rabbit checked the device list bright
Three Heltec entries joined the night
RC32, RC52, RCC6 in a row
With their hardware details set to show
Metadata hops clean and light

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: registering the three Heltec boards in the device registry.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files.

✨ Finishing Touches 💡 1
⚔️ Resolve merge conflicts 💡
  • Resolve merge conflict in branch device-registry/heltec-rc32-rc52-rcc6

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@rcarteraz
rcarteraz marked this pull request as ready for review August 27, 2026 05:36
rcarteraz and others added 2 commits August 26, 2026 22:40
Resolves a conflict in the device hardware list: the Meshnology W12 entry
added on master landed at the same insertion point as the Heltec RC32/RC52/
RCC6 entries, and git aligned the two objects on their shared trailing
requiresDfu/partitionScheme fields. Both sides are kept - 141-143 sit in
numeric order after MESHNOLOGY_W10, and W12 keeps its position ahead of
SEEED_WIO_TRACKER_L1_PRO_1W.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
RC52 is the only nRF52840 board in this set, and softDeviceVariants fails
closed - an absent entry is a refusal, so without this a client cannot
resolve the device at all. Its firmware board definition declares s140
6.1.1 (sd_fwid 0x00B6), corroborated by its nrf52840_s140_v6.ld ldscript
and consistent with every other Heltec nRF52840 entry here; the 7.3.0
entries are all Seeed/Nordic-family boards.

Slotted in hwModel order between HELTEC_MESH_TOWER_V2 and
SEEED_WIO_TRACKER_L1_PRO_1W. No `devices` entry: that array is the
"upgrade your bootloader before OTA" advisory and applies to boards that
shipped without OTA-capable bootloaders, which does not describe a new board.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@rcarteraz
rcarteraz merged commit 77dc788 into master Aug 27, 2026
4 checks passed
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.

1 participant