Skip to the content
6 layers147.8 × 71.1 mmFascia, the printed circuit board in 3D

Companion KiCad project for "Fascia", a 10-inch Android Automotive touch display head unit: sibling to manifold-pcb, thermo-pcb and ecu-pcb, same 12V automotive constraints as the rest of the family.

Size
147.8 × 71.1 mm
Copper layers
6
Thickness
1.6 mm
Parts
118
Nets
129
Pads
825
Tracks, vias
3,716, 247
Pours
2
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
16 Aug 2026
Updated
11 Oct 2026

Overview

Fascia is an open-source printed circuit board by jessiepullaro414, from the jessiepullaro414/Fascia repository on GitHub, published under the MIT licence. It is a 6-layer board of 147.8 × 71.1 mm with 118 parts on 129 nets, routed with 3,716 tracks and 247 vias.

It is built around the TLV767-Q1DRB. Its parts include 47 resistors, 38 capacitors, 9 ICs, 8 connectors and 4 transistors.

Main components

1

README

README.md

Fascia — KiCad schematic + PCB

Companion KiCad project for "Fascia", a 10-inch Android Automotive touch display head unit: sibling to manifold-pcb, thermo-pcb and ecu-pcb, same 12V automotive constraints as the rest of the family.

Unlike the rest of the family this is a two-board project, because the panel is physically detached from the main board and sits across the dash from it:

  1. Carrier board (behind the dash) — a Toradex Verdin iMX95 System on Module on a custom carrier: automotive 12V front end, LVDS display output via a DSI-to-LVDS bridge, backlight control, CAN FD to talk to ecu-pcb, line-level audio pre-outs to an external amplifier, a microphone input, and USB-C for wired CarPlay / Android Auto.
  2. Panel board (in the bezel) — terminates the ribbon at the screen: panel LVDS connector, capacitive touch controller, backlight LED connector.

Bluetooth and Wi-Fi need no carrier hardware — they come with the module's WB variant.

Module: Verdin iMX95 Hexa 8GB Wi-Fi / Bluetooth IT (Toradex PN 0089, 6x Cortex-A55, 8 GB RAM, 32 GB eMMC, -40 to +85 C, $627.25 at quantity 1-99 on 2026-09-30). Chosen over the 4 GB WB IT (PN 0226, $408.15) for headroom: Android Automotive plus a wired CarPlay / Android Auto projection stream is the heavy case, and RAM cannot be added later. The non-WB parts are out because the board relies on the module's wireless. The Verdin modules are pin-compatible, so this can be revisited without a board change.

Status

PCB placed and routed to within 3 connections. build_pcb.py generates Fascia.kicad_pcb: 118 footprints, 574 pads netted across 129 nets, six layers, on a 148 x 71 mm board. route_board.py (ported from the sibling boards) routes it with FreeRouting, widens the power trunks, pours GND on In1 and In4, and then asks kicad-cli DRC how many connections are really open. After a 150-pass run 3 connections are still unrouted: AOUT_RL_N (codec to the audio connector), U9_ADR1_TIE, and LVDS_A_Y0N (bridge to panel connector). FreeRouting oscillated between 3 and 4 for the last 100 passes, so more passes of the same run will not close them; they need a second stochastic attempt or hand-routing. run_drc.py reports schematic parity 0, 12 lib_footprint_mismatch findings that are a KiCad tooling artifact, and one silkscreen-over-mask finding.

Nothing about the differential pairs is tuned: FreeRouting does not length-match, so the DSI and dual-link LVDS pairs are ordinary routed nets with no impedance control. route_board.py prints the resulting intra-pair skew so it is a number, not a guess.

Placement uses the same skyline bottom-left packer as manifold-pcb and thermo-pcb, ported rather than reinvented, with three additions this board needed:

  • Every part is tried both unrotated and rotated 90 degrees, and goes wherever it yields the lowest resulting top edge. That is what turns the tall pin-header connectors on their sides and lets the 0603s backfill the low spots beside the big parts.
  • Keepouts are real packer inputs, not checks applied afterwards.
  • The bridge, socket and panel connector are placed first (PIN_FIRST in build_pcb.py), so the DSI-to-LVDS bridge sits beside the Verdin socket instead of 75 mm away. Area order alone had put it there, and nearly every open net in the first routing run was at that bridge.
  • A passive goes near its own IC (PULL). Once its anchor IC is down, a passive takes the slot closest to it, with a height penalty so it cannot strand a void below. Plain lowest-gap order had put a pull-up 130 mm from the chip it belongs to. Estimated wirelength fell from 7,612 to 5,895 mm (tools/placement_metric.py), and FreeRouting at 12 passes went from 22 unrouted to 4.
  • Spacing between parts (CLEAR) is 2.0 mm, up from 1.3. That alone took 12-pass routing from 22 unrouted to 11, at a cost of 7 mm of height.

Group membership is derived from the netlist: each part joins whichever IC or connector it shares the most non-rail nets with. Rails are excluded deliberately: GND touches everything and would make every part look equally related to everything else.

The Verdin socket is rotated 90 degrees as part of that. Its footprint is 36 x 79 mm, tall and narrow; on its side it is 79 x 36 mm and the board becomes landscape, which is also the shape a dash opening wants.

Schematic complete — every block wired except the backlight. build_schematic.py generates a real, KiCad-loadable schematic containing the Verdin iMX95 X1 connector, the 12 V automotive front end, the 5 V buck, the 1.8 V and 3.3 V rails, CAN FD, the SN65DSI85-Q1 DSI-to-LVDS bridge, the PCM3168A-Q1 audio subsystem with its level shifters, the USB-C port, and the control/sequencing block. No PCB yet.

kicad-cli sch erc reports 10 violations, and every one is either blocked on a datasheet that has not arrived or deliberately optional:

WhatCountWhy it is still open
PWM_3_DSI, GPIO_10_DSI2Backlight — needs the iFan string voltage and current
USB_2_*4Panel touch link — needs the panel's touch interface confirmed
CAN_2_*2Optional second CAN bus; no consumer chosen
DSI_IRQ1Bridge interrupt; wants a spare 1.8 V module GPIO
IGN_SENSE1Ignition sense; wants a module ADC input

160 pins carry real NoConnect items and 40 signal nets are wired.

Footprints are assigned and verified. Every part maps to a real footprint, and the build checks that each named file actually exists — a mistyped library path is otherwise invisible until the netlist reaches the PCB editor and silently drops the part.

The LM61460-Q1 footprint is generated, not borrowed

TI's RJR0014A (VQFN-HR-14) has no KiCad library footprint, and it is not something a generic QFN generator can produce: the pads are all different sizes, unevenly spaced, and the four corner pads are L-shaped.

tools/build_lm61460_footprint.py builds it. The geometry is not eyeballed off the drawing — the LAND PATTERN EXAMPLE on page 55 of TI SNVSB70F is real vector art, so the pad rectangles were extracted from the PDF's own path data and only the scale had to be inferred, from a dimension the drawing states outright (pad 10 is 2.4 × 0.4 mm). That scale then reproduced pad 10's 0.400 mm height exactly, which is what makes the rest of the extraction trustworthy.

Each L-shaped pad is built from two rectangles sharing one pad number — a real KiCad construction this project has met before, in a Keystone fuse holder with two physical pads both numbered "1". It is far safer than approximating an L with its bounding box, which would put copper in the notch and eat the clearance to the neighbouring pads.

All four notches face the outer corner of the pattern, confirmed by rendering the drawing around pads 1, 9 and 11 rather than assuming the symmetry held.

The generator verifies itself twice: internally, that the pad table is coherent (pin numbering, which pads are L-shaped, pad 10's dimensions, overall extent, and that no two different pins overlap), and then by loading the result back through KiCad's own engine. That second check earned its place immediately — the first version emitted trailing ; PINNAME comments on the pad lines, and KiCad's s-expression format has no comment syntax, so the whole library failed to load with nothing more useful than "Unable to load library".

The Verdin module plugs into a standard DDR4 SODIMM socket, and KiCad's SODIMM-260_DDR4_H4.0-5.2_OrientationStd_Socket has exactly 260 pads numbered 1–260 — a direct match for the extracted pinout, so the biggest footprint risk on this board turned out to be no risk at all.

Exposed pads are three different decisions

Every one of these footprints numbers its exposed pad N+1 — 65 on the TQFP-64s, 25 on the VQFN-24, 9 on the SON-8s. Each symbol therefore carries an explicit EP pin, so what happens to that pad is a visible decision on the schematic rather than an accident of the pad having no net:

PartExposed pad
LM74930-Q1NoConnect — must float. The datasheet forbids grounding it
TLV767-Q1, TPS2557-Q1GND
SN65DSI85-Q1, PCM3168A-Q1GND (PowerPAD is reference ground)

The LM74930-Q1's NoConnect is load-bearing: without an explicit pin, that pad is merely netless, and nothing on the drawing would stop a later ground-stitching pass from claiming it.

What is already final:

  • all 260 X1 pins exist, banked into 6 units
  • 47 GND pins tied to ground, 5 VCC pins tied to +5V
  • 158 unused pins carrying real NoConnect items
  • LM74930-Q1 front end fully wired — back-to-back FETs with A and OUT on the shared source node, sense resistor with its 50 Ω tap into CS+, OVCLAMP tied to OV for clamp-with-breaker rather than plain disconnect, and the OV/UVLO dividers, timer, ILIM and IMON networks
  • LM61460-Q1 5 V buck fully wired — BIAS to the output rail (valid because Vout ≤ 12 V), boot network through RBOOT, FB and EN dividers, RT, and pull-ups on the open-drain FLT and PGOOD outputs
  • TLV767-Q1 1.8 V LDO wired — an LDO rather than a buck on purpose: small load, and no switching noise added to a board carrying LVDS next to a car radio. This rail exists because the module's I/O is 1.8 V logic; it feeds the CAN transceiver's VIO now and the bridge later
  • TCAN1044V-Q1 CAN FD link wired — split termination (2×60 Ω with a midpoint capacitor to ground, which shunts common-mode noise on a bus leaving the enclosure on a harness), separate 5 V VCC and 1.8 V VIO decoupling, and a pull-down on STB because the part's internal pull-up would otherwise wake it in standby
  • the module's CAN_1_TX / CAN_1_RX now reach the transceiver
  • SN65DSI85-Q1 bridge wired — DSI channel A in, both LVDS links out, all twelve VCC pins on 1.8 V, VCORE treated as the 1.1 V output it is with its 1 µF, REFCLK resistor-pulled to ground since the pixel clock comes from the D-PHY clock, ADDR strapped low, and the unused DSI channel B inputs plus both RSVD pins left genuinely unconnected with NoConnect items rather than tied off
  • J4 panel LVDS connector, provisional — carries all 20 LVDS signals, but its real pin order and pin count await the panel datasheet
  • PCM3168A-Q1 audio codec wired — five differential pre-outs (front L/R, rear L/R, sub) to J5, microphone into the first differential ADC input, TDM on DIN1, MODE strapped low for the I2C control port
  • A 3.3 V rail and two SN74AXC4T245-Q1 level shifters, because the codec's digital domain cannot be wired directly to the module — see "The audio block needs level shifters" below
  • I2C crosses domains through the classic two-FET translator rather than a push-pull part, which cannot pass an open-drain bus
  • USB-C port wired — TPS2557-Q1 switching VBUS with a ~3.3 A limit, Rp resistors on both CC pins advertising 3 A from a downstream-facing port, ID strapped low for host mode, a divided VBUS sense back to the module, and ESD on every pin a passenger can touch. No PD controller and no negotiation firmware.
  • Control and sequencing wired — JTAG header, power/recovery/reset buttons, and the RTC coin cell behind the ≥47 kΩ current-limiting resistor the datasheet requires (a lower value can stop the module booting). CTRL_PWR_EN_MOCI now gates the 1.8 V and 3.3 V LDOs, so the carrier rails follow the module instead of racing it at power-on.
  • every pin on all nine ICs either netted or explicitly NoConnected

The generator checks for silently merged nets

Blocks are laid out independently, so two can drift into the same region and land one net's stub endpoint exactly on another's. That merges the two nets — electrically catastrophic and near-invisible on the drawing. It happened twice while building this schematic:

  1. a codec decoupling cap's ground stub landed on the power tree's UVLO_DIV label;
  2. the USB block's USB_ILIM stub landed on connector unit D's USB1_VBUS_SENSE stub.

ERC does report this as multiple_net_names, but only for the pair it happens to notice and only after the fact. build_schematic.py now records every terminated coordinate — pin positions and stub endpoints, for both generic parts and the X1 connector — and fails loudly, naming both nets and both owning references. The first version of that check scanned only label positions and missed the second case entirely, which is why it now tracks points rather than labels.

The audio block needs level shifters (and why that is not optional)

The PCM3168A-Q1 has two supply domains: analog VCC at 4.5–5.5 V and digital VDD at 3.0–3.6 V. VDD cannot be run at 1.8 V, so the codec cannot share the module's logic level. Reading the electrical table makes the consequence sharper than "it needs a translator":

CodecVerdin
Input high, min2.0 Vdrives 1.8 V max
Output high, min2.4 V2.1 V absolute maximum

The first row means the module cannot reliably drive the codec. The second row is the dangerous one: the codec's output high is above the module's absolute maximum rating. Wired directly, the codec-to-module direction would not merely fail — it would damage the module.

So every digital line between them is translated: I2S and the clocks through SN74AXC4T245-Q1 translators, and I2C through the classic two-N-FET open-drain circuit, because a push-pull translator cannot pass a bus where either end may pull low.

What exists right now:

  • tools/extract_verdin_pinout.py — extracts the full 260-pin Verdin iMX95 X1 connector pinout from Toradex's own hardware datasheet.
  • verdin_pinout.py — the generated result: all 260 pins, 47 GND, 5 VCC, and the 20 LVDS pins, cross-checked against a second independent table in the same document.
  • verdin_x1.py — functional banking of those 260 pins into multi-unit symbol units, with a verifier that proves the banking is a true partition of the connector.
  • build_schematic.py — generates Fascia.kicad_sch, Fascia.kicad_sym, sym-lib-table and (on first run only) Fascia.kicad_pro.

Three things that were needed to get the first ERC pass down from 268 findings to the real ones, recorded because each cost a debug cycle:

  1. Power symbols must touch the net graphically. A power symbol's own pin sits at its local origin with zero length, so placing it near a connector pin leaves both dangling — 155 pin_not_connected findings. The fix is a short stub wire from the pin out to the symbol, which also keeps the symbol graphic off the pin name.
  2. PWR_FLAGs need the same graphical reachability. A flag placed in isolation, relying on name-based net merging, does not satisfy power_pin_not_driven (54 findings). Placing each flag on a real point of its net clears it.
  3. kicad-cli needs a .kicad_pro to resolve ${KIPRJMOD}. Without one it cannot find the project-local sym-lib-table and reports one lib_symbol_issues warning per placed symbol (60 findings), even though the symbols are embedded in the schematic and perfectly valid.

Everything below the "Design decisions" section is a plan, not a description of something that exists. See "Known open items".

Why X1 is banked into units

A 260-pin connector cannot be one schematic symbol — at 2.54 mm pitch a single block is ~330 mm tall, taller than any sheet this project uses. KiCad's answer is a multi-unit symbol, so verdin_x1.py assigns each pin to a unit based on how this board uses the connector:

UnitPinsContents
A55Power and ground
B16Control, sequencing, JTAG, tamper
C15Display — the DSI link to the bridge, plus backlight control
D16Communications — CAN to ecu-pcb, I2C, USB 2.0 for touch
E158Unused on this board (gets NoConnect items)

Banks are derived from pin names rather than hand-listed pin numbers, so re-running the extractor against a newer datasheet revision cannot silently desynchronise the two files. That only works if the rules stay exhaustive, which verify() enforces: every pin exactly once, nothing invented, nothing dropped, plus explicit assertions on the two groupings most worth getting right —

  • the display bank must be exactly the 15 pins from datasheet Table 22, asserted by number rather than trusted to a pattern;
  • the USB split must put the USB 2.0 data pair in the comms bank and SuperSpeed in the unused bank. This board's only USB is a 2.0 host port for the panel's touch controller, so the SS pairs are unused on purpose. Worth an explicit rule because they appear under two different naming styles — Verdin-standard USB_2_SS* and module-specific USB1_TX1_*/USB1_RX1_* — and a single USB_ pattern silently catches one and misses the other.

Bank E is not filler. Per this project's KiCad notes a deliberately unused pin needs a real NoConnect item, not a stub label, or ERC reports it as a dangling/isolated label — so the unused pins have to be enumerated as carefully as the used ones.

Why this SoC, and why not the one I started with

The project began as "10-inch Android Automotive display on an NXP i.MX 93". The i.MX 93 cannot run Android, and this was worth catching before any board work started:

  • The i.MX 93 has no 3D GPU — only the PXP 2D pixel pipeline.
  • Since Android 10, NXP has excluded GPU-less i.MX parts from Android support outright, because Android's GPU and extension requirements can't be met. Running it would mean maintaining a private Android fork on software rendering.
  • NXP's current i.MX Android BSP covers the 8M Mini/Nano/Plus/Quad, 8ULP, 8QuadMax/XPlus and i.MX 95. Not the 93.

Replaced with the i.MX 95, which has an Arm Mali-G310 (OpenGL ES 3.2, Vulkan 1.2, 2D+3D), is on NXP's Android BSP list, and is automotive qualified.

Why a SoM instead of a raw i.MX 95

A raw i.MX 95 is a 19×19 mm BGA paired with LPDDR5. That forces HDI construction (laser microvias, blind/buried vias, 12–14 layers just to escape the BGA) and roughly 90 length- and skew-matched LPDDR5 nets.

That last part is the disqualifier for this project specifically: FreeRouting cannot do length-matched differential DDR routing, so the DDR work would have to be manual — which directly contradicts this family's rule that the generator scripts are the source of truth and the board is always regenerated, never hand-edited.

Putting the SoC on a Toradex Verdin iMX95 module moves the LPDDR5 and its HDI stackup onto a part Toradex has already qualified, and leaves a carrier board that is connectors, power and differential pairs — squarely inside what the existing generate → route → verify pipeline handles.

Design decisions

Display link: 1920×1200, DSI-to-LVDS bridge on the carrier

The panel is detached and 20 cm–1 m away across the dash, so the link that crosses that gap must be LVDS — differential and low-swing, so it survives alternator and ignition noise. Options for the long run:

OptionVerdict
LVDS over shielded FFCChosen for the cable run. Robust over a dash-length ribbon, and what 10.1" panels natively accept.
MIPI DSI direct to the panelRejected. D-PHY is designed for on-PCB or very short flex (~15–20 cm); unshielded ribbon across a dash is an EMI problem.
HDMINot native on the module. Needs a DSI-to-HDMI bridge on the carrier and a receiver board behind the panel bridging back. Two extra bridges.
FPD-Link III / GMSL2The right answer for genuinely long runs (10 m+), overkill and expensive here.

How the LVDS gets generated is the part that took real work.

The module's own display ceilings, from datasheet Table 3: LVDS 1× up to 1920×1080, MIPI DSI 1× quad lane up to 4K.

The 10.1" panel market is overwhelmingly 16:10 (1280×800 and 1920×1200), not 16:9. 1920×1200 needs ~154 MHz of pixel clock, which is above the module's 1920×1080 native LVDS ceiling — both Toradex and NXP's summary cap i.MX 95 LVDS at 1080p60. Forum figures of 170 MHz for dual-channel split mode are i.MX 6, a different generation, and must not be extrapolated to this part.

So: take MIPI DSI off the module (where 1920×1200 is far inside the 4K ceiling) and convert to dual-channel LVDS on the carrier board, right at the ribbon connector, with a TI SN65DSI85-Q1 — AEC-Q100 qualified, dual-channel LVDS out, 24 bpp, pixel clock 25–154 MHz.

The DSI run stays on-PCB where D-PHY is happy (centimetres); the long, noisy dash run is still LVDS. Cost is one bridge IC.

The module's native LVDS pins (88–144) are therefore unused. They remain documented in verdin_pinout.py in case the design ever falls back to 1080p native.

Unexpected benefit: the whole DSI pin group sits on Verdin-standard Reserved pins (17–55) rather than the Module-specific pins native LVDS uses. This design is therefore more portable to other Verdin modules than the native-LVDS version would have been — it inverts the portability caveat noted below.

Confirmed DSI pin group (Verdin iMX95 datasheet Table 22), which carries not just the lanes but every control signal the bridge and backlight need:

X1 pinSignalRole
23 / 25DSI_1_D3_N / _PDSI data lane 3
29 / 31DSI_1_D2_N / _PDSI data lane 2
35 / 37DSI_1_CLK_N / _PDSI clock
41 / 43DSI_1_D1_N / _PDSI data lane 1
47 / 49DSI_1_D0_N / _PDSI data lane 0
53 / 55I2C_2_DSI_SDA / SCLSN65DSI85-Q1 configuration
17GPIO_9_DSIbridge enable
19PWM_3_DSIbacklight brightness
21GPIO_10_DSIbacklight enable

SN65DSI85-Q1: confirmed from the TI datasheet (SLLSEJ4B)

The mode this whole design depends on is explicitly supported — datasheet Table 5, "Single DSI Input to Dual-Link LVDS":

Single DSI Input on Channel A to Dual-Link LVDS output with Odd pixels on Channel A and Even pixels on Channel B.

Register configuration for that mode:

CSRFieldValue
0x10.6:5DSI_CHANNEL_MODE01 — single-channel DSI receiver
0x10.4:3CHA_DSI_LANES00 — four lanes enabled
0x18.4LVDS_LINK_CFG0 — dual-link LVDS
0x18.3CHA_24BPP_MODE1 — 24 bpp
0x18.1 / 0x18.0CHA/CHB_24BPP_FORMAT1selects Format 1 vs Format 2

Other confirmed facts that drive the schematic:

  • AEC-Q100 Grade 2, −40 °C to +105 °C ambient. Better rated than the Verdin module itself, and consistent with the rest of this family.
  • Single 1.8 V supply (VCC 1.65 / 1.8 / 1.95 V). No second rail.
  • HTQFP-64 (PAP) with thermal pad. RθJA 36.1 °C/W, max case temperature 92.2 °C — the pad needs a real thermal via field.
  • REFCLK (pin 17) is optional — the LVDS pixel clock can be sourced from the free-running D-PHY clock instead. If unused it must be pulled to ground through an external resistor, not left floating.
  • ADDR (pin 64) selects the I2C target address; if strapped high it must go to the same 1.8 V rail as VCC, not any other 1.8 V source.
  • IRQ (pin 33) is an interrupt output back to the SoC.
  • EN may be driven by GPIO_9_DSI or by an RC (≈200 kΩ + ≈200 nF). It must only go high after VCC is valid. To reset with VCC already high, EN must be held low ≥10 ms.
  • Sequencing constraint for the driver: the DSI CLK lane must be in HS and the DSI data lanes driven to LP11 while the device is in reset, before EN is asserted.
  • For 18 bpp the Y3 pairs are left NC; at 24 bpp all four data pairs per link are used — so the panel connector carries 10 pairs.
  • CHA_SYNC_DELAY must be programmed to at least 32 pixel clocks.

Everything is configured over I2C — there is no format strapping. That is a meaningful de-risking result: the VESA-versus-JEIDA mapping question is a software choice (24BPP_FORMAT1), so picking the panel later cannot force a board respin over it.

Timing margins — corrected

An earlier revision of this file claimed 1920×1200 sat "exactly at the bridge's 154 MHz ceiling". That was wrong, and the error mattered: the 25–154 MHz figure is the LVDS output clock per link, and in dual-link mode each link carries half the pixels. TI's own power-table reference case is literally 1920×1200 dual-link with LVDS CLK OUT = 81.6 MHz.

The real picture, with every number now confirmed against a primary source:

ConstraintValueLimitUtilisation
i.MX 95 DSI transmit, per lane~925 Mbps2500 Mbps~37% — huge headroom
LVDS output clock, per link~81.6 MHz154 MHz~53% — comfortable
Bridge DSI input, per lane~925 Mbps1 Gbps~93% — the bottleneck

The i.MX 95 side is confirmed a non-issue: IMX95AEC Rev 8, Table 58, RATE[TX] Transmit Serial Data Rate = 80 to 2500 Mbps per lane, and the feature summary lists "1x 350 MHz MIPI-DSI (4-lane, 2.5 Gbps/lane) supporting 4kp30 or 3840 x 1440p60".

So the SN65DSI85-Q1 is the sole bottleneck in the chain. That is acceptable — TI documents 1920×1200 as a supported use case for this part — but it means the bridge, not the SoC, is what to re-examine if the timing ever fails to close.

The same datasheet confirms the native LVDS ceiling recorded above: "2x 1080p60 LVDS Tx (2x 4-lane or 1x 8-lane)".

  • 1920×1200p60 CVT-RB ≈ 154 MHz pixel clock × 24 bpp = ~3.70 Gbps across 4 lanes = ~925 Mbps/lane. Under the bridge's 1 Gbps limit, with ~7% headroom.
  • With standard (non-reduced) blanking the pixel clock is ~193 MHz → ~1.16 Gbps/lane, which exceeds the bridge limit (though not the SoC's). Reduced-blanking timing is therefore mandatory, not merely preferable.
  • Fallback remains 1920×1080, which relaxes the DSI side to ~830 Mbps/lane.

Layout constraints (i.MX 95 Hardware Design Guide UG10210 Rev 2.0)

  • 100 Ω differential for MIPI DSI and LVDS, ±10% (Table 40). Also 50 Ω single-ended for everything else unless specified. This sits comfortably inside the SN65DSI85-Q1's own 90–132 Ω LVDS output range.
  • For MIPI-DSI compliance tests 1.1.4/1.1.5, keep parasitic capacitance of each DSI trace below 10 pF — relevant because the DSI run crosses the carrier from X1 to the bridge.
  • The module's unused native LVDS pins are simply left not connected (datasheet Table 4). The VDD_LVDS_1P8-to-ground-via-10 kΩ guidance in that same table applies to the SoC, which is Toradex's side of the boundary, not this carrier's.

Note the Verdin carrier must still follow Toradex's own Carrier Board Design Guide (doc 108140) for anything X1-side; UG10210 describes the raw SoC.

For reference, the module's native LVDS pins, should the fallback be needed:

X1 pinChannel 0X1 pinChannel 1
88 / 90LVDS0_CLK_N / _P118 / 120LVDS1_CLK_N / _P
94 / 96LVDS0_D0_N / _P124 / 126LVDS1_D0_N / _P
100 / 102LVDS0_D1_N / _P130 / 132LVDS1_D1_N / _P
106 / 108LVDS0_D2_N / _P136 / 138LVDS1_D2_N / _P
112 / 114LVDS0_D3_N / _P142 / 144LVDS1_D3_N / _P

Candidate panels evaluated

Real parts found, with the specs that actually drive the board design:

Selected: iFan IF101GRL192-120B (2026-08-16), pending the vendor datasheet and pricing. Chosen mainly on temperature — it is a full 10 °C better at both ends than the other 1920×1200 candidate, which is the difference between reliable and marginal on a sun-baked dash — with 89% DCI-P3 gamut as a real bonus for image quality.

https://ifan-display.com/product/10-1-inch-touch-panel-1000-nits-wide-color-gamut-1920x1200/

PartResNitsInterfaceTouchBondedTemp
iFan IF101GRL192-120B ← selected1920×12001000LVDS, 60-pinPCAP inc.?−30 to +80 °C
Riverdi RVT101HVLNWC00-B1280×800~1000LVDSPCAP inc.yesindustrial
CDTech S101BWU78EP1920×12001000LVDS, 45-pin FPCnono−20 to +70 °C
CDTech S101HWX101ED1280×80010004-lane LVDS, 40-pin FPCnono−30 to +80 °C
CDTech S101HWX80NP-FC811280×8003501-ch LVDS, 30-pinILI2511 (USB)no (G+G)−20 to +70 °C
AUO G101UAN02.01920×1200800MIPInono−10 to +60 °C

The market bifurcates, and neither half is the full target spec:

  • You can get 1920×1200 + 1000 nit + touch (iFan), but optical bonding is unconfirmed and there is no public datasheet — it is a contact-the-vendor part.
  • Or you can get **productized optical bonding + PCAP + real datasheets
    • distributor stock** (Riverdi), but only at 1280×800.

The full combination is realistically a semi-custom order with MOQ, not an off-the-shelf purchase.

AUO's G101UAN02.0 is ruled out on two counts despite being the obvious 1920×1200 name: it is MIPI, not LVDS (which would put D-PHY on the dash ribbon, the thing this whole design avoids), and −10 to +60 °C is unusable in a car.

Three things to carry forward:

  1. The backlight boost designs are not interchangeable — 27–34 V at 240 mA versus 13.5–17 V at 360 mA versus 5 V at 530 mA are three different converters. The panel must be chosen before the backlight circuit is designed. iFan publishes only a total figure (9.32 W), so the string configuration has to be asked for.
  2. Temperature does not track resolution. CDTech's 1920×1200 part is −20 to +70 °C while their 1280×800 is −30 to +80 °C. A dash bakes in sun, so this is a real selection criterion, not a footnote — it is the main reason the iFan part leads.
  3. Touch is often USB, not I2C. Both CDTech modules with touch use USB controllers (ILI2511), and iFan lists "USB/I2C". This matters — see below.

Touch interface: USB may beat I2C over this cable run

The original plan assumed I2C touch. The market says otherwise, and on reflection USB is probably the better engineering choice here anyway:

  • I2C is single-ended and was designed for on-board use. Over 20 cm it is fine; over a metre it is marginal — bus capacitance eats the rise time and there is no noise rejection in a car's environment.
  • USB is differential and designed for cables. A metre is nothing. It also arrives as a standard HID device, so Android needs no custom touch driver or device-tree work.
  • Cost is one differential pair on the ribbon instead of two single-ended wires, and a USB host port on the carrier — which the Verdin already has.

Decision still open, but it should be made on cable length, not on which is simpler on paper.

Power tree and part selection

Every part below was verified against its own datasheet, not chosen from memory. Two of them corrected an earlier wrong guess, noted inline.

RolePartKey evidence
Front-end protectionLM74930-Q1AEC-Q100 grade 1 (−40/+125 °C), 4–65 V in, reverse protection to −65 V, adjustable OC/OV, circuit breaker, "meets automotive ISO7637 transient requirements with a suitable TVS diode"
12 V → 5 V buckLM61460-Q1AEC-Q100 grade 1, 3–36 V in (42 V transient), 6 A, synchronous, low-EMI with spread spectrum
CAN FDTCAN1044V-Q1AEC-Q100 grade 1, VIO 1.7–5.5 V with explicit 1.8 V support, CAN FD to 8 Mbps, ±58 V bus fault protection
DSI→LVDS bridgeSN65DSI85-Q1AEC-Q100 grade 2 (−40/+105 °C), single 1.8 V rail, HTQFP-64
Audio codecPCM3168A-Q1AEC-Q100, 24-bit 6-in/8-out codec, differential outputs, I2S/TDM, 104 dB, 64-HTQFP
USB VBUS switchTPS2557-Q1Automotive, current limit adjustable 500 mA–5 A, FAULT output, dual thermal sensing
Wi-Fi / Bluetoothon-module (u-blox MAYA-W260-00B)Wi-Fi 6, Bluetooth Classic/LE 5.4, two U.FL connectors — comes with the Verdin WB variants

The module sets two hard constraints that drove these choices:

  • VCC is 3.135–5.5 V, so the main rail is 5.0 V.
  • Verdin I/O is 1.8 V logic (absolute max 2.1 V). This is the constraint that eliminates most automotive CAN transceivers.
Front-end topology (resolved from the datasheet, not inferred)

TI's own front-page reference circuit for the LM74930-Q1 is titled "VBAT 12-V or 24-V With 200-V Unsuppressed Load Dump — Output Clamp". That is this application almost exactly: an unsuppressed alternator on a 1972 car, with the output clamped rather than disconnected.

The back-to-back FET arrangement is easy to get backwards, so it is written down here:

text
VBAT ──[RSENSE]──┬── Q2 drain            Q2 = pass / load switch  (HGATE)
                 │                       Q1 = ideal diode         (DGATE)
                 Q2 source ──┬── COMMON ──┬── Q1 source
                             │            │
                        OUT (15)      A (2)      ← both pins on COMMON
                                                    (common-source pair)
                                       Q1 drain ── VOUT_PROT ── C (24)

The resolution: A (2) and OUT (15) are the same node. "Back-to-back N-channel MOSFETs in common source configuration" means both FET sources tie together, and the datasheet independently says A is "the source of the external ideal diode MOSFET" while OUT is "the common source rail". C (24) is the ideal diode's drain and therefore the protected output. Direction is confirmed by the ideal-diode spec regulating "10.5 mV A to C forward voltage drop", and by HGATE driving "the first MOSFET in the power path".

Reference-design support components, all named in that circuit: RSENSE with RSET (50 Ω into CS+), RISCP on ISCP, RILIM on ILIM, RMON on IMON, CT on TMR, CVS on VS, CCAP across CAP–VS, and the R1/R2/R3 dividers feeding OV/OVCLAMP and UVLO.

The 5 V rail needs splitting

Rough budget, with the module figure still a placeholder:

LoadEstimate
Verdin iMX95~3 A @ 5 V (unknown — see open items)
USB-C charging3 A @ 5 V
Bridge, codec, CAN, misc~0.5 A
Total on 5 V~6.5 A

That is over the LM61460-Q1's 6 A, so two supplies rather than one bigger one: a main rail for the module and peripherals, and a second dedicated to USB VBUS. Splitting is the better design anyway — a phone drawing a fault current should not be able to brown out the SoC and reboot Android. Using the same part twice also keeps the BOM narrow.

The backlight boost is deliberately not on the 5 V rail — it runs from the protected 12 V directly, since the panel wants ~27–34 V and routing that through 5 V would waste a conversion and eat the budget.

Bluetooth comes free with the module

The Verdin WB variants carry a u-blox MAYA-W260-00B: Wi-Fi 6, Bluetooth Classic / LE 5.4, IEEE 802.15.4, and two U.FL antenna connectors already on the SoM. That means no RF design, no antenna matching and no radio certification work on this carrier — just two U.FL cables out to external antennas.

Bluetooth Classic covers A2DP for streaming and HFP for hands-free calls. Wi-Fi plus Bluetooth together is also exactly what wireless CarPlay and Android Auto need, so the USB-C port is for wired mode and charging rather than being the only way in.

Cost to record: the datasheet carries separate pin tables for "modules without Wi-Fi", so the WB variant consumes some UART and ADC pins that would otherwise reach the carrier. The variant has to be locked before the connector banks are final.

Two corrections worth recording

The CAN transceiver must be the V variant. An earlier draft of this plan named the TCAN1043-Q1, which only level-shifts to 3.3 V or 5 V — it cannot talk to 1.8 V logic at all. Worse, within the correct family the datasheet's own device comparison table reads:

PartLow-voltage I/O support on pin 5
TCAN1044-Q1No — pin 5 is a No-Connect
TCAN1044V-Q1Yes — pin 5 is VIO, 1.8–5.5 V

The suffix is the entire difference. Order the wrong one and the board assembles perfectly and the CAN link never works.

The surge stopper is TI's, not the obvious ADI part. The LTC4364 is the better-known automotive surge stopper and does something the LM74930-Q1 does not — it regulates through an overvoltage event rather than disconnecting. But its datasheet order table lists only C, I and H temperature grades with no AEC-Q100 qualification, which fails this family's standard (see ecu-pcb, where the last unqualified part was deliberately swapped out). The LM74930-Q1 is explicitly -Q1.

Correction — the LM74930-Q1 does clamp through. An earlier revision of this file claimed it protects only by disconnecting the load, and warned that a load dump would therefore collapse the 5 V rail and force an Android reboot. That was wrong, and reading the pin table and spec table settled it:

  • pin 16 is OVCLAMP: "connect this pin to OV pin for overvoltage clamp with circuit breaker (timer) functionality";
  • OVCLAMP has its own rising/falling thresholds (0.59 V / 0.45 V), separate from the plain OV disconnect thresholds;
  • the timer spec includes I(TMR_SRC_OVCLAMP), "TMR source current during overvoltage clamp" — a dedicated clamp state, not a disconnect;
  • and N(A_R_Count) gives 32 auto-retry cycles.

So it regulates the pass FET through an overvoltage event for a period set by the TMR capacitor, then opens the breaker if the event outlasts it, then auto-retries. That is genuine surge-stopper behaviour, and it removes the reboot risk previously recorded here.

What remains real is that the clamp is timed, not indefinite: the TMR capacitor has to be sized to ride out a 200 ms load dump, and the pass FET has to survive dissipating it for that long. FET SOA selection is therefore a genuine design task — see "Known open items".

For scale, the LTC4364 datasheet gives the industry-standard transient shapes: a general automotive transient of tr = 10 µs / VPK = 80 V / τ = 1 ms, and load dump of tr = 5 ms / VPK = 60 V / τ = 200 ms. The 200 ms one carries the energy that matters.

Panel quality matters more than resolution here

Recorded because it should drive the panel budget. In a car, in rough order of impact on how good the display actually looks:

  1. Brightness — consumer panels (250–400 nits) wash out in direct sun; automotive panels run 800–1500 nits. This is the dominant factor and it drives the backlight boost design (string current, thermals).
  2. Optical bonding (OCA/LOCA) — removes the air gap between LCD and cover glass that otherwise destroys daylight contrast; also prevents condensation.
  3. 24-bit colour, not 18-bit — 6-bit-per-channel LVDS panels band visibly on the dark gradients Android Automotive uses.
  4. IPS — driver and passenger both view well off-axis.
  5. Anti-glare / AR coating.

Resolution ranks below all of these. The target spec is a 1080p, ~1000-nit, optically-bonded, 24-bit IPS panel.

Caveat worth recording: LVDS on Verdin is a Module-specific function, not an Always-Compatible or Reserved one (datasheet Table 6 classifies it Total 1 / Always Compatible 0 / Reserved 0 / Module-specific 1). The pins are genuinely on the connector, but this carrier is therefore tied to the Verdin iMX95 specifically and is not portable to an arbitrary other Verdin module. MIPI DSI, by contrast, sits on Verdin-standard Reserved pins (17–55) and would be portable — at the cost of needing a bridge for a dash-length run.

This is also why tools/extract_verdin_pinout.py exists rather than a hand-typed table: the LVDS pins are named MSP_1…MSP_25 in the Verdin specification column and only resolve to LVDS0_CLK_N etc. in the module-specific function column. A parse that reads the wrong column concludes the module has no LVDS at all.

Other confirmed module facts

  • Module: 69.6 × 35.0 × 6.0 mm, 260-pin DDR4 SODIMM edge connector.
  • Odd pins top side, even pins bottom (DDR4 SODIMM numbering).
  • 5 VCC pins (251, 253, 255, 257, 259), 47 GND, plus VCC_BACKUP (249).
  • CAN FD: CAN_1_TX/CAN_1_RX on pins 20/22, CAN_2 on 24/26.
  • I2C_1 on pins 12/14; a dedicated display-side I2C_2_DSI on 53/55.
  • Backlight: PWM_3_DSI (pin 19) for brightness, GPIO_10_DSI (pin 21) for backlight enable via the on-module PCAL6416A I/O expander.
  • HDMI is explicitly not natively supported on this module.

Planned scope

A head unit that displays and sources audio but does not amplify it. Scope revised 2026-08-16 from the original display+touch+CAN.

In scope: display, touch, CAN to ecu-pcb, Bluetooth, line-level pre-outs to an external amplifier, a microphone for calls and voice control, and USB-C for wired CarPlay / Android Auto plus phone charging.

Explicitly not in scope: any power amplifier. This board drives no speakers — it feeds an existing automotive amp over RCA-level pre-outs. That single decision keeps the highest-current, highest-heat, highest-EMI subsystem off the board entirely, which matters in a sealed dash enclosure that already contains a 1000-nit backlight.

Also still out of scope: reversing camera, automotive Ethernet, and any radio tuner.

Carrier board blocks:

  • 12V automotive front end: reverse-polarity protection, load-dump clamping (ISO 7637-2 pulse 5), wide-Vin buck to the module rails.
  • Verdin X1 260-pin SODIMM socket.
  • Module power sequencing: CTRL_PWR_EN_MOCI, CTRL_RESET_MOCI#, CTRL_SLEEP_MOCI#, ignition/ACC sense.
  • MIPI DSI from X1 into a SN65DSI85-Q1 bridge — short, impedance- controlled, length-matched on-board runs; the bridge sits right at the panel connector so the DSI never reaches the ribbon.
  • Bridge configured over I2C_2_DSI, enabled by GPIO_9_DSI.
  • Audio: PCM3168A-Q1 codec on I2S/TDM from the module. Five of its eight DAC channels drive the pre-outs (front L/R, rear L/R, mono sub); one ADC channel takes the microphone. Differential outputs, which is the right choice for running line level across a car to an amp.
  • Microphone connector for a remote mic mounted near the A-pillar or headliner, with bias. Placement beats mic quality in a car by a wide margin, which is why it is off-board.
  • USB-C port for wired CarPlay / Android Auto: USB 2.0 data to the module's USB_1 port, and VBUS from a TPS2557-Q1 switch whose EN and FAULT map onto USB_1_EN and USB_1_OC#. CC1/CC2 carry Rp resistors advertising 3 A as a downstream-facing port — no PD controller and no negotiation firmware.
  • Two U.FL antenna pigtails from the module's on-board wireless out to external Wi-Fi/Bluetooth antennas.
  • Dual-channel LVDS out of the bridge to the panel connector, with common-mode chokes and ESD protection on each of the 10 pairs.
  • Backlight boost driver, PWM-dimmed via PWM_3_DSI, enabled by GPIO_10_DSI, sized for a high-brightness (~1000 nit) panel rather than a consumer-grade one.
  • CAN FD transceiver to ecu-pcb.

Panel board blocks:

  • Ribbon connector from the carrier.
  • Panel LVDS FFC connector — pin count set by the chosen panel (the leading candidate uses 60-pin).
  • Capacitive touch controller — must live at the panel, since capacitive sensing will not tolerate a metre of cable between controller and sensor. Most candidate modules integrate it already. Interface back down the ribbon is USB or I2C, still to be decided (see "Touch interface" above).
  • Backlight LED string connector.

How it's built

Same script-driven, kiutils/kicad-cli-verified workflow as the sibling projects: the generator scripts are the source of truth — always regenerate from them, never hand-edit Fascia.kicad_sch/Fascia.kicad_pcb directly.

tools/extract_verdin_pinout.py is a one-shot data extractor, not part of the per-build pipeline. It takes the Toradex datasheet's local path as an argument (the PDF is Toradex's document and is gitignored, not committed):

bash
python tools/extract_verdin_pinout.py ~/Downloads/200007-verdin_imx95_datasheet.pdf

It refuses to write output unless all 260 pins parse and the LVDS pin numbers it derived from the main pin-assignment tables agree with the separate LVDS table on page 42.

Known open items

  • No BOM or fab outputs yet. See PLAN.md for the full list of what is left and what each step is blocked on.
  • Panel selected but its datasheet is not yet in hand. The iFan IF101GRL192-120B is chosen; a request for datasheet and pricing went to the vendor on 2026-08-16. Until it arrives, anything that depends on the panel's real numbers is blocked:
    • the backlight boost converter (no string V/I published)
    • the panel-side connector footprint and pinout (60-pin, mapping unknown)
    • the touch link (USB vs I2C, see above)
    • bezel/mechanical
  • Questions to put to iFan — none are answerable from their public page:
    • Is optical bonding available, and at what MOQ?
    • LVDS single or dual channel? (1920×1200 at 24 bpp requires dual, so this is really a confirmation, but the 60-pin connector needs a pinout either way.)
    • Backlight string configuration — volts and milliamps, not just the published 9.32 W total. The boost converter cannot be designed without it.
    • Touch controller IC, and is the interface USB or I2C?
    • Connector part number, and is a mating FFC/cable available?
    • Operating temperature is quoted as −30 to +80 °C; confirm storage range and whether an automotive-qualified variant exists.
  • Touch interface undecided — USB versus I2C, see the section above. Leaning USB on cable-length grounds.
  • DSI timing closes on paper but is not yet proven on hardware. Every number in the chain is now confirmed against a primary source and 1920×1200 fits, but with only ~7% headroom on the bridge's DSI input and a hard requirement for reduced-blanking timing. Worth confirming on a Verdin EVK with the real panel before committing to fab. Fallback is 1920×1080.
  • LVDS mapping convention not yet fixed — VESA vs JEIDA (a.k.a. SPWG) differ in bit ordering and are not interchangeable. Determined by the chosen panel.
  • Module temperature rating is industrial, not automotive. The Verdin iMX95 IT variants are −40 °C to +85 °C, unlike the AEC-Q100 parts used across the rest of this family. Acceptable for a cabin/dash mount but a real deviation from the family's engine-bay-rated standard, and worth a deliberate decision rather than an accident.
  • Pass-FET SOA and TMR sizing. The LM74930-Q1's overvoltage clamp is timed rather than indefinite, so the TMR capacitor must be sized to ride out a 60 V / 200 ms load dump, and the pass MOSFET must survive dissipating that event inside its safe operating area. Neither number is chosen yet, and SOA is the one most likely to drive the FET choice.
  • Watch the LM74930-Q1 thermal pad. Its datasheet says the exposed pad (RTN) must be left floating — explicitly "Do Not connect to GND plane". That is the opposite of the near-universal VQFN convention, so both the footprint and the PCB generator need a deliberate exception or the part will be destroyed by a routine ground stitch.
  • Verdin power consumption is still unknown. The module datasheet gives no current figure, deferring to the Verdin Family Specification, which has not been pulled. The 5 V rail is provisionally sized on the LM61460-Q1's 6 A rather than on a real budget.
  • Unit E may need splitting. At 158 pins it is ~200 mm per side, which fits an A3 sheet only marginally. Splitting it into two units of ~79 is the likely fix, but the real constraint will not be known until the symbol generator exists.
  • Verdin iMX95 datasheet is marked Preliminary — Subject to change; the pinout should be re-extracted against a final revision before fab.
  • Carrier must follow the Verdin Carrier Board Design Guide (Toradex doc 108140), which has not yet been reviewed.
  • Toradex publishes free reference carrier schematics with symbols and IPC-7351 footprints — not yet pulled in, but likely the right source for the X1 socket footprint rather than drawing one.

Parts

118
QtyValueFootprintReferences
6100n 1V8Capacitor_SMD:C_0603_1608MetricC16, C17, C18, C19, C20, C21
4100n codecCapacitor_SMD:C_0603_1608MetricC31, C32, C33, C34
410k pullupResistor_SMD:R_0603_1608MetricR44, R45, R46, R47
410k tie-offResistor_SMD:R_0603_1608MetricR33, R34, R35, R36
42k2 pullupResistor_SMD:R_0603_1608MetricR25, R26, R27, R28
310u decoupleCapacitor_SMD:C_0603_1608MetricC28, C29, C30
310u inCapacitor_SMD:C_0603_1608MetricC5, C9, C22
3FB botResistor_SMD:R_0603_1608MetricR11, R18, R24
3FB topResistor_SMD:R_0603_1608MetricR10, R17, R23
2100k FLT puResistor_SMD:R_0603_1608MetricR15, R38
210k biasResistor_SMD:R_0603_1608MetricR31, R32
210u outCapacitor_SMD:C_0603_1608MetricC10, C23
260R termResistor_SMD:R_0603_1608MetricR19, R20
2NFET i2c xlatPackage_TO_SOT_SMD:SOT-23Q3, Q4
2SN74AXC4T245-Q1Package_SO:TSSOP-16_4.4x5mm_P0.65mmU7, U8
10R IDResistor_SMD:R_0603_1608MetricR41
1100k PG puResistor_SMD:R_0603_1608MetricR16
1100k RSTResistor_SMD:R_0603_1608MetricR29
1100k VsenseResistor_SMD:R_0603_1608MetricR42
1100nCapacitor_SMD:C_0603_1608MetricC39
1100n CCAPCapacitor_SMD:C_0603_1608MetricC3
1100n CVSCapacitor_SMD:C_0603_1608MetricC2
1100n INCapacitor_SMD:C_0603_1608MetricC37
1100n RSTCapacitor_SMD:C_0603_1608MetricC35
1100n U7ACapacitor_SMD:C_0603_1608MetricC24
1100n U7BCapacitor_SMD:C_0603_1608MetricC25
1100n U8ACapacitor_SMD:C_0603_1608MetricC26
1100n U8BCapacitor_SMD:C_0603_1608MetricC27
1100n VCCCapacitor_SMD:C_0603_1608MetricC11
1100n VIOCapacitor_SMD:C_0603_1608MetricC12
1100n bootCapacitor_SMD:C_0603_1608MetricC7
1100uFCapacitor_SMD:C_0603_1608MetricC1
110k JTAG VrefResistor_SMD:R_0603_1608MetricR48
110k REFCLKResistor_SMD:R_0603_1608MetricR22
110k Rp CC1Resistor_SMD:R_0603_1608MetricR39
110k Rp CC2Resistor_SMD:R_0603_1608MetricR40
110k STB pdResistor_SMD:R_0603_1608MetricR21
110u 1V8Capacitor_SMD:C_0603_1608MetricC15
1150u VBUSCapacitor_SMD:C_0603_1608MetricC38
11u VCCCapacitor_SMD:C_0603_1608MetricC6
11u VCORECapacitor_SMD:C_0603_1608MetricC14
11u coupleCapacitor_SMD:C_0603_1608MetricC36
12.2uInductor_SMD:L_1210_3225MetricL1
12k2 mic biasResistor_SMD:R_0603_1608MetricR30
12m senseResistor_SMD:R_0603_1608MetricR1
136k ILIMResistor_SMD:R_0603_1608MetricR37
144u outCapacitor_SMD:C_0603_1608MetricC8
147k minResistor_SMD:R_0603_1608MetricR49
14n7 splitCapacitor_SMD:C_0603_1608MetricC13
150RResistor_SMD:R_0603_1608MetricR2
156k VsenseResistor_SMD:R_0603_1608MetricR43
15AFuse:Fuse_Bourns_MF-RG300F1
15k RMONResistor_SMD:R_0603_1608MetricR4
1ButtonsConnector_PinHeader_2.54mm:PinHeader_1x04_P2.54mm_VerticalJ9
1CAN to ECUConnector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ3
1EN botResistor_SMD:R_0603_1608MetricR14
1EN topResistor_SMD:R_0603_1608MetricR13
1ESD DNDiode_SMD:D_SMBD3
1ESD DPDiode_SMD:D_SMBD2
1ESD VBUSDiode_SMD:D_SMBD4
1JTAG debugConnector_PinHeader_2.54mm:PinHeader_1x08_P2.54mm_VerticalJ8
1LM61460-Q1TI_RJR0014A_VQFN-HR:TI_RJR0014A_VQFN-HR-14_4x3.5mmU2
1LM74930-Q1Package_DFN_QFN:Texas_RGE0024H_VQFN-24-1EP_4x4mm_P0.5mm_EP2.7x2.7mmU1
1MicConnector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ6
1NFET diodePackage_TO_SOT_SMD:SOT-23Q1
1NFET passPackage_TO_SOT_SMD:SOT-23Q2
1OV botResistor_SMD:R_0603_1608MetricR6
1OV topResistor_SMD:R_0603_1608MetricR5
1PCM3168A-Q1Package_QFP:Texas_TQFP-64-1EP_10x10mm_P0.5mm_EP8x8mm_Mask4.44x4.44mmU9
1Panel LVDS (provisional)Connector_PinHeader_2.54mm:PinHeader_1x22_P2.54mm_VerticalJ4
1Power inConnector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_VerticalJ2
1Pre-outs to ampConnector_PinHeader_2.54mm:PinHeader_1x11_P2.54mm_VerticalJ5
1RBOOTResistor_SMD:R_0603_1608MetricR9
1RILIMResistor_SMD:R_0603_1608MetricR3
1RTResistor_SMD:R_0603_1608MetricR12
1RTC coin cellBattery:BatteryHolder_Keystone_1058_1x2032J10
1SN65DSI85-Q1Package_QFP:Texas_TQFP-64-1EP_10x10mm_P0.5mm_EP8x8mm_Mask4.44x4.44mmU5
1TCAN1044V-Q1Package_SO:SOIC-8_3.9x4.9mm_P1.27mmU4
1TLV767-Q1Package_DFN_QFN:Texas_DRB0008AU3
1TLV767-Q1 3V3Package_DFN_QFN:Texas_DRB0008AU6

The 111 most common of 118 parts.

Similar boards

  • 6 layers100 × 110 mmFujiNet NES Rev0, the printed circuit board in 3D

    FujiNet NES Rev0

    FujiNetWIFI/fujinet-hardware

    Schematics and design files for FujiNet hardware

    118 parts142
  • 6 layers69.7 × 114.8 mmLow noise power probe, the printed circuit board in 3D

    Low noise power probe

    blinken/power-rail-probe

    Low-noise oscilloscope power rail probe

    118 parts101
  • 6 layers71.1 × 168.4 mmMeshtonic h4m v2, the printed circuit board in 3D

    Meshtonic h4m v2

    Josephrp/meshtonic

    Meshtonic H4M Companion — ESP32-S3 carrier for PortaPack H4M / Mayhem with multi-slot LoRa and standalone Meshtastic

    118 parts11
  • 6 layers50 × 50 mmCalc, the printed circuit board in 3D

    Calc

    pparent76/Librecalc-Hardware

    Hardware of the librecalc project

    118 parts2
  • 6 layers84.5 × 72.2 mmHub standard rev2, the printed circuit board in 3D

    Hub standard rev2

    nathanfraske/CEC-Platform

    ONE board file, kept current by the wave (owner directive 2026-07-25: "the current best should be placed into a candidate folder per board and kept current with only one board ideally so we have a reference").

    117 partsApache-2.0
  • 6 layers27.6 × 12.3 mmMiniscope v4-Wire Free, the printed circuit board in 3D

    Miniscope v4-Wire Free

    fnsangiul/Miniscope-v4-Wire-Free

    Wire-free Miniscope v4 system

    117 parts2
  • 6 layers26.7 × 12.3 mmMiniscope v4-Wire Free, the printed circuit board in 3D

    Miniscope v4-Wire Free

    Aharoni-Lab/Miniscope-v4-Wire-Free

    Wire-free Miniscope v4 system

    117 parts6
  • 6 layers172 × 100 mmTestrack carrier, the printed circuit board in 3D

    Testrack carrier

    esden/redcuttle

    Moved to Codeberg

    117 parts9

Questions

How big is the Fascia PCB?

It measures 147.8 × 71.1 mm and has 6 copper layers, 1.6 mm thick.

What parts does the Fascia use?

118 parts, built around the TLV767-Q1DRB. 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 Fascia KiCad files?

From the jessiepullaro414/Fascia repository on GitHub, at the commit this page was made from: the board is Fascia.kicad_pcb and its schematic Fascia.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Fascia design in my own project?

Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).