June 2016 - flashrom - mail.coreboot.org

Re: [flashrom] New SPI NOR Flash product Support
by Stefan Tauner Aug. 15, 2019

Aug. 15, 2019

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

4 4

80/100/132 column line width policy
by Carl-Daniel Hailfinger Dec. 15, 2018

Dec. 15, 2018

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/

7 9

Spansion S25FL128P......X
by The Raven April 24, 2017

April 24, 2017

I have a spansion S25FL128P......X chip and can do some tests. The "problem" is that i don't know if its an 0 or an 1. On the chip i see only "FL128PIF" and one line lower i see "00299012 C". Probing works (id1 0x01, id2 0x2018): Calibrating delay loop... OK. serprog: Programmer name is "serprog-duino" Found Spansion flash chip "S25FL128P......0" (16384 kB, SPI) on serprog. Found Spansion flash chip "S25FL128P......1" (16384 kB, SPI) on serprog. Found Spansion flash chip "S25FL128S......0" (16384 kB, SPI) on serprog. Found Spansion flash chip "S25FL128S......1" (16384 kB, SPI) on serprog. Found Spansion flash chip "S25FL129P......0" (16384 kB, SPI) on serprog. Found Spansion flash chip "S25FL129P......1" (16384 kB, SPI) on serprog. Multiple flash chip definitions match the detected chip(s): "S25FL128P......0", "S25FL128P......1", "S25FL128S......0", "S25FL128S......1", "S25FL129P......0", "S25FL129P......1" Please specify which chip definition to use with the -c <chipname> option. BTW: Chip was fund on a Dell-Systemboard.

3 6

Re: [flashrom] FYI: flashrom output for Altera EPCQ16
by Stefan Tauner June 30, 2016

June 30, 2016

On Thu, 30 Jun 2016 00:53:28 +0000 "Ma, Peter" <peter.ma(a)intel.com> wrote: > https://www.altera.com/content/dam/altera-www/global/en_US/pdfs/literature/… > > […] > > Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Hello Peter, thanks for your report. The replies this chip sends makes me think that Altera acquired the IP from Micron because the ID is exactly what you would expect from an N25Q016??3E chip, that is a 3.3 V, 16 Mb flash chip. However, as far as I can tell there never was a public datasheet available for such a chip, only its 1.8 V variants (which are supported by flashrom). The IP theory also makes completely sense due to the bonds (no pun intended) between Intel and Micron as well as Intel and Altera ;) The Altera datasheet disguises this by specifying the replies to the RDID identification opcode (Read Device Identification Operation) incompletely: they do not define the first and second byte of the reply. The first byte identifies the flash as ST (now Micron): 0x20. I'll need to dig further to see if there are any clear distinctions between the "Altera" chips and the existing bigger 3.3 V ST models that are also specified in the Altera datasheet but for which I have original Micron datasheets to cross check. If nothing dramatically comes up I'll add the needed chip definition to flashrom. Have you tried what flashrom promises, i.e. that flashrom should fully work with the generic definitions replied by the chip (SFDP)? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 2

FYI: flashrom output for Altera EPCQ16
by Ma, Peter June 30, 2016

June 30, 2016

https://www.altera.com/content/dam/altera-www/global/en_US/pdfs/literature/… # flashrom -VV -p linux_spi:dev=/dev/spidev0.0 flashrom v0.9.8-r1888 on Linux 4.6.2 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.5.1, GCC 5.4.0, little endian Command line (3 args): flashrom -VV -p linux_spi:dev=/dev/spidev0.0 Calibrating delay loop... OS timer resolution is 1 usecs, 444M loops per second, 10 myus = 10 us, 100 myus = 101 us, 1000 myus = 999 us, 10000 myus = 10005 us, 4 myus = 4 us, OK. Initializing linux_spi programmer Using device /dev/spidev0.0 The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26DF161A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT26F004, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45CS1282, 16896 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB011D, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB021D, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB041D, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB081D, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB161D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB321C, 4224 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB321D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB321E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B05T, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B10T, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B40T, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B80T, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B16T, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25B64T, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F05, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25Q128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25QH16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25QH32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25QH64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon EN25S64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25LQ32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q20(B), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q40(B), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for GigaDevice GD25T80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F160S33B8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F160S33T8, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F320S33B8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F320S33T8, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F640S33B8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3273E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L3235D, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6405, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6405D, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P05, 64 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P10-A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P10, 128 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P20-old, 256 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P40-old, 512 kB: Ignoring RES in favour of RDID. Probing for Micron/Numonyx/ST M25P80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25P128, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Nantronics N25S16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD256C, 32 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC Pm25LV016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Spansion S25FL004A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL008A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL016A, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL032A/P, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL128S......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL129P......0, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF020B, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF040B, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0xff, id2 0xff Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST SST25WF080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q40.V, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q80.V, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25Q64.W, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X10, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X20, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X40, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X80, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Unknown SFDP-capable chip, 0 kB: SFDP revision = 1.0 SFDP number of parameter headers is 1 (NPH = 0). SFDP parameter table header 0/0: ID 0x00, version 1.0 Length 36 B, Parameter Table Pointer 0x000030 Parsing JEDEC flash parameter table... 3-Byte only addressing. Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR. Write chunk size is at least 64 B. Flash chip size is 2048 kB. Block eraser 0: 512 x 4096 B with opcode 0x20 Tried to add a duplicate block eraser: 512 x 4096 B with opcode 0x20. Block eraser 1: 32 x 65536 B with opcode 0xd8 done. === SFDP has autodetected a flash chip which is not natively supported by flashrom yet. All standard operations (read, verify, erase and write) should work, but to support all possible features we need to add them manually. You can help us by mailing us the output of the following command to flashrom(a)flashrom.org: 'flashrom -VV [plus the -p/--programmer parameter]' Thanks for your help! === Found Unknown flash chip "SFDP-capable chip" (2048 kB, SPI) on linux_spi. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0xba15 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0xff, id2 0xff Found Unknown flash chip "SFDP-capable chip" (2048 kB, SPI). No operations were specified. Regards, --------------------------------------------------------- Peter Ma | email: peter.ma(a)intel.com Senior Design Engineer | tel: +1 (604) 742 5778 Intel of Canada, Ltd. | fax: +1 (604) 639 1185 #688 - 1333 West Broadway, Vancouver, BC, Canada, V6H 4C1

1 0

Re: [flashrom] Ideas for implementing support for 2nd status register
by Hatim Kanchwala June 27, 2016

June 27, 2016

Hi, Regarding block protection scheme, I am very glad to say I have had a breakthrough observation. After having sifted through around 90 datasheets, I was able to spot a pattern that majority of chips follow. GigaDevice and Winbond , along with some AMIC, Eon, Fudan and Macronix chips follow this pattern - around 50 in number. With this pattern, we can now dynamically generate the entire block protection ranges on-the-go. We don't need to hard-code the tables for these chips anymore and presence (or absence) of SEC, TB, or CMP bits is also handles generically! The exact algorithm is slightly convoluted, but I'll try my best to explain it. Feel free to skip past #5, you will have nothing much to lose. For all practical purposes, the BP4 and BP3 bits are identical to SEC and TB bits respectively. We'll call tuple of (BP3, BP2, BP1) as BP, and X is don't care. 1. For BP=(0,0,0): No protection, SEC=X, TB=X 2. For BP=(1,1,1): All protection, SEC=X, TB=X 3. For (SEC,TB)=(0,0): We introduce a parameter f, such that f = chip_size(in kB) / 64 for chips_size < 4096 kB; and f = 64 for chips_size >= 4096 kB. 3.1 For chip_size >= 4096 kB, we have the following correspondence of fraction of chip_size with BP: (0,0,1) - 1/64 (0,1,0) - 1/32 (0,1,1) - 1/16 ... (1,1,0) - 1/2 3.2 For chip_size = 2048 kB, we have the following correspondence of fraction of chip_size with BP: (0,0,1) - 1/32 (0,1,0) - 1/16 (0,1,1) - 1/8 ... (1,1,0) - 1 3.3 For chip_size = 1024 kB, we have the following correspondence of fraction of chip_size with BP: (0,0,1) - 1/16 (0,1,0) - 1/8 (0,1,1) - 1/4 ... (1,1,0) - 1 3.4 For chip_size = 512 kB, we have the following correspondence of fraction of chip_size with BP: (0,0,1) - 1/8 (0,1,0) - 1/4 ... (1,1,0) - 1 3.5 For chip_size = 256 kB, we have the following correspondence of fraction of chip_size with BP: (0,0,1) - 1/4 (0,1,0) - 1/2 (0,1,1) - 1 (1,0,0) - 0 (1,0,1) - 1/4 (1,1,0) - 1/2 3.6 For chip_size = 128 kB, we have the following correspondence of fraction of chip_size with BP: (0,0,1) - 1/2 (0,1,0) - 1 (0,1,1) - 1 (1,0,0) - 0 (1,0,1) - 1/2 (1,1,0) - 1 (SEC,TB)=(0,0) represents the upper portion of the chip (which means range addresses always end at top boundary). E.g. For a 4096 kB chip, (0,1,0) 1/32 means upper 256 kB - 0x3fff00-0x3fffff 4. For (SEC,TB)=(0,1): This represents the lower portion of the chip (which means range addresses always start at lower boundary). The same mapping defined earlier for fraction of chip_size holds. E.g. For a 512 kB chip, (0,1,0) means lower 128 kB - 0x000000-0x01ffff 5. For (SEC,TB)=(1,X): (0,0,1) - 4 kB (0,1,0) - 8 kB (0,1,1) - 16 kB (1,0,0) - 32 kB (1,0,1) - 32 kB *(1,1,0) - 32 kB We have upper for TB=0, lower for TB=1 E.g. For a 1024 kB chip TB=1, (1,0,0) means lower 32 kB - 0x000000-0x007fff *Some chips have 64 kB block instead of 32 kB. (You will not lose much if you skip up to here) 6. For chips with CMP bit: For all chips that I have seen (and that is well over a 100 SPI chips), the block protection range either starts at lower boundary of chip or ends at upper boundary of chip. So, given the range and size of the chip, we can compute the complement range. Please find attached pattern.c. It is an excerpt from the unmerged code I am working on and contains the implementation of the discussed model (cf. sec_block_pattern_range_generic). There are other functions and structs to show the models impact on the infrastructure. IMO, this is an immense improvement from what we have in ChromiumOS fork and what we have been discussing. Here are the key takeaway points - - Having the status register layout member in struct flashchip is immensely beneficial. A lot of chips can be supported with the generic code, perhaps with only slight adaptation. - Based on David's suggestion, shifting to function pointers was a good choice - it allows flexibility. - Presence (or absence) of CMP, TB (BP3), SEC (BP4) bit is automatically taken of, and the corresponding range is also dynamically generated. - For chips whose ranges cannot be dynamically generated, we have the option of specifying range manually. I think it is best to stick to range for such representation, instead of range of sectors/blocks or portions of chip (as suggested by David in the previous mail). Sticking with range is safe because range is independent of sector/block and will yield the proper result. - Based on Stefan's suggestion some time ago, having pointers to struct status_register and struct wp will allow greater re-use (which is happening a lot!) Please have a look at the source file. The output of the source is here (http://paste.flashrom.org/view.php?id=2940) Further work - - In the current implementation, for chips whose range is dynamically generated we have a pointer to the range and an ID variable to associate the range with the chip (this is so that range is computed once and reused for subsequent calls). If we have another chip then the ID and pointer gets overwritten (like is happening in main() in the source). So when we want to return to the previous chip, we have to again spend the computing cost. This can be enhanced if we use list data structures and append newly computed range tables. That way, we can always revisit a previously computed table at a nominal computing cost. - The computation of BP bitfield from a given range can be enhanced if we factor in CMP bit (if present) - there could be a scenario where CMP=0 and the given range is not possible, but if CMP=1 the range could be possible. - Another way we could enhance it is through suggesting nearest neighbours to the range. (I find this idea theoretically interesting, but practically I cannot come up with use cases) I hope you enjoyed going through the source. It took me a while to sift through so many datasheets and try out varying models, but I was elated with joy when the above algorithm was ready. I am looking forward to your feedback and comments on this. Thanks for your time and patience. Bye, Hatim

2 1

FLASHROM compatibility with SAMSUNG Laptop mainboard
by Antoine BERBACH June 23, 2016

June 23, 2016

Hello, Friends of mine have à SAMSUNG R540 jao4 Laptop who won't boot. I tried to access on the contents of her HDD via my own Laptop and after that I was seriously aggressed, the Bios also is bad! No problem for me, ASUS provide a tool for Bios re-flashing. SAMSUNG has no possibility to restore the bios out of Windows. I am looking for a tool to clean the CMOS by a new Bios restoration. *Question *: have you experience if FLASHROM is compatible for the motherboard off a SAMSUNG R540 jao4. If no possibility for FLASHROM, did you know a solution with Parted Magic to re-flash the Bios for SAMSUNG LAPTOP R540 jao4?? Best regards from Alsace/France Antoine --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

1 0

Need some help please
by jlpinckney28 June 23, 2016

June 23, 2016

I'm trying to use the flash ROMI keep getting error messageCannot find file.libUSB header -1.0 Not found.Is there a book for Flash rom I tried looking on the internet I found too much of nothing.Please help me if anyone canThank you. Sent via the Samsung Galaxy Note® 3, an AT&T 4G LTE smartphone

1 0

[PATCH 0/6] 4-bytes addressing support
by Cédric Le Goater June 20, 2016

June 20, 2016

Hi, Here's an old patchset proposed a while ago by Boris Baykov to add 4byte support to flashrom. I have been using it to flash N25Q256 modules from a raspberry pi quite successfully. Could we restart a review cycle to see what needs fixing ? A port of the complete patchset on 0.9.9 is available here : https://github.com/legoater/flashrom Thanks, C. Boris Baykov (6): 4BA: Basic support for 4-bytes addressing mode extensions 4BA: Flashrom integration for the 4-bytes addressing extensions 4BA: Winbond W25Q256.V chip (32MB) declaration, 4-bytes addr mode 4BA: Support for 4-bytes addressing via Extended Address Register 4BA: Support for new direct-4BA instructions + W25Q256.V update 4BA: Progress visualization for long read, writes and erases Makefile | 2 +- chipdrivers.h | 22 ++ cli_output.c | 3 +- flash.h | 21 ++ flashchips.c | 48 +++ flashrom.c | 61 ++++ serprog.c | 5 +- spi.c | 5 +- spi25.c | 37 ++- spi4ba.c | 920 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ spi4ba.h | 114 ++++++++ 11 files changed, 1231 insertions(+), 7 deletions(-) create mode 100644 spi4ba.c create mode 100644 spi4ba.h -- 2.1.4

2 7

AT25DF161 erase failed on ft2232_spi
by Алексей Елсаков June 13, 2016

June 13, 2016

2 2