X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C87A75.A6A61580@onstor-exch02.onstor.net>; Thu, 28 Feb 2008 18:51:50 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: concrete info on CF status problem
Date: Thu, 28 Feb 2008 18:51:50 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E089F1971@onstor-exch02.onstor.net>
In-Reply-To: <20080228174605.206a0a38@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: concrete info on CF status problem
Thread-Index: Ach6dNkJ2tUKhbTcTWScOPFBPPOjsAAACf4Q
References: <20080225140859.55145d81@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E089F185F@onstor-exch02.onstor.net><20080228162754.3c0479e9@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E089F1902@onstor-exch02.onstor.net> <20080228174605.206a0a38@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>

=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Thursday, February 28, 2008 5:46 PM
> To: Brian Stark
> Cc: Warren Gale
> Subject: Re: concrete info on CF status problem
>=20
> On Thu, 28 Feb 2008 16:51:10 -0800 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> > No, I see nothing.  This is not a board problem -- the interrupt is=20
> > firing and something is then reading the status reg in the 1520.
>=20
> That's OK, I recognize your denial and it's only human, after all.

Good one.

>=20
> > I've tried your old Rev 2 board, a Rev 3 board, and a Rev 4 board.
> > Plus, I can show you the diffs in the netlists between Rev=20
> 2 - Rev 4,=20
> > and there's nothing in the hardware that's changed with any of the=20
> > connections between CF, 1520, and 1125.
>=20
> What about the 1520 itself?  Different rev, different part=20
> no., different supplier, different version? Just because=20
> nothing changed in the netlists doesn't rule out something=20
> not right with the way they were built.  Or if we switched to=20
> a slightly different part that's RoHS compatible or something.

Nope, the 1520 is sole-sourced to TI and it hasn't changed in eons.
Nice try.  It ain't the 1520 or the board -- the interrupt is firing to
the 1125 and then the status reg is read.  I think I need to draw you a
picture.
  =20

> > Like I said, I tried your old board and had no luck.  I=20
> used the same=20
> > kernel on a new board.  I also tried the 1.0.2, 1.0.3, and 1.0.4=20
> > PROMs. This is not a problem with the board or the PROM.
>=20
> Those sound like bettin' words.  How much you care to risk? =20
> Baby needs a new pair of shoes.

You're on.  I'll bet you a nice shiny Mac laptop.  Oh wait, you already
have that.

My babies need a lot more than new pairs of shoes.  It's called college
funds.


>=20
> > Your old board is connected as follows:
> >=20
> > SSC console	10.1.1.100 2001
> > Power 10.1.1.141, port .a2
> > IP addr 10.1.1.125
>=20
> OK, but do you have the CF card monkey tethered to the bench?=20
>  What's the PROM command to get that little guy to pop a=20
> flash out/in?  ~:^)

I'd be happy to be the CF card monkey for you, but that'll have to wait
until tomorrow cuz I'm heading home.  Or you can come by in the morning,
but like I said, I may have to be at home tomorrow afternoon to watch
the kiddies.



>=20
