1- The chip was not erased, it contained the motherboard BIOS. Before starting the tests, I programmed all the chips using the motherboard vendor update disk.

2- The erase.bin only contained 0xFF, so the chip was erased correctly.

3- The bios.bin file contained the original bios.

Greetings.

> Date: Sun, 30 May 2010 16:14:51 +0200
> From: uwe@hermann-uwe.de
> To: master_darkman@hotmail.com
> CC: flashrom@flashrom.org
> Subject: Re: [flashrom] Report for SST29EE020 part
>
> Hi,
>
> thanks for your reports.
>
> On Fri, May 28, 2010 at 07:55:20PM +0200, Néstor a.k.a. DarkMan wrote:
> > attached are the output of the read, erase and write operations for SST29EE020 part.
> >
> > Motherboard: Shuttle AV11V30
> > Processor: Pentium III
> > Chipset: Via Apollo Pro 133
> > Software version: flashrom v0.9.2-r1017 on Linux 2.6.24-27-generic (i686), built with libpci 2.2.4, GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu4), little endian
> >
> > I hope you find this useful.
> > Greetings and thank you for develop this project!
> > Nestor E.
>
>
> > nestor@workstation:/tmp$ sudo flashrom -VE
> > Found chipset "VIA VT82C596", enabling flash write... chipset PCI ID is 1106:0596, OK.
> [...]
> > Found chip "SST SST29EE020A" (256 KB, Parallel) at physical address 0xfffc0000.
> [...]
> > Erasing flash chip... Looking at blockwise erase function 0... trying... 0x000000-0x03ffff,
> > SUCCESS.
>
> Looks OK so far (unless your chip was already fully erased before the -E).
>
>
> > nestor@workstation:/tmp$ sudo flashrom -Vr /tmp/erased.bin
>
> Did you check if erased.bin only contains 0xff bytes, e.g. using hexdump?
>
>
> > nestor@workstation:/tmp$ sudo flashrom -Vw bios.bin
>
> Is this bios.bin a different image than the BIOS you had on the chip
> before?
>
>
> > ===
> > Flash image seems to be a legacy BIOS. Disabling checks.
> > Writing flash chip... Programming page: 0058 at address: 0x00001d00VERIFY FAILED at 0x00001d5a! Expected=0xaf, Read=0xff, failed byte count from 0x00001d00-0x00001d7f: 0x26
> > retrying.
> > 0079 at address: 0x00002780VERIFY FAILED at 0x0000279f! Expected=0x0c, Read=0xff, failed byte count from 0x00002780-0x000027ff: 0x61
> > retrying.
> > 1070 at address: 0x00021700VERIFY FAILED at 0x00021714! Expected=0xa2, Read=0xff, failed byte count from 0x00021700-0x0002177f: 0x6c
> > retrying.
> > 1081 at address: 0x00021c80VERIFY FAILED at 0x00021c8f! Expected=0x02, Read=0xff, failed byte count from 0x00021c80-0x00021cff: 0x70
> > retrying.
> > 1251 at address: 0x00027180VERIFY FAILED at 0x000271ba! Expected=0x72, Read=0xff, failed byte count from 0x00027180-0x000271ff: 0x46
> > retrying.
> > 1291 at address: 0x00028580VERIFY FAILED at 0x000285e4! Expected=0xa2, Read=0xff, failed byte count from 0x00028580-0x000285ff: 0x1c
> > retrying.
> > 1368 at address: 0x0002ac00VERIFY FAILED at 0x0002ac59! Expected=0x24, Read=0xff, failed byte count from 0x0002ac00-0x0002ac7f: 0x27
> > retrying.
> > 1413 at address: 0x0002c280VERIFY FAILED at 0x0002c2de! Expected=0xee, Read=0xff, failed byte count from 0x0002c280-0x0002c2ff: 0x22
> > retrying.
> > 1429 at address: 0x0002ca80VERIFY FAILED at 0x0002caa6! Expected=0xc3, Read=0xff, failed byte count from 0x0002ca80-0x0002caff: 0x59
> > retrying.
> > 1533 at address: 0x0002fe80VERIFY FAILED at 0x0002fed6! Expected=0x77, Read=0xff, failed byte count from 0x0002fe80-0x0002feff: 0x2a
> > retrying.
> > 1600 at address: 0x00032000VERIFY FAILED at 0x00032068! Expected=0x30, Read=0xff, failed byte count from 0x00032000-0x0003207f: 0x18
> > retrying.
> > 1606 at address: 0x00032300VERIFY FAILED at 0x0003236a! Expected=0x7d, Read=0xff, failed byte count from 0x00032300-0x0003237f: 0x16
> > retrying.
> > 1826 at address: 0x00039100VERIFY FAILED at 0x00039157! Expected=0x01, Read=0xff, failed byte count from 0x00039100-0x0003917f: 0x29
> > retrying.
> > 1953 at address: 0x0003d080VERIFY FAILED at 0x0003d0ba! Expected=0xe8, Read=0xff, failed byte count from 0x0003d080-0x0003d0ff: 0x46
> > retrying.
> > 1970 at address: 0x0003d900VERIFY FAILED at 0x0003d957! Expected=0x00, Read=0xff, failed byte count from 0x0003d900-0x0003d97f: 0x29
> > retrying.
> > DONE!at address: 0x0003ff80
> > COMPLETE.
> > Verifying flash... VERIFIED.
>
> This looks not so good. I'm not sure about the exact reason why those
> verifies fail, maybe someone else can comment?
>
>
> Uwe.
> --
> http://hermann-uwe.de | http://sigrok.org
> http://randomprojects.org | http://unmaintained-free-software.org