Reference schematic

EVAL6599

TasosFrago-EVAL6599-EVAL6599-schematic

Loading the viewer…

TasosFrago-EVAL6599-EVAL6599-schematic

Take the project archive: a schematic is a root sheet plus every sub-sheet beside it, and the root alone opens with its hierarchy missing. The archive is zstd-compressed (tar.zst).

1Sheets
68Placed parts
6Net labels
KiCad 8File format

Bill of materials

68 distinct parts

62 resolve to something in the catalog — click through to the component.

RefValueSymbolQty
C102nDevice:C
C112nDevice:C
C12100nDevice:C
C1310uDevice:C
C14100nDevice:C
C15100pDevice:C
C161uDevice:C
C17220pDevice:C
C18330pDevice:C
C1910nDevice:C
C2470nDevice:C
C20470nDevice:C
C212nDevice:C
C2210nDevice:C
C3330nDevice:C
C4680nDevice:C
C5470nDevice:C
C6470nDevice:C
C7470nDevice:C
C8330uDevice:C
C92nDevice:C
D11N5406Diode:1N5406
D2D15XB60lib:D15XB60
D3STTH8R06lib:STTH8R06
D4LL4148Diode:LL4148
D5LL4148Diode:LL4148
D6LL4148Diode:LL4148
F1FuseDevice:Fuse
J1~lib:CON2-IN
JP1Jumper_2_BridgedJumper:Jumper_2_Bridged
JP2Jumper_2_BridgedJumper:Jumper_2_Bridged
L1L_CoupledDevice:L_Coupled
L351uDevice:L_Iron
L4CHDevice:L_Iron
Q1STP12NM50FPlib:STP12NM50FP
Q2STP12NM50FPlib:STP12NM50FP
Q3BC857Clib:BC857C
R11.5MegDevice:R
R10100kDevice:R
R1115kDevice:R
Show the other 28
R1356kDevice:R
R143.3kDevice:R
R156.8Device:R
R165.1kDevice:R
R1715kDevice:R
R186.8Device:R
R191kDevice:R
R22.5Device:Thermistor_NTC
R201kDevice:R
R210.39Device:R
R220.39Device:R
R230.39Device:R
R240.39Device:R
R2530kDevice:R
R26150kDevice:R
R28240kDevice:R
R291.5kDevice:R
R3680kDevice:R
R30620kDevice:R
R31620kDevice:R
R3210kDevice:R
R447Device:R
R52.2MegDevice:R
R6680kDevice:R
R72.2MegDevice:R
R8680kDevice:R
R92.2MegDevice:R
U1L6563Regulator_Controller:L6563

Provenance

Commit
unknown
Licence
CC-BY-4.0

How it is used

Trace's agent reads this design as context — what parts a board like this carries, how they are grouped across sheets, what a plausible layer stack and board size look like for the job. It is not copied. The licence above is permissive, and it, the repository and the commit are recorded so the origin of anything derived from it is always answerable.