flashrom

flashrom@flashrom.org

5 participants
9186 discussions

Supermicro X6DVL-EG2 results
by Jared Mauch 30 Dec '13

30 Dec '13

[root@nat flashrom]# ./flashrom -p internal -Vw ~jared/6eg21257.rom flashrom v0.9.7-r1764 on Linux 2.6.32-358.18.1.el6.x86_64 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.10, GCC 4.4.7 20120313 (Red Hat 4.4.7-3), little endian Command line (4 args): ./flashrom -p internal -Vw /home/jared/6eg21257.rom Calibrating delay loop... OS timer resolution is 1 usecs, 1635M loops per second, 10 myus = 18 us, 100 myus = 98 us, 1000 myus = 983 us, 10000 myus = 9438 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "Supermicro" DMI string system-product-name: "X6DVL-EG2" DMI string system-version: "1234567890" DMI string baseboard-manufacturer: "Supermicro" DMI string baseboard-product-name: "X6DVL-EG2" DMI string baseboard-version: "1234567890" Found Winbond Super I/O, id 0x52 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: 00. 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 6300ESB" with PCI ID 8086:25a1. 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 disabled 0xffe00000/0xffa00000 FWH decode disabled 0xffd80000/0xff980000 FWH decode disabled 0xffd00000/0xff900000 FWH decode disabled 0xffc80000/0xff880000 FWH decode disabled 0xffc00000/0xff800000 FWH decode disabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled OK. The following protocols are supported: FWH. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x89, id2 0xac Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x89, id2 0xac Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Found Intel flash chip "82802AC" (1024 kB, FWH) at physical address 0xfff00000. Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x89, id2 0xac Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x89, id2 0xac 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 0x89, id2 0xac Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x89, id2 0xac Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x89, id2 0xac 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 0x89, id2 0xac Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x89, id2 0xac Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x89, id2 0xac Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x89, id2 0xac Found Intel flash chip "82802AC" (1024 kB, FWH). === This flash part has status UNTESTED for operations: ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash part. Please include the flashrom output with the additional -V option for all operations you tested (-V, -Vr, -VE, -Vw), and mention which mainboard or programmer you tested. Please mention your board in the subject line. Thanks for your help! Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:S, 0x080000-0x08ffff:S, 0x090000-0x09ffff:S, 0x0a0000-0x0affff:S, 0x0b0000-0x0bffff:S, 0x0c0000-0x0cffff:S, 0x0d0000-0x0dffff:S, 0x0e0000-0x0effff:EReady:BE RUN/FINISH:BE ERROR:PROG OK:VPP OK:PROG RUN/FINISH:WP|TBL#|WP#,ABORT:FAILED at 0x000ec000! Expected=0xff, Found=0x07, failed byte count from 0x000e0000-0x000effff: 0x11ef ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything changed. Good. It seems nothing was changed. Writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. Restoring PCI config space for 00:1f:0 reg 0x4e

1 0

Flashrom report/DELL Optiplex 980
by William Voccia 30 Dec '13

30 Dec '13

