Subject: RE: Multia diagnostic translation needed
To: 'Manuel Bouyer' <firstname.lastname@example.org>
From: David Woyciesjes <DAW@yalepress3.unipress.yale.edu>
Date: 06/10/2000 22:10:59
In conversing with mu brother over a couple of Coors today, we figure we'll
replace the flash ROM chips. Being right next to the processor (I'm almost
positive), good chance they got fried with help from the 233 MHz
processor... if not, when I did the fail Safe and blast on my working 166, I
ROM BASE = 38400000; MFG ID = 89; DEV ID = bd ( <- might have been 'db')
but if you recall, i got this from the bad machine...
ROM BASE = 38400000; MFG ID = 89; DEV ID = 9d
Wrong ROM vendor. AMD or Intel Parts expected.
Sound like the flash ROM is limping along, dishing out wrong info, therefore
screwing the firmware blast. Make sense?
--- David A Woyciesjes
--- C & IS Support Specialist
--- Yale University Press
--- (203) 432-0953
--- ICQ # - 905818
From: Manuel Bouyer [mailto:email@example.com]
Sent: Saturday, June 10, 2000 11:35 AM
To: David Woyciesjes
Cc: '''firstname.lastname@example.org' ' '; 'email@example.com'
Subject: Re: Multia diagnostic translation needed
On Fri, Jun 09, 2000 at 03:36:52PM -0400, David Woyciesjes wrote:
> not equal at 00000006 AA 8A
> not equal at 00000007 FF DF
> not equal at 00000009 31 11
> not equal at 0000000A 2E 0E
> not equal at 0000000B 31 11
> not equal at 0000000C 20 00
> not equal at 0000000D 20 00
> not equal at 0000000E 20 00
> not equal at 0000000F 20 00
> not equal at 00000013 20 00
look, bit 0x20 is always low. Could be either the Flash memory chips, or a
buffer on the path if there's one.
Manuel Bouyer <firstname.lastname@example.org>