Product families
EverTag is one platform with three product lines . They share some hardware and firmware concepts, but documentation and design proposals are organized per product line .
Shared platform ≠ shared product docs
230220 is the GPIO pin-out reference for all nRF54 boards, and the Tag/Anchor firmware build covers 230220 + 232200 + 232201. That does not mean Station and Tag share one proposal document or one overview page. When in doubt, split by product line and cross-link.
Products and article numbers
Product line
PCB articles
Power
Typical docs path
EverTag Station (nRF54)
232200–232204, 232210–232211
Wall (Power Base → 5V)
station/
EverTag Tag nRF54
230220+
Battery
tag-nrf54/
EverTag Tag nRF52 (legacy)
230200, 230202, 230204, 230206
Battery
tag-nrf52/
Article
Product
Role
232200–232204
Station
Connectivity Module base (shared outline, variant BOM)
232210–232211
Station
LTE extension (stacks on base)
232506
Station
Enclosure (mechanical — not a PCB article)
230220
Tag nRF54
Tag base — pin-out reference for nRF54 family
Shared vs product-specific
Topic
Shared across nRF54 family
Product-specific
GPIO pin directions and mux rules
Yes — Firmware Compatibility
Function per variant (ACC on Tag, coex on gateway, …)
PAN611 module
Same module on 230220 and 232200–232204
Layout context (coex pads on gateway, ACC/NFC on Tag)
Tag/Anchor firmware build
230220, 232200, 232201
Gateway build is Station-only (232202+)
ST25DV04K NFC
All nRF54 boards
Antenna coil layout differs Tag vs Station
Rev B1 ECN-01 — GPIO remap
One respin, all six base PCBs
Two proposal entry points (Station full map + Tag summary)
Enclosure mounting (screw / slots)
—
Station only (232200–232204, 232210, 232506)
PAN611 antenna keep-out size
Same datasheet rule (5.0 × 3.25 mm)
Two proposals — verify routing per product
Documentation map
Site navigation (intentional)
Location
What appears
Home sidebar
Product overviews, datasheets, revisions policy — no proposal links
PCB tab
Per-product Proposals subsections
Product overview pages
Design proposals (draft) section with links (Station and Tag)
Design proposal conventions
Frontmatter (required on new proposals)
---
required_role : hw_dev
status : draft
ecn_id : ECN-02 # stable reference — cite as Rev B1 ECN-02
target_revision : B1
product_family : station # station | tag-nrf54 | cross-family
change_type : mechanical # gpio | mechanical | rf-layout | footprint | firmware | other
affects : [ 232200 , 232201 ] # article numbers this proposal applies to
excludes : [ 230220 ] # explicit out-of-scope articles
---
Field
Values
Purpose
ecn_id
e.g. ECN-02
Engineering change number — cite as Rev B1 ECN-02 in email, PO, and release packages
product_family
station, tag-nrf54, cross-family
Primary doc home; cross-family = full technical doc with product-specific summaries elsewhere
change_type
gpio, mechanical, rf-layout, footprint, …
Helps agents pick the right template and reviewers
affects
PCB article list
In scope
excludes
PCB article list
Prevents accidentally documenting Tag changes under Station (or vice versa)
Checklist before writing a proposal
Which product line (Station / Tag nRF54)?
Which article numbers go in affects?
What goes in excludes ?
Does the other product need a separate file with a cross-link?
If both products ship in the same B1 respin — note that in each doc; do not merge scope tables across products unless verification is identical.
Examples (Rev B1)