March 2014 - flashrom - mail.coreboot.org

Re: [flashrom] [PATCH] dummyflasher.c: add an "empty" parameter and initialize with random bytes by default
by Carl-Daniel Hailfinger May 9, 2014

May 9, 2014

Am 21.07.2011 17:54 schrieb Stefan Tauner: > previously the dummies were initialized to be empty (all ones), which makes writes skip > erasing altogether. with this patch the default is to fill it with random bytes instead and the > old behavior can be enforced with stating "empty=yes" on the command line. > > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> > Does the following not work for you? dd if=/dev/urandom bs=1k count=4k of=oldimage.bin flashrom -p dummy:emulate=SST25VF032B,image=oldimage.bin -w newimage.bin Regards, Carl-Daniel -- http://www.hailfinger.org/

5 8

Re: [flashrom] [PATCH] Reorganize shutting down.
by Stefan Tauner May 7, 2014

May 7, 2014

On Fri, 30 Aug 2013 02:00:34 +0200 Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> wrote: > This was mainly driven by getting rid of cli_classic_abort_usage() in cli_classic.c. I forgot to mention something and give a rationale for it: Thereby we also get rid of teasing the user to run flashrom again to show usage information. If we think the user should see the usage information we should show it to him or at least a short syntax summary (which we pretty much lack currently: the programmer parameter syntax is not really well explained). (Small) GNU apps seem to favor printing a similar message like we do. nmap, rsync give their whole usage information which is a bit of a pain because it is so long (unlike flashrom's), ping and hd are examples that just print a syntax summary (but they lack a complete usage help). All of the above is stupid. :P Printing a wall of text does not help and is even counterproductive if one can not scroll. Printing how to print help is also a little bit silly if that help text is not very long anyway. The right™ thing in the case of flashrom is IMHO to print the complete usage help (after improving it to explain the programmer parameter syntax better). RFC. > > This makes the whole main function more consistent and fixes a myriad of > (theoretical) memory leaks. This slightly changes output in most error cases. > doit() stops calling programmer_shutdown() with this patch, beware. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

[PATCH] Added SST25WF080
by jharper＠iseis.com May 4, 2014

May 4, 2014

This patch adds support for the SST25WF080 1 Mbyte SPI flash chip. It has been very minimally tested (basically one each read/write/verify), on Windows XP with a USB Blaster as the programmer. It worked, although it was horribly slow (at least 15 minutes to program 1 MB) - but I have not otherwise used this hardware/software combination to program anything, so that might be normal. - Jason Harper ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

3 3

[PATCH] Added support for MX23L3254
by Michael Coppola May 3, 2014

May 3, 2014

I've added a new definition for the Macronix MX23L3254 chip (4M). Since it is a mask ROM, it doesn't support write or erase. Let me know if the definition is incorrect in describing this. Here's the datasheet for reference: http://www.macronix.com/Lists/DataSheet/Attachments/1233/MX23L3254,%203.0-3… Probe and read works when tested on a real chip: $ ./flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -r trying_again2.bin flashrom v0.9.7-r1767 on Linux 3.8.0-37-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found Macronix flash chip "MX23L3254" (4096 kB, SPI) on buspirate_spi. === This flash part has status UNTESTED for operations: ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -VE, -Vw), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Reading flash... done. Signed-off-by: Michael Coppola <michael.n.coppola(a)gmail.com>

2 3

Compatibility with ECS Socket AM2+
by Leif Middelschulte May 3, 2014

May 3, 2014

Hi, firstofall thanks for your effort with flashrom. It’s really great to be able to flash a bios image independently of Windows. Sorry I didn’t catch the entire/verbose output. Nevertheless I could successfully flash a vendor bios for the following Motherboard: http://www.ecs.com.tw/ECSWebSite/Product/Product_Detail.aspx?DetailID=865&M… Regards, Leif

3 2

Is there a sure-fire way to reset any BIOS flash image to its default, out-of-the-box state with no special equipment?
by linx255＠nym.hush.com May 3, 2014

May 3, 2014

Hi, I am seeking an answer to an apparently obscure question. If I install coreboot on my BIOS (UEFI motherboard) and the computer fails to boot, can I reset the BIOS flash to its default image? I've read about possibly changing jumper positions or removing the BIOS battery, but I can't seem to establish if these are sure-fire ways of restoring the original BIOS flash image. I'd like to attempt to install coreboot on a motherboard that doesn't appear to be coreboot-supported, but only if I know I can completely undo this. Is the default BIOS flash image preserved somewhere on a ROM chip or can it only be restored with special equipment? I definitely do not want to end up with an unusable machine. Thanks! Jim

3 3

Erase/write Bios failed on my computer, need some help plz
by Alex Moracchini May 3, 2014

May 3, 2014

Hello Flahsrom staff ! I have a problem with my stuff and flashrom. I want upgrade my Bios version but the erase/write function of flashrom has failed. I use “ASUS P5N32-SLI SE Deluxe” motherboard ( Bios version 0801 ) and i would install this new Bios version : http://fr.driverscollection.com/_440158660264bb85a1400351c90/T%C3%A9l%C3%A9… First operation : # flashrom -p internal flashrom v0.9.7-r1711 on FreeBSD 10.0-RELEASE (i386) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "NVIDIA CK804". Enabling flash write... OK. Found SST flash chip "SST49LF080A" (1024 kB, LPC) at physical address 0xfff00000 . No operations were specified. Second operation : # flashrom -p internal -w P5N32-SLI-SE-ASUS-Deluxe-0901.ROM flashrom v0.9.7-r1711 on FreeBSD 10.0-RELEASE (i386) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "NVIDIA CK804". Enabling flash write... OK. Found SST flash chip "SST49LF080A" (1024 kB, LPC) at physical address 0xfff00000. Reading old flash chip contents... done. Erasing and writing flash chip... writing sector at 0x28c35200 failed! Reading current flash chip contents... done. FAILED at 0x0003c308! Expected=0xff, Found=0x48, failed byte count from 0x00030000-0x0003ffff: 0x3ca7 ERASE FAILED! FAILED! Have you an idea for fix this problem ? Thanks in advance ! Regards. Alex Johnson

3 3

[PATCH] Add support for nforce1 chipset flash enable
by Marcin Kościelnicki May 3, 2014

May 3, 2014

Signed-Off-By: Marcin Kościelnicki <koriakin(a)0x04.net> Index: chipset_enable.c =================================================================== --- chipset_enable.c (revision 1764) +++ chipset_enable.c (working copy) @@ -1075,6 +1075,15 @@ return 0; } +static int enable_flash_nvidia_nforce(struct pci_dev *dev, const char *name) +{ + rpci_write_byte(dev, 0x7a, 0); + if (enable_flash_nvidia_common(dev, name)) + return ERROR_NONFATAL; + else + return 0; +} + static int enable_flash_nvidia_nforce2(struct pci_dev *dev, const char *name) { rpci_write_byte(dev, 0x92, 0); @@ -1417,6 +1426,7 @@ {0x10de, 0x00e0, OK, "NVIDIA", "NForce3", enable_flash_nvidia_nforce2}, /* Slave, should not be here, to fix known bug for A01. */ {0x10de, 0x00d3, OK, "NVIDIA", "CK804", enable_flash_ck804}, + {0x10de, 0x01b2, OK, "NVIDIA", "NForce", enable_flash_nvidia_nforce}, {0x10de, 0x0260, OK, "NVIDIA", "MCP51", enable_flash_ck804}, {0x10de, 0x0261, NT, "NVIDIA", "MCP51", enable_flash_ck804}, {0x10de, 0x0262, NT, "NVIDIA", "MCP51", enable_flash_ck804},

3 2

AN-M2HD(MCP68): flashrom -V
by Vinarz Balázs May 3, 2014

May 3, 2014

Dear Developer! Heres the outputs of the Abit AN-M2HD board. I cant wrote the Winbod chip. xubuntu@xubuntu:~/Desktop$ sudo flashrom -p internal -Eflashrom v0.9.6.1-r1563 on Linux 3.13.0-8-generic (x86_64)flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP67". Enabling flash write... This chipset is not really supported yet. Guesswork...Please send the output of "flashrom -V" to flashrom(a)flashrom.org withyour board name: flashrom -V as the subject to help us finish support for yourchipset. Thanks.OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Erasing and writing flash chip... Erase/write done.xubuntu@xubuntu:~/Desktop$ sudo flashrom -p internal -w JN.BIN flashrom v0.9.6.1-r1563 on Linux 3.13.0-8-generic (x86_64)flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK.Found chipset "NVIDIA MCP67". Enabling flash write... This ch ipset is not really supported yet. Guesswork...Please send the output of "flashrom -V" to flashrom(a)flashrom.org withyour board name: flashrom -V as the subject to help us finish support for yourchipset. Thanks.OK.Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.Reading old flash chip contents... done.Erasing and writing flash chip... writing sector at 0x7fd89382a000 failed!Reading current flash chip contents... done. writing sector at 0x7fd89382a000 failed!FAILED!Uh oh. Erase/write failed. Checking if anything changed.Good. It seems nothing was changed.Writing to the flash chip apparently didn't do anything.This means we have to add special support for your board, programmer or flash chip.Please report this on IRC at irc.freenode.net (channel #flashrom) ormail flashrom@flashrom.org!-------------------------------------------------------------------------------You may now re boot or simply leave the machine running.xub! untu@xubuntu:~/Desktop$ sudo flashrom -p internal -Vflashrom v0.9.6.1-r1563 on Linux 3.13.0-8-generic (x86_64)flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.1, little endianCommand line (3 args): flashrom -p internal -VCalibrating delay loop... OS timer resolution is 1 usecs, 388M loops per second, delay more than 10% too short (got 65% of expected delay), recalculating... 494M loops per second, delay more than 10% too short (got 84% of expected delay), recalculating... 509M loops per second, delay more than 10% too short (got 86% of expected delay), recalculating... 457M loops per second, delay more than 10% too short (got 77% of expected delay), recalculating... 511M loops per second, delay loop is unreliable, trying to continue 10 myus = 9 us, 100 myus = 86 us, 1000 myus = 852 us, 10000 myus = 8542 us, 4 myus = 5 us, OK.Initializing internal programmerNo coreboot table found.DMI string system-manufacturer: " ."DMI string system-product-name: "."DMI string system-version: "Unknow"DMI string baseboard-manufacturer: "http://www.abit.com.tw/"DMI string baseboard-product-name: "AN-M2HD(MCP68)"DMI string baseboard-version: "1.x "DMI string chassis-type: "Desktop"Found chipset "NVIDIA MCP67" with PCI ID 10de:0548. Enabling flash write... This chipset is not really supported yet. Guesswork...ISA/LPC bridge reg 0x8a contents: 0x00, bit 6 is 0, bit 5 is 0Flash bus type is LPCFound SMBus device 10de:0542 at 00:01:1MCP SPI BAR is at 0xfec80000Strange. MCP SPI BAR is valid, but chipset apparently doesn't have SPI enabled.Please send the output of "flashrom -V" to flashrom(a)flashrom.org withyour board name: flashrom -V as the subject to help us finish support for yourchipset. Thanks.OK.The following protocols are supported: LPC.Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content! Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50FLW040B, 5 12 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000.Lockout bits:Hardware bootblock locking (#TBL) is active.Hardware remaining chip locking (#WP) is active..Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xda, id2 0x54Probing for Winb ond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, ! id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash contentProbing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54Found Winbond flash chip "W39V040B" (512 kB, LPC).No operations were specified.Restoring PCI config space for 00:01:0 reg 0x6dRestoring PCI config space for 00:01:0 reg 0x90Restoring PCI config space for 00:01:0 reg 0x8cRestoring PCI config space for 00:01:0 reg 0x88xubuntu@xubuntu:~/Desktop$ Thans

2 1

Support for MX25L12835F
by Tony Li May 3, 2014

May 3, 2014

Hi, Has anyone done support for an MX25L12835F? Thanks, Tony

2 5