Hello, I've attached a verbose Flashrom report for a Dell Optiplex 980 I'm trying to flash. thank you. flashrom v0.9.6.1-r1563 on Linux 3.8.0-19-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.1.9, GCC 4.7.1, little endian Command line (5 args): flashrom -V -w O980-A09.hdr --programmer internal Calibrating delay loop... OS timer resolution is 1 usecs, 1679M loops per second, 10 myus = 10 us, 100 myus = 104 us, 1000 myus = 976 us, 10000 myus = 10145 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "Dell Inc." DMI string system-product-name: "OptiPlex 980 " DMI string system-version: "Not Specified" DMI string baseboard-manufacturer: "Dell Inc." DMI string baseboard-product-name: "0D441T" DMI string baseboard-version: "A01" DMI string chassis-type: "Mini Tower" Found chipset "Intel Q57" with PCI ID 8086:3b0a. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x0 0xffe00000/0xffa00000 FWH IDSEL: 0x0 0xffd80000/0xff980000 FWH IDSEL: 0x0 0xffd00000/0xff900000 FWH IDSEL: 0x0 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 disabled 0xffc00000/0xff800000 FWH decode disabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x300000 bytes BIOS Lock Enable: enabled, BIOS Write Enable: disabled, BIOS_CNTL is 0x2 WARNING: Setting 0xdc from 0x2 to 0x3 on Q57 failed. New value is 0x2. Root Complex Register Block address = 0xfeda8000 GCS = 0xc61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled SPIBAR = 0xfeda8000 + 0x3800 0x04: 0xe008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 WARNING: SPI Configuration Lockdown activated. Reading OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x08: 0x00000000 (FADDR) 0x50: 0x00000a0b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x0a, BRRA 0x0b 0x54: 0x00000000 FREG0: WARNING: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x09ff0700 FREG1: BIOS region (0x00700000-0x009fffff) is read-write. 0x5C: 0x06ff0023 FREG2: WARNING: Management Engine region (0x00023000-0x006fffff) is locked. 0x60: 0x00220021 FREG3: Gigabit Ethernet region (0x00021000-0x00022fff) is read-write. 0x64: 0x00200001 FREG4: WARNING: Platform Data region (0x00001000-0x00020fff) is locked. Please send a verbose log to flashrom(a)flashrom.org if this board is not listed on http://flashrom.org/Supported_hardware#Supported_mainboards yet. Writes have been disabled. You can enforce write support with the ich_spi_force programmer option, but it will most likely harm your hardware! If you force flashrom you will get no support if something breaks. 0x90: 0x04 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf84054 (SSFC) SSFC: SCGO=0, ACS=1, SPOP=0, COP=5, DBC=0, SME=0, SCF=0 0x94: 0x0606 (PREOP) 0x96: 0x4fc8 (OPTYPE) 0x98: 0x029fabab (OPMENU) 0x9C: 0x01050220 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00802005 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x00000000 (FPB) Enabling hardware sequencing due to multiple flash chips detected. SPI Read Configuration: prefetching disabled, caching enabled, PROBLEMS, continuing anyway 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 10240 kB. There is only one partition containing the whole address space (0x000000 - 0x9fffff). There are 2560 erase blocks with 4096 B each. Found Programmer flash chip "Opaque flash chip" (10240 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 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 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 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 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 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: probe_82802ab: id1 0xdc, id2 0x7a, 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 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: probe_82802ab: id1 0xdc, id2 0x7a, 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 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 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 Programmer flash chip "Opaque flash chip" (10240 kB, Programmer-specific). Write/erase is not working yet on your programmer in its current configuration. Aborting. Restoring MMIO space at 0x7f27650948a0 Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

Re: [flashrom] Trouble disabling write-protection on Chromebook
by BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq＠bitmessage.ch 26 Dec '13

26 Dec '13

> Can you try running "flashrom -p host --wp-disable -V" and pasting the > output on paste.flashrom.org? > Here it is: http://paste.flashrom.org/view.php?id=1851 > > If you have a voltmeter handy, you can also try measuring the voltage > on > > > the /WP pin (pin 3). More details on pin configuration can be found in >> the >> > datasheet: >> > >> http://www.winbond-usa.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/… >> > >> >> I don't have voltmeter; I'm sure I could locate one given enough time >> though. Do you have any other suggestions as to steps I might be >> overlooking here? Otherwise, what should I be looking for specifically >> in >> the Winbond data sheet? >> > > Unfortunately I don't have many ideas here... I've only seen this once and > it seemed to be a defective chip since I couldn't change the write-protect > status by removing the chip and using an external programmer. (This was on > a different machine, and not in a retail unit) > > The only reason for failure should be if there is anything bridging the > gap > between the copper pads around the write-protect screw hole, thereby > connecting /WP on the chip to ground. If you have a magnifying glass, can > you inspect just to make sure there is nothing connecting those pads? I took the Chromebook apart and cleaned the area around the write-protect screw hole using alcohol-dabbed q-tips a second time. Visual inspection did not reveal anything that appeared to be joining the two "halves" of the gold screw hole ring. Running "flashrom --wp-disable" as root gave me the same failure message as before, details in the paste. I executed "flashrom -p host --wp-range 0 0" and got this result: flashrom v0.9.4 : 4169bc8 : Sep 21 2013 02:17:24 UTC on Linux 3.4.0 (armv7l), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian expected=0xe0, but actual=0xb8. FAILED Then, executing "flashrom -p host --wp-status" gave this result: flashrom v0.9.4 : 4169bc8 : Sep 21 2013 02:17:24 UTC on Linux 3.4.0 (armv7l), built with libpci 3.1.10, GCC 4.7.x-google 20130114 (prerelease), little endian WP: status: 0x00b8 WP: status.srp0: 1 WP: status.srp1: 0 WP: write protect is enabled. WP: write protect range: start=0x00000000, len=0x00200000

2 1

Re: [flashrom] How to program PIIX4 GPO26 for output to make
by Gelip 26 Dec '13

26 Dec '13

Thx for replay :-). I was not sure wher to improve the code, in flashrom, coreboot or maybe seabios. Now I know :-) P.S. I test command 'setpci -s 00:07.0 b2.w=8000' and this also make flashrom working but byte=e0 is from PCI config space table from vendor BIOS. Thanks again, I will seek help on coreboot list.

1 0

Re: [flashrom] How to program PIIX4 GPO26 for output to make
by Gelip 26 Dec '13

26 Dec '13

Also enable program chip like this: (PCI word register b2) setpci -s 00:07.0 b2.w=e000 or (PCI byte register b3) setpci -s 00:07.0 b3.b=e0 e0h = 224DEC = 11100000 binary (bits 5, 6, 7) Please help add or fix code to make flashrom program.

2 1

Re: [flashrom] How to program PIIX4 GPO26 for output to make flashrom
by Gelip 23 Dec '13

23 Dec '13

I think I found how to enable BIOS chip programming. I make dump PCI config space registers device: 00:07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] while vendor BIOS and while coreboot bios and compare them. I tried to change the DWORD at offset b0 and flashrom no longer displays an error GPO26 :-) This is log after boot debian on coreboot: ======================================================================================== root@debian:~# flashrom -p internal flashrom v0.9.7-r1763 on Linux 2.6.32-5-486 (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. coreboot table found at 0x9fe1c00. Found chipset "Intel PIIX4/4E/4M". Enabling flash write... OK. Enabling full flash access for board "abit BF6"... ERROR: PIIX4 GPO26 not programmed for output. FAILED! Aborting to be safe. Error: Programmer initialization failed. ======================================================================================== No try set PCI register at offset b0: setpci -s 00:07.0 b0.l=e0000105 and now flashrom working :-): ======================================================================================== root@debian:~# flashrom -p internal flashrom v0.9.7-r1763 on Linux 2.6.32-5-486 (i686) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. coreboot table found at 0x9fe1c00. Found chipset "Intel PIIX4/4E/4M". Enabling flash write... OK. Enabling full flash access for board "abit BF6"... OK. Found Winbond flash chip "W49F002U/N" (256 kB, Parallel) at physical address 0xfffc0000. No operations were specified.

1 0

Re: [flashrom] Flashrom fails on write. P4 motherboard
by Gelip 23 Dec '13

23 Dec '13

Cześć. Udało ci się odblokować płytę dla flashrom bo mam podobny problem?

1 0

Checked Pm25LV010 Chip for PEWR
by Matthias Larisch 19 Dec '13

19 Dec '13

Dear all, I successfully flashed a notebooks GPU BIOS SPI Flash Pm25LV010 using flashrom. I don't know why but I used Flashrom 0.9.4 and not the latest one and therefore had to add the WREN feature flag that is already present in 0.9.7. I used the bus pirate with 120kHz SPI mode. Notebook is fine again and a friend of mine happy :) (He flashed some non-mobile gpu bios from within windows using another tool... Don't ask) Regards, Matthias

2 1

Re: [flashrom] Trouble disabling write-protection on Chromebook
by David Hendricks 18 Dec '13

18 Dec '13

On Wed, Dec 18, 2013 at 2:56 PM, David Hendricks <dhendrix(a)google.com>wrote: > On Mon, Dec 16, 2013 at 9:09 PM, < > BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq(a)bitmessage.ch> wrote: > >> >> As root in >> >> developer mode, the output of flashrom -v is "flashrom v0.9.4 : >> 4169bc8 >> >> ...". The first time I ran flashrom --wp-disable, I got a message >> saying >> >> the operation FAILED with error=1. At that point I took the board apart >> >> again and cleaned the write-protect screw hole with q-tips dipped in >> >> rubbing alcohol. When I reassembled the Chromebook and tried again with >> >> flashrom -V --wp-disable, the last few lines I receive are: >> >> >> >> w25_set_srp0: old status: 0xb8 >> >> w25_set_srp0: new status: 0xb8 >> >> w25q_disable_writeprotect(): error=1. >> >> No -i argument is specified, set ignore_fmap. >> >> FAILED >> >> restore_power_management(): Power management enabled >> >> >> >> As you can see, I can't seem to disable write protection on this chip. >> >> I'm >> >> running stock ChromeOS. Any idea what I might be doing wrong? Thanks in >> >> advance. >> > >> > >> > That's weird... Since you have the system taken apart already, can you >> try >> > disconnecting the battery while the machine is unplugged? I'd recommend >> > leaving it disconnected for a minute or so, the idea being to give the >> SPI >> > ROM enough time to fully discharge and reset. >> > >> >> Thanks for responding. I took your advice and disconnected the battery for >> several minutes. After reassembling the board and running flashrom >> --wp-disable again I am receiving the same message (FAILED). flashrom >> --wp-status says: >> >> WP: status: 0x00b8 >> WP: status.srp0: 1 >> WP: status.srp1: 0 >> WP: write protect is enabled. >> WP: write protect range: start=0x00000000, len=0x00200000 > > > Hmmm, that looks correct for normal circumstances (with write-protection > enabled). Flashrom *should* be able to clear bit 7 of SRP0, so the status > should show up be 0x38 after running with --wp-disable. > > Can you try running "flashrom -p host --wp-disable -V" and pasting the > output on paste.flashrom.org? > You can also try "flashrom -p host --wp-range 0 0" and then "flashrom -p host --wp-status" to see if that changes anything. I'm curious if it's just that SRP0 bit that seems stuck. If the /WP pin is not grounded, then hardware write-protection should not be in effect and you should be able to effectively disable write-protection by clearing the range of protected blocks even if SRP0 is set to 1. > > If you have a voltmeter handy, you can also try measuring the voltage >> on > > > the /WP pin (pin 3). More details on pin configuration can be found in >> the >> > datasheet: >> > >> http://www.winbond-usa.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/… >> > >> >> I don't have voltmeter; I'm sure I could locate one given enough time >> though. Do you have any other suggestions as to steps I might be >> overlooking here? Otherwise, what should I be looking for specifically in >> the Winbond data sheet? >> > > Unfortunately I don't have many ideas here... I've only seen this once and > it seemed to be a defective chip since I couldn't change the write-protect > status by removing the chip and using an external programmer. (This was on > a different machine, and not in a retail unit) > > The only reason for failure should be if there is anything bridging the > gap between the copper pads around the write-protect screw hole, thereby > connecting /WP on the chip to ground. If you have a magnifying glass, can > you inspect just to make sure there is nothing connecting those pads? I > assume that since you cleaned the area with rubbing alcohol that there is > no residue from the sticker. I'm wondering if there is a tiny bit of copper > (perhaps from a manufacturing defect) bridging the gap. If so, I'll ask one > of our hardware engineers if it's safe to attempt severing it or if they > have any better ideas. > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] Trouble disabling write-protection on Chromebook
by BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq＠bitmessage.ch 18 Dec '13

18 Dec '13

> On Mon, Dec 16, 2013 at 9:14 AM, < > BM-2cWKH3wgq8zXX9eHfba16oTc8b61ead4Yq(a)bitmessage.ch> wrote: > >> Hello flashrom developers, >> >> I'm having trouble disabling write-protection on my Samsung Arm >> Chromebook. So far I've removed the metallic sticker covering the >> "write-protect screw hole" according to the pictures on the Chromium >> wiki >> < >> http://www.chromium.org/chromium-os/developer-information-for-chrome-os-dev… >> >. >> On the Snow board, this hole ships with no screw in it. > > > Are you sure about that? There should be a screw there... > > I guess I should not have spoken for all Snow boards, but mine certainly did not have a screw in the write-protect screw hole--only the metallic sticker. I did notice this the first time I opened it up, but I wasn't sure what to make of it. >> As root in >> developer mode, the output of flashrom -v is "flashrom v0.9.4 : 4169bc8 >> ...". The first time I ran flashrom --wp-disable, I got a message saying >> the operation FAILED with error=1. At that point I took the board apart >> again and cleaned the write-protect screw hole with q-tips dipped in >> rubbing alcohol. When I reassembled the Chromebook and tried again with >> flashrom -V --wp-disable, the last few lines I receive are: >> >> w25_set_srp0: old status: 0xb8 >> w25_set_srp0: new status: 0xb8 >> w25q_disable_writeprotect(): error=1. >> No -i argument is specified, set ignore_fmap. >> FAILED >> restore_power_management(): Power management enabled >> >> As you can see, I can't seem to disable write protection on this chip. >> I'm >> running stock ChromeOS. Any idea what I might be doing wrong? Thanks in >> advance. > > > That's weird... Since you have the system taken apart already, can you try > disconnecting the battery while the machine is unplugged? I'd recommend > leaving it disconnected for a minute or so, the idea being to give the SPI > ROM enough time to fully discharge and reset. > Thanks for responding. I took your advice and disconnected the battery for several minutes. After reassembling the board and running flashrom --wp-disable again I am receiving the same message (FAILED). flashrom --wp-status says: WP: status: 0x00b8 WP: status.srp0: 1 WP: status.srp1: 0 WP: write protect is enabled. WP: write protect range: start=0x00000000, len=0x00200000 > If you have a voltmeter handy, you can also try measuring the voltage on > the /WP pin (pin 3). More details on pin configuration can be found in the > datasheet: > http://www.winbond-usa.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/… > I don't have voltmeter; I'm sure I could locate one given enough time though. Do you have any other suggestions as to steps I might be overlooking here? Otherwise, what should I be looking for specifically in the Winbond data sheet?

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom