<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hi Carl-Daniel,<br><br>Thanks for the fast feedback. This BIOS has a UEFI boot option which<br>isupports EFI booting an OS. Got it to work for a while and then<br>somehow it managed to hose itself by adding one too many boot options.<br>I suspect a buggy implementation of an EFI boot manager but Intel will<br>not provide any support because (1) I was using Linux and (2) it is<br>a desktop motherboard. I wanted to clean out the EFI boot options.<br><br>Guess I will just have to demand a replacement motherboard under <br>warranty.<br><br>Regards<br>- Finnbarr<br><br><br><br>> Date: Wed, 3 Feb 2010 17:40:07 +0100<br>> From: c-d.hailfinger.devel.2006@gmx.net<br>> To: fpm@hotmail.com<br>> CC: flashrom@flashrom.org<br>> Subject: Re: [flashrom] Error reading Winbond W25x16 on Intel DX48BT2<br>> <br>> Hi Finnbarr,<br>> <br>> On 03.02.2010 17:12, Finnbarr Murphy wrote:<br>> > Here is a failure report against an Intel DX48BT2 motherboard which<br>> > uses a ICH9R and a Winbond W25x16 containing the BIOS.<br>> ><br>> > Command I executed was:<br>> ><br>> > ./flashrom -c W25x16 -rV out.bin<br>> > <br>> > flashrom v0.9.1-r889<br>> > No coreboot table found.<br>> > DMI string 0: " "<br>> > DMI string 1: " "<br>> > DMI string 2: " "<br>> > DMI string 3: "Intel Corporation"<br>> > DMI string 4: "DX48BT2"<br>> > DMI string 5: "AAE26191-205"<br>> > <br>> <br>> Ah, a mainboard manufactured by Intel.<br>> <br>> <br>> > Found chipset "Intel ICH9R", enabling flash write...<br>> > [...]<br>> > 0x98: 0x2002009f (OPMENU)<br>> > 0x9C: 0x00000000 (OPMENU+4)<br>> > [...]<br>> > <br>> <br>> Heh. The BIOS vendor decided to allow writing to the chip (0x02),<br>> erasing (0x20), and identification (0x9f). Reading (0x03) is not allowed.<br>> <br>> <br>> > WARNING: SPI Configuration Lockdown activated.<br>> > <br>> <br>> And the lockdown means that flashrom can't do anything against it.<br>> <br>> <br>> > Generating OPCODES... done<br>> > SPI Read Configuration: prefetching enabled, caching enabled, FAILED!<br>> > This chipset supports the following protocols: FWH,SPI.<br>> > Calibrating delay loop... 805M loops per second, 100 myus = 199 us. OK.<br>> > Probing for Winbond W25x16, 2048 KB: RDID returned 0xef 0x30 0x15. probe_spi_rdid_generic: id1 0xef, id2 0x3015<br>> > Invalid OPCODE 0x05<br>> > Chip status register is 0a<br>> > Found chip "Winbond W25x16" (2048 KB, SPI) at physical address 0xffe00000.<br>> > Reading flash... Invalid OPCODE 0x03<br>> ><br>> ><br>> > Any idea what is going on? According to the W25x16 documentation opcodes<br>> > 0x03 and 0x05 are supported.<br>> > <br>> <br>> Yes, the problem is that Intel decided to disallow any read opcodes in<br>> the chipset configuration. Sorry, but we can't do anything to circumvent<br>> this except for messing with the flash descriptor in a rather dangerous way.<br>> A BIOS/EFI update/downgrade might help.<br>> <br>> Regards,<br>> Carl-Daniel<br>> <br>> -- <br>> Developer quote of the year:<br>> "We are juggling too many chainsaws and flaming arrows and tigers."<br>> <br> </body>
</html>