by Stefan Tauner
On Mon, 9 May 2016 20:46:18 -0700
David Hendricks <dhendrix(a)google.com> wrote:
> Hi Victor,
> From Flashrom's software perspective all chips with the same ID are
> indistinguishable.
>
> Part number often includes characteristics such as package and thermal
> tolerance which do not affect software compatibility.
However, we will add the new names to the in-program (and hence
wiki) database so that this new information becomes public. Thanks for
the heads up, Victor.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
by Carl-Daniel Hailfinger
Hi,
we're hitting the 80 column limit in our code in ways which actually
reduce readability for the code. Examples are various multiline messages
and complicated nested code where refactoring to a separate function
doesn't make sense.
Keeping the old 80 column limit is not really an option anymore.
Standard terminal sizes have one of 80, 100 or 132 columns.
Given the monitor resolutions many people have nowadays, I think it is
safe to say that you can fit two xterms with 100 columns horizonally
next to each other. 100 columns should also be sufficient for a msg_p*
of roughly 80 columns of text.
132 columns provide more leeway, but IMHO that would be too wide for
good readability (and my screen can't fit two xterms side-by-side anymore).
Of course some files have sections where any column limit is not
acceptable (board lists etc.), but the column limit violations should be
limited to the affected file sections, not whole files.
Comments?
I'd like to get this decided today or tomorrow so we know where we need
line breaks in Stefan Tauner's new struct flashchip patch.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
by Paul Kocialkowski
A Hardware Enablement devroom will be taking place at FOSDEM this year,
on Sunday 10 December 2017. This newly-created devroom is the result of
3 proposals that were merged together. It is co-organized by several
individuals.
The devroom covers all aspects related to hardware enablement and
support with free software, including aspects related to boot software,
firmwares, drivers and userspace tools and adaptation.
Proposals for talks related to these topics are welcome and can be
submitted until Sunday 26 November 2017 via the pentabarf interface.
Short talks are encouraged over longer ones in order to cover a wide
range of topics.
The announcement for the devroom, that contains all the useful
information, was published at:
https://lists.fosdem.org/pipermail/fosdem/2017-October/002649.html
Cheers and see you at FOSDEM!
--
Paul Kocialkowski, developer of free digital technology and hardware
support
Website: https://www.paulk.fr/
Coding blog: https://code.paulk.fr/
Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
by Rudolf Marek
Hi,
Attaching a patch which works around the valloc() issue in the DJGPP.
Please apply before the flashrom 1.0.
In the meanwhile, it would be great if someone could test it too,
if needed I will distribute the executable for a test to Rayer (on CC).
I will also try to get some help on DJGPP list, as this issue happens
even with the official RPMs of DJGPP 2.05.
Signed-off-by: Rudolf Marek <r.marek(a)assembler.cz>
Fix the documentation and DOS port.
Update the DOS cross-compile documentation,
and workaround issue with valloc() with the
latest DJGPP.
Thanks
Rudolf
by Alois Schlögl
I'm trying to get a backup of the bios of my desktop computer, but it
fails with this message:
# flashrom -V -p internal -r bios.rom
flashrom v0.9.9-91-g0bfa819 on Linux 4.13.0-0.bpo.1-amd64 (x86_64)
flashrom is free software, get the source code at https://flashrom.org
flashrom was built with libpci 3.5.2, GCC 6.3.0 20170516, little endian
Command line (3 args): /home/as/src/flashrom/flashrom -V -p internal
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Initializing internal programmer
No coreboot table found.
Using Internal DMI decoder.
DMI string chassis-type: "Desktop"
DMI string system-manufacturer: "0000"
DMI string system-product-name: "OEM"
DMI string system-version: "OEM"
DMI string baseboard-manufacturer: "Foxconn"
DMI string baseboard-product-name: "G31MVP"
DMI string baseboard-version: "FAB:1.0"
Found ITE Super I/O, ID 0x8718 on port 0x2e
Found chipset "Intel ICH7/ICH7R" with PCI ID 8086:27b8.
Enabling flash write... Root Complex Register Block address = 0xfed1c000
Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000
/dev/mem mmap failed: Operation not permitted
FAILED!
FATAL ERROR!
Error: Programmer initialization failed.
I tried with flashrom "v0.9.9-r1954" from debian/stable as well as the
latest version from the git repository. Both gave the same results.
Here are the results of the recommended steps fom https://flashrom.org/FAQ :
- The page "https://www.flashrom.org/Supported_hardware " lists
ICH7/ICH7R as supported, but this does not seem to be the case for me.
The user manual of the motherboard is available here:
http://www.produktinfo.conrad.com/datenblaetter/850000-874999/871892-an-0...
- The manual does also not show any jumpers that protect against bios
updates.
- The bios setting "Super BIOS Protect" is disabled.
Do you have any suggestions how to proceed ?
Cheers,
Alois
by Nico Huber
Hi Branden,
On 30.12.2017 07:20, Branden Waldner wrote:
> I could probably do some testing of the dos build if you still need someone to.
thanks, it's tested now. Though if you want to, you can of course give
it some more testing. Just probing the chip should suffice (if probing
would work but anything else not, it's likely not DOS related). Probing
/should/ be safe (with the usual exception of unsupported laptops).
Nico
by Nico Huber
Hi Michael,
On 29.12.2017 15:00, Michael Zhilin wrote:
> Compilation on FreeBSD 12-current is fine,
thanks for the confirmation.
> but could you please merge
> https://patchwork.coreboot.org/patch/4498/ before release?
We've merged your patch to the master branch already. But I deliberately
didn't forward it to the 1.0.x release branch (yet), because nobody con-
firmed yet that it doesn't regress on Linux (I doubt it does after rea-
ding about IEXTEN, but think we should run it at least once anyway; I
don't have any serprog programmer).
Patch is here, if anyone wants to give it a shot on Linux
https://review.coreboot.org/22334/
Nico
by Branden Waldner
Hi,
I could probably do some testing of the dos build if you still need someone to.
Currently I just have freedos setup to run aflash.exe on a board that
doesn't work with flashrom, but I can run it on other boards. Mainly
just the sis630 board (parallel flash) I've got that uses the same
flash chip and is supported and socketed, but I can try reading on
other boards for testing LPC or FWH as well, but I don't have any
socketed to make it easy to just test writes on a spare flash chip
(have several off of failed boards). I don't feel like messing around
with any of my spi flash boards, so at best I could try reading if you
think it's safe.
Cross-compiling it seems kind of annoying, but not overly complicated.
I'd be builidng with a debian stretch i686.
Just send me a response with what you'd like me to test if you still
need it tested.
Branden
by Nico Huber
Hey folks,
we've just tagged a release candidate for flashrom-1.0. It seems very
stable; though, testing of this specific revision was rather limited
[1]. So please test! especially if you use a rare setup (e.g. non-Linux
/ non-x86).
If you don't use Git, you can find a tarball here:
https://review.coreboot.org/cgit/flashrom.git/snapshot/flashrom-1.0-rc2.t...
Nico
[1] Beside being used by developers, it's currently build tested on the
following OS's (mostly thanks to Docker multiarch images):
NetBSD 7.1 amd64
NetBSD 7.1 i386
alpine:amd64-v3.6
alpine:amd64-v3.7
alpine:i386-v3.6
alpine:i386-v3.7
centos:7.2-amd64-clean
centos:7.3-aarch64-clean
centos:7.3-amd64-clean
debian-debootstrap:amd64-sid
debian-debootstrap:amd64-stretch
debian-debootstrap:armhf-stretch
debian-debootstrap:i386-sid
debian-debootstrap:i386-stretch
debian-debootstrap:mips-stretch
debian-debootstrap:mipsel-stretch
debian-debootstrap:powerpc-sid
debian-debootstrap:ppc64el-stretch
fedora:24-x86_64
fedora:25-aarch64
fedora:25-ppc64le
fedora:25-x86_64
ubuntu-debootstrap:amd64-xenial
ubuntu-debootstrap:amd64-zesty
ubuntu-debootstrap:arm64-xenial
ubuntu-debootstrap:i386-xenial
ubuntu-debootstrap:i386-zesty
by Ivan Ivanov
Hi ondrej, I think that - to reliably determine that reading is truly
done without errors,
its needed to read at least two times and then compare the checksums
of read files
Also, you haven't told us - where is this chip located? are you trying
in-system programming?
if yes, make sure that the wires (connecting a programmer and test
clip) are short enough and reliable,
and maybe its a good idea to unite WP/HOLD pins of flash chip with VCC
(if they are not connected to a programmer, currently)
(so that they would be 1 logical level) - but that is if nothing else
helps. This helped me to read/write one cFeon chip that failed in
other cases,
but please note that your macronix could be different and if you have
some time - check the datasheet of your flash chip to make sure
that setting WP/HOLD to 1 is okay
Best regards,
Ivan<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table
style="border-top: 1px solid #D3D4DE;">
<tr>
<td style="width: 55px; padding-top: 18px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp... "
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-ani... "
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
<td style="width: 470px; padding-top: 17px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Без вирусов. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp... "
target="_blank" style="color: #4453ea;">www.avast.ru </a> </td>
</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>
2017-12-22 17:02 GMT+03:00 ondrej ondrej <pondrej3(a)gmail.com>:
> Hi David,
> thank you for your support. Excuse me, I need some time for testing.
> I slow down SPI interface as you recommended me `./flashrom -V -p
> ft2232_spi:type=arm-usb-ocd-h:divisor=60 -o test.txt`, but this
> command don't work for me. I must change semi colon to dash in your
> command "./flashrom -V -p ft2232_spi:type=arm-usb-ocd-h,divisor=60 -c
> MX25L4005(A/C)/MX25L4006E -r file.bin -o test.txt". Maybe this is a
> bug in flashrom.
> I tested (write to them and repeatedly read its contents) some chips
> (MX25L4005A) and two chips from the group of 20 give some errors (for
> details, please see attachments) when I try to write to them. Every
> time when I try to read everything is ok (without errors), but content
> on the chip is not written correctly (in this two cases).
>
> -------
> Error from test12wa.txt:
> flashrom v0.9.9-98-g3083ed9 on Linux 4.0.5-gentoo (x86_64)
> flashrom was built with libpci 3.2.0, GCC 4.8.4, little endian
> Command line (9 args): ./flashrom -VVV -p
> ft2232_spi:type=arm-usb-ocd-h,divisor=60 -c MX25L4005(A/C)/MX25L4006E
> -w file_w.bin -o test12wa.txt
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Initializing ft2232_spi programmer
> Using device type Olimex ARM-USB-OCD-H channel A.
> Disable divide-by-5 front stage
> Set clock divisor
> MPSSE clock: 60.000000 MHz, divisor: 60, SPI clock: 1.000000 MHz
> No loopback of TDI/DO TDO/DI
> Set data bits
> The following protocols are supported: SPI.
> Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB:
> programmer_map_flash_region: mapping MX25L4005(A/C)/MX25L4006E from
> 0x00000000fff80000 to 0x0000000000000000
> Assert CS#
> De-assert CS#
> RDID returned 0xc2 0x20 0x13. probe_spi_rdid_generic: id1 0xc2, id2 0x2013
> Found Macronix flash chip "MX25L4005(A/C)/MX25L4006E" (512 kB, SPI) on
> ft2232_spi.
> Assert CS#
> De-assert CS#
> Chip status register is 0x00.
> Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set
> Chip status register: Bit 6 is not set
> Chip status register: Bit 5 is not set
> Chip status register: Block Protect 2 (BP2) is not set
> Chip status register: Block Protect 1 (BP1) is not set
> Chip status register: Block Protect 0 (BP0) is not set
> Chip status register: Write Enable Latch (WEL) is not set
> Chip status register: Write In Progress (WIP/BUSY) is not set
> programmer_unmap_flash_region: unmapped 0x0000000000000000
> programmer_map_flash_region: mapping MX25L4005(A/C)/MX25L4006E from
> 0x00000000fff80000 to 0x0000000000000000
> Assert CS#
> De-assert CS#
> Block protection is disabled.
> Reading old flash chip contents... Assert CS#
> De-assert CS#
> ....
> ....
>
> Erase/write done.
> Verifying flash... Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> FAILED at 0x00000000! Expected=0x30, Found=0xff, failed byte count
> from 0x00000000-0x0007ffff: 0x80000
> 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!
> programmer_unmap_flash_region: unmapped 0x0000000000000000
>
> -------
> Error from test16wa.txt:
> flashrom v0.9.9-98-g3083ed9 on Linux 4.0.5-gentoo (x86_64)
> flashrom was built with libpci 3.2.0, GCC 4.8.4, little endian
> Command line (9 args): ./flashrom -VVV -p
> ft2232_spi:type=arm-usb-ocd-h,divisor=60 -c MX25L4005(A/C)/MX25L4006E
> -w file_w.bin -o test16wa.txt
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Initializing ft2232_spi programmer
> Using device type Olimex ARM-USB-OCD-H channel A.
> Disable divide-by-5 front stage
> Set clock divisor
> MPSSE clock: 60.000000 MHz, divisor: 60, SPI clock: 1.000000 MHz
> No loopback of TDI/DO TDO/DI
> Set data bits
> The following protocols are supported: SPI.
> Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB:
> programmer_map_flash_region: mapping MX25L4005(A/C)/MX25L4006E from
> 0x00000000fff80000 to 0x0000000000000000
> Assert CS#
> De-assert CS#
> RDID returned 0xc2 0x20 0x13. probe_spi_rdid_generic: id1 0xc2, id2 0x2013
> Found Macronix flash chip "MX25L4005(A/C)/MX25L4006E" (512 kB, SPI) on
> ft2232_spi.
> Assert CS#
> De-assert CS#
> Chip status register is 0x00.
> Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set
> Chip status register: Bit 6 is not set
> Chip status register: Bit 5 is not set
> Chip status register: Block Protect 2 (BP2) is not set
> Chip status register: Block Protect 1 (BP1) is not set
> Chip status register: Block Protect 0 (BP0) is not set
> Chip status register: Write Enable Latch (WEL) is not set
> Chip status register: Write In Progress (WIP/BUSY) is not set
> programmer_unmap_flash_region: unmapped 0x0000000000000000
> programmer_map_flash_region: mapping MX25L4005(A/C)/MX25L4006E from
> 0x00000000fff80000 to 0x0000000000000000
> Assert CS#
> De-assert CS#
> Block protection is disabled.
> Reading old flash chip contents... Assert CS#
> De-assert CS#
> Assert CS#
> ...
> ...
> ...
>
> De-assert CS#
> done. Looking for another erase function.
> Trying erase function 5... not defined. No usable erase functions left.
> FAILED!
> Uh oh. Erase/write failed. Checking if anything has changed.
> Reading current flash chip contents... Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> Assert CS#
> De-assert CS#
> 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!
> programmer_unmap_flash_region: unmapped 0x0000000000000000
>
>
>
> 2017-12-18 1:14 GMT+01:00 David Hendricks <david.hendricks(a)gmail.com>:
>>
>> Hi Ondrej,
>> The MX25L4005A is listed in the flashchips database as being supported, but as you point out the incorrect ID is being seen by the programmer. This is likely due to a signal integrity problem. Please try the following:
>> 1. Slow down the SPI interface by setting a higher divisor value in the programmer parameter, e.g. `./flashrom -V -p ft2232_spi:type=arm-usb-ocd-h:divisor=60 -o test.txt`. Currently your output shows "MPSSE clock: 60.000000 MHz, divisor: 2, SPI clock: 30.000000 MHz" which is generally very fast for an external programmer.
>> 2. Use shorter wires to connect the programmer to the chip, ideally 10cm or less.
>>
>>
>> 2017-12-17 5:19 GMT-08:00 ondrej ondrej <pondrej3(a)gmail.com>:
>>>
>>> Hi flashrom maintainers,
>>>
>>> I failed to read a MX25L4005AM2C (this name is written on chip) via the "Olimex ARM-USB-OCD-H". Maybe
>>> this chip have wrong id? Id for this chip in datasheet is Id1=0xC2, Id2=0x2013
>>>
>>> flashrom v0.9.9-98-g3083ed9 on Linux 4.0.5-gentoo (x86_64)
>>> flashrom was built with libpci 3.2.0, GCC 4.8.4, little endian
>>> Command line (5 args): ./flashrom -V -p ft2232_spi:type=arm-usb-ocd-h -o test.txt
>>> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
>>> Initializing ft2232_spi programmer
>>> Using device type Olimex ARM-USB-OCD-H channel A.
>>> Disable divide-by-5 front stage
>>> Set clock divisor
>>> MPSSE clock: 60.000000 MHz, divisor: 2, SPI clock: 30.000000 MHz
>>> No loopback of TDI/DO TDO/DI
>>> Set data bits
>>> The following protocols are supported: SPI.
>>> Probing for AMIC A25L05PT, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L05PU, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L10PT, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L10PU, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L20PT, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L20PU, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L40PT, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L40PU, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L80P, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L16PT, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L16PU, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25L032, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for AMIC A25LQ64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DF021, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DF041A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DF081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DF321, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DF321A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DF641(A), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DL081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DL161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25DQ161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff
>>> Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff
>>> Probing for Atmel AT25F512B, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff
>>> Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff
>>> Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff
>>> Probing for Atmel AT25FS010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT25FS040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT26DF041, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT26DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT26DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT26DF161A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT26F004, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45CS1282, 16896 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB011D, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB021D, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB041D, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB081D, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB161D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB321C, 4224 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB321D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB321E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel AT45DB642D, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for ESMT F25L008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for ESMT F25L32PA, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B05T, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25P05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B10T, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25P10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B20T, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25P20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B40T, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B80T, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B16T, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B32T, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25P32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25B64T, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25F05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25F10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25F20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25F40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25F80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25F16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25F32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25F64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25Q40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25Q80(A), 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25Q16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25Q32(A/B), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25Q64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25Q128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25QH16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25QH32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25QH64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25QH128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25S10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25S20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25S32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon EN25S64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for ESI ES25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for ESI ES25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for ESI ES25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25LQ40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25LQ80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25LQ32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25LQ64(B), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25LQ128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q20(B), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q40(B), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q80(B), 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q16(B), 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q32(B), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q64(B), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q128B, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25Q128C, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25T80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25VQ21B, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25VQ40C, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25VQ41B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25VQ80C, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for GigaDevice GD25VQ16C, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Intel 25F160S33B8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Intel 25F160S33T8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Intel 25F320S33B8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Intel 25F320S33T8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Intel 25F640S33B8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Intel 25F640S33T8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for ISSI IS25LP128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for ISSI IS25WP128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX23L1654, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX23L3254, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX23L6454, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX23L12854, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L1635D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L3205(A), 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L3273E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L3235D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L6405, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L6405D, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E/MX25L6473F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L12805D, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L25635F/MX25L25645E/MX25L25665E, 32768 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX66L51235F, 65536 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25U1635E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25U3235E/F, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25U6435E/F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25U12835F, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix MX25L6495F, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P05-A, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID.
>>> Probing for Micron/Numonyx/ST M25P10-A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID.
>>> Probing for Micron/Numonyx/ST M25P20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID.
>>> Probing for Micron/Numonyx/ST M25P40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID.
>>> Probing for Micron/Numonyx/ST M25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25P128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PX80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PX16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PX32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M25PX64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M45PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M45PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M45PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M45PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST M45PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST N25Q016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron N25Q256..3E/MT25QL256, 32768 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Micron N25Q512..3E/MT25QL512, 65536 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Nantronics N25S10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Nantronics N25S20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Nantronics N25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Nantronics N25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Nantronics N25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LD256C, 32 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LD512(C), 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LD010(C), 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LD020(C), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LD040(C), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LQ020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LQ040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LQ080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LQ016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LQ032C, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for PMC Pm25LV010A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LV020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LV040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LV080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC Pm25LV016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for Sanyo LE25FU406C/LE25U40CMC, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Sanyo LE25FW203A, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Sanyo LE25FW403A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for Spansion S25FL004A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL016A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL032A/P, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL064A/P, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL204K, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL208K, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL116K/S25FL216K, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL132K, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL164K, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL127S-64kB, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL127S-256kB, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL128P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL128P......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL128S......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL128S......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL129P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Spansion S25FL129P......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xe1, id2 0x9
>>> Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x9, id2 0x9
>>> Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xe1, id2 0x9
>>> Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xe1, id2 0x9
>>> Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xe1, id2 0x9
>>> Probing for SST SST25VF020B, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xe1, id2 0x9
>>> Probing for SST SST25VF040B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xe1, id2 0x9
>>> Probing for SST SST25WF020A, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25WF040B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25WF080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25VF080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25VF016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25VF032B, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25VF064C, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25WF512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25WF010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25WF020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25WF040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST SST25WF080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q40.V, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q80.V, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q16.V, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q32.V, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q64.V, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q128.V, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q256.V, 32768 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q20.W, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q40.W, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q80.W, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q16.W, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q32.W, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25Q128.W, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25X10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25X20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25X40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25X80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25X16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25X32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond W25X64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Unknown SFDP-capable chip, 0 kB: Signature = 0xffffffff (should be 0x50444653)
>>> No SFDP signature found.
>>> Probing for AMIC unknown AMIC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Atmel unknown Atmel SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Eon unknown Eon SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Macronix unknown Macronix SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for PMC unknown PMC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for SST unknown SST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for ST unknown ST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Sanyo unknown Sanyo SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xe1, id2 0x1009
>>> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ft2232_spi.
>>> Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xe1, id2 0x9
>>> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI).
>>> ===
>>> This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE
>>> The 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!
>>> No operations were specified.
>>>
>>>
>>> _______________________________________________
>>> flashrom mailing list
>>> flashrom(a)flashrom.org
>>> https://mail.coreboot.org/mailman/listinfo/flashrom
>>
>>
>
> _______________________________________________
> flashrom mailing list
> flashrom(a)flashrom.org
> https://mail.coreboot.org/mailman/listinfo/flashrom
