- flashrom - mail.coreboot.org

Re: [flashrom] [coreboot] [LinuxBoot] FOSDEM 2019 deadline today
by Ron Minnich 02 Nov '18

02 Nov '18

ok it's in On Fri, Nov 2, 2018 at 3:54 PM Ron Minnich <rminnich(a)google.com> wrote: > > oh, wait, now the talk appears to be there and it lost all the links I > submitted. holy mackeral. > On Fri, Nov 2, 2018 at 3:53 PM Ron Minnich <rminnich(a)google.com> wrote: > > > > so, I just tried submitting an event to that @@@-for-brains fosdem > > pentabarf site. I can't tell what happened but it seems to have thrown > > all my work away. > > > > I can't believe they're still using penta but it used up my charitable > > instincts for the day, so no talk from me. > > > > ron > > On Fri, Nov 2, 2018 at 2:59 PM Carl-Daniel Hailfinger > > <c-d.hailfinger.devel.2006(a)gmx.net> wrote: > > > > > > In that case, I'd also like to point you to the deadline for submitting > > > main track talks which is tomorrow(!). > > > https://fosdem.org/2019/news/2018-08-10-call-for-participation/ > > > Having a coreboot/LinuxBoot talk there would be awesome. Ron/David, > > > could you submit something or do you have someone in mind who can do that? > > > > > > There's also lightning talks, deadline is a bit later. > > > > > > OK, I'm submitting a request for a stand. I need a backup contact for > > > the stand. Who is willing to do that? AFAICS we can still change the > > > backup contact later if life happens. > > > > > > Regards, > > > Carl-Daniel > > > > > > On 02.11.2018 20:48, David Hendricks wrote: > > > > > > > > > > > > On Fri, Nov 2, 2018 at 9:15 AM 'Ron Minnich' via linuxboot > > > > <linuxboot(a)googlegroups.com <mailto:linuxboot@googlegroups.com>> wrote: > > > > > > > > I"m leaning to yes, by which I mean if you do it, I'll show up. > > > > > > > > I can't believe I said that. > > > > On Fri, Nov 2, 2018 at 7:20 AM Carl-Daniel Hailfinger > > > > <c-d.hailfinger.devel.2006(a)gmx.net > > > > <mailto:c-d.hailfinger.devel.2006@gmx.net>> wrote: > > > > > > > > > > Hi! > > > > > > > > > > FOSDEM next year will be on 2 & 3 February 2019. > > > > > The deadline for applying for a stand is today. > > > > > Do we want a coreboot/flashrom/LinuxBoot stand/booth? > > > > > > > > > > > > Same as what Ron said. I think someone from FB can be there to talk > > > > about coreboot/LinuxBoot stuff and perhaps bring some hardware to demo. > > > > > > > > > > >

1 0

Re: [flashrom] [coreboot] [LinuxBoot] FOSDEM 2019 deadline today
by Ron Minnich 02 Nov '18

02 Nov '18

oh, wait, now the talk appears to be there and it lost all the links I submitted. holy mackeral. On Fri, Nov 2, 2018 at 3:53 PM Ron Minnich <rminnich(a)google.com> wrote: > > so, I just tried submitting an event to that @@@-for-brains fosdem > pentabarf site. I can't tell what happened but it seems to have thrown > all my work away. > > I can't believe they're still using penta but it used up my charitable > instincts for the day, so no talk from me. > > ron > On Fri, Nov 2, 2018 at 2:59 PM Carl-Daniel Hailfinger > <c-d.hailfinger.devel.2006(a)gmx.net> wrote: > > > > In that case, I'd also like to point you to the deadline for submitting > > main track talks which is tomorrow(!). > > https://fosdem.org/2019/news/2018-08-10-call-for-participation/ > > Having a coreboot/LinuxBoot talk there would be awesome. Ron/David, > > could you submit something or do you have someone in mind who can do that? > > > > There's also lightning talks, deadline is a bit later. > > > > OK, I'm submitting a request for a stand. I need a backup contact for > > the stand. Who is willing to do that? AFAICS we can still change the > > backup contact later if life happens. > > > > Regards, > > Carl-Daniel > > > > On 02.11.2018 20:48, David Hendricks wrote: > > > > > > > > > On Fri, Nov 2, 2018 at 9:15 AM 'Ron Minnich' via linuxboot > > > <linuxboot(a)googlegroups.com <mailto:linuxboot@googlegroups.com>> wrote: > > > > > > I"m leaning to yes, by which I mean if you do it, I'll show up. > > > > > > I can't believe I said that. > > > On Fri, Nov 2, 2018 at 7:20 AM Carl-Daniel Hailfinger > > > <c-d.hailfinger.devel.2006(a)gmx.net > > > <mailto:c-d.hailfinger.devel.2006@gmx.net>> wrote: > > > > > > > > Hi! > > > > > > > > FOSDEM next year will be on 2 & 3 February 2019. > > > > The deadline for applying for a stand is today. > > > > Do we want a coreboot/flashrom/LinuxBoot stand/booth? > > > > > > > > > Same as what Ron said. I think someone from FB can be there to talk > > > about coreboot/LinuxBoot stuff and perhaps bring some hardware to demo. > > > > > > > >

1 0

Re: [flashrom] [LinuxBoot] FOSDEM 2019 deadline today
by David Hendricks 02 Nov '18

02 Nov '18

On Fri, Nov 2, 2018 at 9:15 AM 'Ron Minnich' via linuxboot < linuxboot(a)googlegroups.com> wrote: > I"m leaning to yes, by which I mean if you do it, I'll show up. > > I can't believe I said that. > On Fri, Nov 2, 2018 at 7:20 AM Carl-Daniel Hailfinger > <c-d.hailfinger.devel.2006(a)gmx.net> wrote: > > > > Hi! > > > > FOSDEM next year will be on 2 & 3 February 2019. > > The deadline for applying for a stand is today. > > Do we want a coreboot/flashrom/LinuxBoot stand/booth? > Same as what Ron said. I think someone from FB can be there to talk about coreboot/LinuxBoot stuff and perhaps bring some hardware to demo.

1 0

Please help adding support for flashing Nvidia GF116 cards - for rescuing the world electrical waste
by hsjfd dfjdfg 02 Nov '18

02 Nov '18

3 2

FOSDEM 2019 deadline today
by Carl-Daniel Hailfinger 02 Nov '18

02 Nov '18

Hi! FOSDEM next year will be on 2 & 3 February 2019. The deadline for applying for a stand is today. Do we want a coreboot/flashrom/LinuxBoot stand/booth? There will be a hardware enablement devroom as well, and we might be able to participate there, but that's not necessarily giving us a chance to talk to people all day. Regards, Carl-Daniel

2 1

Re: [flashrom] New chip erase function
by Nico Huber 28 Oct '18

28 Oct '18

Hello Max, On 10/28/18 6:59 PM, M.Altschaeffel(a)gmx.de wrote: > Hi, > i have a problem with flashing a new blank bios chip. It´s a MX25L3206E chip. the failed byte counts in the log look rather random, which usually means the hardware setup is failing. Did you try to read+verify with this setup? only if reading is 100% reliable, writing will work. Do you have the plain chip connected or is it already soldered to the board? If the former, make sure to connect all input pins, i.e. /HOLD and /WP too. If the latter, power supply can be a problem; using the regular laptop PSU works best (might have to get it into a wake-on-lan state). Also, the T530 lacks pull-ups on the /CS lines of both flash chips. If that is the case for the T430 too, idk, but if, you should make sure that the /CS of the chip you _don't_ want to access is pulled high. Hope that helps, Nico

1 0

Re: [flashrom] Failed p4vxasd2+
by Nico Huber 28 Oct '18

28 Oct '18

Hello Ilya, On 10/28/18 5:47 PM, Илья Пинясов wrote: > Failed p4vxasd2 + > I'm using lubuntu 18.04 do you need any help or did you just want to report this? If you need help, please provide the command you used and the error message you got (a verbose log would be appreciated). Nico

1 0

New chip erase function
by M.Altschaeffel＠gmx.de 28 Oct '18

28 Oct '18

Hi, i have a problem with flashing a new blank bios chip. It´s a MX25L3206E chip. Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Macronix flash chip "MX25L3206E/MX25L3208E" (4096 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0xffb ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xc2e5 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000136! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xb25d ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000157! Expected=0xff, Found=0xfe, failed byte count from 0x00000000-0x003fffff: 0x2ef018 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000073! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x003fffff: 0x2ed6f7 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Looking for another erase function. 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. Apparently at least some data has changed. Your flash chip is in an unknown state. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! I started flashrom with : " sudo flashrom -n --programmer linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip "MX25L3206E/MX25L3208E" -f --write /tmp/t430.rom " I can´t skip the erase function, my thought -n and -f would help but no difference. For any help i would be thankful. Regards, max

1 0

Failed p4vxasd2+
by Илья Пинясов 28 Oct '18

28 Oct '18

Failed p4vxasd2 + I'm using lubuntu 18.04

1 0

Fwd: Intel QS77 chipet on MBA 2012
by Nico Huber 26 Oct '18

26 Oct '18

Sorry, it seems this one got lost in moderation, forwarding... -------- Forwarded Message -------- Subject: Intel QS77 chipet on MBA 2012 Date: Wed, 24 Oct 2018 23:18:40 +0200 From: Laura Martín <hoshi.utsuku(a)gmail.com> To: flashrom(a)flashrom.org Hi all, I'm trying to fix a corrupted EFI on a Macbook Air 13'' of 2012. I messed up with efibootmgr and that's the result... It's not a locked EFI, in the laptop Gentoo is installed, so I can access to the OS, although I can't boot from USB. So, I modified an EFI-dump for my laptop (I checked out it's not locked as well), I made a dump of the current EFI and replaced the serial number and other parameters. The size is OK, I checked out with hexdump. The stanza to made the write is: *# flashrom -p internal:pci=8086:1e56.0 -c "MX25L6406E/MX25L6408E" -V -w /home/m00n/nueva.rom* The output: Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer No coreboot table found. Using Internal DMI decoder. No DMI table found. *Found chipset "Intel QS77" with PCI ID 8086:1e56.* 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... Root Complex Register Block address = 0xfed1c000 GCS = 0xc21: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) ... BIOS_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled .... BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. 0x58: 0x07ff0190 FREG1: BIOS region (0x00190000-0x007fffff) is read-write. 0x5C: 0x018f0001 FREG2: Management Engine region (0x00001000-0x0018ffff) is read-write. 0x74: 0x866f0190 PR0: Warning: 0x00190000-0x0066ffff is read-only. 0x78: 0x9fff0692 PR1: Warning: 0x00692000-0x01ffffff is read-only. Writes have been disabled for safety reasons. You can enforce write support with the ich_spi_force programmer option, but you will most likely harm your hardware! If you force flashrom you will get no support if something breaks. On a few mainboards it is possible to enable write access by setting a jumper (see its documentation or the board itself). 0x90: 0xc4 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf94140 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=1, SME=0, SCF=1 0x94: 0x0606 (PREOP) 0x96: 0x3c6c (OPTYPE) 0x98: 0x0103029f (OPMENU) 0x9c: 0xffd82005 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00800000 (LVSCC) LVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=1 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20 0xD0: 0x00000000 (FPB) OK. Unhandled programmer parameters: pci=8086:1e56.0 Aborting. Error: Programmer initialization failed. Restoring MMIO space at 0x7f50ae5978a0 Restoring PCI config space for 00:1f:0 reg 0xdc So, what I'm doing wrong? It's an old laptop and with external devices I've read that it's possible to flash, From the same device it should be possible to do it .... I suppose that I'm missing some parameter.... But I can't find which. Any help would be appreciated... KR

3 2

Intel QS77 chipet on MBA 2012
by Laura Martín 24 Oct '18

24 Oct '18

Hi all, I'm trying to fix a corrupted EFI on a Macbook Air 13'' of 2012. I messed up with efibootmgr and that's the result... It's not a locked EFI, in the laptop Gentoo is installed, so I can access to the OS, although I can't boot from USB. So, I modified an EFI-dump for my laptop (I checked out it's not locked as well), I made a dump of the current EFI and replaced the serial number and other parameters. The size is OK, I checked out with hexdump. The stanza to made the write is: *# flashrom -p internal:pci=8086:1e56.0 -c "MX25L6406E/MX25L6408E" -V -w /home/m00n/nueva.rom* The output: Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer No coreboot table found. Using Internal DMI decoder. No DMI table found. *Found chipset "Intel QS77" with PCI ID 8086:1e56.* 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... Root Complex Register Block address = 0xfed1c000 GCS = 0xc21: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) ... BIOS_CNTL = 0x01: BIOS Lock Enable: disabled, BIOS Write Enable: enabled .... BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-write. 0x58: 0x07ff0190 FREG1: BIOS region (0x00190000-0x007fffff) is read-write. 0x5C: 0x018f0001 FREG2: Management Engine region (0x00001000-0x0018ffff) is read-write. 0x74: 0x866f0190 PR0: Warning: 0x00190000-0x0066ffff is read-only. 0x78: 0x9fff0692 PR1: Warning: 0x00692000-0x01ffffff is read-only. Writes have been disabled for safety reasons. You can enforce write support with the ich_spi_force programmer option, but you will most likely harm your hardware! If you force flashrom you will get no support if something breaks. On a few mainboards it is possible to enable write access by setting a jumper (see its documentation or the board itself). 0x90: 0xc4 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf94140 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=4, DBC=1, SME=0, SCF=1 0x94: 0x0606 (PREOP) 0x96: 0x3c6c (OPTYPE) 0x98: 0x0103029f (OPMENU) 0x9c: 0xffd82005 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x00800000 (LVSCC) LVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=1 0xC8: 0x00002005 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20 0xD0: 0x00000000 (FPB) OK. Unhandled programmer parameters: pci=8086:1e56.0 Aborting. Error: Programmer initialization failed. Restoring MMIO space at 0x7f50ae5978a0 Restoring PCI config space for 00:1f:0 reg 0xdc So, what I'm doing wrong? It's an old laptop and with external devices I've read that it's possible to flash, From the same device it should be possible to do it .... I suppose that I'm missing some parameter.... But I can't find which. Any help would be appreciated... KR

1 0

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

flashrom error code message
by MIAN VEREST 16 Oct '18

16 Oct '18

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

Unrecognized flash
by Ron Knapp 15 Oct '18

15 Oct '18

Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi. Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xf0, id2 0x7 Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE The chip is mx25L6406EZNI-12gf which I assume would use Macronix MX25L6406E/ PREW 8192 SPI The command that gets the generic message is sudo flashrom -r oldefi1.bin -V -p linux_spi:dev=/dev/spidev0.0 I put exactly what is listed as type and says unknown… pi@pi0w:~ $ sudo flashrom -L | grep MX25L6406E/ Macronix MX25L6406E/ PREW 8192 SPI pi@pi0w:~ $ sudo flashrom -r oldefi1.bin -c "MX25L6406E/" -V -p linux_spi:dev=/dev/spidev0.0 flashrom p1.0-128-g4acc3f3 on Linux 4.14.71+ (armv6l) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.5.2, GCC 6.3.0 20170516, little endian Command line (7 args): flashrom -r oldefi1.bin -c MX25L6406E/ -V -p linux_spi:dev=/dev/spidev0.0 Error: Unknown chip 'MX25L6406E/' specified. Run flashrom -L to view the hardware supported in this flashrom version.

2 1

Chip Support
by Matt Jahnke 08 Oct '18

08 Oct '18

Chip is a xm25qh128a flashrom -p ch341a_spi -VV flashrom v1.0 on Darwin 17.7.0 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with LLVM Clang 9.1.0 (clang-902.0.39.1), little endian Command line (3 args): flashrom -p ch341a_spi -VV Calibrating delay loop... OS timer resolution is 1 usecs, 1582M loops per second, 10 myus = 11 us, 100 myus = 150 us, 1000 myus = 1141 us, 10000 myus = 10718 us, 4 myus = 4 us, OK. Initializing ch341a_spi programmer libusb: info [darwin_claim_interface] no interface found; setting configuration: 1 Device revision is 3.0.4 The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for ESI ES25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for ESI ES25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for ESI ES25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25LQ40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25LQ80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25LQ64(B), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25LQ128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25Q128C, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25VQ21B, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25VQ40C, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25VQ41B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25VQ80C, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for GigaDevice GD25VQ16C, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LQ020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LQ040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LQ080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LQ016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LQ032C, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x20, id2 0x17 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x17, id2 0x17 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0x20, id2 0x17 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0x20, id2 0x17 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x20, id2 0x17 Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x20, id2 0x17 Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x20, id2 0x17 Probing for SST SST25WF020A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25WF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25WF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25Q128.W, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.0 SFDP number of parameter headers is 2 (NPH = 1). SFDP parameter table header 0/1: ID 0x00, version 1.0 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 16384 kB. Block eraser 0: 4096 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 4096 x 4096 B with opcode 0x20. Block eraser 1: 512 x 32768 B with opcode 0x52 Block eraser 2: 256 x 65536 B with opcode 0xd8 done. SFDP parameter table header 1/1: ID 0x20, version 1.0 Length 16 B, Parameter Table Pointer 0x000060 === 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" (16384 kB, SPI) on ch341a_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7018 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x20, id2 0x17 Found Unknown flash chip "SFDP-capable chip" (16384 kB, SPI). No operations were specified.

1 0

FLASHROM fails on my AM1 Kabinis with
by Branko Badrljica 07 Oct '18

07 Oct '18

I'm in dire need te reflash a couple of BIOS chips. Unfotunately, all my boards which I used to use for this purpose are rebellign against me. I have a couple of Kabinis ( Athlon 5370) on cheap AM1 boards and have noticed that "flashrom -p internal" fails on each one with "Found chipset AMD FCH" "Enabling flash write... ERROR: State of SpiAccesMacRomEn or SpiHostAccessRomEn prohibits full access" At first, I thot that I might have miscompiled something in the kernel or that flashrom doesn't jive with my Hardened Gentoo or something like that. So I used Kali Linux and burned it toUSB stick ( it has flasrom packaged). With the exactly the same end result. I've tried git version and versions 0.98 and 0.99. Older one ( 0.96 ?) compained that it doesn't know Kabini's chipset... THis HW used to work with flashrom. What changed ?

4 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom