- flashrom - mail.coreboot.org

Updated invitation: Flashrom Dev Meeting (monthly) @ Every 2 weeks from 4pm to 5pm on Thursday from Thu Jul 28 to Wed Nov 2 (AEST) (flashrom@flashrom.org)
by aklm＠chromium.org 23 Sep '22

23 Sep '22

This event has been updated Changed: time Flashrom Dev Meeting (monthly) Every 2 weeks from 4pm to 5pm on Thursday from Thursday Jul 28 to Wednesday Nov 2 Eastern Australia Time - Sydney Join with Google Meet https://meet.google.com/iuf-mtri-zva?hs=224 Join by phone (AU) +61 2 9051 6791 PIN: 304642402 More phone numbers https://tel.meet/iuf-mtri-zva?pin=9271993818880&hs=0 Monthly meeting of Flashrom project developers. Meeting notes doc: https://docs.google.com/document/d/18qKvEbfPszjsJJGJhwi8kRVDUG3GZ… Guests aklm(a)chromium.org - creator felix.singer12(a)gmail.com david.hendricks(a)gmail.com quasisec(a)google.com nico.h(a)gmx.de Martin Roth src(a)posteo.de martonmiklosqdev(a)gmail.com piotr.krol(a)3mdeb.com Maciej Pijanowski michal.zygowski(a)3mdeb.com th3fanbus(a)gmail.com stefan.k.reinauer(a)gmail.com nartemiev(a)google.com arthur(a)aheymans.xyz evanbenn(a)google.com flashrom(a)flashrom.org c-d.hailfinger.devel.2006(a)gmx.net View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=MmVscGY2cjNsdTZw… Reply for flashrom(a)flashrom.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=MmVscGY2cjNsdTZw… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

Canceled event with note: Flashrom Dev Meeting (monthly) @ Thu Oct 20, 2022 4pm - 5pm (AEDT) (flashrom@flashrom.org)
by aklm＠chromium.org 23 Sep '22

23 Sep '22

This event has been canceled with a note: "Cancelling the meeting for October due to daylight saving changes happening at different dates during the whole month of October." Flashrom Dev Meeting (monthly) Thursday Oct 20, 2022 ⋅ 4pm – 5pm Eastern Australia Time - Sydney Join with Google Meet https://meet.google.com/iuf-mtri-zva?hs=224 Join by phone (AU) +61 2 9051 6791 PIN: 304642402 More phone numbers https://tel.meet/iuf-mtri-zva?pin=9271993818880&hs=0 Monthly meeting of Flashrom project developers. Meeting notes doc: https://docs.google.com/document/d/18qKvEbfPszjsJJGJhwi8kRVDUG3GZ… Guests aklm(a)chromium.org - creator felix.singer12(a)gmail.com david.hendricks(a)gmail.com quasisec(a)google.com nico.h(a)gmx.de Martin Roth src(a)posteo.de martonmiklosqdev(a)gmail.com piotr.krol(a)3mdeb.com Maciej Pijanowski michal.zygowski(a)3mdeb.com th3fanbus(a)gmail.com stefan.k.reinauer(a)gmail.com nartemiev(a)google.com arthur(a)aheymans.xyz evanbenn(a)google.com flashrom(a)flashrom.org c-d.hailfinger.devel.2006(a)gmx.net ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

Canceled event with note: Flashrom Dev Meeting (monthly) @ Thu Oct 6, 2022 4pm - 5pm (AEDT) (flashrom@flashrom.org)
by aklm＠chromium.org 23 Sep '22

23 Sep '22

This event has been canceled with a note: "Cancelling the meeting for October due to daylight saving changes happening at different dates during the whole month of October." Flashrom Dev Meeting (monthly) Thursday Oct 6, 2022 ⋅ 4pm – 5pm Eastern Australia Time - Sydney Join with Google Meet https://meet.google.com/iuf-mtri-zva?hs=224 Join by phone (AU) +61 2 9051 6791 PIN: 304642402 More phone numbers https://tel.meet/iuf-mtri-zva?pin=9271993818880&hs=0 Monthly meeting of Flashrom project developers. Meeting notes doc: https://docs.google.com/document/d/18qKvEbfPszjsJJGJhwi8kRVDUG3GZ… Guests aklm(a)chromium.org - creator felix.singer12(a)gmail.com david.hendricks(a)gmail.com quasisec(a)google.com nico.h(a)gmx.de Martin Roth src(a)posteo.de martonmiklosqdev(a)gmail.com piotr.krol(a)3mdeb.com Maciej Pijanowski michal.zygowski(a)3mdeb.com th3fanbus(a)gmail.com stefan.k.reinauer(a)gmail.com nartemiev(a)google.com arthur(a)aheymans.xyz evanbenn(a)google.com flashrom(a)flashrom.org c-d.hailfinger.devel.2006(a)gmx.net ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

How to start contributing to Flashrom and work with 'Easy Projects' ?
by LN 22 Sep '22

22 Sep '22

2 1

NULLity to represent the default state of struct's
by Edward O'Callaghan 19 Sep '22

19 Sep '22

Hello, While refactoring flashrom.c to move towards a reentrant flashrom a pragmatic choice of utilising NULLity to represent the default state of a struct at instiation was used in the following and related commits - https://review.coreboot.org/c/flashrom/+/67391/ It was brought to my attention that this is perhaps considered a more substantive change to the general practice within flashrom and so I just wanted to give a brief prelude to the rationale and if anyone has any reason why they don't like it. Basically using NULL as the default state rather than an invalid state allows for memory address by value to be in a boolean state of either 'defined to be default' or 'defined to be custom' - over that of a tristate of 'defiled to be default explicitly', 'defined to be custom' or NULL which must be manually validated as 'invalid'. This is quite pragmatic as we can rid ourselves of explicit nullarity checks at runtime and instead have always defined reasonable defaults at compile-time thus making functions domains more well defined at compile-time. It is also pragmatic and arguably more modern from the stand-point of requiring less code to effectively obtain a valid value from the instantiated type not unlike Rust's Default trait or Ada's ability to have default values in a Record and so on. While not particularly novel I did want to follow up on the request to highlight it here. Kindly, Edward.

