Re: [coreboot] coreboot Digest, Vol 46, Issue 148

[Daniele Primon]

Hi, obrain a similar output when trying to flash a proprietary BIOS.
What I guess is that the initial address could be wrong. Here is the
output:

root@debian:~# flashrom -w -v A6T-ASUS-0706.ROMCalibrating delay
loop... OK.No coreboot table found.Found chipset "NVIDIA MCP51",
enabling flash write... OK.Found chip "PMC Pm49FL004" (512 KB) at
physical address 0xfff80000.Flash image seems to be a legacy BIOS.
Disabling checks.Programming page: 0007 at address:
0x00070000Verifying flash... FAILED!  Expected=0xf8, Read=0x68

2008/12/21, [e-mail] :
> Send coreboot mailing list submissions to
>    [e-mail]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://www.coreboot.org/mailman/listinfo/coreboot
> or, via email, send a message with subject or body 'help' to
>    [e-mail]
>
> You can reach the person managing the list at
>    [e-mail]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of coreboot digest..."
>
> Today's Topics:
> Re: need help with #define macro (Joseph Smith)
> Re: flashrom Asus A6T MCP51 PMC Pm49FL004 (razor1394)
>
> Message: 1
> Date: Sun, 21 Dec 2008 10:48:47 -0500
> From: Joseph Smith 
> Subject: Re: [coreboot] need help with #define macro
> To: Peter Stuge 
> Cc: coreboot 
> Message-ID: 
> Content-Type: text/plain; charset="UTF-8"
> > > Sorry, I am still learning more and more every day....
> >
> > And that's a great thing. Please don't let me discourage it.
> > But coreboot isn't really the place to learn C.
>
> I hate to say it Peter sometimes you can be a little discouraging, I think
> it is just embedded in your personality, so I try not to take offence to
> it. For me personally the best way to learn is from my peers, but if it
> irritates people that I ask C related questions on the mailing list I will
> stop, and find help else where.
>
> Message: 2
> Date: Sun, 21 Dec 2008 16:54:46 +0100
> From: razor1394 
> Subject: Re: [coreboot] flashrom Asus A6T MCP51 PMC Pm49FL004
> To: [e-mail]
> Message-ID:
>    
> Content-Type: text/plain; charset="utf-8"
>
> Sorry I forgot...
>
> razor1394@picon:~$ sudo flashrom -V -v backup.bin
> [sudo] password for razor1394:
> Calibrating delay loop... 240M loops per second. OK.
> No coreboot table found.
> Found chipset "NVIDIA MCP51", enabling flash write... OK.
> Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Atmel AT25DF321, 4096 KB: spi_command called, but no SPI
> chipset
> detected
> Probing for AMIC Technology A25L40P, 512 KB: spi_command called, but no SPI
> chipset detected
> Probing for AMIC Technology A49LF040A, 512 KB: probe_jedec: id1 0x9d, id2
> 0x6e
> Probing for AMIC Technology A29040B, 512 KB: probe_29f040b: id1 0xff, id2
> 0xff
> Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0xff, id2
> 0xff
> Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for Macronix MX25L4005, 512 KB: spi_command called, but no SPI
> chipset detected
> Probing for Macronix MX25L8005, 1024 KB: spi_command called, but no SPI
> chipset detected
> Probing for Macronix MX25L1605, 2048 KB: spi_command called, but no SPI
> chipset detected
> Probing for Macronix MX25L3205, 4096 KB: spi_command called, but no SPI
> chipset detected
> Probing for Macronix MX29F002, 256 KB: probe_29f002: id1 0x9d, id2 0x6e
> Probing for PMC Pm25LV010, 128 KB: spi_command called, but no SPI chipset
> detected
> Probing for PMC Pm25LV016B, 2048 KB: spi_command called, but no SPI chipset
> detected
> Probing for PMC Pm25LV020, 256 KB: spi_command called, but no SPI chipset
> detected
> Probing for PMC Pm25LV040, 512 KB: spi_command called, but no SPI chipset
> detected
> Probing for PMC Pm25LV080B, 1024 KB: spi_command called, but no SPI chipset
> detected
> Probing for PMC Pm25LV512, 64 KB: spi_command called, but no SPI chipset
> detected
> Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Found chip "PMC Pm49FL004" (512 KB) at physical address 0xfff80000.
> Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff
> Probing for Spansion S25FL016A, 2048 KB: spi_command called, but no SPI
> chipset detected
> Probing for SST SST25VF016B, 2048 KB: spi_command called, but no SPI
> chipset
> detected
> Probing for SST SST25VF040B, 512 KB: spi_command called, but no SPI chipset
> detected
> Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0xff, id2 0xff
> Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1
> parity violation
> Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1
> parity violation
> Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> Probing for ST M25P05-A, 64 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P10-A, 128 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P20, 256 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P40, 512 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P40-old, 512 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P80, 1024 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P16, 2048 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P32, 4096 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P64, 8192 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M25P128, 16384 KB: spi_command called, but no SPI chipset
> detected
> Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff
> Probing for ST M29W010B, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0x9d, id2 0x6e
> Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0x9d, id2 0x6e
> Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff
> Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff
> Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff
> Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0xff, id2 0xff, id1
> parity violation
> Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W25x10, 128 KB: spi_command called, but no SPI chipset
> detected
> Probing for Winbond W25x20, 256 KB: spi_command called, but no SPI chipset
> detected
> Probing for Winbond W25x40, 512 KB: spi_command called, but no SPI chipset
> detected
> Probing for Winbond W25x80, 1024 KB: spi_command called, but no SPI chipset
> detected
> Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W29EE011, 128 KB:
> ===
>   Probing disabled for Winbond W29EE011 because the probing sequence puts
> the
>   AMIC A49LF040A in a funky state.
>   Use 'flashrom -c W29EE011' if you have a board with this chip.
> ===
> Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1
> parity violation
> Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0xff, did
> 0xff
> Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: vid
> 0x9d, did 0x6e
> Probing for EON unknown EON SPI chip, 0 KB: spi_command called, but no SPI
> chipset detected
> Probing for Macronix unknown Macronix SPI chip, 0 KB: spi_command called,
> but no SPI chipset detected
> Probing for PMC unknown PMC SPI chip, 0 KB: spi_command called, but no SPI
> chipset detected
> Probing for SST unknown SST SPI chip, 0 KB: spi_command called, but no SPI
> chipset detected
> Probing for ST unknown ST SPI chip, 0 KB: spi_command called, but no SPI
> chipset detected
> Flash image seems to be a legacy BIOS. Disabling checks.
> Verifying flash... address: 0x0006e079 FAILED!  Expected=0x09, Read=0x94
>
> 2008/12/21 razor1394
> > I copied the aflash2 folder after installing it with Wine and copied the
> > contents to a USB drive. Then I booted from a Vista live disc with the
> > stick
> > connected but when I tried to launch the aflash2 utility it complained
> > about
> > ASUS ATK0100 UTILITY (ACPI) not being found. So I'm going to try flashing
> > from a USB stick with DOS installed. I know this works in other computers
> > because I have done it several times.
> >
> > 2008/12/21 razor1394
> >
> > razor1394@picon:~$ sudo flashrom -V -v
> > > Calibrating delay loop... 235M loops per second. OK.
> > > No coreboot table found.
> > > Found chipset "NVIDIA MCP51", enabling flash write... OK.
> > > Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff
> > > Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> > > Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> > > Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Atmel AT25DF321, 4096 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for AMIC Technology A25L40P, 512 KB: spi_command called, but no
> > > SPI chipset detected
> > > Probing for AMIC Technology A49LF040A, 512 KB: probe_jedec: id1 0x9d,
> > > id2
> > > 0x6e
> > > Probing for AMIC Technology A29040B, 512 KB: probe_29f040b: id1 0xff,
> > > id2
> > > 0xff
> > > Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0xff, id2
> > > 0xff
> > > Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0xff, id2 0xff
> > > Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff
> > > Probing for Macronix MX25L4005, 512 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for Macronix MX25L8005, 1024 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for Macronix MX25L1605, 2048 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for Macronix MX25L3205, 4096 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for Macronix MX29F002, 256 KB: probe_29f002: id1 0x9d, id2 0x6e
> > > Probing for PMC Pm25LV010, 128 KB: spi_command called, but no SPI
> > > chipset
> > > detected
> > > Probing for PMC Pm25LV016B, 2048 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for PMC Pm25LV020, 256 KB: spi_command called, but no SPI
> > > chipset
> > > detected
> > > Probing for PMC Pm25LV040, 512 KB: spi_command called, but no SPI
> > > chipset
> > > detected
> > > Probing for PMC Pm25LV080B, 1024 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for PMC Pm25LV512, 64 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Found chip "PMC Pm49FL004" (512 KB) at physical address 0xfff80000.
> > >  Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff
> > > Probing for Spansion S25FL016A, 2048 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for SST SST25VF016B, 2048 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for SST SST25VF040B, 512 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0xff, id2 0xff
> > > Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> > > Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0xff, id2 0xff,
> > > id1
> > > parity violation
> > > Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> > > Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> > > Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff,
> > > id1
> > > parity violation
> > > Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff
> > > Probing for ST M25P05-A, 64 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M25P10-A, 128 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M25P20, 256 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M25P40, 512 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M25P40-old, 512 KB: spi_command called, but no SPI
> > > chipset
> > > detected
> > > Probing for ST M25P80, 1024 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M25P16, 2048 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M25P32, 4096 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M25P64, 8192 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M25P128, 16384 KB: spi_command called, but no SPI chipset
> > > detected
> > > Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0xff, id2 0xff
> > > Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0xff, id2 0xff
> > > Probing for ST M29W010B, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0x9d, id2
> > > 0x6e
> > > Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0x9d, id2
> > > 0x6e
> > > Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2
> > > 0xff
> > > Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2
> > > 0xff
> > > Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff
> > > Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0xff, id2 0xff
> > > Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff
> > > Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0xff, id2 0xff, id1
> > > parity violation
> > > Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W25x10, 128 KB: spi_command called, but no SPI
> > > chipset
> > > detected
> > > Probing for Winbond W25x20, 256 KB: spi_command called, but no SPI
> > > chipset
> > > detected
> > > Probing for Winbond W25x40, 512 KB: spi_command called, but no SPI
> > > chipset
> > > detected
> > > Probing for Winbond W25x80, 1024 KB: spi_command called, but no SPI
> > > chipset detected
> > > Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W29EE011, 128 KB:
> > > ===
> > >   Probing disabled for Winbond W29EE011 because the probing sequence
> > > puts
> > > the
> > >   AMIC A49LF040A in a funky state.
> > >   Use 'flashrom -c W29EE011' if you have a board with this chip.
> > > ===
> > > Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff,
> > > id1 parity violation
> > > Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x9d, id2 0x6e
> > > Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0xff,
> > > did
> > > 0xff
> > > Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub:
> > > vid 0x9d, did 0x6e
> > > Probing for EON unknown EON SPI chip, 0 KB: spi_command called, but no
> > > SPI
> > > chipset detected
> > > Probing for Macronix unknown Macronix SPI chip, 0 KB: spi_command
> > > called,
> > > but no SPI chipset detected
> > > Probing for PMC unknown PMC SPI chip, 0 KB: spi_command called, but no
> > > SPI
> > > chipset detected
> > > Probing for SST unknown SST SPI chip, 0 KB: spi_command called, but no
> > > SPI
> > > chipset detected
> > > Probing for ST unknown ST SPI chip, 0 KB: spi_command called, but no SPI
> > > chipset detected
> > > Error: No filename specified.
> > >
> > > 2008/12/21 Peter Stuge
> > >
> > > razor1394 wrote:
> > > > > Reading the old bios worked but writing failed as verification did
> > > > > not pass.
> > > >
> > > > It would be interesting to see the output from verification.
> > > > > Writing was going very slowly. I flashed the backup bios
> > > > > immediately which verified fine and everything worked after reboot.
> > > > > I'm guessing something is suspicious about the new bios.
> > > >
> > > > The problem is quite likely that a GPIO pin of some chip is connected
> > > > to the two write protect pins on the flash chip.
> > > >
> > > > You can run flashrom -V to show their status of them. Please send
> > > > that output also. (Or combine and run flashrom -V -v so we can get
> > > > the verify output in one go.)
> > > > > As the MCP51 flashrom status is marked with a question mark I
> > > > > thought this could be interesting.
> > > >
> > > > Any flashrom failure is interesting! Thanks for the report.
> > > >
> > > > //Peter

