flashrom October 2018

flashrom@flashrom.org

22 participants
27 discussions

Libflashrom development and integration with fwupd
by artur.raglis＠3mdeb.com 24 Oct '18

24 Oct '18

Hello, We would like to contribute to the flashrom project by adding missing libflashrom features like queries, proper flashrom_shutdown etc. Until now, I have implemented and tested missing libflashrom functions from query section [https://www.flashrom.org/Libflashrom] (based on patches from Łukasz Dmitrowski [https://patchwork.coreboot.org/patch/4316/]). There are 2 ways to get required information (e.g. supported programmers): const char **flashrom_supported_programmers(void); //#1 int flashrom_supported_programmers(const char **supported_programmers); //#2 I suppose that returning function status (#2) is not necessary with query functions, so I'll stick to the first approach. What we want to accomplish is remote firmware updates for brand new platforms straight from the factory. To do so, libflashrom will be integrated with fwupd which would control all required lib resources. I have read the conversation in the https://www.mail-archive.com/flashrom@flashrom.org/msg13518.html from which it appears that process callbacks for the progress bar is still high priority task. Are there any new ideas / hints that we need to know for further development? Best regards, Artur Raglis

3 2

IS25LQ080 unlisted chip
by Olev 23 Oct '18

23 Oct '18

I include only important lines (no point pasting probes for everything). I could read the device no problems, did not try programming. Calibrating delay loop... OS timer resolution is 999 usecs, 1860M loops per second, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 999 us, 10000 myus = 9998 us, 3996 myus = 4000 us, OK. Initializing ch341a_spi programmer Device revision is 3.0.4 The following protocols are supported: SPI. Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.5 SFDP number of parameter headers is 2 (NPH = 1). SFDP parameter table header 0/1: ID 0x00, version 1.5 Length 36 B, Parameter Table Pointer 0x000030 Parsing JEDEC flash parameter table... 3-Byte only addressing. Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR. Write chunk size is at least 64 B. Flash chip size is 1024 kB. Block eraser 0: 256 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 256 x 4096 B with opcode 0x20. Block eraser 1: 32 x 32768 B with opcode 0x52 Block eraser 2: 16 x 65536 B with opcode 0xd8 done. SFDP parameter table header 1/1: ID 0x9d, version 1.5 Length 12 B, Parameter Table Pointer 0x000080 === SFDP has autodetected a flash chip which is not natively supported by flashrom yet. All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually. You can help us by mailing us the output of the following command to flashrom(a)flashrom.org: 'flashrom -VV [plus the -p/--programmer parameter]' Thanks for your help! === Found Unknown flash chip "SFDP-capable chip" (1024 kB, SPI) on ch341a_spi.

1 0

Re: [flashrom] Failing to WRITE an eeprom image to an "SST25VF512(A)" eeprom using a Bus Pirate (under Linux)
by awokd 20 Oct '18

20 Oct '18

Adam Ward: > (Flashrom Logfile attached) > > I'm having great difficulty performing a "-w" operation on an SST25VF512(A) > chip using my Bus Pirate under Linux. > > My hardware is as follows: > A brand new EEPROM (fresh from the tube) is *carefully* soldered onto a SMD > SOIC8 breakout board / programming harness I made, the ribbon going to the > bus pirate is less than 80mm long. There is a 0.1 uF decoupling ceramic > cap very close to the power pins on the IC. I have verified that the IC is > receiving 3.3 V from the Bus Pirate. There are no shorts or stray flying > wires anywhere. I have tried turning the speed all the way down to > "spispeed=30k" and the behaviour is the same. I believe the pinouts are > all correct as it looks like the flashrom program can read data from the > chips. > > I have tried 3 separate EEPROM chips (all the same type) just in cast I had > exceeded the write endurance of the silicon. They all fail in the same way > but one of them managed to get to the 5th block before it hanged. > > The log file I have attached just stops at the last line and never gets any > further. > > Can someone suggest a reason for this failure? I really need to get this > working. I can provide photos of the setup if that would help. You could try updating the BP firmware like http://dangerousprototypes.com/forum/viewtopic.php?f=28&t=8498&start=90#p67… . I've read the BP power output is relatively weak. Shouldn't matter if the only thing it's powering is that chip but maybe try an external power supply? Are your CS and WP pins tied appropriately?

1 0

Failing to WRITE an eeprom image to an "SST25VF512(A)" eeprom using a Bus Pirate (under Linux)
by Adam Ward 19 Oct '18

19 Oct '18

(Flashrom Logfile attached) I'm having great difficulty performing a "-w" operation on an SST25VF512(A) chip using my Bus Pirate under Linux. My hardware is as follows: A brand new EEPROM (fresh from the tube) is *carefully* soldered onto a SMD SOIC8 breakout board / programming harness I made, the ribbon going to the bus pirate is less than 80mm long. There is a 0.1 uF decoupling ceramic cap very close to the power pins on the IC. I have verified that the IC is receiving 3.3 V from the Bus Pirate. There are no shorts or stray flying wires anywhere. I have tried turning the speed all the way down to "spispeed=30k" and the behaviour is the same. I believe the pinouts are all correct as it looks like the flashrom program can read data from the chips. I have tried 3 separate EEPROM chips (all the same type) just in cast I had exceeded the write endurance of the silicon. They all fail in the same way but one of them managed to get to the 5th block before it hanged. The log file I have attached just stops at the last line and never gets any further. Can someone suggest a reason for this failure? I really need to get this working. I can provide photos of the setup if that would help. Adam

1 0

Re: [flashrom] flashrom error code message
by Nico Huber 19 Oct '18

19 Oct '18

Hello Mian, On 10/16/18 6:01 AM, MIAN VEREST wrote: > Recently i start to use flashrom software, moreless in a winbond chip i > receive this message, is probably IC could be damage? it's very unlikely to damage a NOR flash. > Verifying flash... FAILED at 0x00016650! Expected=0x3f, Found=0x3d, failed > byte count from 0x00000000-0x007fffff: 0x2 That's just 2B that fail to verify. It could either mean that they weren't written correctly, or that reading is flaky and the failure is spurious. Here's what I'd try: 1. Run verification again (at least 2 times), just use -v instead of -w in your flashrom command. 2a. If you don't always get the same result as above, then reading fails and you'll have to enhance your physical setup somehow. 2b. If you always get the same verification result, reading works, so you can just try again. Flash- rom would only have to fix 2 bytes, that might just work. Nico

1 0

Re: [flashrom] Return to stock chrome book
by Nico Huber 19 Oct '18

19 Oct '18

Hello Edgar, On 10/19/18 7:34 AM, Edgar Correa wrote: > I get an error message when I try to reflash the stock chrome bios onto the > chip and it also says at the beginning that: > Block protection could not be disabled! Chromebooks are supposed to have a write protection screw or switch. Are you sure it's disabled? > Please help me!!!! I am completely lost and need my computer back!!! Please provide more information. Which version of flashrom do you use? There is also a fork of flashrom for Chromebooks, have you tried that? And please provide a full log (add `-o logfile.txt` to your flashrom command and attach that file). And in case you are following some guide or manual, please point us to it. Nico

1 0

Return to stock chrome book
by Edgar Correa 19 Oct '18

19 Oct '18

I get an error message when I try to reflash the stock chrome bios onto the chip and it also says at the beginning that: Block protection could not be disabled! Please help me!!!! I am completely lost and need my computer back!!!

1 0

Test of MX25L25635F programmer: linux_spi:dev=/dev/spidev0.1
by Kasper Revsbech (KREV) 17 Oct '18

17 Oct '18

Herby test report of MX25L25635F attached is reports on: probe read write and erase All tested with susses, from latest master (4acc3f3a8990cda15f04e5eabf028c5cda0d6619) Test setup (if you are interested): A Raspberry Pi 3 programming the MX25L25635F using spi. RPI is directly wired to the NOR flash. Best regards Kasper Revsbech

1 0

Re: [flashrom] flashrom error code message
by MIAN VEREST 16 Oct '18

16 Oct '18

Umm, cheap one :=( but had been working fine til now, with this bios chip. CH341A Black Edition... Thanks. <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Libre de virus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> El lun., 15 de oct. de 2018 a la(s) 23:01, MIAN VEREST (mianverest(a)gmail.com) escribió: > Recently i start to use flashrom software, moreless in a winbond chip i > receive this message, is probably IC could be damage? > > Waiting for your comments. > > thanks in advance. > > Erasing and writing flash chip... Erase/write done in 8 min and 26 sec. > Verifying flash... FAILED at 0x00016650! Expected=0x3f, Found=0x3d, failed > byte count from 0x00000000-0x007fffff: 0x2 > Your flash chip is in an unknown state. > > > > > >

1 0

Re: [flashrom] flashrom error code message
by David Hendricks 16 Oct '18

16 Oct '18

Hello, I've seen this issue in cases where the voltage is not set correctly. What programmer are you using? A verbose log will also help. On Mon, Oct 15, 2018 at 11:28 PM MIAN VEREST <mianverest(a)gmail.com> wrote: > Recently i start to use flashrom software, moreless in a winbond chip i > receive this message, is probably IC could be damage? > > Waiting for your comments. > > thanks in advance. > > Erasing and writing flash chip... Erase/write done in 8 min and 26 sec. > Verifying flash... FAILED at 0x00016650! Expected=0x3f, Found=0x3d, failed > byte count from 0x00000000-0x007fffff: 0x2 > Your flash chip is in an unknown state. > > > > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom October 2018