Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
jamesarich wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 14 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,9 +162,20 @@ itself; a human has to edit it too.
that pattern, don't replace the file.
- **Board gaps are tracked as issues, not guessed at.** `Meshtastic-Android`
flags `NANO_G2_ULTRA` and `NOMADSTAR_METEOR_PRO` as needing bootloader
upgrade support with no board here yet (issues #4, #5) — bringing up a
new board needs real hardware to get `UF2_BOARD_ID`/VID-PID/pin defs
right; don't fabricate a `board.h` without one.
upgrade support (issues #4, #5). Neither is hardware-confirmed yet:
- `NOMADSTAR_METEOR_PRO` is RAK4631-based; diffing its firmware variant
against plain `rak4631`'s shows only peripheral-level differences (RGB
LED driver chip, sensor I2C, buzzer) — nothing this bootloader touches.
Likely needs **no new `src/boards` entry at all**, just confirmation
that `wiscore_rak4631_board`'s existing UF2 flashes and boots on one
(see the [README's RAK4631 note](./README.md#notes-on-rak4631-bootloader)).
- `NANO_G2_ULTRA` needs a genuinely new board — bringing one up requires
real hardware to get `UF2_BOARD_ID`/VID-PID/pin defs right; don't
fabricate a `board.h` without at least sourcing every field from
somewhere real (`meshtastic/firmware`'s own variant files, the
vendor's PlatformIO board manifest, etc.) and flagging clearly what's
still unconfirmed.
Don't close either issue without an actual hardware test.
- **`CURRENT.UF2` dump-and-restore used to hang the device — fixed in #20,
don't reintroduce it.** Root cause: `CURRENT.UF2` was sized off the max
possible app region (`TRUE_USER_FLASH_SIZE`) instead of the real
Expand Down
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ bootloader and SoftDevice zip package").
- Minewsemi MX25LE01
- Nologo ProMicro NRF52840 (aka SuperMini NRF52840)
- RAK 3401
- RAK 4631 ([See note](#notes-on-rak4631-bootloader))
- RAK 4631 ([See note](#notes-on-rak4631-bootloader)) — also covers NomadStar Meteor Pro, see the same note
- RAK WisMesh Tag
- Seeed Studio SenseCAP Card Tracker T1000-E
- Seeed SenseCAP Solar Node P1
Expand Down Expand Up @@ -221,6 +221,8 @@ If the file shows: "Board-ID: nRF52840-SeeedXiaoSense-v1" then the ***SENSE*** v

This version of the RAK4631 bootloader is based on a much newer version (0.9.2) of the Adafruit nRF52 bootloader than what RAK Wireless uses on their official bootloader (0.6.2-11). It has been tested with no problems found; whether RAK's own patches to the Adafruit bootloader introduce any behavioral difference has not been investigated. A variant of the official RAK bootloader with these patches included instead is available [here](https://github.com/oltaco/WisCore_RAK4631_Bootloader/releases).

**NomadStar Meteor Pro** is RAK4631-based hardware with an added RGBW LED and e-ink display bolted on via a WisBlock IO module. Diffing its [firmware variant](https://github.com/meshtastic/firmware/tree/master/variants/nrf52840/rak4631_nomadstar_meteor_pro) against plain RAK4631's shows only peripheral-level differences (the RGB LED driver chip, sensor I2C addresses, a buzzer pin, battery-sense calibration) — nothing this bootloader's MCU/flash/USB identity touches. It should be able to use this same RAK4631 UF2 unchanged, but **this has not been confirmed on real hardware** — if you have one, please try flashing it and report back on [issue #5](https://github.com/meshtastic/Adafruit_nRF52_Bootloader_OTAFIX/issues/5).

---

## Contributing
Expand Down