coreboot Digest, Vol 46, Issue 148

[Uwe Hermann]

On Fri, Jan 02, 2009 at 10:15:32AM +0000, Daniele Primon wrote:
> Hi, obrain a similar output when trying to flash a proprietary BIOS.
> What I guess is that the initial address could be wrong. Here is the
> output:
>
> root@debian:~# flashrom -w -v A6T-ASUS-0706.ROMCalibrating delay
> loop... OK.No coreboot table found.Found chipset "NVIDIA MCP51",
> enabling flash write... OK.Found chip "PMC Pm49FL004" (512 KB) at
> physical address 0xfff80000.Flash image seems to be a legacy BIOS.
> Disabling checks.Programming page: 0007 at address:
> 0x00070000Verifying flash... FAILED!  Expected=0xf8, Read=0x68

Are you sure your board is supported by flashrom, or works without
special support? See http://www.coreboot.org/Flashrom#Supported_mainboards

Also, have you tried the command multiple times (e.g. 5 times) in a row?
Sometimes there are glitches and writing will not work, but on the next
run it will...

Uwe.

coreboot Digest, Vol 46, Issue 148

[Carl-Daniel Hailfinger]

On 07.01.2009 13:49, Uwe Hermann wrote:
> On Fri, Jan 02, 2009 at 10:15:32AM +0000, Daniele Primon wrote:
> > Hi, obrain a similar output when trying to flash a proprietary BIOS.
> > What I guess is that the initial address could be wrong. Here is the
> > output:
> >
> > root@debian:~# flashrom -w -v A6T-ASUS-0706.ROMCalibrating delay
> > loop... OK.No coreboot table found.Found chipset "NVIDIA MCP51",
> > enabling flash write... OK.Found chip "PMC Pm49FL004" (512 KB) at
> > physical address 0xfff80000.Flash image seems to be a legacy BIOS.
> > Disabling checks.Programming page: 0007 at address:
> > 0x00070000Verifying flash... FAILED!  Expected=0xf8, Read=0x68
>
> Are you sure your board is supported by flashrom, or works without
> special support? See http://www.coreboot.org/Flashrom#Supported_mainboards
>
> Also, have you tried the command multiple times (e.g. 5 times) in a row?
> Sometimes there are glitches and writing will not work, but on the next
> run it will...

Although I claimed back then that MCP51 support worked, that may have
been an error. So far I am aware of no reproducible flashing of any chip
on MCP51.

Regards,
Carl-Daniel

flashrom write/verify fails on ASUS A6T

[Peter Stuge]

Hi Daniele,

Daniele Primon wrote:
> Hi, obrain a similar output when trying to flash a proprietary BIOS.
> What I guess is that the initial address could be wrong. Here is the
> output:
>
> root@debian:~# flashrom -w -v A6T-ASUS-0706.ROM
> Calibrating delay loop... OK.
> No coreboot table found.
> Found chipset "NVIDIA MCP51", enabling flash write... OK.
> Found chip "PMC Pm49FL004" (512 KB) at physical address 0xfff80000.
> Flash image seems to be a legacy BIOS.
> Disabling checks.
> Programming page: 0007 at address: 0x00070000
> Verifying flash... FAILED!  Expected=0xf8, Read=0x68

Please run flashrom again with -V on the command line for verbose
output, and send that to the list. (It will be many lines so please
send plain text without changing the formatting.)

Your mainboard requires some code to be added to flashrom. The flash
chip on the board has two input pins (7 and 8) for write protection,
and at least one of them is enabled at the moment. flashrom needs
code that disables them. Many times I find the easiest way to figure
that code out is to trace the pins and connections on the physical
board using a continuity tester, or ohm meter. Do you have access to
a multimeter?

//Peter