[LinuxBIOS] about programming BIOS Savior
Ning (Michael) Qu
quning at gmail.com
Wed Apr 25 02:24:57 CEST 2007
Thanks very much for your reply! I will check the status of WP pin.
But because the flash chip is embedded in the middle of Savior,
perhaps I can't see it clearly. And I haven't tried to flash a chip
directly on the mainboard because I won't take the risk of failing to
booting the system .....
On 4/24/07, Peter Stuge <stuge-linuxbios at cdy.org> wrote:
> On Tue, Apr 24, 2007 at 09:42:29PM +0200, Stefan Reinauer wrote:
> > * Ning (Michael) Qu <quning at gmail.com> [070424 21:30]:
> > > And I check the new content after programming Savior. Only the
> > > last page are programmed. The total is 8 pages (512K), and only
> > > the content from 0x70000 is correctly programmed. What's the
> > > problem? Is there something wrong with flashrom?
> > Maybe some flash protection that "flashrom" does not know about.
> > Can you check the datasheet?
> Yes, this is consistent with the WP# pin being held low on the chip.
> --8<-- Pm49LF002-004 V1.8.pdf p5
> Write Protect: When pulled low, it enables the hardware write
> protection to the memory array except the top bootblock. When pulled
> high, it disables hardware write protection.
> 49LF004 has a 64kb top boot block.
> If you have a continuity tester, please check if pin 7 (pins are
> numbered counter clockwise and pin 1 is the center pin on the side
> with a angled top edge) is connected to GND on the mainboard, and/or
> if there's a jumper.
> You could also check if pin 7 is connected straight through on the
> BIOS savior. Maybe they changed their design for some unknown reason.
> Oh, and did you try to flash a chip directly on the mainboard? Please
> try to write and verify using a few different files.
> linuxbios mailing list
> linuxbios at linuxbios.org
More information about the coreboot