docs: NOMADSTAR_METEOR_PRO likely needs no new board port (#5) - #23
Draft
jamesarich wants to merge 1 commit into
Draft
docs: NOMADSTAR_METEOR_PRO likely needs no new board port (#5)#23jamesarich wants to merge 1 commit into
jamesarich wants to merge 1 commit into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
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
force-pushed
the
docs-nomadstar-meteor-pro
branch
from
August 19, 2026 16:50
ff507a2 to
839e4f4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Issue #5 asked whether
NOMADSTAR_METEOR_PRO(hwModel 96, RAK4631-based) can reusewiscore_rak4631_board's existing bootloader, or needs its ownsrc/boards/entry.Diffed
meshtastic/firmware'svariants/nrf52840/rak4631_nomadstar_meteor_pro/variant.hagainst plainrak4631's. The only differences are peripheral-level, added via a WisBlock IO module:HAS_NCP5623→HAS_LP5562)WB_I2C1_SDA/SCLvs. plainPIN_WIRE_SDA/SCL)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.inieven setsboard = 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 duplicatedwiscore_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
wiscore_rak4631_board's UF2 flashes and boots correctly