view pirelli/mcsi @ 134:c131238c56bf

tiobjd: implemented parsing of the hint input files
author Michael Spacefalcon <msokolov@ivan.Harhan.ORG>
date Mon, 07 Apr 2014 02:41:35 +0000
parents fdfb57a1c5fe
children
line wrap: on
line source

Tracing all 4 MCSI signals starting from the Calypso

MCSI_TxD: Calypso ball L10, L1 trace goes to (3829,474).  The trace on L2 gets
lost in the edge grind-down damage.

MCSI_RxD: Calypso ball M10, no visible trace on L1 - perhaps there is a
micro-via under the ball?  The ball pad coords are (3841,499).  Looking at L2,
the micro-via hypothesis seems to be correct: a trace from those coords goes in
the same bunch as the MCSI_TxD.  But then it gets lost in the damage too.

MCSI_CLK: Calypso ball N10, L1 trace goes to (3898,369).  L2: joins the same
bunch with MCSI_TxD and MCSI_RxD, then gets lost in the damage.

MCSI_FSYNCH: Calypso ball K9, L1 trace goes to (3865,524).  L2: same story as
the others.