feat(online-data): ingest per-board VID:PID tables from upstream vendor manifests

[zackees]

Goal

Extend the online-data USB-VID aggregator (the pipeline introduced in #718 / #719) with per-board VID:PID coverage by ingesting structured board-manifest data from upstream vendors. Today the aggregator carries:

• Vendor names (via the merged usb-vid.json — text DBs + the curated vendor_names_inlined.py overlay covering 253 newer VIDs).
• PlatformIO board catalog (pio-boards.json — names + MCU family but no VID:PID).
• MCU → VID heuristics (mcu_to_vid.json — confidence-scored, not per-board).

What's still missing for the headline VID:PID → board lookup: a precise per-board VID:PID table that says e.g. "0x303A:0x4002 is an ESP32-S3" rather than "any ESP32-S3-family board on VID 0x303A."

Authoritative public sources (in priority order)

Tier	Source	Format	Coverage	Type
1	raspberrypi/usb-pid → Readme.md	Markdown table	VID 0x2E8A PID allocations (Pico, Pimoroni, Cytron, WIZnet, TI USB-TMC etc.)	PID allocation registry
1	espressif/usb-pids → allocated-pids.txt + allocated-pids-espressif-devboards.txt	Plain text (VVVV:PPPP description)	VID 0x303A customer & devboard PIDs (TinyS2, LILYGO, ATMegaZero, ESP32-S3-DevKitC, ESP32-P4 etc.)	PID allocation registry
2	arduino/ArduinoCore-avr → boards.txt	boardname.vid.N=0xVVVV / pid.N=0xPPPP	Leonardo, Micro, Esplora, Yún (VID 0x2341, 0x2A03)	Board-manifest
2	arduino/ArduinoCore-samd → boards.txt	Same	Zero, MKR family, Nano 33 IoT (VID 0x03EB, 0x2341)	Board-manifest
2	espressif/arduino-esp32 → boards.txt	Same	ESP32-S2/S3/C3 family + partner boards (UM TinyS2, LOLIN S2 Mini, etc.)	Board-manifest
2	adafruit/Adafruit_nRF52_Arduino → boards.txt	Same	Feather nRF52840 Express/Sense, ItsyBitsy, Circuit Playground Bluefruit, CLUE (VID 0x239A)	Board-manifest
2	SiliconLabs/arduino → boards.txt	Same	Nano Matter, Seeed XIAO MG24 (VID 0x2341, 0x2886)	Board-manifest (official)
3	stm32duino/Arduino_Core_STM32 → boards.txt	Same	Nucleo, Discovery, Eval, generic STM32 (VID 0x0483, PIDs 0x5740 / 0x3744 / 0x3748 / 0x374B / 0x3753)	Board-manifest (community, not ST-official)
4	NordicSemiconductor/nrf-udev → 71-nrf.rules	udev rules	VID 0x1915 (all Nordic devices) — vendor-level only, no per-product	Auxiliary
4	NordicSemiconductor/nrf-device-setup-js (archived) → README	Prose	Single explicit pair: 0x1915:0x521F PCA10059 bootloader	Auxiliary, archived 2022-01-10

Gaps confirmed by the research

• NXP (MCUXpresso org): no public PID allocation file. Per-example USB descriptors in nxp-mcuxpresso/mcux-sdk-middleware-usb only.
• Microchip (Harmony USB): same shape — per-example USB descriptors, no centralized registry.
• TI: no maintained list. energia/Energia is the closest but explicitly unmaintained.
• STM32: no ST-owned official list. stm32duino/Arduino_Core_STM32 is community-run.

Proposed implementation

Add a new fetch+parse step per source under online-data-tools/, modeled on the existing fetch_gowdy_supplement.py + overlay_usb_vid.py pattern:

1. fetch_rpi_pid_registry.py — parses raspberrypi/usb-pid/Readme.md markdown table → {vidpid: product_name} JSON. Tier-1 (most authoritative).
2. fetch_espressif_pid_registry.py — parses espressif/usb-pids/allocated-pids*.txt (two files) → same shape. Tier-1.
3. fetch_boards_txt.py — generic parser for Arduino-style boards.txt. Walks boardname.vid.N + pid.N pairs and emits {vidpid: f"{board_friendly_name}"}. Used for the 6 tier-2/3 board-manifest repos.
4. overlay_per_board_pids.py — merges all per-board sources into a NEW online-data/data/usb-board-pids.json keyed by 8-hex-digit VVVVPPPP, with {vendor, board, source} per entry. Doesn't disturb the existing usb-vid.json.
5. SQLite consumer — build_sqlite.py populates vidpid from BOTH the existing usb_product rows AND the new per-board source, with the per-board source winning on conflict (it's the authoritative consumer-facing name).
6. Workflow wiring — add the new fetches to update-data.yml with continue-on-error: true (same fault-tolerance pattern as the existing tier-1/2/3 sources).

Output schema sketch

// online-data/data/usb-board-pids.json
{
  "2e8a0003": {"vendor": "Raspberry Pi", "board": "RP2040 Boot",            "source": "raspberrypi/usb-pid"},
  "2e8a000b": {"vendor": "Raspberry Pi", "board": "Pico CircuitPython",     "source": "raspberrypi/usb-pid"},
  "303a8001": {"vendor": "Unexpected Maker", "board": "TinyS2 Arduino",     "source": "espressif/usb-pids"},
  "303a7012": {"vendor": "Espressif",    "board": "ESP32-P4 Function EV",   "source": "espressif/usb-pids"},
  "23418057": {"vendor": "Arduino",      "board": "Nano 33 IoT",            "source": "arduino/ArduinoCore-samd"},
  "239a8029": {"vendor": "Adafruit",     "board": "Feather nRF52840 Express","source":"adafruit/Adafruit_nRF52_Arduino"},
  "23410072": {"vendor": "Arduino",      "board": "Nano Matter",            "source": "SiliconLabs/arduino"}
}

Acceptance criteria

• All 9 sources fetched + parsed nightly by update-data.yml.
• online-data/data/usb-board-pids.json committed with at least 200 per-board entries on first successful run.
• manifest.json advertises the new dataset (alongside usb-vid, pio-boards, vendor_boards).
• The www SQLite vidpid table is populated from this new source, so a canned-query vidpid='2e8a000b' returns "Pico CircuitPython" not just "Pico SDK CDC UART".
• fbuild-core::usb::resolver::pretty(0x303A, 0x4002) resolves through the overlay (tier-2) and returns "Unexpected Maker TinyS2 Arduino" instead of the synthetic "Device 0x4002" placeholder.
• Tests cover each parser (small fixture per format), the overlay merge, and the SQLite ingestion.
• Gaps (NXP / Microchip / TI / non-Espressif Nordic) documented in online-data-tools/README.md.

Out of scope (defer to follow-ups)

• Scraping vendor SDK examples for embedded USB descriptors (NXP / Microchip / TI). Would require navigating each vendor's GitHub forest and is a much larger investment.
• Cross-vendor PID-collision detection (e.g. when an OEM ships under multiple VIDs). Add as usb-board-pid-conflicts.json once the basic ingestion is live.
• Adding the new dataset to the embedded usb-vendors.tar.zst archive in fbuild. The archive is intentionally small (vendor-only); per-PID data stays in the runtime overlay + the www SQLite-over-HTTP backend.

Sub-issue checklist

Per-vendor ingest sub-issues. This meta auto-closes when all are CLOSED.

Tier-1 PID registries (most authoritative)

• vid-ingest: Espressif Systems (0x303A — ESP32 native USB) #723 — Espressif Systems (0x303A — ESP32 native USB)
• vid-ingest: Raspberry Pi Foundation (0x2E8A — RP2040 / RP2350) #724 — Raspberry Pi Foundation (0x2E8A — RP2040 / RP2350)

Tier-2 board-manifests (Arduino-core boards.txt)

• vid-ingest: STMicroelectronics (0x0483 — STM32 + ST-Link) #725 — STMicroelectronics (0x0483 — STM32 + ST-Link)
• vid-ingest: NXP Semiconductors (0x1FC9 — LPC + MIMXRT) #726 — NXP Semiconductors (0x1FC9 — LPC + MIMXRT)
• vid-ingest: Nordic Semiconductor (0x1915 — nRF52) #727 — Nordic Semiconductor (0x1915 — nRF52)
• vid-ingest: Microchip / Atmel (0x03EB, 0x04D8 — AVR + SAMD) #728 — Microchip / Atmel (0x03EB, 0x04D8 — AVR + SAMD)
• vid-ingest: Silicon Labs (0x10C4, 0x2544 — CP210x bridges + xG24 SoC) #729 — Silicon Labs (0x10C4, 0x2544 — CP210x bridges + xG24 SoC)
• vid-ingest: WCH / QinHeng (0x1A86 — CH32V/X + CH340 bridges) #730 — WCH / QinHeng (0x1A86 — CH32V/X + CH340 bridges)
• vid-ingest: FTDI (0x0403 — FT232 bridges) #731 — FTDI (0x0403 — FT232 bridges)
• vid-ingest: Ambiq Micro (0x1CBE — Apollo3) #732 — Ambiq Micro (0x1CBE — Apollo3)
• vid-ingest: Renesas Electronics (0x045B — UNO R4 RA4M1) #733 — Renesas Electronics (0x045B — UNO R4 RA4M1)
• vid-ingest: Arduino (0x2341, 0x2A03 — official Arduino boards) #734 — Arduino (0x2341, 0x2A03 — official Arduino boards)
• vid-ingest: Adafruit (0x239A — Feather/ItsyBitsy/CPB/CLUE/...) #735 — Adafruit (0x239A — Feather/ItsyBitsy/CPB/CLUE)
• vid-ingest: SparkFun Electronics (0x1B4F — RedBoard/Pro Micro/Thing Plus) #736 — SparkFun Electronics (0x1B4F — RedBoard/Pro Micro/Thing Plus)
• vid-ingest: PJRC / Teensy (0x16C0 — Teensy 3.x/4.x/LC) #737 — PJRC / Teensy (0x16C0 — Teensy 3.x/4.x/LC)
• vid-ingest: Seeed Studio (0x2886 — XIAO family) #738 — Seeed Studio (0x2886 — XIAO family)
• vid-ingest: Atmel SAM Cortex-M3 (0x03EB — Arduino Due / SAM3X8E) #739 — Atmel SAM Cortex-M3 (0x03EB — Arduino Due / SAM3X8E)

End-to-end verification (blocked on all of #723–#739)

• vid-ingest: final end-to-end verification (after #723–#739 close) #740 — final end-to-end verification

References

• Source research: see issue body above (catalog table, gaps, caveats).
• Prior work: feat(www): GH Pages site + SQLite-over-HTTP for VID:PID <-> board fuzzy match #718 (www + SQLite-over-HTTP design), feat(www): SQLite-over-HTTP site + nightly publish to www branch (#718) #719 (initial implementation), policy: dump_usb_ids must remain (tier-1 source for online-data aggregation) #720 (dump_usb_ids protection policy).

[zackees]

Source research (deep-research report, verbatim)

Folding in the full original research that motivated this issue. Citation markers (citeturn...) are preserved as-is from the source.

---

GitHub USB VID/PID List Repositories for MCU and Board Vendors

Executive summary

The strongest direct matches to the Espressif-style model of a public, reusable USB PID allocation list are Raspberry Pi and Espressif themselves. Raspberry Pi maintains a dedicated usb-pid repository with a public allocation table under VID 0x2E8A, and Raspberry Pi’s official documentation explicitly points users there when they need a unique PID for RP2040/RP2350-based products. Espressif maintains usb-pids, explicitly described as a repository for customer-allocated PIDs under Espressif VID 0x303A, including a separate file for Espressif-built devboards. citeturn37search1turn23search6turn38search1turn24view0turn24view1

For the other vendors and platforms you named, the public GitHub landscape is much more uneven. The best-maintained public sources are often board-definition manifests such as boards.txt in official Arduino cores, official vendor Arduino cores, or vendor-supported community cores. Those files are not policy repositories, but they do contain high-value VID/PID mappings that are practical for auditing real boards and firmware builds. This is especially true for Arduino AVR, Arduino SAMD, Espressif Arduino, Adafruit nRF52, Silicon Labs Arduino, and STM32duino. citeturn37search3turn26search0turn38search2turn17search2turn26search1turn17search0

For Nordic, there are official GitHub sources with USB-identification evidence, but I did not find a public, centralized, Espressif-style PID allocation list during this research. The closest official material was the nrf-udev rules file, which matches all Nordic devices by vendor ID 0x1915, and the archived nrf-device-setup-js README, which documents a specific bootloader VID/PID pair (0x1915:0x521F) for the PCA10059 nRF52840 dongle. citeturn32view0turn21search2turn40search0

For TI, NXP, and Microchip, I found official GitHub organizations and official USB middleware/example repositories, but I did not locate a public, centralized VID/PID allocation file comparable to allocated-pids.txt in the official GitHub sources reviewed here. For TI specifically, the closest Arduino-style source I found is Energia, but Energia is explicitly unmaintained and points users to TI’s official toolchains instead. citeturn19search0turn15search1turn14search0turn22search1

Search method

I prioritized primary GitHub sources from verified vendor organizations or clearly official project organizations, then looked for files that actually encode VID/PID information: dedicated allocation tables, boards.txt, udev rules, and README files that include explicit vendor/product pairs. Core search patterns were variations of:

site:github.com <vendor> VID PID GitHub
site:github.com <vendor> boards.txt vid pid
site:github.com <vendor> allocated-pids
site:github.com <vendor> USB_VID USB_PID
site:github.com/orgs/<org>/repositories <repo>

I also validated likely results by opening the GitHub repo pages and, where possible, the raw file URLs to confirm that the file really contains VID/PID assignments rather than only prose or issue discussion. This matters because some GitHub search hits were issue pages or forum-style copies of boards.txt content rather than the authoritative source file itself. citeturn37search1turn38search1turn37search3turn26search0turn38search2turn32view0

Catalog of repositories and files

Platform / vendor	Repository name and URL	File path and URL	Short description	Vendors / platforms covered	Official / maintained	Last observed date	Sample VID/PID entries	Sources
Raspberry Pi	raspberrypi/usb-pid	Readme.md	Public PID allocation list under Raspberry Pi VID 0x2E8A; closest analog to Espressif’s repo	RP2040/RP2350 ecosystem plus third parties using Raspberry Pi’s sublicensed VID, including Pimoroni, Cytron, WIZnet, and even a TI RP2040-based USB-TMC entry	Official Raspberry Pi repo; actively maintained	Repo updated Nov 18, 2025	2E8A:0003 RP2040 boot; 2E8A:000B Pico CircuitPython; 2E8A:000C Debug Probe; 2E8A:1000 Cytron Maker Pi RP2040; 2E8A:1107 Texas Instruments USB‑TMC SCPI Interface on RP2040	citeturn37search1turn24view2turn33search1turn23search6
Espressif	espressif/usb-pids	allocated-pids.txt	Customer-allocated PID table under Espressif VID 0x303A	ESP32 USB-capable products from many vendors using Espressif’s shared VID scheme	Official Espressif repo; purpose and PR process explicitly documented	Date not surfaced in the repo snippet I reviewed	303A:8001 Unexpected Maker TinyS2 Arduino; 303A:8002 TinyS2 CircuitPython; 303A:8006 LILYGO TTGO T8 ESP32-S2 Arduino; 303A:800A ATMegaZero ESP32-S2 Arduino; 303A:800C Gravitech CUCUMBER RIS ESP32S2 Arduino	citeturn38search1turn24view0
Espressif devboards	espressif/usb-pids	allocated-pids-espressif-devboards.txt	Separate PID list for Espressif-built hardware and software running on bare Espressif devkits	Espressif devboards such as ESP32-S2/S3 kits, S3 Box family, ESP32-P4 function EV	Official Espressif repo; explicitly referenced by README as the correct file for Espressif-built devboards	Date not surfaced in the repo snippet I reviewed	303A:7000 ESP32-S2-HMI-DevKit-1 UF2; 303A:7001 same board CircuitPython; 303A:7002 ESP32-S3-DevKitC-1 UF2; 303A:700B ESP32-S3-USB-OTG CircuitPython; 303A:7012 ESP32-P4-Function-EV UF2	citeturn38search1turn24view1
Arduino AVR	arduino/ArduinoCore-avr	boards.txt	Official Arduino AVR core; boards.txt encodes many Arduino AVR USB board VID/PID assignments	Arduino AVR USB boards such as Leonardo, Micro, Esplora, Yún; AVR silicon platform	Official Arduino core	Latest release May 21, 2026	2341:0036 Leonardo; 2341:8036 Leonardo alt/build; 2A03:0036 Leonardo alt VID; 2341:0037 Micro; 2341:8037 Micro alt/build	citeturn37search3turn41search2turn24view3
Arduino SAMD	arduino/ArduinoCore-samd	boards.txt	Official Arduino SAMD core; boards.txt includes native-USB board VID/PID values	Atmel/Microchip SAMD21 boards including Zero, MKR family, Nano 33 IoT	Official Arduino core; developed for Atmel’s SAMD21 and actively maintained	Current release date not surfaced in the snippet reviewed	03EB:2157 Arduino Zero EDBG programming port; 2341:804D Arduino Zero native USB; 2341:804E MKR1000; 2341:804F MKR Zero; 2341:8057 Nano 33 IoT	citeturn26search0turn27view0
Espressif Arduino	espressif/arduino-esp32	boards.txt	Large Arduino core manifest with many Espressif and partner-board VID/PID mappings	ESP32-S2/S3/C3 family plus partner boards from Unexpected Maker, SparkFun, Adafruit, LOLIN, DFRobot, others	Official Espressif repo; actively maintained	Latest release Apr 12, 2026	303A:1001 ESP32 Family Device; 303A:0002 ESP32S2 Dev Module; 303A:0003 ESP32S2 Native USB; 303A:8001 UM TinyS2; 303A:80C2 LOLIN S2 Mini	citeturn38search2turn27view4
Adafruit nRF	adafruit/Adafruit_nRF52_Arduino	boards.txt	Arduino BSP for Adafruit nRF52 boards with VID/PID mappings in boards.txt	Adafruit nRF52 boards; also includes Nordic PCA10056 and Particle Xenon as unsupported extras	Official Adafruit repo; maintained	Latest release May 30, 2025	239A:8029 Feather nRF52840 Express; 239A:8087 Feather nRF52840 Sense; 239A:8051 ItsyBitsy nRF52840 Express; 239A:8045 Circuit Playground Bluefruit; 239A:8071 CLUE	citeturn17search2turn40search1turn27view2
STM32	stm32duino/Arduino_Core_STM32	boards.txt	Very large Arduino STM32 manifest with class/family VID/PID mappings for Nucleo, Discovery, Eval, and generic families	STM32 Nucleo, Discovery, Eval, and generic STM32 series boards	Maintained, but not an official ST software ecosystem repo; ST contributes to the community org	Repo updated May 27, 2026	0483:5740; 0483:3744; 0483:3748; 0483:374B; 0483:3753 across Nucleo/Discovery/Eval families	citeturn17search0turn35search4turn27view1
Silicon Labs	SiliconLabs/arduino	boards.txt	Official Silicon Labs Arduino core; boards.txt includes the VID/PID pairs visible for current USB boards	Silicon Labs xG24/xG27/Matter boards; current file exposes explicit VID/PID entries for Arduino Nano Matter and Seeed XIAO MG24	Official Silicon Labs repo; maintained	Latest release Jul 28, 2025	2341:0072 Arduino Nano Matter; 2886:0062 Seeed Studio XIAO MG24 (Sense)	citeturn26search1turn40search2turn27view3
Nordic auxiliary	NordicSemiconductor/nrf-udev	nrf-udev_1.0.1-all/lib/udev/rules.d/71-nrf.rules	Official Nordic udev rules; not a PID allocation table, but a useful official USB-ID artifact	Nordic USB devices broadly matched by vendor ID 1915	Official Nordic repo, but narrow and old	Latest release Jun 7, 2018	1915:* all Nordic USB devices; ttyACM* nodes tagged for Nordic VID 1915	citeturn32view0turn21search0
Nordic archived example	NordicSemiconductor/nrf-device-setup-js	README	Official but archived repo that documents one concrete USB bootloader VID/PID pair	nRF52840 dongle / USB SDFU path	Official, but archived Jan 10, 2022	Archived Jan 10, 2022	1915:521F PCA10059 nRF52840 Dongle bootloader mode	citeturn21search2turn40search0

Interpretation of the table

If your goal is to find a single source of truth for public PID allocations, the best repos are raspberrypi/usb-pid and espressif/usb-pids. If your goal is to find real-world VID/PID assignments used by board packages and firmware ecosystems, the most useful files are the various boards.txt manifests in Arduino cores and vendor Arduino cores. citeturn37search1turn38search1turn37search3turn26search0turn38search2turn17search2turn26search1turn17search0

Gaps and caveats

During this research, I did not locate official GitHub repositories from NXP, Microchip, or Texas Instruments that expose a centralized, Espressif-style public PID-allocation file. The official repositories I found for those vendors are real and useful, but they appear to center on USB middleware, examples, and SDK delivery rather than a public allocation registry. citeturn15search1turn15search6turn14search0turn14search5turn19search0

A few specific caveats matter:

Vendor / platform	What I found	Best GitHub lead reviewed	Practical takeaway	Sources
NXP	Official MCUXpresso org and official USB middleware repo, but no public PID allocation list found in the reviewed sources	nxp-mcuxpresso/mcux-sdk-middleware-usb	Use SDK examples and board descriptors; do not assume there is a public allocation registry	citeturn15search1turn15search6
Microchip	Official Harmony USB repo and example repos, but no public centralized PID list found in the reviewed sources	Microchip-MPLAB-Harmony/usb	Expect per-example or per-project USB descriptors rather than a global public table	citeturn14search0turn14search5
TI	Official TI GitHub org exists, but no maintained official VID/PID list was located; closest Arduino-style source is unmaintained Energia	energia/Energia	For TI, treat Energia only as historical evidence, not a current source of truth	citeturn19search0turn22search1
STM32	Good practical list exists, but the main list repo is community-run rather than a formal ST software repo	stm32duino/Arduino_Core_STM32	Very useful operationally, but not equivalent to a vendor-owned PID policy repository	citeturn35search4turn17search0
Nordic	Official GitHub evidence is thin and fragmented: vendor-wide udev rules plus one archived repo with one explicit pair	NordicSemiconductor/nrf-udev	I did not find a public, centralized Nordic allocation table during this review	citeturn32view0turn40search0

How to verify in a local clone

The following commands are the quickest way to validate the files above in your own clone. They are also the easiest way to bulk-audit new repos you discover.

Clone and inspect

git clone https://github.com/raspberrypi/usb-pid.git
git clone https://github.com/espressif/usb-pids.git
git clone https://github.com/arduino/ArduinoCore-avr.git
git clone https://github.com/arduino/ArduinoCore-samd.git
git clone https://github.com/espressif/arduino-esp32.git
git clone https://github.com/adafruit/Adafruit_nRF52_Arduino.git
git clone https://github.com/SiliconLabs/arduino.git
git clone https://github.com/stm32duino/Arduino_Core_STM32.git
git clone https://github.com/NordicSemiconductor/nrf-udev.git

The repo/file paths above come directly from the repositories cataloged in this report. citeturn37search1turn38search1turn37search3turn26search0turn38search2turn17search2turn26search1turn17search0turn32view0

Grep for the common patterns

# Markdown allocation tables
grep -RniE '0x[0-9A-Fa-f]{4}.*\|' usb-pid usb-pids

# Arduino-style board package manifests
grep -RniE '(^[^#].*\.(vid|pid)\.[0-9]+=|^[^#].*\.build\.(vid|pid)=)' \
  ArduinoCore-avr ArduinoCore-samd arduino-esp32 Adafruit_nRF52_Arduino arduino Arduino_Core_STM32

# USB descriptor constants in code
grep -RniE 'USB_VID|USB_PID|idVendor|idProduct' .

Pull raw files directly

curl -L https://raw.githubusercontent.com/raspberrypi/usb-pid/main/Readme.md | sed -n '25,55p'
curl -L https://raw.githubusercontent.com/espressif/usb-pids/main/allocated-pids.txt | sed -n '1,20p'
curl -L https://raw.githubusercontent.com/espressif/usb-pids/main/allocated-pids-espressif-devboards.txt | sed -n '1,25p'
curl -L https://raw.githubusercontent.com/arduino/ArduinoCore-avr/master/boards.txt | grep -E '^(leonardo|micro|uno)\.'
curl -L https://raw.githubusercontent.com/arduino/ArduinoCore-samd/master/boards.txt | grep -E '^(arduino_zero_native|mkr1000|nano_33_iot)\.'
curl -L https://raw.githubusercontent.com/espressif/arduino-esp32/master/boards.txt | grep -E '^(esp32s2|esp32s2usb|um_tinys2|lolin_s2_mini)\.'
curl -L https://raw.githubusercontent.com/adafruit/Adafruit_nRF52_Arduino/master/boards.txt | grep -E '^(feather52840|itsybitsy52840|cluenrf52840)\.'
curl -L https://raw.githubusercontent.com/SiliconLabs/arduino/main/boards.txt | grep -E '^(nano_matter|xiao_mg24)\.'
curl -L https://raw.githubusercontent.com/NordicSemiconductor/nrf-udev/main/nrf-udev_1.0.1-all/lib/udev/rules.d/71-nrf.rules

Parse into CSV quickly

python3 - <<'PY'
import re, sys, pathlib

roots = [pathlib.Path(p) for p in sys.argv[1:]]
pat = re.compile(r'([^./\s]+)\.(?:build\.)?(vid|pid)(?:\.(\d+))?=(0x[0-9A-Fa-f]+)')
print("file,board,key,index,value")
for root in roots:
    for p in root.rglob("*"):
        if not p.is_file():
            continue
        try:
            text = p.read_text(encoding="utf-8", errors="ignore")
        except Exception:
            continue
        for m in pat.finditer(text):
            board, key, idx, value = m.groups()
            print(f"{p},{board},{key},{idx or ''},{value}")
PY ArduinoCore-avr ArduinoCore-samd arduino-esp32 Adafruit_nRF52_Arduino arduino Arduino_Core_STM32

Device-side verification after flashing

# Linux
lsusb | grep -Ei '303a|2e8a|239a|0483|1915|2341|2a03'

# macOS
system_profiler SPUSBDataType

# Windows PowerShell
Get-PnpDevice -PresentOnly | Select-String -Pattern 'VID_|PID_'

These host-side commands are a good final check that the firmware or board package is actually enumerating with the expected pair. Adafruit’s guides also describe lsusb / host-side VID/PID inspection as a practical verification path. citeturn23search1turn23search3

Update timeline and vendor policy links

Among the sources reviewed, the following six repos are the most useful to watch for change because they are either allocation registries or high-value board-definition manifests with USB IDs. The dates below are the last observed repo update or latest release date surfaced in the sources I reviewed. citeturn35search4turn37search0turn38search2turn40search1turn40search2turn33search1

timeline
    title Last-observed update dates for six high-value repos
    2025-07-28 : SiliconLabs/arduino latest release 3.0.0
    2025-11-18 : raspberrypi/usb-pid repo updated
    2025-05-30 : adafruit/Adafruit_nRF52_Arduino latest release 1.7.0
    2026-04-12 : espressif/arduino-esp32 latest release v3.3.8
    2026-05-21 : arduino/ArduinoCore-avr latest release 1.8.8
    2026-05-27 : stm32duino/Arduino_Core_STM32 repo updated

Loading

The most authoritative vendor policy pages I found are these:

Vendor	Authoritative page	Why it matters	Sources
Raspberry Pi	USB identifiers documentation	Explains when third-party RP2040/RP2350 boards may need unique PIDs and points users to the usb-pid repo	citeturn23search6turn23search10
Espressif	espressif/usb-pids README	Explains the PID-sharing policy under VID 0x303A, who can use it, and the pull-request process	citeturn38search1
Adafruit	How to Add a New Board to CircuitPython FAQ	Explains why CircuitPython expects a unique VID:PID per board and gives an explicit Adafruit example (239A:8023)	citeturn23search4turn23search9

Open questions and limitations

This report is strongest for Raspberry Pi, Espressif, and the Arduino-style board-core ecosystems. It is weaker for NXP, Microchip, and TI because, in the official GitHub sources I reviewed, I did not locate a single public allocation registry equivalent to Raspberry Pi’s or Espressif’s. That absence may mean the list is private, embedded in SDK examples rather than centralized, or published somewhere outside GitHub. citeturn15search1turn15search6turn14search0turn14search5turn19search0

Nordic’s public GitHub evidence is also incomplete for this specific use case: I found official USB-ID artifacts, but not a centralized public allocation list. So if your downstream task is to build a machine-readable cross-vendor database, you will get the best results by treating Raspberry Pi and Espressif as first-class allocation sources, and treating most other repos here as board-manifest sources rather than formal PID registries. citeturn37search1turn38search1turn32view0turn40search0