3 3

Updated invitation with note: Flashrom Dev Meeting (monthly) @ Fri Sep 23, 2022 4pm - 5pm (AEST) (flashrom@flashrom.org)
by aklm＠chromium.org 19 Sep '22

19 Sep '22

This event has been updated with a note: "Moving from 22 Sept to 23 Sept same time." Changed: time Flashrom Dev Meeting (monthly) Friday Sep 23, 2022 ⋅ 4pm – 5pm Eastern Australia Time - Sydney Join with Google Meet https://meet.google.com/iuf-mtri-zva?hs=224 Join by phone (AU) +61 2 9051 6791 PIN: 304642402 More phone numbers https://tel.meet/iuf-mtri-zva?pin=9271993818880&hs=0 Monthly meeting of Flashrom project developers. Meeting notes doc: https://docs.google.com/document/d/18qKvEbfPszjsJJGJhwi8kRVDUG3GZ… Guests aklm(a)chromium.org - creator felix.singer12(a)gmail.com david.hendricks(a)gmail.com quasisec(a)google.com nico.h(a)gmx.de Martin Roth src(a)posteo.de martonmiklosqdev(a)gmail.com piotr.krol(a)3mdeb.com Maciej Pijanowski michal.zygowski(a)3mdeb.com th3fanbus(a)gmail.com stefan.k.reinauer(a)gmail.com nartemiev(a)google.com arthur(a)aheymans.xyz evanbenn(a)google.com flashrom(a)flashrom.org c-d.hailfinger.devel.2006(a)gmx.net View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=MmVscGY2cjNsdTZw… Reply for flashrom(a)flashrom.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=MmVscGY2cjNsdTZw… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

Maybe move dev meeting from 22 Sept to 23 Sept?
by Anastasia Klimchuk 19 Sep '22

19 Sep '22

Hello, The next dev meeting is scheduled for 22 Sept, but it turns out there are some things happening: 1) This is a day right after OSFC which many people are attending. Joining a meeting early in the morning right after the last day of conference, from a hotel room, is not ideal. 2) All of a sudden, AU got a [one-off] public holiday on 22 Sept (National Day of Mourning) With all that, an idea is to move the meeting one day forward, 23 Sept, the same time. What do people think? -- Anastasia.

4 5

Failed Intel Q87 Flash Logs
by Kevin Fluttert 17 Sep '22

17 Sep '22

Here you are. Attached

1 0

error flashrom
by Alex 16 Sep '22

16 Sep '22

zeus@ThinkPadT440:/media/zeus/dados1/X230/bios-backup$ time sudo flashrom --chip "EN25QH64" --programmer ch341a_spi --write factory_bottom.bin flashrom v1.2 on Linux 5.15.0-47-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Eon flash chip "EN25QH64" (8192 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00000001! Expected=0x02, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x2e58e0 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! real 2m49,512s user 0m0,003s sys 0m0,014s zeus@ThinkPadT440:/media/zeus/dados1/X230/bios-backup$

1 0

Need to reflash my Intel NUC6i7KYK BIOS
by Arthur E. Baldwin 14 Sep '22

14 Sep '22

When I used Intel's iFlash2.exe along with FreeDOS to update from their KY0060.BIO to KY0074.BIO, then ALL versions of Linux had an "extra blue" display! The original BIOS did not have this problem, Intel would not take ANY responsibility for this problem, and I think they may have done this on purpose! The iflash2.exe program won't allow you to "go back" to the KY0060.BIO version, but says, "Incompatible BIOS version flashing aborted". I looked on your website for supported hardware, but have not seen my motherboard listed. Do you think there's any hope? Sincerely, Arthur Baldwin MobilePCClinic.Net

1 0

Flashrom -VV output of Windbond 25Q32BVSIG
by Denis Ahrens 13 Sep '22

13 Sep '22

../flashrom/flashrom -VV -p buspirate_spi:dev=/dev/cu.usbserial-A800cGob flashrom v1.2-964-gc8b23a0 on Darwin 21.6.0 (arm64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. flashrom was built with LLVM Clang 13.1.6 (clang-1316.0.21.2.5), little endian Command line (3 args): ../flashrom/flashrom -VV -p buspirate_spi:dev=/dev/cu.usbserial-A800cGob Initializing buspirate_spi programmer Detected Bus Pirate hardware 3.0 ("v3.a") Detected Bus Pirate firmware 7.1 ("v7.1") Using SPI command set v2. SPI speed is 8MHz Bus Pirate v3 or newer detected. Set serial speed to 2M baud. Serial speed is 2000000 baud Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for AMIC A25L010, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25L016, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25L020, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25L032, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25L040, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25L05PT, 64 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L05PU, 64 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L080, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25L10PT, 128 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L10PU, 128 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L16PT, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L16PU, 2048 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L20PT, 256 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L20PU, 256 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L40PT, 512 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L40PU, 512 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25L512, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25L80P, 1024 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25LQ16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for AMIC A25LQ64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF021, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF021A, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF041A, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF081, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF081A, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF161, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF321, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF321A, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DF641(A), 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DL081, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DL161, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25DQ161, 2048 kB: compare_id: id1 0xf7, id2 0xa002 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 AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512B, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25FS010, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25FS040, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25SF041, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25SF081, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25SF128A, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25SF161, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25SF321, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT25SL128A, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT26DF041, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT26DF081A, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT26DF161, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT26DF161A, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT26F004, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45CS1282, 16896 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB011D, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB021D, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB041D, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB081D, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB161D, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB321C, 4224 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB321D, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB321E, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Atmel AT45DB642D, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Boya/BoHong Microelectronics B.25D16A, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Boya/BoHong Microelectronics B.25Q128AS, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ESI ES25P16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ESI ES25P40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ESI ES25P80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ESMT F25L008A, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ESMT F25L32PA, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B05, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B05T, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B10T, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B16T, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B20T, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B32T, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B40T, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B64T, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25B80T, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25F05, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25F10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25F16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25F20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25F32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25F40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25F64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25F80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25P05, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25P10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25P16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25P20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25P32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25P40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25P64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25P80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25Q128, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25Q16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25Q32(A/B), 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25Q40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25Q64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25Q80(A), 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25QH128, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25QH16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25QH32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25QH64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25S10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25S16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25S20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25S32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25S40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25S64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon EN25S80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Fudan FM25F005, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Fudan FM25F01, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Fudan FM25F02(A), 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Fudan FM25F04(A), 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Fudan FM25Q08, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Fudan FM25Q16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Fudan FM25Q32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25B128B/GD25Q128B, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25LQ128C/GD25LQ128D/GD25LQ128E, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25LQ16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25LQ32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25LQ40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25LQ64(B), 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25LQ80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q127C/GD25Q128C, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q16(B), 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q20(B), 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q256D/GD25Q256E, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q32(B), 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q40(B), 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q512, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q64(B), 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25Q80(B), 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25T80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25VQ16C, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25VQ21B, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25VQ40C, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25VQ41B, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25VQ80C, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for GigaDevice GD25WQ80E, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ISSI IS25LP064, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ISSI IS25LP128, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ISSI IS25LP256, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ISSI IS25WP032, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ISSI IS25WP064, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ISSI IS25WP128, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ISSI IS25WP256, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Intel 25F160S33B8, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Intel 25F160S33T8, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Intel 25F320S33B8, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Intel 25F320S33T8, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Intel 25F640S33B8, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Intel 25F640S33T8, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX23L12854, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX23L1654, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX23L3254, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX23L6454, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L12805D, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L1605, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L1635D, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L1635E, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L25635F/MX25L25645G, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L3205(A), 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L3235D, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L3233F/MX25L3273E, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L5121E, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L6405, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L6405D, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L6495F, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25R3235F, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25R6435F, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25U12835F, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25U1635E, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25U25635F, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25U3235E/F, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25U51245G, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25U6435E/F, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX25U8032E, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX66L51235F/MX25L51245G, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix MX66L1G45G, 131072 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P05-A, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P128, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: probe_spi_res1: id 0x15 Probing for Micron/Numonyx/ST M25P64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25P80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PE10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PE20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PE40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M45PE10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M45PE20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M45PE40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q00A..1G, 131072 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q00A..3G, 131072 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q256..1E, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q256..3E, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q512..1G, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron/Numonyx/ST N25Q512..3G, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QL01G, 131072 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QU01G, 131072 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QL02G, 262144 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QU02G, 262144 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QU128, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QL128, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QL256, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QU256, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QL512, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Micron MT25QU512, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Nantronics N25S10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Nantronics N25S16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Nantronics N25S20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Nantronics N25S40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Nantronics N25S80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LD010(C), 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LD020(C), 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LD040(C), 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LD256C, 32 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LD512(C), 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LQ016, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LQ020, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LQ032C, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LQ040, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LQ080, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for PMC Pm25LV010A, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LV016B, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LV020, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LV040, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LV080B, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for SST SST25LF020A, 256 kB: compare_id: id1 0xef, id2 0x15 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for SST SST25VF010(A), 128 kB: compare_id: id1 0xef, id2 0x15 Probing for SST SST25VF016B, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25VF020, 256 kB: compare_id: id1 0xef, id2 0x15 Probing for SST SST25VF020B, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25VF032B, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25VF040, 512 kB: compare_id: id1 0xef, id2 0x15 Probing for SST SST25VF040B, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25VF040B.REMS, 512 kB: compare_id: id1 0xef, id2 0x15 Probing for SST SST25VF064C, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25VF080B, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25VF512(A), 64 kB: compare_id: id1 0xef, id2 0x15 Probing for SST SST25WF010, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25WF020, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25WF020A, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25WF040, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25WF040B, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25WF080, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25WF080B, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST25WF512, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST26VF016B(A), 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST26VF032B(A), 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST SST26VF064B(A), 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ST M95M02, 256 kB: probe_spi_st95: id1 0xff, id2 0xffff Probing for Sanyo LE25FU106B, 128 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for Sanyo LE25FU206, 256 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for Sanyo LE25FU206A, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for Sanyo LE25FW203A, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Sanyo LE25FW403A, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x15, id2 0x15 Probing for Spansion S25FL004A, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL008A, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL016A, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL032A/P, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL064A/P, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL127S-256kB, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL127S-64kB, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL128L, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL128P......0, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL128P......1, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL128S......0, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL128S......1, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL128S_UL Uniform 128 kB Sectors, 16384 kB: Read id bytes: 0x00 0x00 0x00 0x00 0x00 0x00. Probing for Spansion S25FL128S_US Uniform 64 kB Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x16 0x00 0x00 0x00. Probing for Spansion S25FL129P......0, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL129P......1, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL132K, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL164K, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL204K, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL208K, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL256L, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL256S Large Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x16 0x00 0x00 0x00. Probing for Spansion S25FL256S Small Sectors, 16384 kB: Read id bytes: 0xef 0x40 0x16 0x00 0x00 0x00. Probing for Spansion S25FL256S......0, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FL512S, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Spansion S25FS128S Large Sectors, 16384 kB: Read id bytes: 0xff 0xff 0xff 0xff 0xff 0xff. Probing for Spansion S25FS128S Small Sectors, 16384 kB: Read id bytes: 0x00 0x00 0x00 0x00 0x00 0x00. Probing for Winbond W25P16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25P32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25P80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q128.V, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q128.V..M, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q128.W, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q128.JW.DTR, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q16.V, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q16.W, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q20.W, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q256FV, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q256JV_Q, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q256JV_M, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q256JW, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q256JW_DTR, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q32.V, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q32.W, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q32JW...M, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q40.V, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q40BW, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q40EW, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q512JV, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q512NW-IM, 65536 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q64BV/W25Q64CV/W25Q64FV, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q64JV-.Q, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q64JV-.M, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q64.W, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q64JW...M, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q80.V, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q80BW, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25Q80EW, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25X05, 64 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25X10, 128 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25X16, 2048 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25X20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25X32, 4096 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25X40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25X64, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond W25X80, 1024 kB: compare_id: id1 0xf7, id2 0xa002 Probing for XMC XM25QH64C, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for XMC XM25QU64C, 8192 kB: compare_id: id1 0xf7, id2 0xa002 Probing for XMC XM25QH128C, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for XMC XM25QU128C, 16384 kB: compare_id: id1 0xf7, id2 0xa002 Probing for XMC XM25QH256C, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for XMC XM25QU256C, 32768 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Zetta Device ZD25D20, 256 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Zetta Device ZD25D40, 512 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.0 SFDP number of parameter headers is 256 (NPH = 255). SFDP parameter table header 0/255: ID 0x00, version 1.0 Length 36 B, Parameter Table Pointer 0x000080 Parsing JEDEC flash parameter table... 3-Byte only addressing. Status register is volatile and writes to the status register have to be enabled with WREN (0x06). Write chunk size is at least 64 B. Flash chip size is 4096 kB. Block eraser 0: 1024 x 4096 B with opcode 0x20 Block size of erase Sector Type 1 (2^255) is too big for flashrom. done. SFDP parameter table header 1/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xffffff SFDP parameter table header 2/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 3/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 4/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 5/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0xffffff SFDP Parameter Table 5 supposedly overflows addressable SFDP area. This most probably indicates a corrupt SFDP parameter table header. Skipping it. SFDP parameter table header 6/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xffffff SFDP parameter table header 7/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 8/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 9/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 10/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0xffffff SFDP Parameter Table 10 supposedly overflows addressable SFDP area. This most probably indicates a corrupt SFDP parameter table header. Skipping it. SFDP parameter table header 11/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xffffff SFDP parameter table header 12/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 13/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 14/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 15/255: ID 0x00, version 241.0 Length 1020 B, Parameter Table Pointer 0xffffff SFDP Parameter Table 15 supposedly overflows addressable SFDP area. This most probably indicates a corrupt SFDP parameter table header. Skipping it. SFDP parameter table header 16/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x423b08 SFDP parameter table header 17/255: ID 0xee, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 18/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 19/255: ID 0x10, version 0.216 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 20/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0xffffff SFDP Parameter Table 20 supposedly overflows addressable SFDP area. This most probably indicates a corrupt SFDP parameter table header. Skipping it. SFDP parameter table header 21/255: ID 0x00, version 127.0 Length 1020 B, Parameter Table Pointer 0xffffff SFDP Parameter Table 21 supposedly overflows addressable SFDP area. This most probably indicates a corrupt SFDP parameter table header. Skipping it. SFDP parameter table header 22/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 23/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 24/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 25/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0xffffff SFDP Parameter Table 25 supposedly overflows addressable SFDP area. This most probably indicates a corrupt SFDP parameter table header. Skipping it. SFDP parameter table header 26/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0xffffff SFDP Parameter Table 26 supposedly overflows addressable SFDP area. This most probably indicates a corrupt SFDP parameter table header. Skipping it. SFDP parameter table header 27/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 28/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 29/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 30/255: ID 0xff, version 255.255 Length 1020 B, Parameter Table Pointer 0xffffff SFDP Parameter Table 30 supposedly overflows addressable SFDP area. This most probably indicates a corrupt SFDP parameter table header. Skipping it. SFDP parameter table header 31/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 32/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 33/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 34/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 35/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 36/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 37/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 38/255: ID 0x00, version 128.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 39/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000080 SFDP parameter table header 40/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x800000 SFDP parameter table header 41/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 42/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 43/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 44/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 45/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 46/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 47/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 48/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 49/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 50/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 51/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 52/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 53/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 54/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 55/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 56/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 57/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 58/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 59/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 60/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 61/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 62/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 63/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 64/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 65/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 66/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 67/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 68/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 69/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 70/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 71/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 72/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 73/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 74/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 75/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 76/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 77/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 78/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 79/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 80/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 81/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 82/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 83/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 84/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 85/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 86/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 87/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 88/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 89/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 90/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 91/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 92/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 93/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 94/255: ID 0x00, version 128.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 95/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 96/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 97/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 98/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 99/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 100/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 101/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 102/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 103/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 104/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 105/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 106/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 107/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 108/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 109/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 110/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 111/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 112/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 113/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 114/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 115/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 116/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 117/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 118/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 119/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 120/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 121/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 122/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 123/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 124/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 125/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 126/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 127/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 128/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 129/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 130/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 131/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 132/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 133/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 134/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 135/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 136/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 137/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 138/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 139/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 140/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 141/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 142/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 143/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 144/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 145/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 146/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 147/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 148/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 149/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 150/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 151/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 152/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 153/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 154/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 155/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 156/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 157/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 158/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 159/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 160/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 161/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000080 SFDP parameter table header 162/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 163/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 164/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 165/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 166/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 167/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 168/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 169/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 170/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 171/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 172/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 173/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 174/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 175/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 176/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 177/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 178/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 179/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 180/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 181/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 182/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 183/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 184/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 185/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 186/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 187/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 188/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 189/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 190/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 191/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 192/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 193/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 194/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 195/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 196/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 197/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000080 SFDP parameter table header 198/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x800000 SFDP parameter table header 199/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 200/255: ID 0x80, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 201/255: ID 0x00, version 128.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 202/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000080 SFDP parameter table header 203/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 204/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 205/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 206/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 207/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 208/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 209/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 210/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 211/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 212/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 213/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 214/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 215/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 216/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 217/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 218/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 219/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 220/255: ID 0xff, version 0.255 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 221/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 222/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 223/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 224/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 225/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 226/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 227/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 228/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 229/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 230/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 231/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 232/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 233/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 234/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 235/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 236/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 237/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 238/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 239/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 240/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 241/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 242/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 243/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 244/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 245/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 246/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 247/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 248/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 249/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 250/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 251/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 SFDP parameter table header 252/255: ID 0x00, version 255.0 Length 1020 B, Parameter Table Pointer 0x000000 SFDP parameter table header 253/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x00ffff SFDP parameter table header 254/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0xff0000 SFDP parameter table header 255/255: ID 0x00, version 0.0 Length 0 B, Parameter Table Pointer 0x000000 === 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! === Added layout entry 00000000 - 003fffff named complete flash Found Unknown flash chip "SFDP-capable chip" (4096 kB, SPI) on buspirate_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: RDID byte 0 parity violation. compare_id: id1 0x00, id2 0x00 Probing for Atmel unknown Atmel SPI chip, 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Eon unknown Eon SPI chip, 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Macronix unknown Macronix SPI chip, 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for PMC unknown PMC SPI chip, 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for SST unknown SST SPI chip, 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for ST unknown ST SPI chip, 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Generic unknown SPI chip (RDID), 0 kB: compare_id: id1 0xf7, id2 0xa002 Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: id1 0xef, id2 0x15 Found Unknown flash chip "SFDP-capable chip" (4096 kB, SPI). No operations were specified. Raw bitbang mode version 1 Bus Pirate shutdown completed.

1 0

Build System Changes / Call for testing
by Thomas Heijligen 12 Sep '22

12 Sep '22

Hi flashrom community, we've just merged a big overhaul to the meson build system, especially the programmer selection. Now it is easy to select a singe or a group of programmers, which was really painful before. Besides that, the meson file now works on non Linux systems, too. To use meson you need to install meson (>=0.53.0) and ninja beside the other flashrom dependencies from your package distributor. Create a buildconfiguration in <builddir> with `meson <builddir>` Compile the configuration with `ninja -C <builddir>` Newer versions of meson may offer a nicer set of commands. Have a look at https://mesonbuild.com/Quick-guide.html To create to build a configuration with custom flags, use `meson -Doption=value <builddir>` A single programmer can for example be selected by `-Dprogrammer=ch341a_spi` or multiple by `-Dprogrammer=ch341a_spi,dediprog`. All pci based programmers can be selected by `-Dprogrammer=group_pci`. The default for the programmer is `auto`, which selects all proper working programmers. The option `all` selects also those programmers. For all options, please have a look at meson_options.txt in the flashrom repository. For aditional documentation look at Documentation/building.md in the flashrom repository. Beside all efforts to get things working, there are still some limits: - On MacOS only external programmers are supported. The old solution for internal programmer with DirectHW is in an unknown state. - Crosscompiling to libpayload is not working. - Crosscompiling to dos with djgpp is likely to fail - Windows should be working with MinGW (MSYS2) but is not tested well - The unit tests might be failing to compile or run on non Linux platforms, use `meson -Dtests=disabled <builddir>` to exclude them from getting build. - Platforms with libusb < 1.0.16 or older FreeBSD / DragonFly BSDs might fail to compile. https://review.coreboot.org/c/flashrom/+67073 will drop this down to >=1.0.9. I hope you will all enjoy these improvements and have fun testing it. If you find bugs or have problems, please respond to this mail. -- Thomas

1 0

Lenovo ideapad 330S AMD FP4
by Balázs Vinarz 10 Sep '22

10 Sep '22

Hello there! I'm sending you the outputs of lspci and flashrom's output, when using internal flash. I hope you can do some improvement. flashrom v1.2 on Linux 5.15.53-1-lts (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x61 does not match known values. Please report this to flashrom(a)flashrom.org and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway ======================================================================== You seem to be running flashrom on an unknown laptop. Some internal buses have been disabled for safety reasons. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.

1 0

FAILED: mAL10 Computer-on-Modules on Kontron Type 10 evaluation carrier board 2
by Graichen Michael 09 Sep '22

09 Sep '22

for your information =========== dev@mate:/tmp$ sudo flashrom -p internal --ifd -i bios -w coreboot.rom --noverify-all [sudo] Passwort für dev: flashrom v1.2 on Linux 5.15.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). No DMI table found. Found chipset "Intel Apollo Lake". Enabling flash write... Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed. New value is 0xaa. SPI Configuration is locked down. Enabling hardware sequencing because some important opcode is locked. PROBLEMS, continuing anyway ======================================================================== You may be running flashrom on an unknown laptop. We could not detect this for sure because your vendor has not set up the SMBIOS tables correctly. Some internal buses have been disabled for safety reasons. You can enforce using all buses by adding -p internal:laptop=this_is_not_a_laptop to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Reading ich descriptor... done. Using region: "bios". Reading old flash chip contents... done. Erasing and writing flash chip... Transaction error between offset 0x00001000 and 0x00001fff (= 0x00001000 + 4095)! Reading current flash chip contents... done. Looking for another erase function. Looking for another erase function. Looking for another erase function. Looking for another erase function. 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. Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Michael Graichen Research & Development ________________________________ T +49 631 34146-0<tel:+49%20631%2034146-0> michael.graichen(a)wipotec.com<mailto:michael.graichen@wipotec.com> <https://www.wipotec.com> wipotec.com<https://www.wipotec.com> | wipotec-wt.com<https://www.wipotec-wt.com> | wipotec-ocs.com<https://www.wipotec-ocs.com> WIPOTEC GmbH Adam-Hoffmann-Str. 26 67657 Kaiserslautern Germany [https://www.wipotec-ocs.com/fileadmin/wipotec-ocs/signature/linkedin.png] <https://www.linkedin.com/company/wipotec> [https://www.wipotec-ocs.com/fileadmin/wipotec-ocs/signature/facebook.png] <https://www.facebook.com/wipotec> [https://www.wipotec-ocs.com/fileadmin/wipotec-ocs/signature/youtube.png] <https://www.youtube.com/c/WIPOTECOCS> ________________________________ [cid:wipotec_38ce1105-f549-48fe-a3be-9e29d2b24123.gif]<https://www.wipotec.com><mailto:event@wipotec.com> Legal information: WIPOTEC GmbH | HRB 2317 Kaiserslautern Management: T. Düppre, U. Wagner, Dr. W. Schmitz, F. Köhler, J. Kühn You can find detailed data privacy guidelines<https://www.wipotec.com/en/policy/> on our website.

1 0

Introduction to the community - Dhiren
by dhiren serai 09 Sep '22

09 Sep '22

Hello everyone, I'm Dhiren Serai and I'm interested in contributing to one of GSOC 2022 Ideas called Design and implement new CLI based on libflashrom and extend the API as necessary . I'm new to C world but definitely not new to programming so I think I can adapt to this and get some hands dirty in Linux world. I'm also familiar with Linux concepts as I have been using it since 4 years so that shouldn't be a problem. I liked the gsoc 2022 idea which was proposed but as I'm not a student anymore I cannot do it as part of GSOC, but I have done open source contribution since 2 years so shouldn't be a problem for me to get started. I would like to work on this in the normal course of my time as a hobby. :D I'm excited to work on this. :D

2 3

Flash chip not identified
by Aagi Girish 08 Sep '22

08 Sep '22

Hi Team, We are trying to install coreboot firmware on our hardware for a customer requirement and the flashrom utility did not identify the flash chip. Attached the information that you have requested. Our hardware information can be found at the link below. Please let us know which programmer / flash chip needs to be selected from the list below the link. https://www.hyperscalers.com/quanta-qct-server-1u/D43K-1U-AMD-server-EPYC-q… -p | --programmer <name>[:<param>] specify the programmer device. One of internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, ft2232_spi, serprog, buspirate_spi, dediprog, developerbox, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_mtd, linux_spi, usbblaster_spi, pickit2_spi, ch341a_spi, digilent_spi, stlinkv3_spi. Thanks, Aagi [HS Signiatures] <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hyperscalers.com_&d…> Aaromal Girish Appliance Engineer p +61 1300 113 112 Hyperscalers.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hyperscalers.com_&d…> aagi.girish(a)hyperscalers.com<mailto:aagi.girish@hyperscalers.com> [cid:image002.jpg@01D8C374.7EA5B000] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.hyperscalers.com_O…> [cid:image003.jpg@01D8C374.7EA5B000] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.hyperscalers.com_q…> [cid:image004.jpg@01D8C374.7EA5B000] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.hyperscalers.com_p…> [cid:image005.jpg@01D8C374.7EA5B000] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.hyperscalers.com_I…> Hyperscale x86 Tier 1 Original x86 Lab as a Service LaaS IP-Appliance Design

1 0

FCH device found but SMBus revision 0x61 does not match known values.
by Alex Ortiz 06 Sep '22

06 Sep '22

1 0

i have no video on my laptop screen, so i need to flash the bios blind
by Hamid Mazuji 31 Aug '22

31 Aug '22

i don't know if my screen is blank because of a hardware issue or setting, but i can not even access the bios. the screen is blank at the very start i came across flashrom and coreboot pages after a duckduck search, but i can't figure out what environment these programs are designed for, or how to use the programs. for example, i can't figure out if i can use these programs to flash a bios without any keyboard input (because there's no video) are there pages on what flashrom is and how to use it or what coreboot is, and how to use it i did look around, but these questions weren't part of the faqs

1 0

lash chip is in an unknown state
by Delevic 29 Aug '22

29 Aug '22

Hi, I just tried to flash bios in nvidia p106-100 with. But I get errors : sudo flashrom --programmer ch341a_spi -w p106v.rom flashrom v1.2 on Linux 5.15.0-46-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q40EW" (512 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0xe0, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0xe0, failed byte count from 0x00000000-0x00007fff: 0x8000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0xe0, failed byte count from 0x00000000-0x0000ffff: 0x10000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0xe0, failed byte count from 0x00000000-0x0007ffff: 0x80000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0xe0, failed byte count from 0x00000000-0x0007ffff: 0x80000 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! What to do next ? Best Regards Delevic

2 2

Erase/write error
by domimoel＠web.de 28 Aug '22

28 Aug '22

2 1

flashrom dev meeting notes 26.08.22
by Felix Singer 26 Aug '22

26 Aug '22

# 25th Aug 2022, 6:00 - 7:00 UTC+0 Attendees: Alex, Felix, Evan, Anastasia, Edward ## Decisions Summary * A link pointing to the meeting will be added on the Contacts page. * We want to discuss the minimum required versions of our (build- )dependencies. We don’t want ifdefs checking for library versions in the code. When a programmer doesn’t support a library version, the build system should not enable it. ## Agenda * [aklm] Are there any objections if I will add info about this meeting on the Contacts page? * Clarify this is NOT a support forum, not a troubleshooting forum * [Felix] Rework the flash chips database / minimize the compiled version of flashchips.c in size * In most cases, embedded applications only need a small selection of the available flash chips. If we are able to shrink it somehow, this could free useful space for other applications or use cases. * One approach: Currently, flash chips are grouped by vendors. So add compiler flags enabling or disabling these. * Another approach: Rework the way flash chips are organized. * flashchips.c is pretty inflexible and it’s complicated to get this in a format so that flash chips can be listed on the website. * Thus, store flash chips in an JSON file (may be any other format), which opens lots of possibilities. * The website could just use the JSON and list the data. For flashrom itself, we could write a little script (and add this to the build system) which converts the JSON data to C code. This way, we also could filter for specific flash chip characteristics (protocols, vendor, name, …), in case only a group or some specific chips are wanted. * Another advantage: We could add an API to (lib-)flashrom so that the user can use their own JSON file and so the user can add new (or change) flash chips without recompiling flashrom very easily. So flash chips can be compiled into flashrom but they also can be loaded using the JSON format. * Edward: there are patches for review [https://review.coreboot.org/q/topic:declarative_flashchips.c_complete](http… * [Felix/Thomas] We should define minimum required versions of libraries and (build-)dependencies * [https://review.coreboot.org/c/flashrom/+/65919](https://review.coreboot.org… * Created a sheet to collect the versions * [https://review.coreboot.org/c/flashrom/+/66436](https://review.coreboot.org… * If defs is not great * If someone is using such an old libusb version, then ch341a programmer should not be built in at all * We want to hold the patch for a moment * TODO : create ticket to move the discussion there, add a comment to the patch 66436 , link the ticket >> [https://ticket.coreboot.org/issues/409](https://ticket.coreboot.org/issues/… * Programmer param discussion * Board enable for i2c * [Joursoir] Flashrom CLI should have bash-completion (auto-complete text with TAB key while typing a command). Task for new contributors/next GSoC. * Useful for new users * Can be smaller project or larger project, can be broken into several phases * Felix: Not supported by standard bash, needs one extra packet. But most systems have it anyway. * Joursoir: Might need a bit of planning, think how to structure bash * We need to agree on what’s the end goals * Flashchips: too many of them, let’s not include it * Edward: Start as simple as possible, and then see how it goes. * Everyone: A very good idea * Joursoir (Alex) is a contact person for the project

1 0

Unify flashrom range types
by Evan Benn 25 Aug '22

25 Aug '22

# Introduction The goal is to unify the integer type used for ranges. libflashrom has 2 ranges in the API: write protect (wp) ranges and layout ranges. The types for these are not consistent between wp and layout, between getters and setters, and between the API and the implementation. Additionally the types are different sized depending on the platform (ie size_t on 32 vs 64 bit). Demo: https://review.coreboot.org/c/flashrom/+/67004 # Background / Motivation Assertion: Flashrom only cares about fairly normal platforms (32 and 64 bit pointers). size_t: size_t is the C type returned by sizeof. It is an unsigned integer. Throughout the C library it is used as the type for counting the length of and indexing into arrays. It is at least 16 bits. It is often the same size as uintptr_t and void* but this is not required. uintptr_t: A C type large enough to hold a pointer. unsigned int: At least 16 bits, probably 32 bits on all the platforms we care about. uint32_t: Exactly 32 bit type, not required to exist (ie, flashrom won't compile on platforms where this doesn’t exist). usize: A rust type corresponding to uintptr_t. uintptr: A go type corresponding to uintptr_t. Go also has C.size_t. # Flashrom Today getsize -> size_t read/write/verify -> size_t implementation: unsigned int https://source.chromium.org/chromiumos/chromiumos/codesearch/+/cc9524d9ebf5… Based on the implementation using `unsigned int`, Flashrom probably only works with up to 32 bit sized flashes. layout_add_region -> size_t, (start, end) layout_get_region -> unsigned int (start, len) impl: uint32_t (start, end) https://source.chromium.org/chromiumos/chromiumos/codesearch/+/cc9524d9ebf5… These types are probably fine on 32 bit platforms where they are all the same. On 64 bit you could add a region that will be truncated / wrapped without warning. The get and add using different ranges; (start, end) and (start, len) is very confusing - I have already gotten this wrong several times while refactoring. wp_set_range -> size_t (start, len) wp_get_range -> size_t (start, len) impl: size_t (start, len) All consistent here. wp_ranges_count -> size_t wp_ranges_get_range -> unsigned int impl: size_t Changing the get_range to take a size_t seems like a simple fix here. This is unlikely to ever cause a bug but is a strange style. # Rust Bindgen can be told to treat size_t as usize. Without this flag a rust type for size_t is chosen for the platform (ie u32 on 32 bit, u64 on 64 bit). Only usize can be used to index slices in rust. # Proposal ## Goal Unify all the length types (internal and external) Unify all the range bounds ((start, len) vs (start, end)) Make bindings straightforward ## Non goal 16 bit platforms >32 bit sized flashes Change the libflashrom API and the flashrom internals to use uint32_t for all flash sizes and ranges. Keep size_t for host related sizes, eg the buffer size in flashrom_layout_read_fmap_from_buffer or flashrom_image_verify. Add a layout_add (start, len) method and try to deprecate the (start, end) method. This will make all of the methods use the same concept of range. The wp implementation uses (start, len) while the layout implementation uses (start, end). I do not propose to change this. In the rust fat bindings, use usize to represent all ranges and offsets. After libflashrom changes from the current implementation to uint32_t, the rust bindings must convert between u32 and usize. We will only support 32 and 64 bit usize, so this will be straightforward. The rust bindings will reject attempts to provide values > 32bit at runtime. # Alternatives Use uint64_t. This has the pro of supporting large SPI flash on 64 bit platforms. However this wont make large flash supported on 32 bit platforms, as single buffers are passed around for data access; flashrom_image_write (struct flashrom_flashctx *flashctx, void *buffer, size_t buffer_len, const void *refbuffer) Use size_t everywhere. Size_t makes some sense to use, as the implementation and API deals with full flash sized buffers, and they can only be indexed by size_t sized ranges anyway. For example flashrom would support 16 bit of flash on a 16 bit platform, and 64 bit of flash on a 64 bit platform. However, tying the usable flash size to the platform size doesn't really make sense and is likely to cause confusion, and we probably only care about 32 bit flash. Use a typedef, eg chipsize_t. I think this is reasonable internally but don't prefer it. It would theoretically allow a simple change to swap from 32 to 64 bit flashes. However C won't warn about code using the wrong type while they are 'compatible', see for example the functions using unsigned int and uint32_t interchangeably in the codebase already. And this won't really work for libflashrom, it's too messy to make the API function differently depending on library compile time choices, this really creates incompatible APIs with identical names. For supporting larger-than-size_t size data objects, see posix lseek64 and friends. Use u32 for the rust API. This makes sense as it pushes out-of-range errors into the user code. However it complicates a lot of usage as u32 constantly need to be converted into usize to do array indexing. https://review.coreboot.org/c/flashrom/+/67004

1 0

Issue tracker version update / disabling of login methods
by Felix Singer 19 Aug '22

19 Aug '22

Hi all, the Redmine developers released version 5.0 some months ago and updating to this version will have some effects on us. So, I would like to open a thread to discuss these issues with you and how we deal with that situation. Currently, we are on the 4.2 branch and it still gets security and bug fixes, but I can't tell at which point they will stop supporting it. We enabled the login over OpenID, which is implemented natively and not integrated over a plugin. With version 5.0, support for that was removed. I assume this is due to that the implementation is based on an older OpenID standard and there are not many users of it anymore (TM). The newer standard seems to be called "OpenID Connect", but it's not supported by Redmine. Also, we are using a plugin which allows the login over a Google account. The compatibility of that plugin breaks with version 5.0. The problem is that we have users for both and with version 5.0 they won't be able to use these methods anymore. However, I have an idea for a solution. I took a look at the Redmine database and I played around with the Google login method. My tests showed that it creates a normal user account, as it is done with the registration, just with the little difference that no password is set disabling the login over password. These accounts also have an user name and an email address. As soon as I set a password, I was able to login using the user name. So, my idea is that we just go with these changes and affected users use the functionality to reset their password, which means they will have a "normal" user account then. In preparation to that version update, we should disable these login methods so that no new users will make use of them. Other ideas? What's your opinion? // Felix

3 4

Read from W25Q256JV_Q returns only zeroes
by Olof Gross 18 Aug '22

18 Aug '22

Hi, im trying to apply me_cleaner to a HP ProBook 450 G8. It has a W25Q256JVEQ WSON8 chip soldered so i bought a WSON connector thingy and try to read from it with a pi: olle@raspberrypi:~ $ sudo flashrom/flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=10000 -c W25Q256JV_Q -V -r hp-bios-original.bin flashrom v1.2-887-g6c1b0ac on Linux 5.15.56-v7+ (armv7l) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). flashrom was built with GCC 10.2.1 20210110, little endian Command line (7 args): flashrom/flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=10000 -c W25Q256JV_Q -V -r hp-bios-original.bin Initializing linux_spi programmer Using device /dev/spidev0.0 Using 10000kHz clock get_max_kernel_buf_size: Using value from /sys/module/spidev/parameters/bufsiz as max buffer size. linux_spi_init: max_kernel_buf_size: 4096 The following protocols are supported: SPI. Probing for Winbond W25Q256JV_Q, 32768 kB: compare_id: id1 0xef, id2 0x4019 Added layout entry 00000000 - 01ffffff named complete flash Found Winbond flash chip "W25Q256JV_Q" (32768 kB, SPI) on linux_spi. Chip status register is 0x00. This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). === This flash part has status UNTESTED for operations: PROBE READ 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 chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading flash... done. Looks great? It correctly identifies the chip and i get a file of the right size. Its just that it contains only zeroes. Thirty-two million of them. Not great. I used freshly compiled flashrom from git, hardware was a raspi 2b rev1.1 running raspbian bullseye freshly updated. What would you suggest as a next step? Try different speed settings, desolder the chip, what more? And yeah, the batteries (main, clock) were disconnected. Regards, Olof

1 0

"MT25QU256" Verifying flash... FAILED
by svv 18 Aug '22

18 Aug '22

sudo flashrom -p ft2232_spi:type=arm-usb-ocd-h,port=A,divisor=8 -c MT25QU256 -w image.img flashrom v1.2 on Linux 5.4.0-58-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Micron flash chip "MT25QU256" (32768 kB, SPI) on ft2232_spi. === This flash part has status UNTESTED for operations: PROBE READ 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 chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00001000! Expected=0x00, Found=0xff, failed byte count from 0x00000000-0x01ffffff: 0x250e23 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!

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom