[ixp1200] Re: Hardware problem: won't book the BootMgr...

[Kenneth M. Mackenzie]

Hi Scott,

  It apparently was indeed a problem with the flash, although I don't
know how we did it because as far as I know we didn't write the flash
on that board.  We had been experimenting with updating the flash on
*another* board (strictly in circuit) about that time, though, so
someone may have become confused... :-)

  After scrambling a bit to locate a prom burner with a TSOP head
we're now back in business.  And, heh, emboldened to write all over
them flash chips.

  Thanks for the encouragement to consider it a possible software
problem! (and also for your previous notes on handling the flash
chips).

-- Ken

----------------

Date: Mon, 9 Jul 2001 17:39:43 -0400
From: "Scott C. Karlin" <scott at cs.princeton.edu>
To: ixp1200 at cs.princeton.edu
Subject: [ixp1200] Re: Hardware problem: won't book the BootMgr...
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.SOL.4.21.0107091421250.22515-100000 at felix.cc.gatech.edu>; from austen at cc.gatech.edu on Mon, Jul 09, 2001 at 02:28:12PM -0400
Sender: owner-ixp1200 at cs.princeton.edu
Reply-To: ixp1200 at cs.princeton.edu
Content-Type: text/plain; charset=us-ascii
Content-Length: 1080

On Mon, Jul 09, 2001 at 02:28:12PM -0400, Austen McDonald wrote:
> 
> 	My IXP appears not to boot the BootMgr: when I turn it on, it just
> sets the LEDs to 00 and then sits--no output on the serial or anything. I
> can boot it into diagnostics but it fails (or rather, doesnt get past) the
> IRQ/FIQ test: it never prints test complete. All the jumpers are set to
> factory default. Does anyone know what is wrong with it and to how fix it?

Is this in the provided passive backplane or a PC motherboard?

Have you been removing/installing the flash chips in the sockets?

Are you changing the clock speed settings?

I had similar trouble when installing an IXP1200 board in an
active backplane with updated flash which explicitly set the
clock speed.

I was using a Rev B0 chip (which should run at 199 MHz) on a
board which was only designed for 167 MHz.  When I inadvertantly
attempted to set the clock to 199 MHz very early in the boot
sequence, I observed the behaviour you describe.  Once I changed
things so that I was only running at 167 MHz, everything was fine.

Scott