flashrom December 2012

flashrom@flashrom.org

33 participants
119 discussions

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

Re: [flashrom] flashrom OPCODES for SPI
by Stefan Tauner 13 Dec '12

13 Dec '12

On Wed, 12 Dec 2012 11:13:49 +0400 Николай Николаев <evrinoma(a)gmail.com> wrote: > i'm trying to reprogram spi chip with bios. My sdk-board is consist from > motherboard and especial board. Motherboard has own flash bios chip like a > mx25l6405 and chip SPI interface QM67. Especial board has a spi flash chip > sst25vf016. Used jumpers i'm easy select flash bios chip for programming, > and i select chip sst25vf016. Chip set QM67 is locked to change value > registers opcodes and preop codes. This is codes value match with mx25l6405 > codes. And i can't reprogram selected chip, because opcodes select chip > didn't match with opcodes stored in QM67. > In function > spi_write_status_register Flashrom source code algorithm trying change mode > spi status register to write by sending unlock command JEDEC_WRSR and > JEDEC_EWSR = 0x50. But preop codes register have a value JEDEC_WREN=0x06, > and don't have a value JEDEC_EWSR=0x50. And STATUS register can't be > unlocked, if i change value JEDEC_EWSR on 0x06 (chip sst25vf016 support > this code) the STATUS register is unlock successful. Hi, I don't have a complete SST25VF016 datasheet. In the SST25VF080 datasheet WREN is mentioned but not in relation to WRSR but only "normal" erase/write functions. The SST25VF016B datasheet however clearly states: "The WREN instruction may also be used to allow execution of the Write-Status-Register (WRSR) instruction" It is of course possible that both, the SST25VF080 and the SST25VF016, support WREN for WRSR and your report is a good hint that this is true. Can you confirm that you have the SST25VF016 and not some variation like the SST25VF016B? The "right" way to add support for you would have been to change the chip definition of the SST25VF016B in flashchips.c by swapping FEATURE_WRSR_EWSR for FEATURE_WRSR_EITHER. As you saw in spi_write_status_register, using WREN is the default if both are supported (or none is selected). I have done so in my local branch for the 016 and 80(A) chips and will commit that later. > And now we have a read > and erase function but function write doesn't work, because algorithm use > default_spi_write_aai function. That function use opcode > JEDEC_AAI_WORD_PROGRAMM but opcodes and preopcodes registers doesn't have > this code and we can't write new bios image in flash. But if we will be use > function spi_chip_write_1 we successful write our image into flash chip > sst25vf016. Good. > What you think about, if we exclude some parameters from structure FLASHCTX > (like a feature_bits) and add array of OPCODES (with real opcodes for real > chip) and add function to detect access opcodes for used chips? There is nothing wrong with the feature bits, although the chipset code (in your case ichspi.c) could be more intelligent in handling this (ATM the write enable commands are handled by generic code only). The Intel chipsets are very special and your case even more, so I don't want to introduce complicated changes just because of this (also with the fix i mentioned earlier, it should just work now even on your configuration, feel free to disprove me). The write command/opcode is different. Clearly we want to have something similar to the erasers so that we can have multiple write functions/opcodes per flash chip. This is on my TODO list, but I don't have much time to work on it... -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

W836xx: SuperMicro X8DTU-F: flashrom -V
by Scott Silverman 12 Dec '12

12 Dec '12

# ./flashrom --programmer internal -V flashrom v0.9.6.1-r1564 on Linux 2.6.29.6-sxtickless (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 2.2.3, GCC 4.1.2 20080704 (Red Hat 4.1.2-48), little endian Command line (3 args): ./flashrom --programmer internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 1466M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1001 us, 10000 myus = 10012 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Supermicro" DMI string system-product-name: "X8DTU" DMI string system-version: "1234567890" DMI string baseboard-manufacturer: "Supermicro" DMI string baseboard-product-name: "X8DTU" DMI string baseboard-version: "1234567890" DMI string chassis-type: "Main Server Chassis" W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 1a. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found chipset "Intel ICH10R" with PCI ID 8086:3a16. Enabling flash write... 0x7fffffff/0x7fffffff FWH IDSEL: 0x0 0x7fffffff/0x7fffffff FWH IDSEL: 0x0 0x7fffffff/0x7fffffff FWH IDSEL: 0x1 0x7fffffff/0x7fffffff FWH IDSEL: 0x1 0x7fffffff/0x7fffffff FWH IDSEL: 0x2 0x7fffffff/0x7fffffff FWH IDSEL: 0x2 0x7fffffff/0x7fffffff FWH IDSEL: 0x3 0x7fffffff/0x7fffffff FWH IDSEL: 0x3 0x7fffffff/0x7fffffff FWH IDSEL: 0x4 0x7fffffff/0x7fffffff FWH IDSEL: 0x5 0x7fffffff/0x7fffffff FWH IDSEL: 0x6 0x7fffffff/0x7fffffff FWH IDSEL: 0x7 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x0 Root Complex Register Block address = 0xfed1c000 GCS = 0x460: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0x2008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=0, FLOCKDN=0 Programming OPCODES... done 0x08: 0x003fffc0 (FADDR) 0x90: 0x04 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0x007f10 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=63, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05d80302 (OPMENU) 0x9C: 0xc79f0190 (OPMENU+4) 0xA0: 0x00000000 (BBAR) SPI Read Configuration: prefetching disabled, caching enabled, OK. The following protocols are supported: FWH, SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for AMIC A25LQ032, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Chip status register is 00 Found Atmel flash chip "AT25DF321" (4096 kB, SPI) at physical address 0xffc00000. Chip status register is 00 Chip status register: Sector Protection Register Lock (SRPL) is not set Chip status register: Bit 6 is not set Chip status register: Erase/Program Error (EPE) is not set Chip status register: WP# pin (WPP) is asserted Chip status register: Software Protection Status (SWP): no sectors are protected Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for EMST F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for GigaDevice GD25Q20, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for GigaDevice GD25Q40, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for GigaDevice GD25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for GigaDevice GD25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for GigaDevice GD25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for GigaDevice GD25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for GigaDevice GD25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L512, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L1005, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L2005, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L4005, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L8005, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L3205, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix MX25L12805, 16384 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Numonyx M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Numonyx M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Numonyx M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Numonyx M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Numonyx M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Numonyx N25Q064, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for PMC Pm25LV010, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for PMC Pm25LV512, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Sanyo LF25FW203A, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Spansion S25FL032A, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Spansion S25FL064A, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25LF080A, 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25VF010, 128 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25Q80, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25Q32, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4700 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x41, id2 0x4d, 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 PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x41, id2 0x4d, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: 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 SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x41, id2 0x4d, 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content 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: 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 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 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 0x41, id2 0x4d, 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 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 Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x41, id2 0x4d, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 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 (dual mode), 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Atmel flash chip "AT25DF321" (4096 kB, SPI). No operations were specified. Restoring MMIO space at 0x7fc32bb528a0 Restoring MMIO space at 0x7fc32bb5289c Restoring MMIO space at 0x7fc32bb52898 Restoring MMIO space at 0x7fc32bb52896 Restoring MMIO space at 0x7fc32bb52894 Restoring PCI config space for 00:1f:0 reg 0xdc Thanks, Scott Silverman | IT | Simplex Investments | 312-360-2444 230 S. LaSalle St., Suite 4-100, Chicago, IL 60604

1 0

32 kB chip compatibility
by Sebastian S. Slowalk 12 Dec '12

12 Dec '12

Hi, just wanted to know why flashrom isn't compatible for 32 kB chips, (i.e. 27c256 ones). I'm working with car ECU's eproms and would thank that. Thanks anyway, Sebastian

2 2

Re: [flashrom] [PATCH 3/3] [RFC] Unify usbdev_status and pcidev_status into dev_status.
by Carl-Daniel Hailfinger 12 Dec '12

12 Dec '12

Am 17.11.2012 20:09 schrieb Stefan Tauner: > Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Is there a reason you introduce a .devices struct member inside struct programmer_entry in patch 1 just to rename it to .dev in patch 3? Regards, Carl-Daniel > diff --git a/flashrom.c b/flashrom.c > index d873276..ae8f70c 100644 > --- a/flashrom.c > +++ b/flashrom.c > @@ -65,7 +65,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "internal", > .type = OTHER, > - .devices.note = NULL, > + .devs.note = NULL, > .init = internal_init, > .map_flash_region = physmap, > .unmap_flash_region = physunmap, > @@ -78,7 +78,7 @@ const struct programmer_entry programmer_table[] = { > .name = "dummy", > .type = OTHER, > /* FIXME */ > - .devices.note = "Dummy device, does nothing and logs all accesses\n", > + .devs.note = "Dummy device, does nothing and logs all accesses\n", > .init = dummy_init, > .map_flash_region = dummy_map, > .unmap_flash_region = dummy_unmap, > @@ -90,7 +90,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "nic3com", > .type = PCI, > - .devices.pci = nics_3com, > + .devs.status = nics_3com, > .init = nic3com_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -103,7 +103,7 @@ const struct programmer_entry programmer_table[] = { > /* This programmer works for Realtek RTL8139 and SMC 1211. */ > .name = "nicrealtek", > .type = PCI, > - .devices.pci = nics_realtek, > + .devs.status = nics_realtek, > .init = nicrealtek_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -115,7 +115,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "nicnatsemi", > .type = PCI, > - .devices.pci = nics_natsemi, > + .devs.status = nics_natsemi, > .init = nicnatsemi_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -127,7 +127,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "gfxnvidia", > .type = PCI, > - .devices.pci = gfx_nvidia, > + .devs.status = gfx_nvidia, > .init = gfxnvidia_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -139,7 +139,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "drkaiser", > .type = PCI, > - .devices.pci = drkaiser_pcidev, > + .devs.status = drkaiser_pcidev, > .init = drkaiser_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -151,7 +151,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "satasii", > .type = PCI, > - .devices.pci = satas_sii, > + .devs.status = satas_sii, > .init = satasii_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -163,7 +163,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "atahpt", > .type = PCI, > - .devices.pci = ata_hpt, > + .devs.status = ata_hpt, > .init = atahpt_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -175,7 +175,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "ft2232_spi", > .type = USB, > - .devices.usb = devs_ft2232spi, > + .devs.status = devs_ft2232spi, > .init = ft2232_spi_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -188,7 +188,7 @@ const struct programmer_entry programmer_table[] = { > .name = "serprog", > .type = OTHER, > /* FIXME */ > - .devices.note = "All programmer devices speaking the serprog protocol\n", > + .devs.note = "All programmer devices speaking the serprog protocol\n", > .init = serprog_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -201,7 +201,7 @@ const struct programmer_entry programmer_table[] = { > .name = "buspirate_spi", > .type = OTHER, > /* FIXME */ > - .devices.note = "Dangerous Prototypes Bus Pirate\n", > + .devs.note = "Dangerous Prototypes Bus Pirate\n", > .init = buspirate_spi_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -214,7 +214,7 @@ const struct programmer_entry programmer_table[] = { > .name = "dediprog", > .type = OTHER, > /* FIXME */ > - .devices.note = "Dediprog SF100\n", > + .devs.note = "Dediprog SF100\n", > .init = dediprog_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -227,7 +227,7 @@ const struct programmer_entry programmer_table[] = { > .name = "rayer_spi", > .type = OTHER, > /* FIXME */ > - .devices.note = "RayeR parallel port programmer\n", > + .devs.note = "RayeR parallel port programmer\n", > .init = rayer_spi_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -240,7 +240,7 @@ const struct programmer_entry programmer_table[] = { > .name = "pony_spi", > .type = OTHER, > /* FIXME */ > - .devices.note = "Programmers compatible with SI-Prog, serbang or AJAWe\n", > + .devs.note = "Programmers compatible with SI-Prog, serbang or AJAWe\n", > .init = pony_spi_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -252,7 +252,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "nicintel", > .type = PCI, > - .devices.pci = nics_intel, > + .devs.status = nics_intel, > .init = nicintel_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -264,7 +264,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "nicintel_spi", > .type = PCI, > - .devices.pci = nics_intel_spi, > + .devs.status = nics_intel_spi, > .init = nicintel_spi_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -276,7 +276,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "ogp_spi", > .type = PCI, > - .devices.pci = ogp_spi, > + .devs.status = ogp_spi, > .init = ogp_spi_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -288,7 +288,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "satamv", > .type = PCI, > - .devices.pci = satas_mv, > + .devs.status = satas_mv, > .init = satamv_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > @@ -300,7 +300,7 @@ const struct programmer_entry programmer_table[] = { > { > .name = "linux_spi", > .type = OTHER, > - .devices.note = "Device files /dev/spidev*.*\n", > + .devs.note = "Device files /dev/spidev*.*\n", > .init = linux_spi_init, > .map_flash_region = fallback_map, > .unmap_flash_region = fallback_unmap, > diff --git a/programmer.h b/programmer.h > index 21fa707..90033a9 100644 > --- a/programmer.h > +++ b/programmer.h > @@ -96,15 +96,22 @@ enum programmer_type { > struct programmer_entry { > const char *vendor; > const char *name; > const enum programmer_type type; > union { > const struct pcidev_status *const pci; > const struct usbdev_status *const usb; > const char *const note; > - } devices; > + } devs; > > int (*init) (void); > -- http://www.hailfinger.org/

2 3

flashrom OPCODES for SPI
by Николай Николаев 12 Dec '12

12 Dec '12

hello i'm trying to reprogram spi chip with bios. My sdk-board is consist from motherboard and especial board. Motherboard has own flash bios chip like a mx25l6405 and chip SPI interface QM67. Especial board has a spi flash chip sst25vf016. Used jumpers i'm easy select flash bios chip for programming, and i select chip sst25vf016. Chip set QM67 is locked to change value registers opcodes and preop codes. This is codes value match with mx25l6405 codes. And i can't reprogram selected chip, because opcodes select chip didn't match with opcodes stored in QM67. In function spi_write_status_register Flashrom source code algorithm trying change mode spi status register to write by sending unlock command JEDEC_WRSR and JEDEC_EWSR = 0x50. But preop codes register have a value JEDEC_WREN=0x06, and don't have a value JEDEC_EWSR=0x50. And STATUS register can't be unlocked, if i change value JEDEC_EWSR on 0x06 (chip sst25vf016 support this code) the STATUS register is unlock successful. And now we have a read and erase function but function write doesn't work, because algorithm use default_spi_write_aai function. That function use opcode JEDEC_AAI_WORD_PROGRAMM but opcodes and preopcodes registers doesn't have this code and we can't write new bios image in flash. But if we will be use function spi_chip_write_1 we successful write our image into flash chip sst25vf016. What you think about, if we exclude some parameters from structure FLASHCTX (like a feature_bits) and add array of OPCODES (with real opcodes for real chip) and add function to detect access opcodes for used chips? sorry for my English

1 0

← Newer
1
...
6
7
8
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom December 2012