flashrom

flashrom@flashrom.org

5 participants
9161 discussions

x1 Carbon 1st Gen Boots to Black Screen
by realraw＠tuta.io 27 Jan '18

27 Jan '18

Followed the coreboot wiki entry perfectly, and had no issues reading the flash chip. The 4MB Bios chip in my x1 differs from the Wiki Entry: Found Micron/Numonyx/ST flash chip "N25Q032..3E" (4096 kB, SPI) on linux_spi. Not sure if that impacts anything, however booting I am faced with a Black Screen. Fan is not running at all, and appears nothing is happening. I found this link as well: http://coreboot.coreboot.narkive.com/zUOsG1zN/lenovo-x1-carbon-3460-screen-… Flashed the rom at the end of the suggested mailing list comment, and still black screen. I have included the vbios in my build, so I'm not sure what's wrong. -realraw

2 1

Re: [flashrom] ERASE FAILED on Macronix Bios Chip x220 (Expected 0xff, Found=0x5a)
by Nico Huber 27 Jan '18

27 Jan '18

Hi realraw, you dropped the mailing list in your reply; by accident, I assume. On 27.01.2018 11:01, realraw(a)tuta.io wrote: > The stock bios is currently set at 1.40 and I decided I was going to try > to update to the latest BIOS. However the stock BIOS update utility > does not work, and neither does the USB Bios Boot Utility. Now I see an > error pop up on boot saying, 'Intel ME is in Recovery Mode'. The ME is a microcontroller built into the chipset. You always have to assume that it's running while you flash externally, so it's not unlikely that it gets confused. > > I believe the BIOS has some sort of write protection on, that will not > allow me to erase the BIOS. Is there anything that can be done besides > physically removing the BIOS chip and swapping it for another? The BIOS has no means to control the flash chip, while the system is shut down. Removing the chip to flash, should always work, though. I don't see any reason to swap the chip. > > My setup is the Pomona SOIC 8 Pin clip, female to female jumpers and the > RPi3. I am SSHing into the Pi3 from my w530, and issuing the commands > through that. The RPi3 is connected via the standard power cable that > came with it, and the Thinkpad has Wake - On LAN enabled, but at this > point I believe the issue had to do with something other than my > equipment. Currently the BIOS is on version 1.40, and it was a custom > BIOS that had been floating around the internet. What I missed was what device you are trying to flash. I figured it now from the subject line. I little hidden, IMHO. You should always mention what you are trying to do in the email's body. I'm confident that your problem is not related to any write-protection (nobody else run into such issues with an X220, AFAIK). There are basi- cally two ways to flash an X220: 1. Remove all power (battery + AC) from the board and power the flash chip over the clip. This is generally discouraged unless you know exactly that the other chips on your board are protected against powering up as well (some ThinkPads have a diode on the VCC trace to the flash chip for that). You connect VCC to the clip in this case. 2. Wake-on-LAN state: Use the regular AC to power the board but keep the machine shut down. In this state a lot of components on the board are already active, including the flash chip. Do not attach VCC through the clip, if you do this! I would generally recommend 2. if you have a multimeter and can check that the flash chip is indeed powered. When you attach a network cable you can also see if the LEDs at the ethernet port light up, but this is no 100% reliable indication. Last but not least, the flash chip has two pins /HOLD and /WP that should be pulled up (to VCC). The mainboard should already take care of that, but you should check with a multimeter if that is the case. If not, or if you can't verify it, you should pull these two pins high. Hope that helps, Nico

1 0

ERASE FAILED on Macronix Bios Chip x220 (Expected 0xff, Found=0x5a)
by The_Raven Raven 26 Jan '18

26 Jan '18

I had similar problems. See here: https://www.mail-archive.com/flashrom@flashrom.org/msg13042.html To keep a long story short: As i can remember, i had 4 chips, 2 working and 2 not working. Dont know why. Option 1: Parts of the chip is write protected Option 2: Chip is broken. BTW: Strange "spispeed". Try with "30000"

1 0

ERASE FAILED on Macronix Bios Chip x220 (Expected 0xff, Found=0x5a)
by realraw＠tuta.io 26 Jan '18

26 Jan '18

After having tried all 4 options of flashchips on my bios, they will all fail to erase and then finally write the new Coreboot ROM I've compiled. I have changed power sources, methods of powering the Pi3, as well as all the different SPI speeds. Found Macronix flash chip "MX25L6405" (8192 kB, SPI) on linux_spi.Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on linux_spi.Found Macronix flash chip "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E" (8192 kB, SPI) on linux_spi.Multiple flash chip definitions match the detected chip(s): "MX25L6405", "MX25L6405D", "MX25L6406E/MX25L6408E", "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E" I noticed while Googling flashrom troubleshooting it said something about 'turning write-protection off'. I have absolutely no issues reading the BIOS, and I have md5sum checked it multiple times and they all give the same reading. It seems as if something else is missing that's not allowing the chip to be erased. Here is a log I've included from one of the many failed attempts: flashrom v0.9.9-r1954 on Linux 4.9.77-v7+ (armv7l)flashrom was built with libpci 3.3.1, GCC 5.3.1 20160205, little endianCommand line (8 args): flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=4096 -w /home/pi/coreboot/coreboot.rom -c MX25L6406E/MX25L6408E -o logfile.txtCalibrating delay loop... OS timer resolution is 1 usecs, 595M loops per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 998 us, 10000 myus = 10035 us, 4 myus = 5 us, OK.Initializing linux_spi programmerUsing device /dev/spidev0.0Using 4096 kHz clockThe following protocols are supported: SPI.Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017Found Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on linux_spi.Chip status register is 0x00.Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not setChip status register: Bit 6 is not setChip status register: Block Protect 3 (BP3) is not setChip status register: Block Protect 2 (BP2) is not setChip status register: Block Protect 1 (BP1) is not setChip status register: Block Protect 0 (BP0) is not setChip status register: Write Enable Latch (WEL) is not setChip status register: Write In Progress (WIP/BUSY) is not setThis chip may contain one-time programmable memory. flashrom cannot readand may never be able to write it, hence it may not be able to completelyclone the contents of this chip (see man page for details).Block protection is disabled.Reading old flash chip contents... done.Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x00000fff: 0xe8ERASE FAILED!Reading current flash chip contents... done. Looking for another erase function.Trying erase function 1... 0x000000-0x00ffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x0000ffff: 0x299dERASE FAILED!Reading current flash chip contents... done. Looking for another erase function.Trying erase function 2... 0x000000-0x00ffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x0000ffff: 0x299dERASE FAILED!Reading current flash chip contents... done. Looking for another erase function.Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x007fffff: 0x5d0197ERASE FAILED!Reading current flash chip contents... done. Looking for another erase function.Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00000010! Expected=0xff, Found=0x5a, failed byte count from 0x00000000-0x007fffff: 0x5d0197ERASE FAILED!Looking for another erase function.No usable erase functions left.FAILED!Uh oh. Erase/write failed. Checking if anything has changed.Reading current flash chip contents... done.Good, writing to the flash chip apparently didn't do anything.Please check the connections (especially those to write protection pins) betweenthe programmer and the flash chip. If you think the error is caused by flashromplease report this on IRC at chat.freenode.net (channel #flashrom) ormail flashrom(a)flashrom.org, thanks!

2 1

AT45DB081D Chip tested -> OK
by The_Raven Raven 26 Jan '18

26 Jan '18

Hi I have tested Chip "AT45DB081D" (found on a NIC). Chip works fine. Test Steps: - Read - Erase - Written Data1 - Written Data2 (overwritten) Data1 and Data2 generated with "dd" from "/dev/urandom". Greets

1 0

Re: [flashrom] Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by Nico Huber 26 Jan '18

26 Jan '18

On 26.01.2018 08:41, The_Raven Raven wrote: > I think this is a bug with debian 9, with debian 8 it works without this > parameter. The only bug here is that flashrom doesn't choose a default by itself (or that we didn't tell people to set spispeed= from the very begin- ning). Currently, flashrom just leaves whatever the hardware is con- figured to, which may still work for different setups. You just don't know, and it works less likely now. So, patches are welcome. Nico

1 0

Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by The_Raven Raven 26 Jan '18

26 Jan '18

I think this is a bug with debian 9, with debian 8 it works without this parameter. Searched a long time for this solution, finally i found this report which helps me: https://github.com/flashrom/flashrom/issues/29 Now i see that Nico changed it in the wiki. -> https://flashrom.org/RaspberryPi Thanks! Too bad he changed it not a week ago, that would have me much time saved. ;-) Think you can change it from 1000 to 30000 because it is much much faster and works stable. Greets

1 0

Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by Mamoru Inugami 25 Jan '18

25 Jan '18

Thank you for your reply. I tried your suggestion, I could ientify my chip ! Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xef, id2 0x16 Found Winbond flash chip "W25Q64.W" (8192 kB, SPI). Thank you for your kindly helps !

1 0

Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by The_Raven Raven 25 Jan '18

25 Jan '18

This is a problem (Bug) of raspi. Try this command: flashrom -V -p linux_spi:dev=/dev/spidev0.0,spispeed=30000

1 0

Flashing a Winbond W25Q64FV using a RaspberrPI still fails
by Mamoru Inugami 25 Jan '18

25 Jan '18

Hi, I try to flash Winbond W25Q64FV via Raspberry Pi 3. Datasheet : http://www.alldatasheet.com/datasheet-pdf/pdf/555558/WINBOND/W25Q64FV.html It fails the same as 2016 post, "Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI)." https://mail.coreboot.org/pipermail/flashrom/2016-March/014548.html The attached file is output of flashrom 1.0 with -o option. If you have any help, please inform me.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom