Skip to content

Add all ti-sysblocks chip recommendations - #112

Open
seveibar wants to merge 8 commits into
mainfrom
add-ti-sysblocks-chips
Open

Add all ti-sysblocks chip recommendations#112
seveibar wants to merge 8 commits into
mainfrom
add-ti-sysblocks-chips

Conversation

@seveibar

@seveibar seveibar commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add all 810 unique TI product families referenced by tscircuit/ti-sysblocks
  • expose 800 exact orderable-MPN components and reuse 10 existing family definitions
  • keep raw chip modules as plain lib/chips/*.tsx; reserve *.circuit.tsx for runnable examples, subcircuits, and simulations
  • retain component footprints while removing the footprint-selection, footprint-catalog, and materialization JSON artifacts
  • add package-aware pin maps and a schematic-layout helper that preserves tscircuit's 0.2 mm adjacent-pin spacing
  • add 21 reusable, named TI-reference blocks with matching schematic-only snapshots
  • let tscircuit autoroute every example schematic: no manual schematic geometry, <schematictext>, custom drawing symbols, or schematicRouteHints
  • disable SPICE solving in CI through platformConfig.spiceEngineMap; local simulation engines remain enabled
  • add a CI workflow that validates reference evidence and checks schematic-only snapshots

The sysblocks diagrams use generic TI product-page names rather than exact package variants. Each of the 800 generated families therefore selects one active orderable MPN/package in lib/chips/ti-sysblocks-chip-catalog.json; the exact MPN export remains available when the package choice must be explicit.

Reusable TI reference blocks

The example library intentionally samples useful public TI reference circuits instead of inventing a circuit for every chip. Each block named-exports a reusable component, default-exports the same component as a runnable example, records its first-party TI figure/page in examples/ti-reference-examples.json, and has one reviewed schematic snapshot.

Examples use ordinary <trace> elements only to declare electrical connectivity; tscircuit chooses the schematic paths. Repository validation rejects manual schematic geometry, <schematictext>, custom drawing symbols, and schematicRouteHints in every runnable example. An example is omitted when automatic layout cannot reproduce the cited TI figure readably.

  • Power and drivers: BQ25185_TypicalBatteryCharger, DRV8833_ParallelMotorDriver, TLV755P_TypicalApplication, TPS22919_LoadSwitchTypicalApplication, TPS61165_WhiteLedDriver, TPS61299_5VBoostConverter, TPS62A01_1V8BuckConverter, TPS7A20_TypicalApplication, TPS92612_LinearLedDriver
  • Analog, sensing, and conversion: ADS7042_DirectSensorInterface, INA138_BasicCurrentSense, LM358B_InvertingAmplifier, LMT70_AnalogTemperatureToAdc, OPA320_SecondOrderLowPassFilter, OPA371D_LowSideCurrentSense
  • Logic, interface, clocking, wireless, and timing: CC2340R5MODA_TypicalApplication, LMC555_MonostableLedFlasher, LMK1C1104_ClockFanout, SN74AHC1G14_SwitchDebouncer, SN74AUP1G17_TurnOnPulseGenerator, TCAN1044A_5VCanInterface

The generated examples/index.ts exports all blocks and the typed TiReferenceBlockComponents map. Families without a sufficiently clear public TI schematic are deliberately skipped.

Validation

  • bun run validate:ti-sysblocks — 810 families: 689 JLCPCB, 111 TI-datasheet, 10 existing
  • bun run validate:ti-reference-examples — 21 evidence-backed blocks, including 20 sysblocks families
  • bun scripts/validate-ti-reference-examples.ts --verify-evidence — all 21 first-party TI evidence URLs resolve
  • bun test scripts — 47 passing
  • bun run typecheck
  • bun run format:check
  • CI=true bun run snapshot:schematics — all 22 runnable example schematics match their snapshots
  • git diff --check

The hosted tscircuit/build result is not treated as a gate for this PR because the package is too large for that builder, per maintainer direction.

@seveibar
seveibar marked this pull request as ready for review August 23, 2026 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant