Seeed Studio XIAO nrf52-based boards modularization

[ndoo]

• env:seeed_xiao_nrf52840_kit
  • Define user button (PIN_BUTTON1) -> GPIO D0 (physical button on the Wio-SX1262 for XIAO is wired to GPIO D0)
  • As a compromise, remove L76K GNSS module feature (pin conflict with PIN_BUTTON1)
• env:seeed_xiao_nrf52840_wio-sx1262_v1_1 (DIY)
  • board_level = extra
  • XIAO ESP32S3 & Wio-SX1262 Kit ships with this PCB (i.e. you DIY and swapped that Wio-SX1262 to a XIAO-nRF52480)
  • Define user button (PIN_BUTTON1) -> GPIO D4 (physical button on the Wio-SX1262 for XIAO PCB v1.1
  • I2C defined for feature parity with removed diy/seeed-xiao-nrf52840-wio-sx1262 variant
• env:seeed_xiao_nrf52840_kit_l76k (DIY)
  • board_level = extra
  • XIAO L76K GNSS module support
  • As a compromise, remove user button feature (pin conflict with PIN_GPS_STANDBY)
• env:seeed_xiao_nrf52840_kit_i2c (DIY)
  • board_level = extra
  • Define D6 -> SDA, D7 -> SCL
• env:seeed_xiao_nrf52840_kit_oled (DIY)
  • board_level = extra
  • Define D6 -> SDA, D7 -> SCL and USE_SSD1306
• env:seeed-xiao-nrf52840-wio-sx1262 (DIY)
  • Removed as it is superseded by env:seeed_xiao_nrf52840_wio-sx1262_v1_1

🤝 Attestations

• I have tested that my proposed changes behave as described.
• I have tested that my proposed changes do not cause any obvious regressions on the following devices:
  • Heltec (Lora32) V3
  • LilyGo T-Deck
  • LilyGo T-Beam
  • RAK WisBlock 4631
  • Seeed Studio T-1000E tracker card
  • Other (please specify below)
    • env:seeed_xiao_nrf52840_kit
    • env:seeed_xiao_nrf52840_kit_i2c
    • env:seeed_xiao_nrf52840_kit_oled

[fifieldt]

Thanks for putting so much thought into this

[ndoo]

Based on suggestions on Discord#nrf52, moved the DIY (board_level = extra) boards into DIY and inherited the environments from the non-DIY XIAO.

It may be a bit more confusing since all the pin logic is in the variant.h of another folder, but I added a comment to variants/diy/platformio.ini that directs devs to that variant.h.

Either approach of (a) having all the extra build envs in the official variant or (b) having all the extra build envs in DIY is fine by me, up to the maintainers to decide which is preferable.

[ndoo]

Hm, an unintended consequence of deriving everything from the officially supported board is that they will show up with the supported hardware model over the mesh instead of unsupported hardware. Is that okay?

If not, I will add -DPRIVATE_HW to the DIY environments.

[porkcube]

seeed-xiao-nrf52840-wio-sx1262 (DIY) isn't just a user button difference, the original ESP32 Kit Wio (PCB v1.1) and nRF52840 Kit Wio (PCB v1.0) have a few more pins that are jumbled. Checked our your branch and confirmed that env:seeed_xiao_nrf52840_kit and seeed_xiao_nrf52840_kit_i2c build cleanly but don't actually work as result in NOTE! Record critical error 3 at src/main.cpp:1281

Pin	DIY	New
CS	D3	D4
DIO1	D0	D1
BUSY	D1	D3

[ndoo]

seeed-xiao-nrf52840-wio-sx1262 (DIY) isn't just a user button difference, the original ESP32 Kit Wio (PCB v1.1) and nRF52840 Kit Wio (PCB v1.0) have a few more pins that are jumbled. Checked our your branch and confirmed that env:seeed_xiao_nrf52840_kit and seeed_xiao_nrf52840_kit_i2c build cleanly but don't actually work as result in NOTE! Record critical error 3 at src/main.cpp:1281

Pin DIY New
CS D3 D4
DIO1 D0 D1
BUSY D1 D3

I shall add a variant in to cover the old PCB use case, but what's a good name for the env section?

[porkcube]

That is a very good question! Perhaps something that explicates it's DIY or the PCB rev ala seeed-xiao-nrf52840-wio-sx1262_DIY or seeed-xiao-nrf52840-wio-sx1262_v1.0 / seeed-xiao-nrf52840-wio-sx1262_v1.1 ?

[ndoo]

That is a very good question! Perhaps something that explicates it's DIY or the PCB rev ala seeed-xiao-nrf52840-wio-sx1262_DIY or seeed-xiao-nrf52840-wio-sx1262_v1.0 / seeed-xiao-nrf52840-wio-sx1262_v1.1 ?

Good idea. I won't touch the original env name for the nrf kit, but the seeed-xiao-nrf52840-wio-sx1262_v1.1 name sounds good.

seeed-xiao-nrf52840-wio-sx1262 (DIY) isn't just a user button difference, the original ESP32 Kit Wio (PCB v1.1) and nRF52840 Kit Wio (PCB v1.0) have a few more pins that are jumbled. Checked our your branch and confirmed that env:seeed_xiao_nrf52840_kit and seeed_xiao_nrf52840_kit_i2c build cleanly but don't actually work as result in NOTE! Record critical error 3 at src/main.cpp:1281

Pin DIY New
CS D3 D4
DIO1 D0 D1
BUSY D1 D3

Oh yes, I noticed the diy/seeed-xiao-nrf52840-wio-sx1262 variant had this defined:
#define SX126X_RXEN 38

Is that actually valid?

[porkcube]

That is a very good question! Perhaps something that explicates it's DIY or the PCB rev ala seeed-xiao-nrf52840-wio-sx1262_DIY or seeed-xiao-nrf52840-wio-sx1262_v1.0 / seeed-xiao-nrf52840-wio-sx1262_v1.1 ?

Good idea. I won't touch the original env name for the nrf kit, but the seeed-xiao-nrf52840-wio-sx1262_v1.1 name sounds good.

v1.0 is the nRF Kit version so should work with the "official" Kit firmware, it's just the v1.1 PCB from the ESP32 Kit + your own Xiao nRF52840 that the DIY firmware was built for (because I couldn't wait for Seeed's official kit)

seeed-xiao-nrf52840-wio-sx1262 (DIY) isn't just a user button difference, the original ESP32 Kit Wio (PCB v1.1) and nRF52840 Kit Wio (PCB v1.0) have a few more pins that are jumbled. Checked our your branch and confirmed that env:seeed_xiao_nrf52840_kit and seeed_xiao_nrf52840_kit_i2c build cleanly but don't actually work as result in NOTE! Record critical error 3 at src/main.cpp:1281
Pin DIY New
CS D3 D4
DIO1 D0 D1
BUSY D1 D3

Oh yes, I noticed the diy/seeed-xiao-nrf52840-wio-sx1262 variant had this defined: #define SX126X_RXEN 38

Is that actually valid?

38 should be valid... it just seems to not also be in the variant.cpp to have a D# labelling

[ndoo]

@porkcube please test this commit -> env:seeed_xiao_nrf52840_wio-sx1262_v1_1

I believe it should be feature/pinout parity with the removed variant.

[ndoo]

Summary updated to reflect the changes since.

[porkcube]

@ndoo Confirming seeed_xiao_nrf52840_wio-sx1262_v1_1 works as expected (node boots up fine, and user button detected).

Thank you so much for cleaning up the variant mess and for the Ikokas!

[ndoo]

That’s a relief. As long as there’s no regression I hope these variants are useful to the community. If this gets merged I actually have a local branch which adds a bunch of E22 variants …

…

On Mon, May 12, 2025 at 02:23 porkcube ***@***.***> wrote: *porkcube* left a comment (meshtastic/firmware#6788) <#6788 (comment)> @ndoo <https://github.com/ndoo> Confirming seeed_xiao_nrf52840_wio-sx1262_v1_1 works as expected (node boots up fine, and user button detected). Thank you so much for cleaning up the variant mess and for the Ikokas! — Reply to this email directly, view it on GitHub <#6788 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACAFACMTTZKM5BD5NY4OKL256ITZAVCNFSM6AAAAAB43UT4Y6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZQGAZTQOBRGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[garthvh]

Hm, an unintended consequence of deriving everything from the officially supported board is that they will show up with the supported hardware model over the mesh instead of unsupported hardware. Is that okay?

If not, I will add -DPRIVATE_HW to the DIY environments.

The diy variants need to be properly labeled as diy

[ndoo]

Hm, an unintended consequence of deriving everything from the officially supported board is that they will show up with the supported hardware model over the mesh instead of unsupported hardware. Is that okay?
If not, I will add -DPRIVATE_HW to the DIY environments.

The diy variants need to be properly labeled as diy

Rebased on master and done as requested, build tested.

[ndoo]

Squashed commits for readability

[ndoo]

Converting to draft to make some smaller incremental PRs instead.

[ndoo]

Closing PR in favor of piecemeal DIY variant additions.