flashrom June 2013

flashrom@flashrom.org

29 participants
125 discussions

Correupted Bios
by Mike Kallan 09 Jun '13

09 Jun '13

Dear Sir/Madam Let me brief you what happened... I bought a refurbished HP Desktop 4 months ago, and I set up the system FIRST time yesterday. Everything worked find till I updated the bios to the latest. At the end of the flashing, I got a message saying couldn't update the bios and I was forced to reboot the computer. Since that time, my computer doesn't work at all... I flush the bios from the mother board changing the pin and my computer started working except my keyboard and mouse doesn't work at all. So I have to shut down the computer manually by pressing power button on the desktop... If I restart the computer, I won't get anything on the monitor... I would be very grateful you will be able to help me in this situation. My computer details are as follows Model#: HP Pavilion P7-1141 (P7-1000) Prod#: QX351AAR#ABA Motherboard Name: AAHD3-HB Socket Type: FM1 Chipset: AMD Hudson-D3 FCH Form Factor: uATX: 24.3 cm (9.6 inches) x 24.3 cm (9.6 inches) Processor AMD Quad-Core A8-3800 Socket Type: FM1 Memory 8gb (Max. 16-GB) 4-Slots Hard Drive 1-TB 7200rpm Video AMD Radeon HD 6550D (Shared) Audio AMD Hudson-D3 Mother Board Spec & Clearing CMOS http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&dlc=en&docname=c029… http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us… Thanks in advance Mike

1 0

Re: [flashrom] FAILED: <Elitegroup GF8200A>
by Stefan Tauner 08 Jun '13

08 Jun '13

On Fri, 7 Jun 2013 21:09:21 -0400 Knowledge <dark.knowledge.lnx(a)gmail.com> wrote: > thanks in advance, but came up with a misfortune, there was a power > outage in my area and did not have UPS, to start again the pc and did > not respond, I am on a black screen T_T..... > > there will be some way to load the bios by other means? appreciate any > information of hope :'( that's very unfortunate :/ before you try anything else, try to reset the cmos memory (with a jumper usually). maybe the update was successful "enough" and the black screen is just caused by non-default settings. if that does not help there are essentially two options: 1. using the recovery code if it is still intact 2. using an external programmer to rewrite the flash chip usually there is a small part of the bios with a very limited initialization of the mainboard that is able to read bios files from floppy disks and write them to the flash chip (known as bootblock). but there is no floppy connector on that board AFAICS... no idea how this stuff works nowadays. some boards have special means to update via USB sticks, but no idea how good that works in general. also, we don't know if that part of the flash is ok. the error happened in the part where the bootblock usually is... the other option is to use an external programmer which can be another mainboard which also has a dip8 socket for its flash chip. (see http://flashrom.org/Technology#DIP8:_Dual_In-line_Package.2C_8_pins) it is possible to boot with the original chip and then swap it with the wrongly written one and write it again. this does not work with all boards but many. another option is to use a separate device to access the flash chip. for example you could use an arduino or a buspirate or any other embedded hardware that can connect to a PC with some effort. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] FAILED: <Elitegroup GF8200A>
by Knowledge 08 Jun '13

08 Jun '13

PD: I use my old pc pentium III for contact 2013/6/7, Knowledge <dark.knowledge.lnx(a)gmail.com>: > thanks in advance, but came up with a misfortune, there was a power > outage in my area and did not have UPS, to start again the pc and did > not respond, I am on a black screen T_T..... > > there will be some way to load the bios by other means? appreciate any > information of hope :'( > > sorry for my bad English, greetings from chile. > > > > 2013/6/7, Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at>: >> Hi, >> >> can you please retry to write your update with >> sudo flashrom -p internal -w 78NAA512.ROM -VVV -o retry.log >> and if that still fails please try to write the backup with >> sudo flashrom -p internal -w backup.rom -VVV -o backup_write.log >> and send us the files, thanks. >> >> -- >> Kind regards/Mit freundlichen Grüßen, Stefan Tauner >> > > > -- > -- > <a href="dark.knowledge.lnx(a)gmail.com"><img > src="http://img262.imageshack.us/img262/1382/mailex5.png" > border="0"</></a> > > <a href="http://ubuntucounter.geekosophical.net" title="The Ubuntu > Counter Project - user number # 15441"><img > src="http://ubuntucounter.geekosophical.net/img/ubuntu-user2.php?user=15441" > alt="The Ubuntu Counter Project - user number # 15441" /></a> > -- -- <a href="dark.knowledge.lnx(a)gmail.com"><img src="http://img262.imageshack.us/img262/1382/mailex5.png" border="0"</></a> <a href="http://ubuntucounter.geekosophical.net" title="The Ubuntu Counter Project - user number # 15441"><img src="http://ubuntucounter.geekosophical.net/img/ubuntu-user2.php?user=15441" alt="The Ubuntu Counter Project - user number # 15441" /></a>

