

Adapter
TinyGo firmware for an RP2350-based USB/PoE-LAN instrument gateway: bridges USBTMC/USB488 and HiSLIP to GPIB
- Size
- 62 × 67 mm
- Copper layers
- 4
- Thickness
- 1.61 mm
- Parts
- 92
- Nets
- 116
- Pads
- 381
- Tracks, vias
- 1,208, 102
- Pours
- 3
- Routed
- Yes
- KiCad
- KiCad 10.0 (file 20260206)
- Created
- 23 Sep 2026
- Updated
- 14 Oct 2026
Overview
Adapter is an open-source printed circuit board by tridentsx, from the tridentsx/tmc-gateway repository on GitHub. It is a 4-layer board of 62 × 67 mm with 92 parts on 116 nets, routed with 1,208 tracks and 102 vias.
It is built around the RP2354A, SN75160BDW and SN75161BDW, with the DP9900LPB-5V1.4A, AP2114H-3.3TRG1 and W5500 among its other parts. Its parts include 30 resistors, 26 capacitors, 6 ICs, 4 connectors and 3 diodes. It belongs with the interfaces and adapters boards and the RP2350 boards of this library.
Main components
12RP2354A
QFN-60(7x7)150MHz 32 Bit ARM Cortex-M33 Built-in+External Power-on reset (POR)、Undervoltage detection (BOR/LVD/LVR/LVI)、Watchdog reset、Built-in general-purpose timer、Integrated LDO、Calendar function、True random number generator (TRNG)、Hardware ECC check、Independent watchdog (IWDG) QFN-60(7x7) Microcontrollers (MCU/MPU/SOC) ROHSRaspberry PiMicrocontrollers (MCU/MPU/SOC)SN75160BDW
SOIC-20-300mil0℃~+70℃ 1 20ns@5V,15pF 4.75V~5.25V 48mA 5.2mA 8 Bidirectional Open-drain SOIC-20 Buffers, Drivers, Receivers, Transceivers ROHSTexas InstrumentsBuffers, Drivers, Receivers, TransceiversSN75161BDW
SOIC-20-300mil0℃~+70℃ 1 110mA 20ns@5V,30pF 4.75V~5.25V 48mA 5.2mA 8 Bidirectional Power-off isolation、Output enable SN75161B Schmitt trigger Tri-State SOIC-20-300mil Buffers, Drivers, Receivers, Transceivers ROHSTexas InstrumentsBuffers, Drivers, Receivers, TransceiversDP9900LPB-5V1.4A
SMDSMD Ethernet Modules ROHSSDAPOEthernet ModulesAP2114H-3.3TRG1
SOT-223-40℃~+85℃@(Ta) 1 1A 3.3V 30uVrms 450mV@(1A) 65dB@(1kHz) 65uA 6V Fixed Over Current Protection、Over Temperature Protection Positive SOT-223 Voltage Regulators - Linear, Low Drop Out (LDO) Regulators ROHSDiodes IncorporatedVoltage Regulators - Linear, Low Drop Out (LDO) RegulatorsW5500
LQFP-48_7x7-40℃~+85℃ 10BASE-T、100BASE-TX 3.3V 32KB SPI SPI Wake-up function、Programmable LED indication、Low-power mode Yes LQFP-48(7x7) Ethernet Controllers ROHSWIZNETEthernet ControllersMB6S-TP
MBS-55℃~+150℃ 1V@0.4A 35A 500mA 5uA@600V 600V Single-Phase Rectifier MBS Bridge Rectifiers ROHSMicro Commercial ComponentsBridge Rectifiers112-024-113R001
插件插件 New Arrivals ROHSNorCompUncategorisedCF4012M00012001
SMD3225-4P-40℃~+85℃ 12MHz 12pF 40Ω Crystal Oscillator ±10ppm ±30ppm SMD3225-4P Crystals ROHShuaxindianziCrystalsX322525MOB4SI
SMD3225-4P-40℃~+85℃ 12pF 25MHz 50Ω Crystal Oscillator ±10ppm ±20ppm SMD3225-4P Crystals ROHSYXCCrystalsAO3401A
SOT-231 P-Channel 14nC@10V 30V 47mΩ@10V、60mΩ@4.5V、85mΩ@2.5V 4A 55pF 645pF 80pF 900mV SOT-23 MOSFETs ROHSAlpha & Omega SemiconductorMOSFETsHH-1M1608-121JT
06030603 New Arrivals ROHSTT ElectronicsUncategorised
README
README.mdtmc-gateway
A PoE Ethernet- and USB-attached GPIB instrument gateway: one small board, plugged directly into an instrument's IEEE-488 connector, that exposes it to the network and to USB simultaneously.
What it does
One RP2354A-based adapter per GPIB instrument, acting as that instrument's GPIB System Controller and Controller-in-Charge, reachable over:
- HiSLIP (IVI-6.1) over Ethernet/PoE, TCP port 4880
- USBTMC and its USB488 subclass over USB
- Raw SCPI over TCP port 5025 (planned; not yet built)
The central architectural rule, carried over from the design specification:
HiSLIP, USBTMC/USB488, raw SCPI, and any future management interface never manipulate GPIB pins directly. They submit operations to one serialized GPIB engine.
That engine is gpib.Instrument — see
Software below.
Hardware
| MCU | RP2354A (RP2350 family, 2 MB integrated flash), QFN-60 |
| Ethernet | WIZnet W5500 (SPI) |
| PoE | DP9900LPB isolated PD module, IEEE 802.3af, with a USB-C alternate power path (§30.1) |
| GPIB transceivers | TI SN75160B (data bus) + SN75161B (management bus) |
| GPIB connector | 24-pin IEEE-488, NorComp 112-024-113R001 |
| USB | USB-C (USBTMC/USB488, plus alternate power input) |
Board is 62×68 mm, 4 copper layers. Schematic is complete and verified —
confirmed by actually running the checks below, not just citing an old note:
scripts/netlist-check.py reports 124 checks, 0 failures; ERC reports 3
pin_not_driven errors, all on W5500 (U2) SPI inputs (SCS/SCLK/MOSI)
flagged because the driving RP2354A pins are bidirectional across a
hierarchical sheet link — a severity-policy question, not a wiring defect.
PCB has all 93 footprints placed but is not yet routed.
docs/design-spec.md— the master design specification. One document by design: Part I is the HiSLIP library (tridentsx/hislip, developed in that separate repository), Part II is this hardware, Part III is this firmware, and Parts IV–VII (milestones, acceptance criteria, design decisions, risk register) span all three. Source comments inhislipcite it by section, e.g. "§5.1".docs/netlist-spec.md/docs/netlist-spec.nets— the canonical net tablescripts/netlist-check.pyverifies the exported schematic netlist against.docs/rp2354a-pinmap.md— the RP2354A GPIO assignment: 8 data lines and the DAV/NDAC/NRFD handshake lines suggested for PIO, ATN/SRQ/REN/IFC/EOI as plain GPIO, SPI0 to the W5500.
Software
gpib/ the Instrument abstraction every front end drives (no
firmware, no bus driver -- just the interface)
hislipfront/ adapts gpib.Instrument to tridentsx/hislip's server.Device
usbtmcfront/ adapts gpib.Instrument to USBTMC/USB488 Bulk-OUT messages
usbep/ portable, unit-tested USB packet reassembly (host->device)
and chunking (device->host) usbtmcfront's messages ride on
cmd/firmware/ the real (skeleton) RP2354A firmware entry point --
tinygo-only, gated by the "tinygo" build tag
cmd/tinygocheck/ not firmware -- exists so `just tinygo` has a real main
package to build and link, exercising gpib/hislipfront/
usbtmcfront together under mainline go's dependency
graph but a real tinygo build
cmd/debugconsole/ host-side only (plain go build, no tinygo tag): a
terminal UI for cmd/firmware's CDC debug consolegpib.Instrument is deliberately not a copy of hislip/server.Device,
despite both stating the identical "must not know it's GPIB" principle:
RemoteEnable, LocalLockout, and GoToLocal are three separate methods
here, because USB488's own control requests (REN_CONTROL, GO_TO_LOCAL,
LOCAL_LOCKOUT) are three separate requests, not HiSLIP's one combined
RemoteLocal(mode) call. Both front ends translate onto the same granular
primitives instead of one needing to reconstruct a combined mode it never
actually received.
Status
| Piece | State |
|---|---|
gpib.Instrument abstraction | Defined |
hislipfront (HiSLIP → gpib.Instrument) | Implemented, unit-tested |
usbtmcfront (USBTMC/USB488 → gpib.Instrument) | Core Bulk-OUT dispatch implemented, unit-tested — see scope below |
usbep (USB packet reassembly/chunking) | Implemented, unit-tested — real edge cases (exact-multiple-of-packet-size, empty message, byte-at-a-time feed) |
cmd/firmware (real USB descriptor + endpoint wiring) | Skeleton exists and actually builds: tinygo build -target=pico2 produces a real, well-formed flashable UF2. Backed by a stub gpib.Instrument — no real GPIB bus driver yet. Verified on real hardware (a W5500-EVB-Pico2, RP2350): descriptor enumerates exactly as designed, and a real USBTMC RequestDevDepMsgIn round trip over EP3 OUT/IN produces a correctly encoded response — see below. |
GPIB bus driver (the concrete gpib.Instrument) | Not started |
| Raw SCPI front end | Not started |
Real, load-bearing constraints found by reading TinyGo 0.42.0's actual
machine/usb source (not assumed): it hardcodes a maximum of 3 USB
interfaces total (a fixed-size array, not a slice), so a USB CDC debug
console (2 interfaces) plus USBTMC (1) exactly fills the budget, with no
room left for anything else on this port. Its outgoing-transfer path does
not itself split a payload larger than one packet across multiple
packets — that's what usbep.ChunkSender and cmd/firmware's
TxHandler callback do, deliberately, rather than being handled for free
by the framework.
usbtmcfront's stated scope, deliberately not (yet) covered:
- Works on one already-reassembled logical USBTMC message, not raw USB
transfers — splitting a message across several USB packets and the
alignment padding USBTMC requires between messages is a transport-framing
concern for whatever wires it to a real USB endpoint later, the same
split
hislip/server'sStreamabstraction makes. - TermChar-based early read termination is decoded but ignored.
- Every control-transfer-based USBTMC/USB488 request —
GET_CAPABILITIES,INITIATE_CLEAR,READ_STATUS_BYTE,REN_CONTROL,GO_TO_LOCAL,LOCAL_LOCKOUT, the abort requests — is not implemented at all; only the three Bulk-OUT message types (DevDepMsgOut,RequestDevDepMsgIn,Trigger) are.
One real, non-mechanical piece of protocol work is still open before the bus driver can start: the real IEEE-488.1 three-wire handshake and ATN-based addressing. Nothing here has been verified against real GPIB hardware yet; treat any bus-timing claim in this repo's history as reasoned from the spec text, not measured.
Real-hardware findings (cmd/firmware, W5500-EVB-Pico2 / RP2350)
Confirmed by actually flashing and exercising the board, not just building for it:
- The composed descriptor (CDC debug console + USBTMC/USB488) enumerates
exactly as designed: 3 interfaces, correct classes (CDC
0x02/0x02/0x010x0A/0x00/0x00, USBTMC/USB4880xFE/0x03/0x01), correct endpoint addresses (0x03/0x83for the shared USBTMC bulk endpoint).
- A real
RequestDevDepMsgInBulk-OUT write followed by a Bulk-IN read, issued from the host with go-usb, round-trips correctly end to end throughusbtmcRxHandler→usbep.Reassembler→usbtmcfront.Handler→usbep.ChunkSender→usbtmcTxHandler. - Two real firmware bugs were found and fixed this way, both specific to
running inside TinyGo's bare-metal USB interrupt handlers, not to the
protocol logic itself:
main()calledmachine.EnableCDCa second time. TinyGo's own runtime (initUSB, which runs beforemain) already calls it viamachine/usb/cdc.EnableUSBCDCwith working handlers; the redundant call overwrote them with no-op stubs, silently breaking the debug console.usbtmcRxHandlercalledprintln,reasm.Feed,append, andusbtmcfront.Handler.HandleBulkOutdirectly — all either blocking or allocating — from inside a USB interrupt handler. TinyGo's bare-metal allocator is not interrupt-safe, so this corrupted state the moment a real bulk transfer arrived. The handler now only copies the raw packet into a fixed-size ring with a plain array copy (no allocation, no blocking); reassembly, dispatch, and response encoding all run in the main loop instead, which drains that ring alongside a lightweight event log and a heartbeat print, giving an unambiguous liveness signal during this kind of debugging.
Built for the next real-hardware session, not just this one:
cmd/firmware's CDC console is now interactive (help/version/
stats/last/clear/uptime/ping), backed by persistent counters
(packets in, messages reassembled, responses sent, ring overflows, TX
failures) and a bounded hex dump of the last message/response — confirmed
working on real hardware, including the counters incrementing correctly
across a real bulk transfer and last showing the exact bytes exchanged.
See cmd/firmware/debug.go. version reports the exact git commit (plus
-dirty if built from an uncommitted tree) and build time, baked in by
just firmware's -ldflags -X, so it's possible to confirm which build
is actually running on a given board.
cmd/debugconsole is the host-side companion: a terminal UI
(go run ./cmd/debugconsole, or just debugconsole) with a menu of the
commands above plus a free-text box for anything not in that list yet,
so a real-hardware session doesn't mean hand-typing into screen/
picocom/a pyserial script. Plain go build, no tinygo tag — runs on
the development machine against an already-flashed, already-connected
board, never on the RP2350 itself.
Related repositories
- tridentsx/hislip — the HiSLIP protocol/server/client library
this board's Ethernet-side front end is built on. Intended, once
finished, to be offered to the
gotmcorganisation. - tridentsx/usbtmc — a fork of gotmc/usbtmc
adding a driver backed by tridentsx/go-usb (no cgo, no
libusb), intended to be contributed upstream. Its new
wiresubpackage is the USBTMC wire-format vocabulary this board's USB-side front end will build on. - tridentsx/go-usb — the pure-Go USB backend behind the
usbtmcdriver above.
Building what exists today
go build ./...
go vet ./...
go test ./...kicad-cli sch export netlist --format kicadsexpr -o build/adapter.net hardware/adapter.kicad_sch
python3 scripts/netlist-check.py docs/netlist-spec.nets build/adapter.net # expect 131/0
kicad-cli sch erc --severity-error -o /tmp/erc.rpt hardware/adapter.kicad_schParts
92| Qty | Value | Footprint | References |
|---|---|---|---|
| 9 | 100n | Capacitor_SMD:C_0805_2012Metric | C2, C3, C4, C8, C9, C10, C12, C18, C22 |
| 8 | 10k | Resistor_SMD:R_0805_2012Metric | R2, R7, R9, R15, R25, R26, R27, R28 |
| 5 | 4u7 | Capacitor_SMD:C_0805_2012Metric | C5, C6, C7, C13, C17 |
| 4 | 3R3 | Resistor_SMD:R_0805_2012Metric | R20, R21, R22, R23 |
| 4 | 49R9 | Resistor_SMD:R_0805_2012Metric | R10, R12, R13, R17 |
| 3 | 1u | Capacitor_SMD:C_0805_2012Metric | C16, C23, C24 |
| 2 | 0R | Resistor_SMD:R_0805_2012Metric | R1, R11 |
| 2 | 100k | Resistor_SMD:R_0805_2012Metric | R6, R8 |
| 2 | 15p | Capacitor_SMD:C_0805_2012Metric | C25, C26 |
| 2 | 18p | Capacitor_SMD:C_0805_2012Metric | C14, C15 |
| 2 | 330 | Resistor_SMD:R_0805_2012Metric | R16, R24 |
| 2 | 4k7 | Resistor_SMD:R_0805_2012Metric | R4, R5 |
| 2 | 5k1 | Resistor_SMD:R_0805_2012Metric | R29, R30 |
| 2 | MB6S-TP | adapter:MBS_L4.7-W4.0-P2.50-LS7.0-TL | D1, D2 |
| 2 | MountingHole_Pad | MountingHole:MountingHole_3.2mm_M3_Pad | H1, H2 |
| 1 | 10R | Resistor_SMD:R_0805_2012Metric | R3 |
| 1 | 10n | Capacitor_SMD:C_0805_2012Metric | C19 |
| 1 | 10u | Capacitor_SMD:C_0805_2012Metric | C11 |
| 1 | 112-024-113R001 | adapter:CONN_112-024-113R001_NRC | J1 |
| 1 | 12MHz | Crystal:Crystal_SMD_3225-4Pin_3.2x2.5mm | X1 |
| 1 | 12k4 | Resistor_SMD:R_0805_2012Metric | R19 |
| 1 | 1M | Resistor_SMD:R_0805_2012Metric | R14 |
| 1 | 1k | Resistor_SMD:R_0805_2012Metric | R18 |
| 1 | 1n | Capacitor_SMD:C_0805_2012Metric | C1 |
| 1 | 22n | Capacitor_SMD:C_0805_2012Metric | C21 |
| 1 | 25MHz | Crystal:Crystal_SMD_3225-4Pin_3.2x2.5mm | X2 |
| 1 | 2N7002 | Package_TO_SOT_SMD:SOT-23 | Q2 |
| 1 | 3u3 | Inductor_SMD:L_0805_2012Metric | L1 |
| 1 | 47u/16V | Capacitor_SMD:C_1206_3216Metric | C20 |
| 1 | AO3401A | Package_TO_SOT_SMD:SOT-23 | Q1 |
| 1 | AP2114H-3.3TRG1 | adapter:SOT-223_L6.7-W3.5-P2.30-BR | U5 |
| 1 | DP9900LPB-5V1.4A | adapter:COMM-SMD_DP9900LPB-5V1.4A | M1 |
| 1 | HH-1M1608-121JT | Inductor_SMD:L_0603_1608Metric | L2 |
| 1 | HR871150C | adapter:RJ45-TH_HR871150C | J2 |
| 1 | PWR_SEL | Connector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_Vertical | J4 |
| 1 | RP2354A | adapter:QFN-60_L7.0-W7.0-P0.40-TL-EP3.4 | U1 |
| 1 | SN75160BDW | Package_SO:SOIC-20W_7.5x12.8mm_P1.27mm | U3 |
| 1 | SN75161BDW | Package_SO:SOIC-20W_7.5x12.8mm_P1.27mm | U4 |
| 1 | TPS3839G33DBZR | Package_TO_SOT_SMD:SOT-23 | U6 |
| 1 | TP_3V3 | TestPoint:TestPoint_Pad_D1.5mm | TP_3V3 |
| 1 | TP_5V | TestPoint:TestPoint_Pad_D1.5mm | TP_5V1 |
| 1 | TP_ATN | TestPoint:TestPoint_Pad_D1.5mm | TP_ATN1 |
| 1 | TP_DAV | TestPoint:TestPoint_Pad_D1.5mm | TP_DAV1 |
| 1 | TP_DC | TestPoint:TestPoint_Pad_D1.5mm | TP_DC1 |
| 1 | TP_GND | TestPoint:TestPoint_Pad_D1.5mm | TP_GND1 |
| 1 | TP_GPIO22 | TestPoint:TestPoint_Pad_D1.5mm | TP_GPIO221 |
| 1 | TP_IFC | TestPoint:TestPoint_Pad_D1.5mm | TP_IFC1 |
| 1 | TP_NDAC | TestPoint:TestPoint_Pad_D1.5mm | TP_NDAC1 |
| 1 | TP_NRFD | TestPoint:TestPoint_Pad_D1.5mm | TP_NRFD1 |
| 1 | TP_SRQ | TestPoint:TestPoint_Pad_D1.5mm | TP_SRQ1 |
| 1 | TP_SWCLK | TestPoint:TestPoint_Pad_D1.5mm | TP_SWCLK1 |
| 1 | TP_SWDIO | TestPoint:TestPoint_Pad_D1.5mm | TP_SWDIO1 |
| 1 | TP_TE | TestPoint:TestPoint_Pad_D1.5mm | TP_TE1 |
| 1 | USB-C | adapter:USB-C_SMD-TYPE-C-31-M-12_1 | J3 |
| 1 | W5500 | Package_QFP:LQFP-48_7x7mm_P0.5mm | U2 |
| 1 | green | LED_SMD:LED_0805_2012Metric | LED1 |
Similar boards
- 2 layers85 × 56 mm

