Skip to content

docs: NOMADSTAR_METEOR_PRO likely needs no new board port (#5) - #23

Draft
jamesarich wants to merge 1 commit into
masterfrom
docs-nomadstar-meteor-pro
Draft

docs: NOMADSTAR_METEOR_PRO likely needs no new board port (#5)#23
jamesarich wants to merge 1 commit into
masterfrom
docs-nomadstar-meteor-pro

Conversation

@jamesarich

Copy link
Copy Markdown
Collaborator

Summary

Issue #5 asked whether NOMADSTAR_METEOR_PRO (hwModel 96, RAK4631-based) can reuse wiscore_rak4631_board's existing bootloader, or needs its own src/boards/ entry.

Diffed meshtastic/firmware's variants/nrf52840/rak4631_nomadstar_meteor_pro/variant.h against plain rak4631's. The only differences are peripheral-level, added via a WisBlock IO module:

  • RGB LED driver chip (HAS_NCP5623HAS_LP5562)
  • Sensor I2C bus addresses (WB_I2C1_SDA/SCL vs. plain PIN_WIRE_SDA/SCL)
  • A buzzer pin, some battery-sense calibration constants, an RTC module

Nothing touches this bootloader's MCU, flash layout, or USB identity — it's the same RAK4631 module underneath, just with more peripherals wired onto the WisBlock header. Its own platformio.ini even sets board = wiscore_rak4631 (the same PlatformIO board definition plain RAK4631 uses).

Changes

  • README.md: notes NomadStar Meteor Pro under the existing RAK4631 note, explaining why it should already work.
  • AGENTS.md: updates the board-gaps gotcha with this finding.

No new src/boards/ entry — opening a board PR that just duplicated wiscore_rak4631_board's files for identical bootloader-relevant hardware would add confusion, not clarity.

Why draft

This is a documented, sourced inference from firmware's variant files, not a hardware confirmation. If someone with this device flashes wiscore_rak4631_board's existing UF2 onto one and confirms it boots correctly, this can come out of draft and #5 can close — referencing that confirmation.

Test plan

  • Docs only, no code/board changes — CI unaffected
  • Real NomadStar Meteor Pro hardware: confirm wiscore_rak4631_board's UF2 flashes and boots correctly

@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 52443885-beed-47ba-a864-6603df42876b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

Diffed meshtastic/firmware's variants/nrf52840/rak4631_nomadstar_meteor_pro
variant.h against plain rak4631's: the only differences are peripheral-level
(RGB LED driver chip - NCP5623 vs LP5562, sensor I2C addresses, a buzzer
pin, battery-sense calibration constants added via a WisBlock IO module).
Nothing touches this bootloader's MCU, flash layout, or USB identity - it's
the same RAK4631 module underneath.

That means wiscore_rak4631_board's existing UF2 should already work on
this hardware unchanged, with no new src/boards/ entry needed. Documenting
this finding in README and AGENTS.md rather than opening a new board PR
that would just duplicate wiscore_rak4631_board's files for no reason -
but it's still unconfirmed on a real device, so not closing #5 yet.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@jamesarich
jamesarich force-pushed the docs-nomadstar-meteor-pro branch from ff507a2 to 839e4f4 Compare August 19, 2026 16:50
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