flashrom

flashrom@flashrom.org

9164 discussions

Re: [flashrom] Intel D945GCNL Success
by Stefan Tauner 25 Dec '12

25 Dec '12

On Thu, 20 Dec 2012 19:30:26 -0500 Justin Chevrier <jchevrier(a)gmail.com> wrote: > Hi Guys, > > Attached is a successful write (after erasing the contents of the flash) on > the board listed in the subject. I'm running the original rev 10 BIOS > (5/23/2007) on this board, not sure if a newer version of the BIOS on this > board corrects the 'Unknown' chassis type or not. Unfortunately I haven't > been able to investigate as Intel's site only has '.bio' files that don't > match the flash size. I've tried a few things (eg. Intel2AMI) to extract > the true flash file but haven't had any success. Any thoughts on this, or > am I stuck with the Intel tools? > > As always thanks for the great tool! Thanks for the report! I'll add the board to our list of supported boards. If you could send us the output of 'lspci -nnv' too I can whitelist it regarding the chassis type problem too. I am not aware of any tools that can be used to extract (non-AMI) binaries from, but if you find anything out I would be glad to hear it so that we can integrate it into bios_extract. You may wanna play around with ITK: http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/de… but I have little hope... -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] [PATCH] Add a "device" parameter for Dediprog.
by Stefan Tauner 25 Dec '12

25 Dec '12

On Tue, 18 Dec 2012 00:44:53 +0100 Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> wrote: > This patch adds a "device" parameter for Dediprog which enables use of > multiple dediprogs connected to a single machine. Very handy for test racks. > > Example usage: > flashrom -p dediprog:device=0 > flashrom -p dediprog:device=1 > etc... > > The patch was originally written by Nathan Laredo. > Thanks to David Hendricks for submitting it upstream. > Additional error handling, rebasing etc. by Stefan Tauner. > > Signed-off-by: Nathan Laredo <nil(a)google.com> > Signed-off-by: David Hendricks <dhendrix(a)google.com> > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> > --- > That looked way easier (because it was tested and acked on IRC), > than it was in the end, meh. > I have tested the various new input checks, but not the successful path. > Someone needs to write a manpage entry for this option (please). committed in r1628 including a manpage entry written by myself. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

[commit] r1628 - trunk
by repository service 25 Dec '12

25 Dec '12

Author: stefanct Date: Mon Dec 24 23:07:36 2012 New Revision: 1628 URL: http://flashrom.org/trac/flashrom/changeset/1628 Log: Add a "device" parameter for Dediprog. This patch adds a "device" parameter for Dediprog which enables use of multiple dediprogs connected to a single machine. Very handy for test racks. Example usage: flashrom -p dediprog:device=0 flashrom -p dediprog:device=1 etc... The patch was originally written by Nathan Laredo. Thanks to David Hendricks for submitting it upstream. Additional error handling, man page etc. by Stefan Tauner. Signed-off-by: Nathan Laredo <nil(a)google.com> Signed-off-by: David Hendricks <dhendrix(a)google.com> Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Modified: trunk/dediprog.c trunk/flashrom.8 Modified: trunk/dediprog.c ============================================================================== --- trunk/dediprog.c Fri Nov 30 17:46:45 2012 (r1627) +++ trunk/dediprog.c Mon Dec 24 23:07:36 2012 (r1628) @@ -19,6 +19,7 @@ #include <stdio.h> #include <string.h> +#include <errno.h> #include <usb.h> #include "flash.h" #include "chipdrivers.h" @@ -46,7 +47,8 @@ #endif /* Might be useful for other USB devices as well. static for now. */ -static struct usb_device *get_device_by_vid_pid(uint16_t vid, uint16_t pid) +/* device parameter allows user to specify one device of multiple installed */ +static struct usb_device *get_device_by_vid_pid(uint16_t vid, uint16_t pid, unsigned int device) { struct usb_bus *bus; struct usb_device *dev; @@ -54,8 +56,11 @@ for (bus = usb_get_busses(); bus; bus = bus->next) for (dev = bus->devices; dev; dev = dev->next) if ((dev->descriptor.idVendor == vid) && - (dev->descriptor.idProduct == pid)) - return dev; + (dev->descriptor.idProduct == pid)) { + if (device == 0) + return dev; + device--; + } return NULL; } @@ -777,8 +782,9 @@ int dediprog_init(void) { struct usb_device *dev; - char *voltage; + char *voltage, *device; int millivolt = 3500; + long usedevice = 0; int ret; msg_pspew("%s\n", __func__); @@ -792,11 +798,35 @@ msg_pinfo("Setting voltage to %i mV\n", millivolt); } + device = extract_programmer_param("device"); + if (device) { + char *dev_suffix; + errno = 0; + usedevice = strtol(device, &dev_suffix, 10); + if (errno != 0 || device == dev_suffix) { + msg_perr("Error: Could not convert 'device'.\n"); + free(device); + return 1; + } + if (usedevice < 0 || usedevice > UINT_MAX) { + msg_perr("Error: Value for 'device' is out of range.\n"); + free(device); + return 1; + } + if (strlen(dev_suffix) > 0) { + msg_perr("Error: Garbage following 'device' value.\n"); + free(device); + return 1; + } + msg_pinfo("Using device %li.\n", usedevice); + } + free(device); + /* Here comes the USB stuff. */ usb_init(); usb_find_busses(); usb_find_devices(); - dev = get_device_by_vid_pid(0x0483, 0xdada); + dev = get_device_by_vid_pid(0x0483, 0xdada, (unsigned int) usedevice); if (!dev) { msg_perr("Could not find a Dediprog SF100 on USB!\n"); return 1; Modified: trunk/flashrom.8 ============================================================================== --- trunk/flashrom.8 Fri Nov 30 17:46:45 2012 (r1627) +++ trunk/flashrom.8 Mon Dec 24 23:07:36 2012 (r1628) @@ -1,4 +1,4 @@ -.TH FLASHROM 8 "Feb 15, 2012" +.TH FLASHROM 8 "Dec, 2012" .SH NAME flashrom \- detect, read, write, verify and erase flash chips .SH SYNOPSIS @@ -651,6 +651,15 @@ can be .BR 0V ", " 1.8V ", " 2.5V ", " 3.5V or the equivalent in mV. +.sp +An optional +.B device +parameter specifies which of multiple connected Dediprog devices should be used. +Please be aware that the order depends on libusb's usb_get_busses() function and that the numbering starts +at 0. +Usage example to select the second device: +.sp +.B " flashrom \-p dediprog:device=1" .SS .BR "rayer_spi " programmer The default I/O base address used for the parallel port is 0x378 and you can use

1 0

Re: [flashrom] My mainboard is not on the list, but I need to upgrade the Bios
by Gianfranco Liuzzi 24 Dec '12

24 Dec '12

----- Original Message ----- From: Stefan Tauner Sent: 12/15/12 12:42 PM To: Gianfranco Liuzzi Subject: Re: [flashrom] My mainboard is not on the list, but I need to upgrade the Bios On Fri, 14 Dec 2012 21:08:41 -0500 "Gianfranco Liuzzi" <gielle(a)mail.com> wrote: Hi, while there is no guarantee that it will work (and you have to choose the right image of course), I do not see any potential problems in the log. > Multiple flash chips were detected: "W39V040B", "W39V040FB" > Please specify which chip to use with the -c <chipname> option. You just has to use the option to select one of the chips. If you want to make sure then look at the chip on the board, but the two chips are similar enough that both should work. Good luck! -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner I was a bit worried about it not working. Can I ask just two other questions, just to be sure since I don't want to lose this mainboard? 1) http://www.asrock.com/mb/VIA/775Dual-VSTA/?cat=Download&os=BIOS This is the download page. Which one should I download, the Windows one or the DOS one? 2) Can you type me the exact command I should input in the terminal with the options in the right order? Not that I don't know how to use it, but I want to be sure I don't accidentally screw up anything. Thanks in advance.

2 1

Report: Gigabyte H55M-S2V F3 read
by dpcimanager＠users.sourceforge.net 21 Dec '12

21 Dec '12

flashrom v0.9.6.1-r1622 on Darwin 12.2.0 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, LLVM Clang 4.1 ((tags/Apple/clang-421.11.66)), little endian Command line (5 args): ~/Library/Developer/Xcode/DerivedData/DPCIManager-bbelwcudjjohmwcfgruzebxpgera/Build/Products/Debug/DPCIManager.app/Contents/MacOS/flashrom -V -r ~/Downloads/Gigabyte H55M-S2V F3.rom -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 396M loops per second, 10 myus = 10 us, 100 myus = 99 us, 1000 myus = 1036 us, 10000 myus = 10406 us, 4 myus = 4 us, OK. Initializing internal programmer Mapping low megabyte at 0x00000400, unaligned size 0xffc00. Mapping low megabyte, 0xffc00 bytes at unaligned 0x00000400. No coreboot table found. DMI string system-manufacturer: "Gigabyte Technology Co., Ltd." DMI string system-product-name: "H55M-S2V" DMI string system-version: " " DMI string baseboard-manufacturer: "Gigabyte Technology Co., Ltd." DMI string baseboard-product-name: "H55M-S2V" DMI string baseboard-version: " " DMI string chassis-type: "Desktop" Found ITE Super I/O, ID 0x8720 on port 0x2e Found chipset "Intel H55" with PCI ID 8086:3b06. Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes BIOS_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled Root Complex Register Block address = 0xfed1c000 GCS = 0xc44: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0x6000 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=0, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=0 Programming OPCODES... done 0x06: 0x3f00 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=63, SME=0 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. 0x58: 0x08ff0000 FREG1: BIOS region (0x00000000-0x008fffff) is read-write. 0x5C: 0x05ff0001 FREG2: Management Engine region (0x00001000-0x005fffff) is read-write. 0x90: 0x00 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 0x91: 0xf84100 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=1, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05d80302 (OPMENU) 0x9C: 0xc79f0190 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00000000 (LVSCC) LVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=0 0xC8: 0x00000000 (UVSCC) UVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=0 0xD0: 0x00000000 (FPB) Enabling hardware sequencing due to multiple flash chips detected. SPI Read Configuration: prefetching disabled, caching enabled, OK. No IT87* serial flash segment enabled. The following protocols are supported: FWH, Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Found 2 attached SPI flash chips with a combined density of 9216 kB. There is only one partition containing the whole address space (0x000000 - 0x8fffff). There are 36864 erase blocks with 256 B each. Found Programmer flash chip "Opaque flash chip" (9216 kB, Programmer-specific) at physical address 0x0. Probing 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 Intel 82802AB, 512 kB: probe_82802ab: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x21, id2 0x67, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x21, id2 0x67, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x21, id2 0x67, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x21, id2 0x67, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0x21, id2 0x49, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x21, id2 0x67, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x21, id2 0x67, 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: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0x21, id2 0x49, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x21, id2 0x67, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x21, id2 0x67, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xf5, id2 0x9b, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Programmer flash chip "Opaque flash chip" (9216 kB, Programmer-specific). Reading flash... Reading 9437184 bytes starting at 0x000000. done. Restoring MMIO space at 0x1000cc8a0 Restoring MMIO space at 0x1000cc89c Restoring MMIO space at 0x1000cc898 Restoring MMIO space at 0x1000cc896 Restoring MMIO space at 0x1000cc894 Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

Intel D945GCNL Success
by Justin Chevrier 21 Dec '12

21 Dec '12

Hi Guys, Attached is a successful write (after erasing the contents of the flash) on the board listed in the subject. I'm running the original rev 10 BIOS (5/23/2007) on this board, not sure if a newer version of the BIOS on this board corrects the 'Unknown' chassis type or not. Unfortunately I haven't been able to investigate as Intel's site only has '.bio' files that don't match the flash size. I've tried a few things (eg. Intel2AMI) to extract the true flash file but haven't had any success. Any thoughts on this, or am I stuck with the Intel tools? As always thanks for the great tool! Justin

1 0

Re: [flashrom] Fwd: BPv3.6 w flashrom
by Nabs 19 Dec '12

19 Dec '12