- 2 layers160 × 100 mm

Csa petio v1
fachat/csa_cbmio
IO Board for CS/A bus, to implement Commodore B-Series I/O
99 partsGPL-3.0 - 2 layers58 × 99.8 mm

Senior Capstone
achihuahua22/Alex-Harris-Capstone
This project builds on an-ven’s graspib project by adding more RS232 support and a UART breakout pin.
38 parts1MIT - 2 layers90.2 × 72.8 mm

- 2 layers119.4 × 96.5 mm

- 4 layers280 × 80 mm

Iteration3
Arjit40/Underwater-ROBOT-PCB-with-stm32h473vit6-and-ethernet-W5500-IC--iteration-3
165 parts - 4 layers50 × 21.4 mm

- 2 layers37.3 × 63.9 mm

Questions
How big is the Adapter PCB?
It measures 62 × 67 mm and has 4 copper layers, 1.61 mm thick.
What parts does the Adapter use?
92 parts, built around the RP2354A, SN75160BDW, SN75161BDW and DP9900LPB-5V1.4A. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
Where can I download the Adapter KiCad files?
From the tridentsx/tmc-gateway repository on GitHub, at the commit this page was made from: the board is hardware/adapter.kicad_pcb and its schematic hardware/adapter.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Can I use the Adapter design in my own project?
Its repository states no licence, so its author keeps all rights: ask tridentsx before reusing the design.