@dheerajsom/pinhub 0.1.0

package/README.md

@@ -0,0 +1,152 @@
+# pinhub — pinout diagrams in your terminal
+
+`pinhub` installs a tiny cross-platform command, **`ph`**, that draws hardware
+board pinout diagrams straight in your terminal — pin numbers, GPIO names,
+power/ground rails, and the safety warnings that matter, sourced from official
+vendor documentation.
+
+```text
+$ ph rpi5
+
+Raspberry Pi 5 — Raspberry Pi
+Source: Raspberry Pi GPIO documentation (official) — see ph raspberry-pi-5 --source
+⚠ GPIO uses 3.3 V logic. Do not apply 5 V to any GPIO pin.
+
+40-pin GPIO header (J8)
+  ┌────────────────────┬────┬────┬───────────────────┐
+  │ 3V3                │  1 │  2 │ 5V                │
+  │ GPIO2 / SDA1       │  3 │  4 │ 5V                │
+  │ GPIO3 / SCL1       │  5 │  6 │ GND               │
+  │ GPIO4 / GPCLK0     │  7 │  8 │ GPIO14 / TXD0     │
+  │ GND                │  9 │ 10 │ GPIO15 / RXD0     │
+  │ …                  │  … │  … │ …                 │
+  └────────────────────┴────┴────┴───────────────────┘
+```
+
+Works on Windows (PowerShell, Windows Terminal), macOS (Terminal, iTerm2), and
+Linux. No network access, no telemetry — all board data ships in the package.
+
+## Install
+
+Requires Node.js 18.18 or newer.
+
+```bash
+npm install -g pinhub
+ph rpi5
+```
+
+See [SETUP.md](SETUP.md) for step-by-step setup, installing from source, and
+troubleshooting.
+
+Planned package-manager support: Homebrew, winget/Scoop/Chocolatey, Fedora
+RPM/dnf, and Debian/Ubuntu deb/apt.
+
+## Usage
+
+```bash
+ph <board>            # render a pinout diagram
+ph list               # all boards in the catalog
+ph search <query>     # find boards by name, alias, or manufacturer
+ph info <board>       # description, headers, warnings, sources, aliases
+ph help               # usage help
+ph --version          # version
+```
+
+Board names are forgiving: `ph rpi5`, `ph pi5`, `ph raspberry-pi-5`, and
+`ph raspberry pi 5` all resolve to the same board, case-insensitively.
+
+### Output flags
+
+| Flag | Effect |
+| --- | --- |
+| `--compact` | Tighter, borderless layout for small terminals |
+| `--ascii` | ASCII-only borders and symbols (no Unicode) |
+| `--no-color` | Disable ANSI colors |
+| `--json` | Emit the board's full data as JSON (stdout is pure JSON) |
+| `--source` | Print the board's documentation source links |
+| `--width <n>` | Override the detected terminal width |
+
+Examples:
+
+```bash
+ph rpi5
+ph esp32
+ph pico --compact
+ph rpi5 --ascii --no-color
+ph uno --json | jq '.headers[].name'
+ph rpi5 --source
+```
+
+## Boards
+
+| Board | Try |
+| --- | --- |
+| Raspberry Pi 5 (40-pin GPIO header) | `ph rpi5` |
+| Raspberry Pi Pico | `ph pico` |
+| Raspberry Pi Pico W | `ph pico-w` |
+| Arduino UNO R3 | `ph uno` |
+| ESP32 DevKit V1 (DOIT, 30-pin) | `ph esp32` |
+
+## Color and accessibility
+
+- Pin categories are color-coded (power red/yellow, ground gray, GPIO green,
+  communication cyan, analog blue, reserved magenta), but color is never the
+  only signal — labels, category names, and the `*` reserved marker survive
+  `--no-color` and piping.
+- The [`NO_COLOR`](https://no-color.org/) environment variable is honored, as
+  is `--no-color`.
+- When output is piped or redirected (not a TTY), color is disabled
+  automatically and the layout stays stable.
+- `--ascii` avoids all Unicode for legacy terminals and screen readers that
+  struggle with box-drawing characters.
+- On narrow terminals the diagram degrades gracefully: full bordered table →
+  compact pairs → vertical list. Warnings and source lines are never truncated.
+
+## Hardware safety disclaimer
+
+Pinout data is hardware-critical. Every board in the catalog cites its
+sources (`ph <board> --source`), preferring official vendor documentation;
+third-party sources are explicitly marked. Board *variants and revisions can
+differ* — especially ESP32 dev boards — so always verify against your exact
+board's silkscreen and vendor documentation before wiring anything.
+Miswiring power pins can permanently damage your hardware. Use at your own
+risk.
+
+## Contributing boards
+
+Board data lives in `src/boards/`, one module per board, using the typed model
+in `src/model.ts`. To add a board:
+
+1. Create `src/boards/<board-id>.ts` exporting a `Board` object.
+   - Every pin needs a `physical` number, a grid `position`, a `label`, and a
+     `category`.
+   - Include at least one **official** source URL (datasheet, schematic, or
+     vendor pinout). Third-party sources are allowed only when official
+     documentation is unavailable and must be marked `official: false`.
+   - Include the safety warnings that apply (logic level, strapping pins,
+     reserved pins, revision differences).
+2. Register it in `src/boards/index.ts` and add aliases people actually type.
+3. Run `npm test` — catalog invariant tests check sources, warnings, alias
+   uniqueness, and pin-grid consistency.
+
+## Development
+
+```bash
+cd cli
+npm install
+npm run dev -- rpi5     # run from TypeScript source
+npm test                # vitest suite (alias, JSON, rendering, snapshots)
+npm run lint            # eslint
+npm run build           # compile to dist/
+npm run package:check   # npm pack --dry-run
+```
+
+The CLI entry point is `src/cli.ts`; `src/run.ts` contains the whole command
+surface as a testable function that writes to captured buffers. Renderers live
+in `src/render/` behind a small abstraction (`dual-row` bordered table,
+compact pairs, and vertical list), so new header layouts can be added without
+touching board data. CI runs lint, tests, build, and a smoke test on Windows,
+macOS, and Linux via GitHub Actions.
+
+To publish: `npm publish` from `cli/` (the `prepublishOnly` hook lints, tests,
+and builds; the `files` allowlist ships only `dist/`).

package/SETUP.md

@@ -0,0 +1,126 @@
+# Setting up the PinHub CLI (`ph`)
+
+This guide walks you through installing the `pinhub` package so the `ph`
+command is available in your terminal, on Windows, macOS, or Linux.
+
+## 1. Prerequisites
+
+The only requirement is **Node.js 18.18 or newer** (which includes npm).
+
+Check what you have:
+
+```bash
+node --version
+npm --version
+```
+
+If you need Node.js:
+
+- **Windows:** `winget install OpenJS.NodeJS.LTS`, or download from
+  [nodejs.org](https://nodejs.org/).
+- **macOS:** `brew install node`, or download from
+  [nodejs.org](https://nodejs.org/).
+- **Linux:** use your distribution's package manager or
+  [nodesource](https://github.com/nodesource/distributions), e.g.
+  `sudo dnf install nodejs` / `sudo apt install nodejs npm`.
+
+No `sudo` is required to *run* `ph`, and the CLI itself never touches the
+network — all board data is bundled.
+
+## 2. Install from npm (recommended)
+
+```bash
+npm install -g pinhub
+```
+
+Then verify:
+
+```bash
+ph --version
+ph rpi5
+```
+
+If `ph` prints a pinout diagram, you're done.
+
+> **Note on `sudo npm install -g` (macOS/Linux):** if global installs fail
+> with a permissions error, prefer fixing your npm prefix over using sudo:
+> `npm config set prefix ~/.npm-global` and add `~/.npm-global/bin` to your
+> `PATH`.
+
+## 3. Install from source (this repository)
+
+```bash
+git clone https://github.com/<your-org>/PinHub.git
+cd PinHub/cli
+npm install
+npm run build
+npm install -g .
+```
+
+`npm install -g .` links the built CLI into your global npm bin, giving you
+the same `ph` command as an npm install. Alternatively, run it in place
+without installing:
+
+```bash
+node dist/cli.js rpi5
+# or straight from TypeScript during development:
+npm run dev -- rpi5
+```
+
+## 4. First steps
+
+```bash
+ph list                 # see every board in the catalog
+ph rpi5                 # Raspberry Pi 5 GPIO header
+ph pico                 # Raspberry Pi Pico
+ph uno                  # Arduino UNO R3
+ph esp32                # ESP32 DevKit V1 (DOIT, 30-pin)
+ph search raspberry     # find boards
+ph info esp32           # warnings, sources, aliases
+ph rpi5 --source        # official documentation links
+```
+
+Useful flags: `--compact` (small terminals), `--ascii` (no Unicode),
+`--no-color`, `--json` (script-friendly), `--width <n>`.
+
+Board names are forgiving — `ph rpi5`, `ph pi5`, and `ph raspberry pi 5` all
+work. If you guess wrong, `ph` suggests the closest matches.
+
+## 5. Troubleshooting
+
+**`ph` is not recognized / command not found**
+The npm global bin directory is not on your `PATH`.
+
+- Find it with `npm prefix -g`. On Windows that directory itself (e.g.
+  `C:\Users\you\AppData\Roaming\npm`) must be on `PATH`; on macOS/Linux it's
+  `<prefix>/bin`.
+- Open a *new* terminal after installing — `PATH` changes don't apply to
+  already-open sessions.
+
+**Boxes render as `?` or garbled characters**
+Your terminal or font doesn't support Unicode box-drawing. Use `ph <board>
+--ascii`. On legacy Windows consoles, Windows Terminal is recommended;
+`chcp 65001` can also help with piped output.
+
+**No colors, or you want no colors**
+Color is automatically disabled when output is piped or when the
+[`NO_COLOR`](https://no-color.org/) environment variable is set. Force it off
+per-invocation with `--no-color`.
+
+**The diagram looks cramped or wraps badly**
+`ph` adapts to terminal width and falls back to a compact layout, but you can
+control it: widen the terminal, or use `--compact`, or `--width 100`.
+
+**Uninstall**
+
+```bash
+npm uninstall -g pinhub
+```
+
+## 6. A note on hardware safety
+
+`ph` shows each board's voltage levels, reserved pins, and boot-strap pins,
+and cites its documentation sources — but board revisions differ (ESP32
+boards especially). Always cross-check your exact board's silkscreen and the
+official documentation (`ph <board> --source`) before wiring. 3.3 V GPIO does
+not forgive 5 V.

package/dist/boards/arduino-uno-r3.d.ts

@@ -0,0 +1,2 @@
+import type { Board } from "../model.js";
+export declare const arduinoUnoR3: Board;

package/dist/boards/arduino-uno-r3.js

@@ -0,0 +1,133 @@
+function col(physical, label, category, extra = {}) {
+    return {
+        physical,
+        position: { row: physical, column: 1 },
+        label,
+        category,
+        ...extra,
+    };
+}
+const V5 = { voltage: "5 V" };
+export const arduinoUnoR3 = {
+    id: "arduino-uno-r3",
+    name: "Arduino UNO R3",
+    manufacturer: "Arduino",
+    aliases: ["uno", "uno-r3", "arduino-uno", "arduino-uno-r3", "arduino-uno-rev3"],
+    description: "Classic ATmega328P Arduino board with the reference UNO shield headers and 2×3 ICSP header. Digital IO is 5 V logic.",
+    revisionNote: "This is the ATmega328P UNO R3. The newer UNO R4 boards keep the shield shape but use a different microcontroller — check `docs.arduino.cc` for R4 pin functions.",
+    warnings: [
+        {
+            severity: "danger",
+            text: "Digital IO is 5 V logic. Level-shift 3.3 V-only sensors and modules.",
+        },
+        {
+            severity: "warning",
+            text: "The 3.3 V regulator output is current-limited (~50 mA); do not power large peripherals from it.",
+        },
+        {
+            severity: "info",
+            text: "A4/A5 double as I2C SDA/SCL and are internally connected to the dedicated SDA/SCL pins next to AREF.",
+        },
+        {
+            severity: "info",
+            text: "SPI is available on D10–D13 and on the ICSP header.",
+        },
+    ],
+    sources: [
+        {
+            title: "Arduino UNO Rev3 documentation",
+            url: "https://docs.arduino.cc/hardware/uno-rev3/",
+            official: true,
+        },
+        {
+            title: "Arduino UNO Rev3 full pinout PDF",
+            url: "https://content.arduino.cc/assets/A000066-full-pinout.pdf",
+            official: true,
+        },
+        {
+            title: "Arduino UNO Rev3 datasheet",
+            url: "https://docs.arduino.cc/resources/datasheets/A000066-datasheet.pdf",
+            official: true,
+        },
+    ],
+    headers: [
+        {
+            id: "digital-high",
+            name: "Digital header (SCL…D8)",
+            description: "Top edge, left to right with the USB port on the left.",
+            layout: { rows: 10, columns: 1 },
+            pins: [
+                col(1, "SCL", "communication", { functions: ["I2C SCL"], ...V5, notes: ["Connected to A5"] }),
+                col(2, "SDA", "communication", { functions: ["I2C SDA"], ...V5, notes: ["Connected to A4"] }),
+                col(3, "AREF", "analog", { notes: ["Analog reference voltage input"] }),
+                col(4, "GND", "ground"),
+                col(5, "D13", "communication", { gpio: "PB5", functions: ["SPI SCK", "LED_BUILTIN"], ...V5 }),
+                col(6, "D12", "communication", { gpio: "PB4", functions: ["SPI MISO"], ...V5 }),
+                col(7, "D11", "communication", { gpio: "PB3", functions: ["SPI MOSI", "PWM"], ...V5 }),
+                col(8, "D10", "communication", { gpio: "PB2", functions: ["SPI SS", "PWM"], ...V5 }),
+                col(9, "D9", "gpio", { gpio: "PB1", functions: ["PWM"], ...V5 }),
+                col(10, "D8", "gpio", { gpio: "PB0", ...V5 }),
+            ],
+        },
+        {
+            id: "digital-low",
+            name: "Digital header (D7…D0)",
+            description: "Top edge, continues right of the D8 header.",
+            layout: { rows: 8, columns: 1 },
+            pins: [
+                col(1, "D7", "gpio", { gpio: "PD7", ...V5 }),
+                col(2, "D6", "gpio", { gpio: "PD6", functions: ["PWM"], ...V5 }),
+                col(3, "D5", "gpio", { gpio: "PD5", functions: ["PWM"], ...V5 }),
+                col(4, "D4", "gpio", { gpio: "PD4", ...V5 }),
+                col(5, "D3", "gpio", { gpio: "PD3", functions: ["PWM", "INT1"], ...V5 }),
+                col(6, "D2", "gpio", { gpio: "PD2", functions: ["INT0"], ...V5 }),
+                col(7, "D1", "communication", { gpio: "PD1", functions: ["UART TX"], ...V5, notes: ["Shared with USB serial"] }),
+                col(8, "D0", "communication", { gpio: "PD0", functions: ["UART RX"], ...V5, notes: ["Shared with USB serial"] }),
+            ],
+        },
+        {
+            id: "power",
+            name: "Power header",
+            description: "Bottom edge, left to right with the barrel jack on the left.",
+            layout: { rows: 8, columns: 1 },
+            pins: [
+                col(1, "NC", "nc", { notes: ["Reserved, leave unconnected"] }),
+                col(2, "IOREF", "power", { ...V5, notes: ["IO reference voltage for shields"] }),
+                col(3, "RESET", "reserved", { notes: ["Active-low reset"] }),
+                col(4, "3V3", "power", { voltage: "3.3 V", notes: ["~50 mA regulator output"] }),
+                col(5, "5V", "power", { voltage: "5 V" }),
+                col(6, "GND", "ground"),
+                col(7, "GND", "ground"),
+                col(8, "VIN", "power", { voltage: "7–12 V recommended", notes: ["Unregulated input"] }),
+            ],
+        },
+        {
+            id: "analog",
+            name: "Analog input header",
+            description: "Bottom edge, right of the power header.",
+            layout: { rows: 6, columns: 1 },
+            pins: [
+                col(1, "A0", "analog", { gpio: "PC0", ...V5 }),
+                col(2, "A1", "analog", { gpio: "PC1", ...V5 }),
+                col(3, "A2", "analog", { gpio: "PC2", ...V5 }),
+                col(4, "A3", "analog", { gpio: "PC3", ...V5 }),
+                col(5, "A4", "analog", { gpio: "PC4", functions: ["I2C SDA"], ...V5 }),
+                col(6, "A5", "analog", { gpio: "PC5", functions: ["I2C SCL"], ...V5 }),
+            ],
+        },
+        {
+            id: "icsp",
+            name: "ICSP header (2×3)",
+            description: "Pin 1 (MISO) is marked with a dot on the silkscreen.",
+            layout: { rows: 3, columns: 2 },
+            pins: [
+                { physical: 1, position: { row: 1, column: 1 }, label: "MISO", category: "communication", functions: ["SPI MISO"], ...V5 },
+                { physical: 2, position: { row: 1, column: 2 }, label: "5V", category: "power", voltage: "5 V" },
+                { physical: 3, position: { row: 2, column: 1 }, label: "SCK", category: "communication", functions: ["SPI SCK"], ...V5 },
+                { physical: 4, position: { row: 2, column: 2 }, label: "MOSI", category: "communication", functions: ["SPI MOSI"], ...V5 },
+                { physical: 5, position: { row: 3, column: 1 }, label: "RESET", category: "reserved", notes: ["Active-low reset"] },
+                { physical: 6, position: { row: 3, column: 2 }, label: "GND", category: "ground" },
+            ],
+        },
+    ],
+};

package/dist/boards/esp32-devkit-v1.d.ts

@@ -0,0 +1,2 @@
+import type { Board } from "../model.js";
+export declare const esp32DevkitV1: Board;

package/dist/boards/esp32-devkit-v1.js

@@ -0,0 +1,143 @@
+/**
+ * DOIT ESP32 DevKit V1, 30-pin variant. Physical numbering is positional
+ * (DOIT boards do not silkscreen pin numbers): 1–15 down the left side and
+ * 16–30 down the right side, viewed from above with the USB port at the
+ * bottom.
+ */
+function pin(physical, label, category, extra = {}) {
+    const left = physical <= 15;
+    return {
+        physical,
+        position: { row: left ? physical : physical - 15, column: left ? 1 : 2 },
+        label,
+        category,
+        ...extra,
+    };
+}
+const V33 = { voltage: "3.3 V" };
+const INPUT_ONLY = ["Input only — no output driver, no internal pull resistors"];
+export const esp32DevkitV1 = {
+    id: "esp32-devkit-v1",
+    name: "ESP32 DevKit V1 (DOIT, 30-pin)",
+    manufacturer: "DOIT (ESP32-WROOM-32 module by Espressif)",
+    aliases: [
+        "esp32",
+        "esp32-devkit",
+        "esp32-devkit-v1",
+        "esp32-devkitv1",
+        "doit-esp32-devkit-v1",
+        "esp32-wroom-32",
+        "esp32-devkitc",
+    ],
+    description: "The ubiquitous 30-pin ESP32-WROOM-32 breadboard dev kit. Wi-Fi + Bluetooth, two breadboard-friendly headers, 3.3 V logic.",
+    revisionNote: "ESP32 dev boards vary a lot: 30-pin DevKit V1, 36-pin variants, and the 38-pin Espressif ESP32-DevKitC all have different headers. Verify the silkscreen of your exact board before wiring anything.",
+    warnings: [
+        {
+            severity: "danger",
+            text: "GPIO uses 3.3 V logic. Do not apply 5 V to any GPIO pin.",
+        },
+        {
+            severity: "danger",
+            text: "GPIO0, GPIO2, GPIO5, GPIO12 and GPIO15 are boot-strapping pins; external pull-ups/downs at reset can stop the board from booting or flashing.",
+        },
+        {
+            severity: "warning",
+            text: "GPIO34–GPIO39 (VP, VN, D34, D35) are input-only and have no internal pull resistors.",
+        },
+        {
+            severity: "warning",
+            text: "ADC2 channels cannot be used while Wi-Fi is active; prefer ADC1 (VP, VN, D32–D35) for analog reads.",
+        },
+        {
+            severity: "info",
+            text: "TX0/RX0 (GPIO1/GPIO3) carry the USB serial console and are used for flashing.",
+        },
+    ],
+    sources: [
+        {
+            title: "Espressif ESP32-WROOM-32 datasheet",
+            url: "https://www.espressif.com/sites/default/files/documentation/esp32-wroom-32_datasheet_en.pdf",
+            official: true,
+        },
+        {
+            title: "Espressif ESP32 series datasheet",
+            url: "https://www.espressif.com/sites/default/files/documentation/esp32_datasheet_en.pdf",
+            official: true,
+        },
+        {
+            title: "Last Minute Engineers — ESP32 DevKit pinout reference (third-party board layout)",
+            url: "https://lastminuteengineers.com/esp32-pinout-reference/",
+            official: false,
+        },
+    ],
+    headers: [
+        {
+            id: "main",
+            name: "30-pin breadboard headers",
+            description: "Viewed from above, USB port at the bottom. Pins numbered 1–15 down the left and 16–30 down the right (positional; not silkscreened).",
+            layout: { rows: 15, columns: 2 },
+            pins: [
+                pin(1, "EN", "reserved", { notes: ["Chip enable / reset (active low), wired to the EN button"], ...V33 }),
+                pin(2, "VP", "analog", { gpio: "GPIO36", functions: ["ADC1_CH0"], notes: INPUT_ONLY, ...V33 }),
+                pin(3, "VN", "analog", { gpio: "GPIO39", functions: ["ADC1_CH3"], notes: INPUT_ONLY, ...V33 }),
+                pin(4, "D34", "analog", { gpio: "GPIO34", functions: ["ADC1_CH6"], notes: INPUT_ONLY, ...V33 }),
+                pin(5, "D35", "analog", { gpio: "GPIO35", functions: ["ADC1_CH7"], notes: INPUT_ONLY, ...V33 }),
+                pin(6, "D32", "analog", { gpio: "GPIO32", functions: ["ADC1_CH4", "Touch9"], ...V33 }),
+                pin(7, "D33", "analog", { gpio: "GPIO33", functions: ["ADC1_CH5", "Touch8"], ...V33 }),
+                pin(8, "D25", "analog", { gpio: "GPIO25", functions: ["DAC1", "ADC2_CH8"], ...V33 }),
+                pin(9, "D26", "analog", { gpio: "GPIO26", functions: ["DAC2", "ADC2_CH9"], ...V33 }),
+                pin(10, "D27", "gpio", { gpio: "GPIO27", functions: ["ADC2_CH7", "Touch7"], ...V33 }),
+                pin(11, "D14", "gpio", { gpio: "GPIO14", functions: ["HSPI CLK", "ADC2_CH6"], ...V33 }),
+                pin(12, "D12", "gpio", {
+                    gpio: "GPIO12",
+                    functions: ["HSPI MISO", "ADC2_CH5"],
+                    notes: ["Boot strap: must be low at reset"],
+                    ...V33,
+                }),
+                pin(13, "D13", "gpio", { gpio: "GPIO13", functions: ["HSPI MOSI", "ADC2_CH4"], ...V33 }),
+                pin(14, "GND", "ground"),
+                pin(15, "VIN", "power", { voltage: "5 V", notes: ["5 V input when not powered over USB"] }),
+                pin(16, "D23", "communication", { gpio: "GPIO23", functions: ["VSPI MOSI"], ...V33 }),
+                pin(17, "D22", "communication", { gpio: "GPIO22", functions: ["I2C SCL"], ...V33 }),
+                pin(18, "TX0", "communication", {
+                    gpio: "GPIO1",
+                    functions: ["UART0 TX"],
+                    notes: ["USB serial console / flashing"],
+                    ...V33,
+                }),
+                pin(19, "RX0", "communication", {
+                    gpio: "GPIO3",
+                    functions: ["UART0 RX"],
+                    notes: ["USB serial console / flashing"],
+                    ...V33,
+                }),
+                pin(20, "D21", "communication", { gpio: "GPIO21", functions: ["I2C SDA"], ...V33 }),
+                pin(21, "D19", "communication", { gpio: "GPIO19", functions: ["VSPI MISO"], ...V33 }),
+                pin(22, "D18", "communication", { gpio: "GPIO18", functions: ["VSPI CLK"], ...V33 }),
+                pin(23, "D5", "communication", {
+                    gpio: "GPIO5",
+                    functions: ["VSPI CS"],
+                    notes: ["Boot strap: outputs PWM at boot; keep high at reset"],
+                    ...V33,
+                }),
+                pin(24, "TX2", "communication", { gpio: "GPIO17", functions: ["UART2 TX"], ...V33 }),
+                pin(25, "RX2", "communication", { gpio: "GPIO16", functions: ["UART2 RX"], ...V33 }),
+                pin(26, "D4", "gpio", { gpio: "GPIO4", functions: ["ADC2_CH0", "Touch0"], ...V33 }),
+                pin(27, "D2", "gpio", {
+                    gpio: "GPIO2",
+                    functions: ["ADC2_CH2", "Touch2"],
+                    notes: ["Onboard LED; boot strap: must be floating or low at reset"],
+                    ...V33,
+                }),
+                pin(28, "D15", "gpio", {
+                    gpio: "GPIO15",
+                    functions: ["ADC2_CH3", "HSPI CS"],
+                    notes: ["Boot strap: keep high at reset to silence boot log"],
+                    ...V33,
+                }),
+                pin(29, "GND", "ground"),
+                pin(30, "3V3", "power", { voltage: "3.3 V", notes: ["Regulator output"] }),
+            ],
+        },
+    ],
+};

package/dist/boards/index.d.ts

@@ -0,0 +1,2 @@
+import type { Board } from "../model.js";
+export declare const boards: Board[];

package/dist/boards/index.js

@@ -0,0 +1,12 @@
+import { raspberryPi5 } from "./raspberry-pi-5.js";
+import { raspberryPiPico } from "./raspberry-pi-pico.js";
+import { raspberryPiPicoW } from "./raspberry-pi-pico-w.js";
+import { arduinoUnoR3 } from "./arduino-uno-r3.js";
+import { esp32DevkitV1 } from "./esp32-devkit-v1.js";
+export const boards = [
+    raspberryPi5,
+    raspberryPiPico,
+    raspberryPiPicoW,
+    arduinoUnoR3,
+    esp32DevkitV1,
+];

package/dist/boards/pico-shared.d.ts

@@ -0,0 +1,3 @@
+import type { Header } from "../model.js";
+export declare function picoEdgeHeader(): Header;
+export declare function picoDebugHeader(swdName: string): Header;