Hi, i would just like to thank you and let you know i've got it working with flashrom now! :) What worked was to connect the four signal pins to their counterparts (MISO, MOSI, CS, CLK), Ground to Ground, and also Vcc to 3V3, and disconnect the AC power and battery. Kind regards, Nabs ________________________________ From: Idwer Vollering <vidwer(a)gmail.com> To: flashrom <flashrom(a)flashrom.org> Cc: Nabil <nabil.gergis(a)yahoo.com.au>; Nabs <ch12011-7(a)yahoo.com.au> Sent: Wednesday, 5 December 2012 11:32 PM Subject: Fwd: [flashrom] BPv3.6 w flashrom Forwarding. Please "reply to all". ---------- Forwarded message ---------- From: Nabs <ch12011-7(a)yahoo.com.au> Date: 2012/12/5 Subject: Re: [flashrom] BPv3.6 w flashrom To: "vidwer(a)gmail.com" <vidwer(a)gmail.com> Just had a Eureka moment. I think what confused me was the fact that the cables were soldered onto the actual soic clip! So all I need to do is desolder and resolder them into their correct layouts, or desolder and use alligator clips instead? Is that right? Cheers, Nabs. ________________________________ From: Idwer Vollering <vidwer(a)gmail.com>; To: Nabs <ch12011-7(a)yahoo.com.au>; Cc: flashrom(a)flashrom.org <flashrom(a)flashrom.org>; Subject: Re: [flashrom] BPv3.6 w flashrom Sent: Wed, Dec 5, 2012 12:05:04 PM 2012/12/5 Nabs <ch12011-7(a)yahoo.com.au>: > Hi, sorry for the trouble. I'm running bus piratev3.6, bootloaderv4.4, > firmwarev6.1 on flashrom-0.9.6.1, i plan to run the BP at 1M. > > When i run the command "flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -Vr > oldbios.bin" > I get: > " > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on > buspirate_spi. > Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, > id2 0x0 > Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE > WRITE > " etc... > > > I think i have the wiring wrong which is why i get that error, i wonder if > you could help me as its my first time? > I'm trying to use In-circuit programming with a soldered bios chip using an > 'SOIC 8 clip' and it has 8 wires. But the bus pirate has 10 pins. > > From another thread, these are the connections i need: > Bus Pirate "MISO" (Pin 1) <----- SPI Device "DO" (Wire/Pin 2) > Bus Pirate "CS" (Pin 2) -----> SPI Device "CS" (Wire/Pin 1) > Bus Pirate "MOSI" (Pin 3) -----> SPI Device "DI" (Wire/Pin 5) > Bus Pirate "CLK" (Pin 4) -----> SPI Device "CLK" (Wire/Pin 6) > Bus Pirate "GND" (Pin 10) <----> SPI Device "GND" (Wire/Pin 4) > > It appears to me that GND is pin 10 and that the wires of the SOIC8 clip > only contact pins 1-8, so how can this work? > > Also, could i just check the layout of the pins on the bus pirate if i'm > reading it correctly on BPv3.6: > 10 9 > 8 7 > 6 5 > 4 3 > 2 1 > > Corresponding to: > GND 3V3 > +5V ADC > VPU AUX > CLK MOSI > CS MISO Forget the existence of +5V, VPU, ADC and AUX for now ( http://dangerousprototypes.com/docs/Bus_Pirate_I/O_Pin_Descriptions ), connect the clip to the buspirate so that the clip passes the buspirate pins like mentioned in this post: http://www.coreboot.org/pipermail/flashrom/2012-November/010178.html This works for me, with a MX25L1605A soic8 chip: CS# (CS) [1 chip 8] VCC (bridge with buspirate pin 3+7) SO (MISO) [2 chip 7] HOLD# (+3V3) WP# (bridge with buspirate pin 7+8) [3 chip 6] SCLK (CLK) GND (GND) [4 chip 5] SI (MOSI) > > Or are the pin numbers read in the opposite direction? > ie > 9 10 > 7 8 > 5 6 > 3 4 > 1 2 > > Here's an image of my bus pirate if it helps: > http://dangerousprototypes.com/wp-content/media/2012/11/Bus-Pirate-v3.6inte… > > Your help is much appreciated and i appreciate your patience, Nabs. > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

[PATCH] Add a "device" parameter for Dediprog.
by Stefan Tauner 18 Dec '12

18 Dec '12

This patch adds a "device" parameter for Dediprog which enables use of multiple dediprogs connected to a single machine. Very handy for test racks. Example usage: flashrom -p dediprog:device=0 flashrom -p dediprog:device=1 etc... The patch was originally written by Nathan Laredo. Thanks to David Hendricks for submitting it upstream. Additional error handling, rebasing etc. by Stefan Tauner. Signed-off-by: Nathan Laredo <nil(a)google.com> Signed-off-by: David Hendricks <dhendrix(a)google.com> Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- That looked way easier (because it was tested and acked on IRC), than it was in the end, meh. I have tested the various new input checks, but not the successful path. Someone needs to write a manpage entry for this option (please). This should be applied to r1627. dediprog.c | 40 +++++++++++++++++++++++++++++++++++----- 1 file changed, 35 insertions(+), 5 deletions(-) diff --git a/dediprog.c b/dediprog.c index a81cf83..c2b66cc 100644 --- a/dediprog.c +++ b/dediprog.c @@ -19,6 +19,7 @@ #include <stdio.h> #include <string.h> +#include <errno.h> #include <usb.h> #include "flash.h" #include "chipdrivers.h" @@ -46,7 +47,8 @@ static void print_hex(void *buf, size_t len) #endif /* Might be useful for other USB devices as well. static for now. */ -static struct usb_device *get_device_by_vid_pid(uint16_t vid, uint16_t pid) +/* device parameter allows user to specify one device of multiple installed */ +static struct usb_device *get_device_by_vid_pid(uint16_t vid, uint16_t pid, unsigned int device) { struct usb_bus *bus; struct usb_device *dev; @@ -54,8 +56,11 @@ static struct usb_device *get_device_by_vid_pid(uint16_t vid, uint16_t pid) for (bus = usb_get_busses(); bus; bus = bus->next) for (dev = bus->devices; dev; dev = dev->next) if ((dev->descriptor.idVendor == vid) && - (dev->descriptor.idProduct == pid)) - return dev; + (dev->descriptor.idProduct == pid)) { + if (device == 0) + return dev; + device--; + } return NULL; } @@ -777,8 +782,9 @@ static int dediprog_shutdown(void *data) int dediprog_init(void) { struct usb_device *dev; - char *voltage; + char *voltage, *device; int millivolt = 3500; + long usedevice = 0; int ret; msg_pspew("%s\n", __func__); @@ -792,11 +798,35 @@ int dediprog_init(void) msg_pinfo("Setting voltage to %i mV\n", millivolt); } + device = extract_programmer_param("device"); + if (device) { + char *dev_suffix; + errno = 0; + usedevice = strtol(device, &dev_suffix, 10); + if (errno != 0 || device == dev_suffix) { + msg_perr("Error: Could not convert 'device'.\n"); + free(device); + return 1; + } + if (usedevice < 0 || usedevice > UINT_MAX) { + msg_perr("Error: Value for 'device' is out of range.\n"); + free(device); + return 1; + } + if (strlen(dev_suffix) > 0) { + msg_perr("Error: Garbage following 'device' value.\n"); + free(device); + return 1; + } + msg_pinfo("Using device %li.\n", usedevice); + } + free(device); + /* Here comes the USB stuff. */ usb_init(); usb_find_busses(); usb_find_devices(); - dev = get_device_by_vid_pid(0x0483, 0xdada); + dev = get_device_by_vid_pid(0x0483, 0xdada, (unsigned int) usedevice); if (!dev) { msg_perr("Could not find a Dediprog SF100 on USB!\n"); return 1; -- Kind regards, Stefan Tauner

1 0

Re: [flashrom] My mainboard is not on the list, but I need to upgrade the Bios
by Gianfranco Liuzzi 15 Dec '12

15 Dec '12

----- Original Message ----- From: Stefan Tauner Sent: 12/14/12 03:13 AM To: gielle(a)mail.com Subject: Re: [flashrom] My mainboard is not on the list, but I need to upgrade the Bios On Thu, 13 Dec 2012 20:30:51 -0500 gielle(a)mail.com wrote: > I need to upgrade the BIOS version of my mainboard, but is not on the list of supported mainboards. Can you tell me if it will work based on data from similar mainboards? It's an ASRock 775Dual VSTA with a Pentium D processor. Current BIOS version is 2.58, I need it upgraded to 2.90. > please send us the output of flashrom -p internal -V (you can use the -o option to redirect it to a file). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner Here is the output of "flashrom -o /home/lex/flash -p internal -V" Thanks for the reply. flashrom v0.9.5.2-r1546 on Linux 3.2.0-4-amd64 (x86_64) flashrom was built with libpci 3.1.7, GCC 4.6.2, little endian Command line (5 args): flashrom -o /home/lex/flash -p internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 2007M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus = 10005 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "To Be Filled By O.E.M." DMI string system-product-name: "775Dual-VSTA" DMI string system-version: "To Be Filled By O.E.M." DMI string baseboard-manufacturer: " " DMI string baseboard-product-name: "775Dual-VSTA" DMI string baseboard-version: " " DMI string chassis-type: "Desktop" W836xx Hardware Monitor at port 0295 Found Winbond Super I/O, id 60 Found chipset "VIA VT8237A" with PCI ID 1106:3337. Enabling flash write... OK. The following protocols are supported: Non-SPI. Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT29C010A, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT29C020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT29C040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT49BV512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT49F002(N), 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT49F002(N)T, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT49F020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT49F040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Catalyst CAT28F512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Bright BM29F040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for EMST F49B002UA, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Eon EN29F010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)B, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29F002(A)(N)T, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Eon EN29LV640B, 8192 kB: probe_en29lv640b: id1 0x0000, id2 0x0000 Probing for Fujitsu MBM29F004BC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F004TC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Fujitsu MBM29F400BC, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Fujitsu MBM29F400TC, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for Hyundai HY29F002T, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Hyundai HY29F002B, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Hyundai HY29F040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F001BN/BX-B, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Intel 28F001BN/BX-T, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Intel 28F002BC/BL/BV/BX-T, 256 kB: probe_82802ab: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F008S3/S5/SC, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F004B5/BE/BV/BX-T, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 28F400BV/BX/CE/CV-T, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F001T, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)B, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F002(N)T, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29F040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX29LV040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for MoselVitelic V29C51000B, 64 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for MoselVitelic V29C51000T, 64 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for MoselVitelic V29C51400B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for MoselVitelic V29C51400T, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for MoselVitelic V29LC51000, 64 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for MoselVitelic V29LC51001, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for MoselVitelic V29LC51002, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for PMC Pm29F002T, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm29F002B, 256 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV010, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV020, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm39LV512, 64 kB: probe_jedec_common: id1 0x05, id2 0xf0, 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 0x54 Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Sharp LH28F008BJT-BTLZ1, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST28SF040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST29EE010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST29LE010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST29EE020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST29LE020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39SF512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39SF010A, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39SF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39SF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39VF512, 64 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39VF010, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39VF020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39VF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST39VF080, 1024 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, 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 0x54 Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xda, id2 0x54 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 M29F002B, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F002T/NT, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29F400BB, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for ST M29F400BT, 512 kB: probe_m29f400bt: id1 0xff, id2 0xff Probing for ST M29W010B, 128 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M29W512B, 64 kB: probe_jedec_common: id1 0x05, id2 0xf0, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x0f, id2 0x6a, 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, 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 SyncMOS/MoselVitelic {F,S,V}29C51001B, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SyncMOS/MoselVitelic {F,S,V}29C51001T, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SyncMOS/MoselVitelic {F,S,V}29C51002B, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SyncMOS/MoselVitelic {F,S,V}29C51002T, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SyncMOS/MoselVitelic {F,S,V}29C51004B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SyncMOS/MoselVitelic {F,S,V}29C51004T, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SyncMOS/MoselVitelic {S,V}29C31004B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for SyncMOS/MoselVitelic {S,V}29C31004T, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for TI TMS29F002RB, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for TI TMS29F002RT, 256 kB: probe_jedec_common: id1 0x0f, id2 0x6a, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012-old, 128 kB: Old Winbond W29* probe method disabled because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29C010(M)/W29C011A/W29EE011/W29EE012-old' if you have a board with such a chip. Probing for Winbond W29C010(M)/W29C011A/W29EE011/W29EE012, 128 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W29C020(C)/W29C022, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W29C040/P, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W39L040, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Found Winbond flash chip "W39V040B" (512 kB, LPC) at physical address 0xfff80000. Lockout bits: Hardware bootblock locking (#TBL) is not active. Hardware remaining chip locking (#WP) is not active.. Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Found Winbond flash chip "W39V040FB" (512 kB, FWH) at physical address 0xfff80000. Lockout bits: Hardware bootblock locking (#TBL) is not active. Hardware remaining chip locking (#WP) is not active.. Lock status of block at 0x00000000 is Full Access. Lock status of block at 0x00010000 is Full Access. Lock status of block at 0x00020000 is Full Access. Lock status of block at 0x00030000 is Full Access. Lock status of block at 0x00040000 is Full Access. Lock status of block at 0x00050000 is Full Access. Lock status of block at 0x00060000 is Full Access. Lock status of block at 0x00070000 is Full Access. Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W49F002U/N, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W49F020, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0xda, id2 0x54 Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0xda, id2 0x54 Multiple flash chips were detected: "W39V040B", "W39V040FB" Please specify which chip to use with the -c <chipname> option. Restoring PCI config space for 00:11:0 reg 0x40 Restoring PCI config space for 00:11:0 reg 0x41

2 1

My mainboard is not on the list, but I need to upgrade the Bios
by gielle＠mail.com 14 Dec '12

14 Dec '12

I need to upgrade the BIOS version of my mainboard, but is not on the list of supported mainboards. Can you tell me if it will work based on data from similar mainboards? It's an ASRock 775Dual VSTA with a Pentium D processor. Current BIOS version is 2.58, I need it upgraded to 2.90. Thanks in advance.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom