flashrom

flashrom@flashrom.org

1 participants
9187 discussions

Re: [flashrom] Help: unable to upgrade bios
by David Hendricks 10 Jan '12

10 Jan '12

On Mon, Jan 9, 2012 at 3:20 AM, Raghuramchary Jallipalli < Raghuramchary.Jallipalli(a)lntinfotech.com> wrote: > Thanks David.**** > > As you said, the reason for not programming is due to wrong op.atomic > configuration. Is there any way to set these properly? > It should be set automatically. Carl-Daniel clarified on IRC that the "atomic" cycle flag will always be 0 at the stage they are printed. Sorry for the confusion! I recommend adding a debug print to ich9_run_opcode() to see what the "atomic" flag ends up being: Index: ichspi.c =================================================================== --- ichspi.c (revision 1483) +++ ichspi.c (working copy) @@ -908,6 +908,7 @@ This means the timeout must be sufficient for chip erase of slow high-capacity chips. */ + msg_pdbg("opcode: 0x%02x, spi_type: %u, atomic: %u\n", op.opcode, op.spi_type, op.atomic); switch (op.atomic) { case 2: /* Select second preop. */ Then run "flashrom -V -p internal:this_is_not_a_laptop -r foo.bin" and make sure that the sector erase opcode (0x20) and byte program opcode (0x02) show either "1" or "2" for op.atomic. This will help us to prove whether or not this is the problem you are encountering. **** > > Yes jumper selects the ROM at a time. > Okay. I do not think Flashrom is confused about the flash part, then. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

ASUS M2V-MX SE: Can Winbond flash chip W39V040B (512 kB, LPC) be used?
by Paul Menzel 10 Jan '12

10 Jan '12

Dear Flashrom folks, I got two spare boards with socketed flash chips and hope they can be used also for the ASUS M2V-MX SE which is supported by coreboot [1]. One board is the ASRock AM2NF6G-VSTA with a Winbond flash chip W39V040B (512 kB, LPC) [3]. Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Found Winbond flash chip "W39V040B" (512 kB, LPC). This output says LPC but the shipped flash chip in the ASUS M2V-MX SE seems to be SPI [2]. This chipset supports the following protocols: LPC,FWH,SPI. Calibrating delay loop... OK. Found chip "AMIC A25L40P" (512 KB, SPI) at physical address 0xfff80000. In my board there is the Macronix flash chip MX25L4005 (512 kB, SPI). $ sudo ./flashrom flashrom v0.9.4-r1483 on Linux 3.1.0-1-amd64 (x86_64), built with libpci 3.1.8, GCC 4.6.2, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "VIA VT8237S". Enabling flash write... Mapping VT8237S MMIO registers at 0xfed02000, unaligned size 0x70. OK. Found Macronix flash chip "MX25L4005" (512 kB, SPI) at physical address 0xfff80000. No operations were specified. So the vendor flash chip is SPI but it says the chipset also supports LPC. Is such a socket universal so that I can use the LPC flash chip Winbond W39V040B? Thanks, Paul [1] http://www.asus.com/Product.aspx?P_ID=rO7Bu9kq3D25tXHl&content=specificatio… [2] http://www.coreboot.org/ASUS_M2V-MX_SE [3] http://www.flashrom.org/pipermail/flashrom/2012-January/008512.html

1 1

Re: [flashrom] I lost my backup image and now my pc doesn't start...!
by Stefan Tauner 10 Jan '12

10 Jan '12

On Sun, 8 Jan 2012 16:33:54 +0200 İlhan Kahraman <ilhan805(a)gmail.com> wrote: > It has not respond anything after that, not even any fan has cycled... hello İlhan, your whole story sounds to me a bit like if the hardware has broken coincidentally at the same moment as you wrote to the flash chip. Not starting the fans at power-up is a quite uncommon symptom because normally this is not handled by the host software. if i understood your mails correctly you have re-used the rest of the hardware with the new board and everything works? IMHO the only things that could make the fans not spin are: - broken power supply and/or connections - broken mainboard (voltage regulators, traces, capacitors etc) - shorts by lost screws etc. - broken/dusted or unconnected fan :) i guess this wont help you much, but besides the steps you tried already, i dont know anything either, sorry. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

[PATCH] Fix error messages regarding long options
by Stefan Tauner 10 Jan '12

10 Jan '12

Use getopt_long's flag field to distinguish short and long options where needed and name both variants if this is not sufficient. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- the const bits are not really needed, but at least they make more sense than the static modifier i hope :) option_index is used to index the long_options array hence it has to be guaranteed to be in its range. getopt_long guarantees this in the case opt == 0 afaics so we are safe. cli_classic.c | 28 +++++++++++++++++++--------- 1 files changed, 19 insertions(+), 9 deletions(-) diff --git a/cli_classic.c b/cli_classic.c index da658a6..f864b05 100644 --- a/cli_classic.c +++ b/cli_classic.c @@ -177,13 +177,15 @@ int main(int argc, char *argv[]) enum programmer prog = PROGRAMMER_INVALID; int ret = 0; - static const char optstring[] = "r:Rw:v:nVEfc:m:l:i:p:Lzh"; - static const struct option long_options[] = { + const char const optstring[] = "r:Rw:v:nVEfc:m:l:i:p:Lzh"; + int long_verify = -1; + int long_noverify = -1; + const struct option const long_options[] = { {"read", 1, NULL, 'r'}, {"write", 1, NULL, 'w'}, {"erase", 0, NULL, 'E'}, - {"verify", 1, NULL, 'v'}, - {"noverify", 0, NULL, 'n'}, + {"verify", 1, &long_verify, 'v'}, + {"noverify", 0, &long_noverify, 'n'}, {"chip", 1, NULL, 'c'}, {"verbose", 0, NULL, 'V'}, {"force", 0, NULL, 'f'}, @@ -214,6 +216,10 @@ int main(int argc, char *argv[]) */ while ((opt = getopt_long(argc, argv, optstring, long_options, &option_index)) != EOF) { + if (opt == 0) { + opt = long_options[option_index].val; + } + switch (opt) { case 'r': if (++operation_specified > 1) { @@ -241,8 +247,10 @@ int main(int argc, char *argv[]) cli_classic_abort_usage(); } if (dont_verify_it) { - fprintf(stderr, "--verify and --noverify are" - "mutually exclusive. Aborting.\n"); + fprintf(stderr, "%s and %s are " + "mutually exclusive. Aborting.\n", + long_verify != -1 ? "--verify" : "-v", + long_noverify != -1? "--noverify" : "-n"); cli_classic_abort_usage(); } filename = strdup(optarg); @@ -250,8 +258,10 @@ int main(int argc, char *argv[]) break; case 'n': if (verify_it) { - fprintf(stderr, "--verify and --noverify are" - "mutually exclusive. Aborting.\n"); + fprintf(stderr, "%s and %s are " + "mutually exclusive. Aborting.\n", + long_verify != -1 ? "--verify" : "-v", + long_noverify != -1? "--noverify" : "-n"); cli_classic_abort_usage(); } dont_verify_it = 1; @@ -310,7 +320,7 @@ int main(int argc, char *argv[]) break; case 'p': if (prog != PROGRAMMER_INVALID) { - fprintf(stderr, "Error: --programmer specified " + fprintf(stderr, "Error: --programmer/-p specified " "more than once. You can separate " "multiple\nparameters for a programmer " "with \",\". Please see the man page " -- 1.7.1

1 0

Re: [flashrom] flashrom -V
by Stefan Tauner 10 Jan '12

10 Jan '12

On Mon, 9 Jan 2012 22:40:53 +0100 Luc Chante <luc.chante(a)gmail.com> wrote: > flashrom v0.9.4-r1455 on Linux 2.6.32-220.2.1.el6.centos.plus.x86_64 (x86_64), built with libpci 3.1.4, GCC 4.4.5 20110214 (Red Hat 4.4.5-6), little endian > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OS timer resolution is 1 usecs, 2912M loops per second, 10 myus = 11 us, 100 myus = 101 us, 1000 myus = 1000 us, 10000 myus = 9986 us, 4 myus = 5 us, OK. > Initializing internal programmer > No coreboot table found. > DMI string system-manufacturer: "System manufacturer" > DMI string system-product-name: "System Product Name" > DMI string system-version: "System Version" > DMI string baseboard-manufacturer: "ASUSTeK Computer INC." > DMI string baseboard-product-name: "P5N7A-VM" > DMI string baseboard-version: "Rev 1.xx" > DMI string chassis-type: "Desktop" > Found chipset "NVIDIA MCP79" with PCI ID 10de:0aac. > This chipset is marked as untested. If you are using an up-to-date version > of flashrom 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... > ISA/LPC bridge reg 0x8a contents: 0x40, bit 6 is 1, bit 5 is 0 > Flash bus type is SPI > SPI on this chipset is WIP. Please report any success or failure by mailing us the verbose output to flashrom(a)flashrom.org, thanks! > Found SMBus device 10de:0aa2 at 00:03:2 > MCP SPI BAR is at 0xf9f80000 > SPI control is 0xc052, req=0, gnt=0 > 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. > This chipset supports the following protocols: SPI. > […] > Found Winbond flash chip "W25X80" (1024 kB, SPI). > No operations were specified. Hello Luc, thanks for your report! I have marked the chipset and mainboard as tested and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

flashrom output
by Armin 10 Jan '12

10 Jan '12

Hello, I've flashed sucessfully a ASUS M2A-VM HDMI Mainboard. Here is the output: $ sudo flashrom -Vw 2302.BIN flashrom v0.9.4-r1394 on Linux 3.0.0-14-generic (x86_64), built with libpci 3.1.7, GCC 4.6.1, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 666M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 1011 us, 10000 myus = 10013 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "M2A-VM HDMI" DMI string baseboard-version: "1.XX " DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8716 on port 0x2e Found chipset "AMD SB600" with PCI ID 1002:438d. Enabling flash write... SPI base address is at 0x0 ROM strap override is not active OK. This chipset supports the following protocols: LPC, FWH. No IT87* serial flash segment enabled. Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xf8, id2 0x0d, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, 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 0xd0 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xf8, id2 0x0d, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xf8, id2 0x0d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xf8, id2 0x0d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xf8, id2 0x0d, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Found Winbond flash chip "W39V080A" (1024 kB, LPC) at physical address 0xfff00000. Lockout bits: Hardware bootblock locking (#TBL) is not active. Hardware remaining chip locking (#WP) is not active.. Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 === This flash part has status UNTESTED for operations: PROBE READ 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, -Vw, -VE), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x00ffff:S, 0x010000-0x01ffff:EW, 0x020000-0x02ffff:E, 0x030000-0x03ffff:EW, 0x040000-0x04ffff:EW, 0x050000-0x05ffff:EW, 0x060000-0x06ffff:EW, 0x070000-0x07ffff:EW, 0x080000-0x08ffff:EW, 0x090000-0x09ffff:W, 0x0a0000-0x0affff:W, 0x0b0000-0x0bffff:S, 0x0c0000-0x0cffff:S, 0x0d0000-0x0dffff:W, 0x0e0000-0x0effff:EW, 0x0f0000-0x0fffff:EW Erase/write done. Verifying flash... VERIFIED. $ sudo flashrom -Vr old_bios.BIN flashrom v0.9.4-r1394 on Linux 3.0.0-14-generic (x86_64), built with libpci 3.1.7, GCC 4.6.1, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 2 usecs, 664M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 997 us, 10000 myus = 10067 us, 8 myus = 9 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "M2A-VM HDMI" DMI string baseboard-version: "1.XX " DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8716 on port 0x2e Found chipset "AMD SB600" with PCI ID 1002:438d. Enabling flash write... SPI base address is at 0x0 ROM strap override is not active OK. This chipset supports the following protocols: LPC, FWH. No IT87* serial flash segment enabled. Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, 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 0xd0 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Found Winbond flash chip "W39V080A" (1024 kB, LPC) at physical address 0xfff00000. Lockout bits: Hardware bootblock locking (#TBL) is not active. Hardware remaining chip locking (#WP) is not active.. Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 === This flash part has status UNTESTED for operations: PROBE READ 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, -Vw, -VE), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Reading flash... done. $ sudo flashrom -V flashrom v0.9.4-r1394 on Linux 3.0.0-14-generic (x86_64), built with libpci 3.1.7, GCC 4.6.1, little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OS timer resolution is 1 usecs, 665M loops per second, 10 myus = 12 us, 100 myus = 101 us, 1000 myus = 1010 us, 10000 myus = 10009 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "M2A-VM HDMI" DMI string baseboard-version: "1.XX " DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8716 on port 0x2e Found chipset "AMD SB600" with PCI ID 1002:438d. Enabling flash write... SPI base address is at 0x0 ROM strap override is not active OK. This chipset supports the following protocols: LPC, FWH. No IT87* serial flash segment enabled. Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, 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 0xd0 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xda, id2 0xd0 Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x75, id2 0x91, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xaa, id2 0xbb, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Found Winbond flash chip "W39V080A" (1024 kB, LPC) at physical address 0xfff00000. Lockout bits: Hardware bootblock locking (#TBL) is not active. Hardware remaining chip locking (#WP) is not active.. Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xda, id2 0xd0 Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xda, id2 0xd0 === This flash part has status UNTESTED for operations: PROBE READ 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, -Vw, -VE), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! No operations were specified. Cheers and thanks for writing flashrom Armin

2 1

X8DTT-H
by Jimmie Tauriainen 09 Jan '12

09 Jan '12

Hi, This is a Supermicro X8DTT-HIBQF but it uses the same BIOS as X8DTT-H as refered in DMI. Probably all H8DTT* boards uses same. Anyway attaching flashrom -V outputs. root@spts-10-143:~/flashrom# dmidecode -t baseboard # dmidecode 2.9 SMBIOS 2.6 present. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Supermicro Product Name: X8DTT-H Version: 2.0 Serial Number: 1234567890 Asset Tag: 1234567890 Features: Board is a hosting board Board is replaceable Location In Chassis: 1234567890 Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Best regards, Jimmie