1 0

Re: [flashrom] FAILED: <Elitegroup GF8200A>
by Stefan Tauner 08 Jun '13

08 Jun '13

Hi, can you please retry to write your update with sudo flashrom -p internal -w 78NAA512.ROM -VVV -o retry.log and if that still fails please try to write the backup with sudo flashrom -p internal -w backup.rom -VVV -o backup_write.log and send us the files, thanks. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

FAILED: <Elitegroup GF8200A>
by Knowledge 07 Jun '13

07 Jun '13

detected NVIDIA MCP78S DMI string system-manufacturer: "ECS" DMI string system-product-name: "GeForce 8000 series" DMI string system-version: "1.0 " DMI string baseboard-manufacturer: "ECS" DMI string baseboard-product-name: "GeForce 8000 series" DMI string baseboard-version: "1.0 " DMI string chassis-type: "Desktop" Found chipset "NVIDIA MCP78S" with PCI ID 10de:075c. wasabi@wasabi-G:~/Descargas/bios$ sudo flashrom -p internal -r backup.rom flashrom v0.9.6.1-r1563 on Linux 3.9.3-pf (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "NVIDIA MCP78S". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... This chipset is not really supported yet. Guesswork... SPI on this chipset is WIP. Please report any success or failure by mailing us the verbose output to flashrom(a)flashrom.org, thanks! Mapping NVIDIA MCP6x SPI at 0xfbf80000, unaligned size 0x544. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. Found Winbond flash chip "W25X80" (1024 kB, SPI) at physical address 0xfff00000. Reading flash... done. wasabi@wasabi-G:~/Descargas/bios$ sudo flashrom -p internal -w 78NAA512.ROM flashrom v0.9.6.1-r1563 on Linux 3.9.3-pf (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "NVIDIA MCP78S". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... This chipset is not really supported yet. Guesswork... SPI on this chipset is WIP. Please report any success or failure by mailing us the verbose output to flashrom(a)flashrom.org, thanks! Mapping NVIDIA MCP6x SPI at 0xfbf80000, unaligned size 0x544. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. Found Winbond flash chip "W25X80" (1024 kB, SPI) at physical address 0xfff00000. Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFY FAILED at 0x000ff300! Expected=0x00, Read=0xff, failed byte count from 0x00000000-0x000fffff: 0xff Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! product page http://www.ecs.com.tw/ECSWebSite/Product/Product_Detail.aspx?DetailID=873&C… bios downloaded http://download.ecsusa.com/dlfileecs/bios/mb/p4/GF8200A/78NAA512.zip -- -- <a href="dark.knowledge.lnx(a)gmail.com"><img src="http://img262.imageshack.us/img262/1382/mailex5.png" border="0"</></a> <a href="http://ubuntucounter.geekosophical.net" title="The Ubuntu Counter Project - user number # 15441"><img src="http://ubuntucounter.geekosophical.net/img/ubuntu-user2.php?user=15441" alt="The Ubuntu Counter Project - user number # 15441" /></a>

1 0

Re: [flashrom] Added chipsets
by Stefan Tauner 04 Jun '13

04 Jun '13

On Mon, 3 Jun 2013 22:38:01 -0400 Steven Zakulec <spzakulec(a)gmail.com> wrote: > So, I think Stefan is going to handle the review of the S25FL128S / 256S > Spansion chips since they're a bit unusual. I'll handle those and maybe some other nitpicks when you two are done, yes. > The E and the uniform sector comment. This is because there are certain > chips that once had (or still do) have hybrid sector setups- the top block > of the chip could have one value, and the bottom block another. There are 3 possible erase sector layouts in this chip family. 'E' has uniform sectors (meaning that every erase address range done by any one opcode is equal in size) and then there are two other variants that split the top or bottom block into a number of subdivisions. As explained on IRC these were invented and useful earlier in computer history for bootblocks. But since flash chips got bigger and usually include quite fine-grained erase opcodes today, I don't think many of those variants of this family are in the wild, but that might be overly naive and optimistic. :) > Flashrom can only handle uniform sectors right now. That is incorrect. Flashrom *does* support them (e.g. Am29F002(N)BT). The problem is that with the current probing methods supported flashrom can not distinguish between those variants of the Micron chips. See Numonxy datasheet of the N25Q128 with "subsectors" (Rev 7, May 2011), section 9.1.1 Read Identification (RDID) explains how to identify the (non-)uniform layouts (respectively) with the bits in the first EDID byte (the second one seems to be not specified btw). The problem is: currently flashrom does only read the first 3 bytes (which is everything there was before they (Atmel has the patent afaik (yes this seems to be really patentable in countries with ridiculous patent rules)) to extend RDID like that). This will be solved by my in my GSoC project this summer. Until then I think it is ok to add them and expect them to be uniform. If there are really non-uniform variants out there the will be erase errors, but using another erase operation (which is done automatically) will work fine. But it is certainly a good idea to document that, hence the comments in flashchips.h. > +#define ST_N25Q256A13 0xBA19 /* N25Q256, 3.0V */ > should be: > +#define ST_N25Q256__3 0xBA19 /* N25Q256, 3.0V */ > > +#define ST_N25Q256A11 0xBB19 /* N25Q256, 1.8V */ > should be: > +#define ST_N25Q256__1 0xBB19 /* N25Q256, 1.8V */ > > +#define ST_N25Q512A13 0xBA20 /* N25Q512, 3.0V */ > should be: > +#define ST_N25Q512__3 0xBA20 /* N25Q512, 3.0V */ > > +#define ST_N25Q512A11 0xBB20 /* N25Q512, 1.8V */ > should be: > +#define ST_N25Q512__1 0xBB20 /* N25Q512, 1.8V */ > > +#define ST_N25Q00AA13 0xBA21 /* N25Q00A, 3.0V */ > should be: > +#define ST_N25Q00A__3 0xBA21 /* N25Q00A, 3.0V */ and please mention non-uniformness if you spot it in one of those datasheets (I have not checked that, but I guess Steven did so already). I will handle any further iterations of this patch set (so please be sure to mail it to the mailing list, Nikolay). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Added chipsets
by Steven Zakulec 04 Jun '13

04 Jun '13

So, I think Stefan is going to handle the review of the S25FL128S / 256S Spansion chips since they're a bit unusual. I'm going to cover the flashchips.h part of the patch, and some issues with chip names/IDs that came up in review of the flashchips.h part. In general, chip names should contain only important characters- unimportant characters should be marked with a . or an _ depending on the field in flashchips.c and with an _ for names in flashchips.h. See http://www.flashrom.org/pipermail/flashrom/2012-July/009599.html for the reasoning here, and N25Q064..1E for an example. The Spansion chips you've added seem to have an extra letter at the end that's not important, so I would remove it. >From flashchips.h: #define ST_N25Q032__1E 0xBB16 /* N25Q032, 1.8V, (uniform sectors expected) */ #define ST_N25Q064__3E 0xBA17 /* N25Q064, 3.0V, (uniform sectors expected) */ #define ST_N25Q064__1E 0xBB17 /* N25Q064, 1.8V, (uniform sectors expected) */ Here's examples of chips with names that have been shortened due to unimportant characters. The underscore ( _ ) is used to replace the unimportant characters. There's also another item there that's important: #define ST_N25Q064__1E 0xBB17 /* N25Q064, 1.8V, (uniform sectors expected) */ The E and the uniform sector comment. This is because there are certain chips that once had (or still do) have hybrid sector setups- the top block of the chip could have one value, and the bottom block another. Flashrom can only handle uniform sectors right now. The N25Q128A13 is a great example of this: the Numonyx datasheet from Feb 2011 mentions it has uniform sectors, but the May 2011 sheet says it has top or bottom sectors +#define ST_N25Q128A13 0xBA18 /* N25Q128, 3.0V */ should be: +#define ST_N25Q128__3E 0xBA18 /* N25Q128, 3.0V, (uniform sectors expected) */ +#define ST_N25Q128A11 0xBB18 /* N25Q128, 1.8V */ should be: +#define ST_N25Q128__1E 0xBB18 /* N25Q128, 1.8V, (uniform sectors expected) */ +#define ST_N25Q256A13 0xBA19 /* N25Q256, 3.0V */ should be: +#define ST_N25Q256__3 0xBA19 /* N25Q256, 3.0V */ +#define ST_N25Q256A11 0xBB19 /* N25Q256, 1.8V */ should be: +#define ST_N25Q256__1 0xBB19 /* N25Q256, 1.8V */ +#define ST_N25Q512A13 0xBA20 /* N25Q512, 3.0V */ should be: +#define ST_N25Q512__3 0xBA20 /* N25Q512, 3.0V */ +#define ST_N25Q512A11 0xBB20 /* N25Q512, 1.8V */ should be: +#define ST_N25Q512__1 0xBB20 /* N25Q512, 1.8V */ +#define ST_N25Q00AA13 0xBA21 /* N25Q00A, 3.0V */ should be: +#define ST_N25Q00A__3 0xBA21 /* N25Q00A, 3.0V */ Please adjust the .name and .model_id fields in flashchips.c so the names are properly shortened as done above: .name uses periods in place of characters .model_id uses underscores ( _ ) in place of characters Please see N25Q064..3E for an example of this in flashchips.c I realize this may be a lot to take in, so ask questions, and if I can't answer it, hopefully someone else on the list can.

1 0

mac address problem with nvidia MCP55V-Pro
by Jon Morby 02 Jun '13

02 Jun '13

hi … I don't suppose anyone has any experience updating or fixing MAC addresses on Nvidea nVIDIA MCP55V-Pro (Supermicro H8DMT+) ? Following an experimental reflash everything went well, except afterwards we noticed the mac address had been reset link/ether 66:77:44:22:33:12 brd ff:ff:ff:ff:ff:ff -- Jon Morby FidoNet - the internet made simple! 10 - 16 Tiller Road, London, E14 8PX tel: 0845 004 3050 / fax: 0845 004 3051

4 5

Re: [flashrom] Added chipsets
by Stefan Tauner 02 Jun '13

02 Jun '13

On Fri, May 17, 2013 at 1:12 AM, Николай Николаев <evrinoma(a)gmail.com>wrote: > Hi Steven > > "Please add page programming eraseblocks" > what did you mean? > > I think this patch is big and i will write a function page erase blocks > (DB hex) after committing patch. Hi Nikolay, I would very much prefer if you could add that function before we commit the M45 series. Feel free to split the existing patch on chip families... I will probably do that anyway before committing it. Another general nitpick: if it is not too much of a hassle please do not spread the TODO comment for the .printlock field over 3 lines; "/* TODO: improve */" is used everywhere else and your editor probably expanded that automatically. Thanks for your continued effort (and thanks to Steven for his reviews too). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] z68extreme4 mainboard
by Stefan Tauner 01 Jun '13

01 Jun '13

On Thu, 16 May 2013 15:21:23 +1000 David MacKinnon <blaedd(a)gmail.com> wrote: > 0x54: 0x000f0000 FREG0: WARNING: Flash Descriptor region (0x00000000-0x0000ffff) is read-only. > 0x58: 0x07ff0400 FREG1: BIOS region (0x00400000-0x007fffff) is read-write. > 0x5C: 0x03ff0010 FREG2: WARNING: Management Engine region (0x00010000-0x003fffff) is locked. > 0x60: 0x00001fff FREG3: Gigabit Ethernet region is unused. > 0x64: 0x00001fff FREG4: Platform Data region is unused. Hello David, thanks for your report! The problem is the locked ME region as quoted above. For more details please see http://flashrom.org/ME I have added the board to our list of (un)supported boards (with an appropriate note) and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom June 2013