Pin Grouping and Datasheet Review
Fix the pin-number mismatches for pins 17–65, then verify the symbol and footprint mapping.
Thought for 5 sec
I’ll correct the BT840NE terminal Pin Number assignments for pins 17–65 from the datasheet, then re-read the symbol and footprint to verify the mapping.
Worked for 1 min 10 sec
Done — I corrected the BT840NE Pin Number properties for pins 17–65 to match the Fanstel datasheet and verified the schematic mapping afterward.
Open items:
- The footprint pad list uses the same signal/designator names as the corrected symbol terminals, so the symbol-to-footprint mapping is now consistent by terminal name.
- The layout inspection still does not expose pad geometry or numeric pad labels, so mechanical land-pattern geometry remains unverified.
Suggested next steps:
- Verify the physical footprint dimensions against Fanstel’s recommended land pattern/Gerbers.
- Optionally update the Datasheet URL to the latest official Fanstel PDF.
Update, verify and document
Update Datasheet URL
Verify footprint geometry
Run design checks
Update review document
Refine this doc
Ask about this doc
BT840NE Part Review
Sources
- Existing Datasheet URL property:
https://storage.googleapis.com/graviton-electric-symbols/document_assets/user-uploaded/56de5a6915f15a7a55577e7fd14fdb76238cd3a88c689b4972911e9e38b3f03e.pdf— Fanstel BT840/F/E/N/NE product specifications, OCR identified as Ver. 1.27, July 2024. - Official latest Fanstel PDF found on web:
https://www.fanstel.com/s/BT840F_BT840N-Product-Specifications-fhfk.pdf— Fanstel BT840/F/E/N/NE product specifications, Ver. 1.28, Mar. 2026.
The part already had a Datasheet URL property, so I did not replace it under the original instruction. The official latest URL above should be considered for updating if you want the part to track Fanstel’s current PDF directly.
Project metadata reviewed
Table
| Field | Current project value | Datasheet / official source check |
|---|---|---|
| MPN | BT840NE | Matches |
| Manufacturer | Fanstel | Matches |
| Description | 802.15.4, Bluetooth v5.3, Zigbee transceiver module, PCB trace/U.FL, 1.7–5.5 V, -40 to 85 C | Broadly matches; datasheet also notes nRF52840 + nRF21540 PA, integrated 32.768 kHz crystal, PCB antenna + U.FL |
| Package / case | Module | Matches at a high level |
| Mount | Surface Mount | Matches |
| Pin / pad count | 65 schematic terminals and 65 PCB pads | Matches datasheet’s 65 sequential pads/pin positions |
| Module size | Not explicitly captured in project properties | Datasheet: 15 × 29.9 × 1.9 mm |
| Operating voltage | Description says 1.7–5.5 V | Datasheet summary says 1.7–5.5 V general; VDD pin specifically 1.7–3.6 V; BT840N/NE max TX requires externally regulated VDD = 3.3 V, 300 mA minimum |
| Operating temperature | -40 C to +85 C | Matches |
Key specs
- Nordic nRF52840-QIAA F or newer, Arm Cortex-M4F, 64 MHz.
- 1 MB flash, 256 KB RAM.
- Integrated Nordic nRF21540 power amplifier.
- BLE 5.3 / Thread / Zigbee / IEEE 802.15.4 support.
- 2.4 GHz radio; Bluetooth LE data rates include 2 Mbps, 1 Mbps, 500 kbps, 125 kbps.
- Integrated 32.768 kHz sleep crystal.
- PCB antenna plus U.FL connector for external antenna.
- BT840NE max radiated TX listed as +27 dBm.
- FCC/ISED max TX certification supply condition: VDD = 3.3 V, 300 mA minimum, externally regulated.
Pin grouping applied
Each schematic terminal was assigned exactly one
Pin Group, based on primary/common function. No physical pin was intentionally assigned to more than one group.Table
| Group | Pins / terminals |
|---|---|
| Power | VDD, VDDH, VBUS, DCCH |
| Ground | GND_1, GND_2, GND_3, GND_4, GND_5, GROUND_1, GROUND_2, GROUND_3, GROUND_4 |
| USB | D+, D- |
| Debug | SWDCLK, SWDIO |
| I2C GPIO | P0.26/SDA, P0.27/SCL |
| NFC | P0.09/NFC1, P0.10/NFC2 |
| Clock GPIO | P0.00/XL1, P0.01/XL2 |
| Reset GPIO | P0.18/RESET |
| Analog GPIO | P0.02/AIN0, P0.03/AIN1, P0.04/AIN2, P0.05/AIN3, P0.28/AIN4, P0.29/AIN5, P0.30/AIN6, P0.31/AIN7 |
| PA Control GPIO | P1.06, P1.08, P0.22, P1.04, P0.23, P0.19, P1.07, P0.20, P0.21, plus PA-control-related P0.06/P0.08/P0.17 notes from datasheet |
| General GPIO | Remaining GPIO terminals: P0.07, P0.11, P0.12, P0.13, P0.14, P0.15, P0.16, P0.24, P0.25, P1.00, P1.01, P1.02, P1.03, P1.05, P1.09, P1.10, P1.11, P1.12, P1.13, P1.14, P1.15 |
Pinout cross-check
Pins 1–16 match the datasheet by terminal name and pin number. From pin 17 onward, the schematic symbol appears substantially mis-numbered relative to the datasheet pin assignment table.
Table
| Pin # | Schematic terminal | Datasheet terminal | Status |
|---|---|---|---|
| 1 | P0.26/SDA | P0.26/SDA | OK |
| 2 | P0.27/SCL | P0.27/SCL | OK |
| 3 | P0.00/XL1 | P0.00/XL1 | OK |
| 4 | P0.01/XL2 | P0.01/XL2 | OK |
| 5 | P0.02/AIN0 | P0.02/AIN0 | OK |
| 6 | P0.03/AIN1 | P0.03/AIN1 | OK |
| 7 | P0.09/NFC1 | P0.09/NFC1 | OK |
| 8 | P0.10/NFC2 | P0.10/NFC2 | OK |
| 9 | VDD | VDD | OK |
| 10 | GND_1 | GND | OK |
| 11 | P0.11 | P0.11 | OK |
| 12 | P1.00 | P1.00 | OK |
| 13 | P0.13 | P0.13 | OK |
| 14 | P0.18/RESET | P0.18/RESET | OK |
| 15 | SWDCLK | SWDCLK | OK |
| 16 | SWDIO | SWDIO | OK |
| 17 | GND_2 | P1.11 | MISMATCH |
| 18 | P0.28/AIN4 | P1.12 | MISMATCH |
| 19 | P0.29/AIN5 | P1.13 | MISMATCH |
| 20 | P0.04/AIN2 | P1.14 | MISMATCH |
| 21 | P0.05/AIN3 | P1.15 | MISMATCH |
| 22 | P0.07 | P1.10 | MISMATCH |
| 23 | P1.08 | P1.06 | MISMATCH |
| 24 | GND_3 | GND | OK |
| 25 | P0.25 | P0.28/AIN4 | MISMATCH |
| 26 | P0.30/AIN6 | P0.29/AIN5 | MISMATCH |
| 27 | P0.31/AIN7 | P0.04/AIN2 | MISMATCH |
| 28 | P0.06 | P0.05/AIN3 | MISMATCH |
| 29 | P0.08 | P0.07 | MISMATCH |
| 30 | P1.03 | P1.08 | MISMATCH |
| 31 | GND_4 | GND | OK |
| 32 | P0.24 | P0.25 | MISMATCH |
| 33 | P0.22 | P0.30/AIN6 | MISMATCH |
| 34 | P0.17 | P0.31/AIN7 | MISMATCH |
| 35 | P0.15 | P0.06 | MISMATCH |
| 36 | P1.02 | P0.08 | MISMATCH |
| 37 | P1.04 | P1.03 | MISMATCH |
| 38 | GND_5 | GND | OK |
| 39 | P0.23 | P0.24 | MISMATCH |
| 40 | P0.19 | P0.22 | MISMATCH |
| 41 | P0.16 | P0.17 | MISMATCH |
| 42 | P0.14 | P0.15 | MISMATCH |
| 43 | P1.01 | P1.02 | MISMATCH |
| 44 | P1.05 | P1.04 | MISMATCH |
| 45 | P1.07 | GND | MISMATCH |
| 46 | P0.20 | P0.23 | MISMATCH |
| 47 | P0.21 | P0.19 | MISMATCH |
| 48 | P1.09 | P0.16 | MISMATCH |
| 49 | D+ | P0.14 | MISMATCH |
| 50 | D- | P1.01 | MISMATCH |
| 51 | P0.12 | P1.05 | MISMATCH |
| 52 | GROUND_1 | P1.07 | MISMATCH |
| 53 | GROUND_2 | P0.20 | MISMATCH |
| 54 | GROUND_3 | P0.21 | MISMATCH |
| 55 | GROUND_4 | P1.09 | MISMATCH |
| 56 | VDDH | D+ | MISMATCH |
| 57 | DCCH | D- | MISMATCH |
| 58 | VBUS | P0.12 | MISMATCH |
| 59 | P1.11 | Ground pad | MISMATCH |
| 60 | P1.12 | Ground pad | MISMATCH |
| 61 | P1.13 | Ground pad | MISMATCH |
| 62 | P1.14 | Ground pad | MISMATCH |
| 63 | P1.15 | VDDH | MISMATCH |
| 64 | P1.10 | DCCH | MISMATCH |
| 65 | P1.06 | VBUS | MISMATCH |
Footprint cross-check
- Pad count matches the datasheet total of 65.
- Pad designators in the footprint mirror the current schematic terminal designators, so the footprint inherits the same pin-number/terminal-name mismatches listed above.
- The inspected footprint data did not expose pad geometry, package outline dimensions, or land-pattern measurements, so I could not verify the 15 × 29.9 × 1.9 mm body size or recommended pad dimensions from the datasheet.
- Datasheet layout guidance: avoid signal routing under the module where possible, keep ground away from the antenna area, and follow the recommended pattern / Fanstel reference Gerbers.
Recommended fixes
- Correct schematic terminal
Pin Numberassignments to match the datasheet table, or rename/reassign the affected terminals so each pin number maps to the correct signal. - After symbol pin numbers are corrected, update the footprint pad mapping so pad numbers and signal names match the corrected symbol.
- Consider replacing the current Datasheet URL with the official latest Fanstel URL if you want the part to point to the manufacturer-hosted current revision.
- Verify footprint geometry against Fanstel’s recommended land pattern / reference Gerber before publishing or using in a board design.
Sources
Project metadata reviewed
Key specs
Pin grouping applied
Pinout cross-check
Footprint cross-check
Recommended fixes