4 5

flashrom -V
by Luc Chante 09 Jan '12

09 Jan '12

missing files

1 0

flashrom -V
by Luc Chante 09 Jan '12

09 Jan '12

MB : Asus P5N7A-VM old bios vers. : 512 new bios vers. : 519 # flashrom flashrom v0.9.4-r1455 on Linux 2.6.32-220.2.1.el6.centos.plus.x86_64 (x86_64), built with libpci 3.1.4, GCC 4.4.5 20110214 (Red Hat 4.4.5-6), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found chipset "NVIDIA MCP79". This chipset is marked as untested. If you are using an up-to-date version of flashrom 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 0xf9f80000, 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. This chipset supports the following protocols: SPI. Found Winbond flash chip "W25X80" (1024 kB, SPI) at physical address 0xfff00000. No operations were specified. Saving old ROM : Succed Writind new ROM : Succed (no reboot now) After rebooting it works just fine. Thx for flashrom utility.

1 0

Re: [flashrom] Help: unable to upgrade bios
by Raghuramchary Jallipalli 09 Jan '12

09 Jan '12

Thanks David. As you said, the reason for not programming is due to wrong op.atomic configuration. Is there any way to set these properly? Yes jumper selects the ROM at a time. Thanks for the help, Raghu From: David Hendricks [mailto:dhendrix@google.com] Sent: Saturday, January 07, 2012 4:42 AM To: Raghuramchary Jallipalli Cc: flashrom(a)flashrom.org; V Balaji; Vishnuvardhan Reddy Subject: Re: [flashrom] Help: unable to upgrade bios On Fri, Jan 6, 2012 at 5:12 AM, Raghuramchary Jallipalli <Raghuramchary.Jallipalli(a)lntinfotech.com<mailto:Raghuramchary.Jallipalli@lntinfotech.com>> wrote: The force option enable worked and we were able to program the AT25DF321A flash. But the contents are wrong and the board was not able to come up. Please see attached for the verbose output for both read and write. There is a high likelihood that either the Management Engine (ME) or embedded controller (EC) is interfering with Flashrom operation. One concern is that flashrom does not appear to set the op.atomic field properly: 0x94: 0x0606 (PREOP) 0x96: 0x0be4 (OPTYPE) 0x98: 0x02030105 (OPMENU) 0x9C: 0xff9f3c20 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xD0: 0x00000000 (FPB) Reading OPCODES... done preop0=0x06, preop1=0x06 op[0]=0x05, 0, 0 op[1]=0x01, 1, 0 op[2]=0x03, 2, 0 op[3]=0x02, 3, 0 op[4]=0x20, 3, 0 op[5]=0x3c, 2, 0 op[6]=0x9f, 0, 0 op[7]=0xff, 0, 0 The third column shows that none of the opcodes are configured as atomic cycles. Thus, Flashrom does not know to set the SPIC_ACS bit (http://flashrom.org/trac/flashrom/browser/trunk/ichspi.c#L782) when processing these opcodes. If the "atomic" field is not set properly, then it is possible for ME or EC to interfere with flashrom in between write enable (WREN) opcodes such as block erase and program page. On Fri, Jan 6, 2012 at 5:12 AM, Raghuramchary Jallipalli <Raghuramchary.Jallipalli(a)lntinfotech.com<mailto:Raghuramchary.Jallipalli@lntinfotech.com>> wrote: For your info, the board has two flashes(each 4MB) and the bios resides on the second(we have a jumper option to select the flash device). We are confused whether the flashrom selects the correct flash device and program it. Are both ROMs logically present? Or will the jumper only enable one ROM at a given time? If there are multiple ROMs present, then Flashrom use the "Hardware Sequencing" method of flashing when it detects the "Number of Components" (NC) > 0 in the flash descriptor region: http://flashrom.org/trac/flashrom/browser/trunk/ichspi.c#L1742 See FLMAP0 in the Intel documentation for more details, and ensure the NC field is programmed appropriately for your mainboard configuration. -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc. ________________________________ The contents of this e-mail and any attachment(s) may contain confidential or privileged information for the intended recipient(s). Unintended recipients are prohibited from taking action on the basis of information in this e-mail and using or disseminating the information, and must notify the sender and delete it from their system. L&T Infotech will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in this e-mail" ************************************************************************* This email and attachments have been scanned for potential proprietary or sensitive information leakage. Websense Data Security, Protecting Your Information from the Inside Out. www.websense.com *************************************************************************

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom