- flashrom - mail.coreboot.org

Re: [flashrom] Macronix MX23L6454 probe/read success (buspirate_spi)
by Steven Honeyman 08 Mar '15

08 Mar '15

On 8 March 2015 at 00:46, Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > On 8 March 2015 at 00:24, Stefan Tauner > <stefan.tauner(a)alumni.tuwien.ac.at> wrote: >> On Sat, 7 Mar 2015 02:24:49 +0000 >> Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: >> >>> Probe and Read both worked, no problems >>> >>> Log: >>> >>> […] >>> Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Found Macronix flash chip "MX23L6454" (8192 kB, SPI) on buspirate_spi. >>> Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 >>> 0xc2, id2 0x517 >>> Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: >>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>> Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: >>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>> Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: >>> probe_spi_rdid_generic: id1 0xc2, id2 0x517 >>> Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 >>> parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 >>> Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 >>> kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, >>> id2 0x00 >>> Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. >>> probe_spi_rdid_generic: id1 0x00, id2 0x00 >>> […] >> >> Hello Steven, >> >> thanks for your report! >> The log looks quite suspicious in terms of reproducibility. The excerpt >> above shows that the chip replied two different things when queried with >> probe_spi_rdid_generic: all zeros and the correct ID (0xc2517) >> respectively. This is usually an indication for wiring problems. If it >> was that inconsistent all the time you would probably not be able to >> read a good image. Did you read the chip multiple times and compared >> the results? > > Hmmm, I didn't (because it was so slow), but I can do if you think > there were issues. > > I only had a quick look through the image but it looked to be what I > was expecting. > I'll dump the image using some other software/hardware and make sure > that matches too. ...ok definitely a false positive on the "works OK" status! 3rd resolder, 8th read attempt now. I haven't got two matching files yet. It keeps missing chunks out, at regular intervals, but different positions each time. I'm happy to upload/send the files & logs somewhere if they'd be useful to you? Tomorrow I'll try and find something else that will recognise & read this. The chip came from a working board so I know the ROM is good.

1 0

Re: [flashrom] Macronix MX23L6454 probe/read success (buspirate_spi)
by Stefan Tauner 08 Mar '15

08 Mar '15

On Sat, 7 Mar 2015 02:24:49 +0000 Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > Probe and Read both worked, no problems > > Log: > > […] > Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 > 0xc2, id2 0x517 > Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 > 0xc2, id2 0x517 > Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 > 0xc2, id2 0x517 > Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 > 0xc2, id2 0x517 > Found Macronix flash chip "MX23L6454" (8192 kB, SPI) on buspirate_spi. > Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 > 0xc2, id2 0x517 > Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: > probe_spi_rdid_generic: id1 0xc2, id2 0x517 > Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: > probe_spi_rdid_generic: id1 0xc2, id2 0x517 > Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: > probe_spi_rdid_generic: id1 0xc2, id2 0x517 > Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 > parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 > Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 > kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, > id2 0x00 > Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. > probe_spi_rdid_generic: id1 0x00, id2 0x00 > […] Hello Steven, thanks for your report! The log looks quite suspicious in terms of reproducibility. The excerpt above shows that the chip replied two different things when queried with probe_spi_rdid_generic: all zeros and the correct ID (0xc2517) respectively. This is usually an indication for wiring problems. If it was that inconsistent all the time you would probably not be able to read a good image. Did you read the chip multiple times and compared the results? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Regarding FPGA-based flash chip emulator project
by vin ben 07 Mar '15

07 Mar '15

Hi Flashrom, I am Vinamra. I want to contribute to the FPGA-based flash chip emulator project in the summer of code program. I have good experience with digital design and VHDL . Can you please get me started. many thanks -Vinamra

1 0

Regarding FPGA-based flash chip emulator project
by vin ben 07 Mar '15

07 Mar '15

Hi Flashrom, I am Vinamra. I want to contribute to the FPGA-based flash chip emulator project in the summer of code program. I have good experience with digital design and VHDL . Can you please get me started. many thanks -Vinamra

1 0

Macronix MX23L6454 probe/read success (buspirate_spi)
by Steven Honeyman 07 Mar '15

07 Mar '15

Probe and Read both worked, no problems Log: flashrom v0.9.8-r1887 on Linux 3.19.0-e6540 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.3.0, GCC 4.9.2 20150204 (prerelease), little endian Command line (5 args): flashrom -p buspirate_spi:dev=/dev/ttyUSB0 -r mx.bin -V Calibrating delay loop... OS timer resolution is 1 usecs, 3268M loops per second, 10 myus = 10 us, 100 myus = 121 us, 1000 myus = 1013 us, 10000 myus = 10006 us, 4 myus = 14 us, OK. Initializing buspirate_spi programmer Baud rate is 115200 now. Detected Bus Pirate hardware v3.5 Detected Bus Pirate firmware 6.2 Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for AMIC A25L05PT, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L05PU, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L10PT, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L10PU, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L20PT, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L20PU, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L40PT, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L40PU, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L80P, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L16PT, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L16PU, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25L020, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25L032, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25LQ16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for AMIC A25LQ64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF021, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF041A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF321, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF321A, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DF641(A), 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DL081, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DL161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25DQ161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F512B, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x00, id2 0x00 Probing for Atmel AT25FS010, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT25FS040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF041, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF081A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF161, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26DF161A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT26F004, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45CS1282, 16896 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB011D, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB021D, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB041D, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB081D, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB161D, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB321C, 4224 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Atmel AT45DB321D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB321E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Atmel AT45DB642D, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for ESMT F25L008A, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for ESMT F25L32PA, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B05T, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B10T, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25B20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25B20T, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B40T, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x509 Probing for Eon EN25B80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25B80T, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25B16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25B16T, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25P16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25B32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B32T, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25P32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25B64T, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F05, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25F80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25F16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25F32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25F64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q80(A), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q32(A/B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25Q64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25Q128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Eon EN25QH64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Eon EN25QH128, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S40, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon EN25S64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25LQ32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q512, 64 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q20(B), 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for GigaDevice GD25Q40(B), 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for GigaDevice GD25Q80(B), 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q16(B), 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q32(B), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q64(B), 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25Q128B, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for GigaDevice GD25T80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F160S33B8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F160S33T8, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F320S33B8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Intel 25F320S33T8, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Intel 25F640S33B8, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Intel 25F640S33T8, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L1654, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L3254, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX23L6454, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Found Macronix flash chip "MX23L6454" (8192 kB, SPI) on buspirate_spi. Probing for Macronix MX23L12854, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L2005(C)/MX25L2006E, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L4005(A/C)/MX25L4006E, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L8005/MX25L8006E/MX25L8008E/MX25V8005, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1605, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L1605A/MX25L1606E/MX25L1608E, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1635D, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3205(A), 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L3206E/MX25L3208E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3273E, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L3235D, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6405, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6405D, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6406E/MX25L6408E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Macronix MX25L12805D, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L12835F/MX25L12845E/MX25L12865E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U1635E, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U3235E/F, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U6435E/F, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25U12835F, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix MX25L6495F, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P05-A, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P05, 64 kB: probe_spi_res1: id 0x0 Probing for Micron/Numonyx/ST M25P10-A, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P10, 128 kB: probe_spi_res1: id 0xff Probing for Micron/Numonyx/ST M25P20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 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 0xc2, id2 0x517 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 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25P32, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P64, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25P128, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M25PE80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PE16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX80, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M25PX64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST M45PE20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST M45PE16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Micron/Numonyx/ST N25Q016, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S10, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S20, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Nantronics N25S40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Nantronics N25S16, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD256C, 32 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LD512(C), 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD010(C), 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD020(C), 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LD040(C), 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV512(A), 64 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for PMC Pm25LV040, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV080B, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC Pm25LV016B, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo LE25FW106, 128 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW406A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FU406B, 512 kB: probe_spi_res2: id1 0xff, id2 0xff Probing for Sanyo LE25FW203A, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo LE25FW403A, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Sanyo LE25FW418A, 512 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW806, 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Sanyo LE25FW808, 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for Spansion S25FL004A, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL008A, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL016A, 2048 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL032A/P, 4096 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL064A/P, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL204K, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL208K, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL116K/S25FL216K, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL132K, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL164K, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL127S-64kB, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL127S-256kB, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128P......0, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128P......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Spansion S25FL128S......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL128S......1, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL129P......0, 16384 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Spansion S25FL129P......1, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25LF020A, 256 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25LF040A, 512 kB: probe_spi_res2: id1 0x7f, id2 0xff Probing for SST SST25LF080(A), 1024 kB: probe_spi_res2: id1 0x0, id2 0x0 Probing for SST SST25VF512(A), 64 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF010(A), 128 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF020, 256 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF020B, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF040, 512 kB: probe_spi_rems: id1 0x0, id2 0x0 Probing for SST SST25VF040B, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST SST25VF040B.REMS, 512 kB: probe_spi_rems: id1 0x7f, id2 0xff Probing for SST SST25VF080B, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF016B, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF032B, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25VF064C, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF512, 64 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF010, 128 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF020, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF040, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for SST SST25WF080, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q40.V, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q80.V, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25Q16.V, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q32.V, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q64.V, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q128.V, 16384 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q20.W, 256 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q40.W, 512 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q80.W, 1024 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q16.W, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q32.W, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X10, 128 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X20, 256 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X40, 512 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Winbond W25X16, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X32, 4096 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond W25X64, 8192 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Unknown SFDP-capable chip, 0 kB: No SFDP signature found. Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Macronix unknown Macronix SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for PMC unknown PMC SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for SST unknown SST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for ST unknown ST SPI chip, 0 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x517 Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, id2 0x0 Found Macronix flash chip "MX23L6454" (8192 kB, SPI). This chip's main memory can not be erased/written by design. === This flash part has status UNTESTED for operations: PROBE READ The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading flash... done. Raw bitbang mode version 1 Bus Pirate shutdown completed.

1 0

clean myself
by harold h 06 Mar '15

06 Mar '15

hello i would like to remove some traces of myself on the web, including my real name and my email address in these pages: http://comments.gmane.org/gmane.linux.bios.flashrom/3286 http://marc.info/?l=flashrom&m=138333170616302&w=2 http://marc.info/?a=138333182900004&r=1&w=2 http://static-173-79-223-25.washdc.fios.verizon.net/?l=flashrom&r=2&b=20131… http://www.flashrom.org/pipermail/flashrom/2013-November/011835.html thanks you for understand me Best regards, thanks you

1 0

About frser-duino baudrate and other stuff (was Re: MX25L6445E erase and write failed!)
by Urja Rannikko 04 Mar '15

04 Mar '15

Hi, >> I got a bit carried away reading the serprog-duino firmware code >> and decided to just see what it'd look like with my frser-* codebase. >> So, fresh out of the oven, and untested (i tested on my m644p before i >> converted it for the m328p): >> https://github.com/urjaman/frser-duino >> To use it: >> git clone git://github.com/urjaman/frser-duino >> cd frser-duino >> make && make program >> >> (the defaults are for the u2 arduino, eg. ttyACM0 and 115200, i didnt >> have time to work the makefile magic that hard.) >> So I heard this works at 115200... I made a change in the Makefile that should allow you to change the speed used by serprog* to something faster, namely 2000000 ;) I think it should be okay - i remember gnutoo claiming the U2 can do it with the delay he had added and i added that to frser-duino uart.c... (* without changing the bootloader speed...) So, if you want to test that, in the frser-duino tree git pull and change the Makefile so it says FRBAUD:=2000000 then make && make program And try out if everything still works. (now with -p serprog:dev=/dev/ttyACM0:2000000 i guess) Also compared to serprog-duino, frser-duino should allow setting SPI frequency ( although the default 8mhz is propably ok) but just in case of long wires... eg -p serprog:dev=/dev/ttyACM0:2000000,spispeed=1M The hardware can do 7 steps between 8 MHz and 125 kHz when the AVR is at 16 Mhz. -- Urja Rannikko

1 0

Re: [flashrom] MX25L6445E erase and write failed!
by Urja Rannikko 04 Mar '15

04 Mar '15

Hi, > I've an idea. Maybe you've managed to switch the MX25L6445E into the > "individual block protection mode" (read the datasheet page 30 - its > an OTP, once done once its for good) and now it isnt actually > erasing/writing anything at all (that 1M just happens to have > succeeded previously) because flashrom currently doesnt know of the > invidividual block unlock commands (or even the GBULK gang block > unlock) and thinks everything is ok because the status register looks > like unlocked. > > So maybe read the current contents into a file and modify a little bit > in the erased area (eg. swap out the first 4k to random data*) and see > if it writes. My theory is it wont. > > *here's example commands: > flashrom <insert your parameters> -r current.bin > dd if=/dev/urandom of=4krandom.bin bs=1024 count=4 > dd if=current.bin bs=1024 skip=4 of=current-4.bin > cat 4krandom.bin current-4.bin > modified.bin > flashrom <parameters> -w modified.bin > > Somebody'd need to write a patch to flashrom to use the RDSCUR command > to see if WPSEL is set to see for sure. But support for this wouldnt > hurt anyways. I'll see if i have time later in the evening to make a > prototype/test patch for this... I already had the datasheet open, so... here it is (in slightly crude form). https://github.com/urjaman/flashrom/commit/b51f09e5f21bf14d492c7d006e0bdd86… there's the commit if somebody wants to just web see. To test, in the flashrom-serprog git tree you have: git pull git checkout mx25l6445e-debug make ./flashrom ... -- Urja Rannikko

1 0

Re: [flashrom] MX25L6445E erase and write failed!
by Urja Rannikko 04 Mar '15

04 Mar '15

Hi, Could you please keep this in the mailing list... On Wed, Mar 4, 2015 at 9:09 AM, The Raven <originalraven(a)hotmail.com> wrote: > Hi Again > > After a long time flashrom trys other erase options. > Have a look here: > -0x0f5fff:E, 0x0f6000-0x0f6fff:E, 0x0f7000-0x0f7fff:E, > 0x0f8000-0x0f8fff:E, 0x0f9000-0x0f9fff:E, 0x0fa000-0x0fafff:E, > 0x0fb000-0x0fbfff:E, 0x0fc000-0x0fcfff:E, 0x0fd000-0x0fdfff:E, > 0x0fe000-0x0fefff:E, 0x0ff000-0x0fffff:E, 0x100000-0x100fff:EFAILED at > 0x00100000! Expected=0xff, Found=0xeb, failed byte count from > 0x00100000-0x00100fff: 0xfe5 > ERASE FAILED! > Reading current flash chip contents... done. Looking for another erase > function. > Trying erase function 1... 0x000000-0x007fff:S, 0x008000-0x00ffff:S, > 0x010000-0x017fff:S, 0x018000-0x01ffff:S, 0x020000-0x027fff:S, > 0x028000-0x02ffff:S, 0x030000-0x037fff:S, 0x038000-0x03ffff:S, > 0x040000-0x047fff:S, 0x048000-0x04ffff:S, 0x050000-0x057fff:S, > 0x058000-0x05ffff:S, 0x060000-0x067fff:S, 0x068000-0x06ffff:S, > 0x070000-0x077fff:S, 0x078000-0x07ffff:S, 0x080000-0x087fff:S, > 0x088000-0x08ffff:S, 0x090000-0x097fff:S, 0x098000-0x09ffff:S, > 0x0a0000-0x0a7fff:S, 0x0a8000-0x0affff:S, 0x0b0000-0x0b7fff:S, > 0x0b8000-0x0bffff:S, 0x0c0000-0x0c7fff:S, 0x0c8000-0x0cffff:S, > 0x0d0000-0x0d7fff:S, 0x0d8000-0x0dffff:S, 0x0e0000-0x0e7fff:S, > 0x0e8000-0x0effff:S, 0x0f0000-0x0f7fff:S, 0x0f8000-0x0fffff:S, > 0x100000-0x107fff:EFAILED at 0x00100000! Expected=0xff, Found=0xeb, > failed byte count from 0x00100000-0x00107fff: 0x7f69 > ERASE FAILED! > Reading current flash chip contents... done. Looking for another erase > function. > Trying erase function 2... 0x000000-0x00ffff:S, 0x010000-0x01ffff:S, > 0x020000-0x02ffff:S, 0x030000-0x03ffff:S, 0x040000-0x04ffff:S, > 0x050000-0x05ffff:S, 0x060000-0x06ffff:S, 0x070000-0x07ffff:S, > 0x080000-0x08ffff:S, 0x090000-0x09ffff:S, 0x0a0000-0x0affff:S, > 0x0b0000-0x0bffff:S, 0x0c0000-0x0cffff:S, 0x0d0000-0x0dffff:S, > 0x0e0000-0x0effff:S, 0x0f0000-0x0fffff:S, 0x100000-0x10ffff:EFAILED at > 0x00100000! Expected=0xff, Found=0xeb, failed byte count from > 0x00100000-0x0010ffff: 0xfb20 > ERASE FAILED! > Reading current flash chip contents... done. Looking for another erase > function. > Trying erase function 3... 0x000000-0x7fffff:EFAILED at 0x00100000! > Expected=0xff, Found=0xeb, failed byte count from 0x00000000-0x007fffff: > 0x26be30 > ERASE FAILED! > Reading current flash chip contents... done. Looking for another erase > function. > Trying erase function 4... 0x000000-0x7fffff:EFAILED at 0x00100000! > Expected=0xff, Found=0xeb, failed byte count from 0x00000000-0x007fffff: > 0x26be30 > ERASE FAILED! > Looking for another erase function. > No usable erase functions left. > FAILED! > > As you can see it always fails at the same byte count. I am still not > sure if this problem is related to serprog. > > Greetings I've an idea. Maybe you've managed to switch the MX25L6445E into the "individual block protection mode" (read the datasheet page 30 - its an OTP, once done once its for good) and now it isnt actually erasing/writing anything at all (that 1M just happens to have succeeded previously) because flashrom currently doesnt know of the invidividual block unlock commands (or even the GBULK gang block unlock) and thinks everything is ok because the status register looks like unlocked. So maybe read the current contents into a file and modify a little bit in the erased area (eg. swap out the first 4k to random data*) and see if it writes. My theory is it wont. *here's example commands: flashrom <insert your parameters> -r current.bin dd if=/dev/urandom of=4krandom.bin bs=1024 count=4 dd if=current.bin bs=1024 skip=4 of=current-4.bin cat 4krandom.bin current-4.bin > modified.bin flashrom <parameters> -w modified.bin Somebody'd need to write a patch to flashrom to use the RDSCUR command to see if WPSEL is set to see for sure. But support for this wouldnt hurt anyways. I'll see if i have time later in the evening to make a prototype/test patch for this... -- Urja Rannikko

1 0

W836xx: FUJITSU D3222-B1: flashrom -V
by crow 03 Mar '15

03 Mar '15

$ sudo flashrom -V -p internal flashrom v0.9.7-r1711 on Linux 3.18.6-1-ARCH (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.8.2, little endian Command line (3 args): flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 3691M loops per second, 10 myus = 10 us, 100 myus = 103 us, 1000 myus = 1007 us, 10000 myus = 10010 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "FUJITSU" DMI string system-product-name: "D3222-B1" DMI string system-version: " " DMI string baseboard-manufacturer: "FUJITSU" DMI string baseboard-product-name: "D3222-B1" DMI string baseboard-version: "S26361-D3222-B1 " DMI string chassis-type: "Mini Tower" W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 00. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found chipset "Intel Q87" with PCI ID 8086:8c4e. This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode enabled 0xffe00000/0xffa00000 FWH decode enabled 0xffd80000/0xff980000 FWH decode enabled 0xffd00000/0xff900000 FWH decode enabled 0xffc80000/0xff880000 FWH decode enabled 0xffc00000/0xff800000 FWH decode enabled 0xff700000/0xff300000 FWH decode enabled 0xff600000/0xff200000 FWH decode enabled 0xff500000/0xff100000 FWH decode enabled 0xff400000/0xff000000 FWH decode enabled Maximum FWH chip size: 0x100000 bytes BIOS_CNTL = 0x2a: BIOS Lock Enable: enabled, BIOS Write Enable: disabled Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0xdc from 0x2a to 0x0b on Q87 failed. New value is 0x2a. Root Complex Register Block address = 0xfed1c000 GCS = 0xc61: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0xf008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=1 Warning: SPI Configuration Lockdown activated. Reading OPCODES... done 0x06: 0x3f00 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=63, SME=0 0x50: 0x00004a4b (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x4a, BRRA 0x4b 0x54: 0x00000000 FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x07ff0500 FREG1: BIOS region (0x00500000-0x007fffff) is read-write. 0x5C: 0x04ff0003 FREG2: Warning: Management Engine region (0x00003000-0x004fffff) is locked. 0x60: 0x00020001 FREG3: Gigabit Ethernet region (0x00001000-0x00002fff) is read-write. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see http://flashrom.org/ME for details. Writes have been disabled for safety reasons. You can enforce write support with the ich_spi_force programmer option, but you will most likely harm your hardware! If you force flashrom you will get no support if something breaks. On a few mainboards it is possible to enable write access by setting a jumper (see its documentation or the board itself). 0x90: 0xc0 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 0x91: 0xfc4010 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=0, SME=0, SCF=4 0x94: 0x0006 (PREOP) 0x96: 0x043b (OPTYPE) 0x98: 0x05203b02 (OPMENU) 0x9C: 0x0000019f (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xC4: 0x80802045 (LVSCC) LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xC8: 0x00002045 (UVSCC) UVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=0 0xD0: 0x50444653 (FPB) Enabling hardware sequencing because some important opcode is locked. SPI Read Configuration: prefetching enabled, caching enabled, PROBLEMS, continuing anyway The following protocols are supported: FWH, Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Found 1 attached SPI flash chip with a density of 8192 kB. The flash address space (0x000000 - 0x7fffff) is divided at address 0x653000 in two partitions. The first partition ranges from 0x000000 to 0x652fff. In that range are 1619 erase blocks with 4096 B each. The second partition ranges from 0x653000 to 0x7fffff. In that range are 429 erase blocks with 4096 B each. Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific) at physical address 0x0. Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0x58, id2 0x01, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AB, 512 kB: probe_82802ab: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 kB: probe_82802ab: id1 0x17, id2 0x0e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0x58, id2 0x01, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Sharp LHF00L04, 1024 kB: probe_82802ab: id1 0x17, id2 0x0e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF002A/B, 256 kB: probe_jedec_common: id1 0x58, id2 0x01, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 kB: probe_jedec_common: id1 0x7d, id2 0xf4, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 kB: probe_jedec_common: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 kB: probe_82802ab: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 kB: probe_jedec_common: id1 0x17, id2 0x0e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 kB: probe_82802ab: id1 0x17, id2 0x0e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xf7, id2 0x85, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0x17, id2 0x0e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0x17, id2 0x0e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 kB: probe_82802ab: id1 0x58, id2 0x01, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 kB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xf7, id2 0x85, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 kB: probe_82802ab: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 kB: probe_82802ab: id1 0x17, id2 0x0e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FA, 512 kB: probe_jedec_common: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FB, 512 kB: probe_jedec_common: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040FC, 512 kB: probe_jedec_common: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002FA, 256 kB: probe_jedec_common: id1 0x58, id2 0x01, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 kB: probe_jedec_common: id1 0x17, id2 0x0e, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 kB: probe_jedec_common: id1 0x0c, id2 0x00, id1 parity violation, id1 is normal flash content, id2 is normal flash content Found Programmer flash chip "Opaque flash chip" (8192 kB, Programmer-specific). No operations were specified. Restoring MMIO space at 0x7f9f728468a0 Restoring PCI config space for 00:1f:0 reg 0xdc $

1 0

Re: [flashrom] [coreboot] New flashrom logo - please vote!
by Stefan Tauner 03 Mar '15

03 Mar '15

On Mon, 2 Mar 2015 09:03:59 -0800 Vadim Bendebury <vbendeb(a)chromium.org> wrote: > Not that I care much, but I can't help it: this new symbol looks very > much like the infamous SS Bolts: > http://www.adl.org/combating-hate/hate-on-display/c/ss-bolts.html#.VPSXeFX3… Yes, it could be mistaken for a sig rune although it clearly differs (the rune is not formed as an arrow on the bottom but is symmetric). I would not use two of this or similar symbols side by side because it could easily be seen as a political statement I definitely don't want to make. But on the other hand there are a lot of other (admittedly less known) runes and symbols used by the SS or other Nazi organizations that we use on a daily basis probably without even knowing it... (e.g. https://en.wikipedia.org/wiki/Runic_insignia_of_the_Schutzstaffel#mediaview…) So thanks for bringing this up - it is a valid concern - but I draw the line not to cross elsewhere. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

3 2

Re: [flashrom] MX25L6445E erase and write failed!
by Urja Rannikko 03 Mar '15

03 Mar '15

Hi, Just "forwarding" (really replying) this to the mailing list so others can see too. I see no serprog errors this time, so now it starts to feel like maybe some kind of flashrom problem (4k erase doesnt work after that addr? why?), but not sure. I'll take a look at the definitions and datasheet etc later, now at work. On Tue, Mar 3, 2015 at 10:52 AM, The Raven <originalraven(a)hotmail.com> wrote: > Okidoki Dr. Johnes ;-) > > Have tested the "MX25L6445E" with normal flashrom and frser-duino -> > Same error as before! > > Then i have compiled and used your special flashrom version (no compiler > errors) with frser-duino -> Also same error! :-( > > Here is the whole log: > > raven@PC ~/flashrom-master $ ./flashrom -p > serprog:dev=/dev/ttyACM0:115200 -c > "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E" -VE > flashrom v0.9.8-unknown on Linux 3.13.0-24-generic (i686) > flashrom is free software, get the source code at http://www.flashrom.org > > flashrom was built with libpci 3.2.1, GCC 4.8.2, little endian > Command line (5 args): ./flashrom -p serprog:dev=/dev/ttyACM0:115200 -c > MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E -VE > Calibrating delay loop... OS timer resolution is 1 usecs, 1083M loops > per second, 10 myus = 10 us, 100 myus = 143 us, 1000 myus = 963 us, > 10000 myus = 10405 us, 4 myus = 5 us, OK. > Initializing serprog programmer > Baud rate is 115200 now. > serprog: connected - attempting to synchronize > ... > serprog: Synchronized > serprog: Interface version ok. > serprog: Bus support: parallel=off, LPC=off, FWH=off, SPI=on > serprog: Maximum write-n length is 256 > serprog: Maximum read-n length is 23552 > serprog: Programmer name is "frser-duino" > serprog: Serial buffer size is 1020 > serprog: operation buffer size is 12 > serprog: Output drivers enabled > The following protocols are supported: SPI. > Probing for Macronix MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E, 8192 > kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2017 > Found Macronix flash chip "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E" > (8192 kB, SPI) on serprog. > 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: Block Protect 3 (BP3) 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 > This chip may contain one-time programmable memory. flashrom cannot read > and may never be able to write it, hence it may not be able to completely > clone the contents of this chip (see man page for details). > Erasing and writing flash chip... Trying erase function 0... > 0x000000-0x000fff:E, 0x001000-0x001fff:E, 0x002000-0x002fff:E, > 0x003000-0x003fff:E, 0x004000-0x004fff:E, 0x005000-0x005fff:E, > 0x006000-0x006fff:E, 0x007000-0x007fff:E, 0x008000-0x008fff:E, > 0x009000-0x009fff:E, 0x00a000-0x00afff:E, 0x00b000-0x00bfff:E, > 0x00c000-0x00cfff:E, 0x00d000-0x00dfff:E, 0x00e000-0x00efff:E, > 0x00f000-0x00ffff:E, 0x010000-0x010fff:E, 0x011000-0x011fff:E, > 0x012000-0x012fff:E, 0x013000-0x013fff:E, 0x014000-0x014fff:E, > 0x015000-0x015fff:E, 0x016000-0x016fff:E, 0x017000-0x017fff:E, > 0x018000-0x018fff:E, 0x019000-0x019fff:E, 0x01a000-0x01afff:E, > 0x01b000-0x01bfff:E, 0x01c000-0x01cfff:E, 0x01d000-0x01dfff:E, > 0x01e000-0x01efff:E, 0x01f000-0x01ffff:E, 0x020000-0x020fff:E, > 0x021000-0x021fff:E, 0x022000-0x022fff:E, 0x023000-0x023fff:E, > 0x024000-0x024fff:E, 0x025000-0x025fff:E, 0x026000-0x026fff:E, > 0x027000-0x027fff:E, 0x028000-0x028fff:E, 0x029000-0x029fff:E, > 0x02a000-0x02afff:E, 0x02b000-0x02bfff:E, 0x02c000-0x02cfff:E, > 0x02d000-0x02dfff:E, 0x02e000-0x02efff:E, 0x02f000-0x02ffff:E, > 0x030000-0x030fff:E, 0x031000-0x031fff:E, 0x032000-0x032fff:E, > 0x033000-0x033fff:E, 0x034000-0x034fff:E, 0x035000-0x035fff:E, > 0x036000-0x036fff:E, 0x037000-0x037fff:E, 0x038000-0x038fff:E, > 0x039000-0x039fff:E, 0x03a000-0x03afff:E, 0x03b000-0x03bfff:E, > 0x03c000-0x03cfff:E, 0x03d000-0x03dfff:E, 0x03e000-0x03efff:E, > 0x03f000-0x03ffff:E, 0x040000-0x040fff:E, 0x041000-0x041fff:E, > 0x042000-0x042fff:E, 0x043000-0x043fff:E, 0x044000-0x044fff:E, > 0x045000-0x045fff:E, 0x046000-0x046fff:E, 0x047000-0x047fff:E, > 0x048000-0x048fff:E, 0x049000-0x049fff:E, 0x04a000-0x04afff:E, > 0x04b000-0x04bfff:E, 0x04c000-0x04cfff:E, 0x04d000-0x04dfff:E, > 0x04e000-0x04efff:E, 0x04f000-0x04ffff:E, 0x050000-0x050fff:E, > 0x051000-0x051fff:E, 0x052000-0x052fff:E, 0x053000-0x053fff:E, > 0x054000-0x054fff:E, 0x055000-0x055fff:E, 0x056000-0x056fff:E, > 0x057000-0x057fff:E, 0x058000-0x058fff:E, 0x059000-0x059fff:E, > 0x05a000-0x05afff:E, 0x05b000-0x05bfff:E, 0x05c000-0x05cfff:E, > 0x05d000-0x05dfff:E, 0x05e000-0x05efff:E, 0x05f000-0x05ffff:E, > 0x060000-0x060fff:E, 0x061000-0x061fff:E, 0x062000-0x062fff:E, > 0x063000-0x063fff:E, 0x064000-0x064fff:E, 0x065000-0x065fff:E, > 0x066000-0x066fff:E, 0x067000-0x067fff:E, 0x068000-0x068fff:E, > 0x069000-0x069fff:E, 0x06a000-0x06afff:E, 0x06b000-0x06bfff:E, > 0x06c000-0x06cfff:E, 0x06d000-0x06dfff:E, 0x06e000-0x06efff:E, > 0x06f000-0x06ffff:E, 0x070000-0x070fff:E, 0x071000-0x071fff:E, > 0x072000-0x072fff:E, 0x073000-0x073fff:E, 0x074000-0x074fff:E, > 0x075000-0x075fff:E, 0x076000-0x076fff:E, 0x077000-0x077fff:E, > 0x078000-0x078fff:E, 0x079000-0x079fff:E, 0x07a000-0x07afff:E, > 0x07b000-0x07bfff:E, 0x07c000-0x07cfff:E, 0x07d000-0x07dfff:E, > 0x07e000-0x07efff:E, 0x07f000-0x07ffff:E, 0x080000-0x080fff:E, > 0x081000-0x081fff:E, 0x082000-0x082fff:E, 0x083000-0x083fff:E, > 0x084000-0x084fff:E, 0x085000-0x085fff:E, 0x086000-0x086fff:E, > 0x087000-0x087fff:E, 0x088000-0x088fff:E, 0x089000-0x089fff:E, > 0x08a000-0x08afff:E, 0x08b000-0x08bfff:E, 0x08c000-0x08cfff:E, > 0x08d000-0x08dfff:E, 0x08e000-0x08efff:E, 0x08f000-0x08ffff:E, > 0x090000-0x090fff:E, 0x091000-0x091fff:E, 0x092000-0x092fff:E, > 0x093000-0x093fff:E, 0x094000-0x094fff:E, 0x095000-0x095fff:E, > 0x096000-0x096fff:E, 0x097000-0x097fff:E, 0x098000-0x098fff:E, > 0x099000-0x099fff:E, 0x09a000-0x09afff:E, 0x09b000-0x09bfff:E, > 0x09c000-0x09cfff:E, 0x09d000-0x09dfff:E, 0x09e000-0x09efff:E, > 0x09f000-0x09ffff:E, 0x0a0000-0x0a0fff:E, 0x0a1000-0x0a1fff:E, > 0x0a2000-0x0a2fff:E, 0x0a3000-0x0a3fff:E, 0x0a4000-0x0a4fff:E, > 0x0a5000-0x0a5fff:E, 0x0a6000-0x0a6fff:E, 0x0a7000-0x0a7fff:E, > 0x0a8000-0x0a8fff:E, 0x0a9000-0x0a9fff:E, 0x0aa000-0x0aafff:E, > 0x0ab000-0x0abfff:E, 0x0ac000-0x0acfff:E, 0x0ad000-0x0adfff:E, > 0x0ae000-0x0aefff:E, 0x0af000-0x0affff:E, 0x0b0000-0x0b0fff:E, > 0x0b1000-0x0b1fff:E, 0x0b2000-0x0b2fff:E, 0x0b3000-0x0b3fff:E, > 0x0b4000-0x0b4fff:E, 0x0b5000-0x0b5fff:E, 0x0b6000-0x0b6fff:E, > 0x0b7000-0x0b7fff:E, 0x0b8000-0x0b8fff:E, 0x0b9000-0x0b9fff:E, > 0x0ba000-0x0bafff:E, 0x0bb000-0x0bbfff:E, 0x0bc000-0x0bcfff:E, > 0x0bd000-0x0bdfff:E, 0x0be000-0x0befff:E, 0x0bf000-0x0bffff:E, > 0x0c0000-0x0c0fff:E, 0x0c1000-0x0c1fff:E, 0x0c2000-0x0c2fff:E, > 0x0c3000-0x0c3fff:E, 0x0c4000-0x0c4fff:E, 0x0c5000-0x0c5fff:E, > 0x0c6000-0x0c6fff:E, 0x0c7000-0x0c7fff:E, 0x0c8000-0x0c8fff:E, > 0x0c9000-0x0c9fff:E, 0x0ca000-0x0cafff:E, 0x0cb000-0x0cbfff:E, > 0x0cc000-0x0ccfff:E, 0x0cd000-0x0cdfff:E, 0x0ce000-0x0cefff:E, > 0x0cf000-0x0cffff:E, 0x0d0000-0x0d0fff:E, 0x0d1000-0x0d1fff:E, > 0x0d2000-0x0d2fff:E, 0x0d3000-0x0d3fff:E, 0x0d4000-0x0d4fff:E, > 0x0d5000-0x0d5fff:E, 0x0d6000-0x0d6fff:E, 0x0d7000-0x0d7fff:E, > 0x0d8000-0x0d8fff:E, 0x0d9000-0x0d9fff:E, 0x0da000-0x0dafff:E, > 0x0db000-0x0dbfff:E, 0x0dc000-0x0dcfff:E, 0x0dd000-0x0ddfff:E, > 0x0de000-0x0defff:E, 0x0df000-0x0dffff:E, 0x0e0000-0x0e0fff:E, > 0x0e1000-0x0e1fff:E, 0x0e2000-0x0e2fff:E, 0x0e3000-0x0e3fff:E, > 0x0e4000-0x0e4fff:E, 0x0e5000-0x0e5fff:E, 0x0e6000-0x0e6fff:E, > 0x0e7000-0x0e7fff:E, 0x0e8000-0x0e8fff:E, 0x0e9000-0x0e9fff:E, > 0x0ea000-0x0eafff:E, 0x0eb000-0x0ebfff:E, 0x0ec000-0x0ecfff:E, > 0x0ed000-0x0edfff:E, 0x0ee000-0x0eefff:E, 0x0ef000-0x0effff:E, > 0x0f0000-0x0f0fff:E, 0x0f1000-0x0f1fff:E, 0x0f2000-0x0f2fff:E, > 0x0f3000-0x0f3fff:E, 0x0f4000-0x0f4fff:E, 0x0f5000-0x0f5fff:E, > 0x0f6000-0x0f6fff:E, 0x0f7000-0x0f7fff:E, 0x0f8000-0x0f8fff:E, > 0x0f9000-0x0f9fff:E, 0x0fa000-0x0fafff:E, 0x0fb000-0x0fbfff:E, > 0x0fc000-0x0fcfff:E, 0x0fd000-0x0fdfff:E, 0x0fe000-0x0fefff:E, > 0x0ff000-0x0fffff:E, 0x100000-0x100fff:EFAILED at 0x00100000! > Expected=0xff, Found=0xeb, failed byte count from 0x00100000-0x00100fff: > 0xfe5 > ERASE FAILED! > Reading current flash chip contents... > > Again same address "0x00100000". > What can i do or what should i test? Any idea? Maybe more "V" for verbose? > Now i try to write random data, but i guess it does also not work. But i > give it a try. > > Greetings > > Am 02.03.2015 um 23:51 schrieb Urja Rannikko: >> Hi, >> >> I'm also addressing the mailing list now, because i think the last bit >> is interesting to more people. >> >> On Mon, Mar 2, 2015 at 11:48 PM, The Raven <originalraven(a)hotmail.com> wrote: >>> Hi again >>>> I'd like to know how the "U2" firmware fails, and this flashrom might >>>> be better at breaking it and telling what happened: >>>> This is how to use that my flashrom branch: >>>> git clone git://github.com/urjaman/flashrom flashrom-serprog >>>> cd flashrom-serprog >>>> git checkout serprog-improvements >>>> make >>>> ./flashrom .... <same parameters here as you used before ...> >>>> >>>> And report me what happened... then, there's a second thing i just made. >>> Does not compile! >>> I got this: >>> serprog.c: In function ‘serprog_map’: >>> serprog.c:1128:3: error: format ‘%d’ expects argument of type ‘int’, but >>> argument 5 has type ‘size_t’ [-Werror=format=] >>> msg_pwarn(MSGHEADER "incompatible mapping '%s' phys_addr 0x%08X len >>> %d, returning NULL\n", >>> ^ >>> cc1: all warnings being treated as errors >>> make: *** [serprog.o] Fehler 1 >>> >>> Can you tell me whats wrong? Tomorrow i try it again. >> Sorry, my compiler was too old and it didnt produce this warning thus >> i didnt notice it. >> I think fixed it in my branch, so you can >> git pull >> make >> to try again with the fix. >> If there are other warnings that get in the way, you can >> disable -Werror with >> make WARNERROR=no >> >> and send me all the warnings it produced so i can fix them all. >> Thanks a lot for reporting this :) >> >>>> I got a bit carried away reading the serprog-duino firmware code >>>> and decided to just see what it'd look like with my frser-* codebase. >>>> So, fresh out of the oven, and untested (i tested on my m644p before i >>>> converted it for the m328p): >>>> https://github.com/urjaman/frser-duino >>>> To use it: >>>> git clone git://github.com/urjaman/frser-duino >>>> cd frser-duino >>>> make && make program >>>> >>>> (the defaults are for the u2 arduino, eg. ttyACM0 and 115200, i didnt >>>> have time to work the makefile magic that hard.) >>>> >>>> With luck it might work, but I'm expecting failure. Report where it failed. >>>> If its something simple you can fix it too if you want to, just commit >>>> it and send me the git format-patch -1 :) >>>> If it compiled and programmed, then try the flashrom-serprog again >>>> And if that works try the stock flashrom too. >>> Have tried this with the "normal" flashrom and it seems to work with the >>> "M25P10-A"!!! >>> >>> Look the "short" log: >>> Found Micron/Numonyx/ST flash chip "M25P10-A" (128 kB, SPI). >>> === >>> This flash part has status UNTESTED for operations: 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! >>> Erasing and writing flash chip... Trying erase function 0... >>> 0x000000-0x007fff:E, 0x008000-0x00ffff:E, 0x010000-0x017fff:E, >>> 0x018000-0x01ffff:E >>> Erase/write done. >>> serprog: Output drivers disabled >>> >>> Done! This was never possible with the "other" serprog code! >>> >>> And writing of random data: >>> Found Micron/Numonyx/ST flash chip "M25P10-A" (128 kB, SPI). >>> === >>> This flash part has status UNTESTED for operations: WRITE >>> The test status of this chip may have been updated in the latest development >>> version of flashrom. If you are running the latest development version, >>> please email a report to flashrom(a)flashrom.org if any of the above >>> operations >>> work correctly for you with this flash chip. Please include the flashrom log >>> file for all operations you tested (see the man page for details), and >>> mention >>> which mainboard or programmer you tested in the subject line. >>> Thanks for your help! >>> Reading old flash chip contents... done. >>> Erasing and writing flash chip... Trying erase function 0... >>> 0x000000-0x007fff:W, 0x008000-0x00ffff:W, 0x010000-0x017fff:W, >>> 0x018000-0x01ffff:W >>> Erase/write done. >>> Verifying flash... VERIFIED. >>> serprog: Output drivers disabled >>> >>> Also done! I think this looks really good! :-) >>> Tomorrow i try the MX25L6445E, let's see what happens! >>> >>> THX for your help and making things better! :-) >>> >> I sent this to the mailing list too because that seems like a report >> for M25P10-A write tested ok :) >> >> > -- Urja Rannikko

1 0

Re: [flashrom] PLCC chip flashing via Raspberry GPIO
by Stefan Tauner 03 Mar '15

03 Mar '15

On Tue, 3 Mar 2015 03:07:09 +0700 Darmawan Salihun <darmawan.salihun(a)gmail.com> wrote: > Is it now possible to flash PLCC chip with Raspberry Pi? > > AFAIK, SPI chips are already supported but I have a PLCC flash chip > right now to work with (Winbond W39V040FC). PLCC (the physical package) support different protocols, cf. http://flashrom.org/Technology#Communication_bus_protocol The W39V040FC is a FWH chip and thus could in theory be accessed with a RaspberryPi - it has enough GPIO ports. I am not sure if they can be toggled fast enough, but I'd guess so. The problem is rather to write the respective software/driver - AFAIK there is none yet. It would definitely be easier to get a similar board and try hotswapping the flash chip. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Trouble disabling write-protection on Chromebook
by JC C 03 Mar '15

03 Mar '15

Skickat från min iPhone

1 0

Re: [flashrom] MX25L6445E erase and write failed!
by Urja Rannikko 02 Mar '15

02 Mar '15

Hi, I'm also addressing the mailing list now, because i think the last bit is interesting to more people. On Mon, Mar 2, 2015 at 11:48 PM, The Raven <originalraven(a)hotmail.com> wrote: > Hi again >> I'd like to know how the "U2" firmware fails, and this flashrom might >> be better at breaking it and telling what happened: >> This is how to use that my flashrom branch: >> git clone git://github.com/urjaman/flashrom flashrom-serprog >> cd flashrom-serprog >> git checkout serprog-improvements >> make >> ./flashrom .... <same parameters here as you used before ...> >> >> And report me what happened... then, there's a second thing i just made. > Does not compile! > I got this: > serprog.c: In function ‘serprog_map’: > serprog.c:1128:3: error: format ‘%d’ expects argument of type ‘int’, but > argument 5 has type ‘size_t’ [-Werror=format=] > msg_pwarn(MSGHEADER "incompatible mapping '%s' phys_addr 0x%08X len > %d, returning NULL\n", > ^ > cc1: all warnings being treated as errors > make: *** [serprog.o] Fehler 1 > > Can you tell me whats wrong? Tomorrow i try it again. Sorry, my compiler was too old and it didnt produce this warning thus i didnt notice it. I think fixed it in my branch, so you can git pull make to try again with the fix. If there are other warnings that get in the way, you can disable -Werror with make WARNERROR=no and send me all the warnings it produced so i can fix them all. Thanks a lot for reporting this :) > >> I got a bit carried away reading the serprog-duino firmware code >> and decided to just see what it'd look like with my frser-* codebase. >> So, fresh out of the oven, and untested (i tested on my m644p before i >> converted it for the m328p): >> https://github.com/urjaman/frser-duino >> To use it: >> git clone git://github.com/urjaman/frser-duino >> cd frser-duino >> make && make program >> >> (the defaults are for the u2 arduino, eg. ttyACM0 and 115200, i didnt >> have time to work the makefile magic that hard.) >> >> With luck it might work, but I'm expecting failure. Report where it failed. >> If its something simple you can fix it too if you want to, just commit >> it and send me the git format-patch -1 :) >> If it compiled and programmed, then try the flashrom-serprog again >> And if that works try the stock flashrom too. > Have tried this with the "normal" flashrom and it seems to work with the > "M25P10-A"!!! > > Look the "short" log: > Found Micron/Numonyx/ST flash chip "M25P10-A" (128 kB, SPI). > === > This flash part has status UNTESTED for operations: 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! > Erasing and writing flash chip... Trying erase function 0... > 0x000000-0x007fff:E, 0x008000-0x00ffff:E, 0x010000-0x017fff:E, > 0x018000-0x01ffff:E > Erase/write done. > serprog: Output drivers disabled > > Done! This was never possible with the "other" serprog code! > > And writing of random data: > Found Micron/Numonyx/ST flash chip "M25P10-A" (128 kB, SPI). > === > This flash part has status UNTESTED for operations: WRITE > The test status of this chip may have been updated in the latest development > version of flashrom. If you are running the latest development version, > please email a report to flashrom(a)flashrom.org if any of the above > operations > work correctly for you with this flash chip. Please include the flashrom log > file for all operations you tested (see the man page for details), and > mention > which mainboard or programmer you tested in the subject line. > Thanks for your help! > Reading old flash chip contents... done. > Erasing and writing flash chip... Trying erase function 0... > 0x000000-0x007fff:W, 0x008000-0x00ffff:W, 0x010000-0x017fff:W, > 0x018000-0x01ffff:W > Erase/write done. > Verifying flash... VERIFIED. > serprog: Output drivers disabled > > Also done! I think this looks really good! :-) > Tomorrow i try the MX25L6445E, let's see what happens! > > THX for your help and making things better! :-) > I sent this to the mailing list too because that seems like a report for M25P10-A write tested ok :) -- Urja Rannikko

1 0

PLCC chip flashing via Raspberry GPIO
by Darmawan Salihun 02 Mar '15

02 Mar '15

Is it now possible to flash PLCC chip with Raspberry Pi? AFAIK, SPI chips are already supported but I have a PLCC flash chip right now to work with (Winbond W39V040FC). Kind Regards, Darmawan -------------------------------------------------------------------- -= Знания людей принадлежат миру =- [-Human knowledge belongs to the world-]

1 0

Re: [flashrom] [coreboot] New flashrom logo - please vote!
by Vadim Bendebury 02 Mar '15

02 Mar '15

On Mon, Mar 2, 2015 at 11:14 AM, Corey Osgood <corey.osgood(a)gmail.com> wrote: > On Mon, Mar 2, 2015 at 12:03 PM, Vadim Bendebury <vbendeb(a)chromium.org> wrote: >> Not that I care much, but I can't help it: this new symbol looks very >> much like the infamous SS Bolts: >> http://www.adl.org/combating-hate/hate-on-display/c/ss-bolts.html#.VPSXeFX3… > > I can see where you're coming from, but IMO it's a bit of a stretch. > > -Corey I am sure there will be more people who would make this mental connection. But as I said, just my 2c, up to you guys. -vb

1 0

Re: [flashrom] [coreboot] New flashrom logo - please vote!
by Corey Osgood 02 Mar '15

02 Mar '15

On Mon, Mar 2, 2015 at 12:03 PM, Vadim Bendebury <vbendeb(a)chromium.org> wrote: > Not that I care much, but I can't help it: this new symbol looks very > much like the infamous SS Bolts: > http://www.adl.org/combating-hate/hate-on-display/c/ss-bolts.html#.VPSXeFX3… I can see where you're coming from, but IMO it's a bit of a stretch. -Corey

1 0

Re: [flashrom] [PATCH RFC] Access PCI BARs through sysfs
by Stefan Tauner 02 Mar '15

02 Mar '15

On Thu, 26 Feb 2015 13:53:13 -0800 Ed Swierk <eswierk(a)skyportsystems.com> wrote: > On Thu, Feb 26, 2015 at 4:10 AM, Patrick Georgi <pgeorgi(a)google.com> wrote: > > 2015-02-26 1:57 GMT+01:00 Ed Swierk <eswierk(a)skyportsystems.com>: > >> Running flashrom on a Linux system with CONFIG_STRICT_DEVMEM=y, I can now > >> successfully program the SPI flash on an Intel 10G NIC using the > > > >> +#if !defined(__DJGPP__) && !defined(__LIBPAYLOAD__) > >> +static void *pcidev_mapbar_sysfs(struct pci_dev *dev, const char *descr, int bar, off_t offset, size_t length) > > Isn't that actually Linux specific, instead of non-djgpp-or-libpayload specific? > > I suppose that's a safe assumption, though I don't know much about any > of the other platforms flashrom supports. libpci already figures out > whether the platform supports sysfs. I piggyback off that logic by > checking pacc->method. > > Here we're just deciding whether the platform uses mmap() to access > physical address space. I followed the same approach used in > physmap.c, since pcidev_mapbar_sysfs() is doing the same thing as > sys_physmap_rw_uncached(), just with a PCI resource file instead of > /dev/mem. > > But I can switch to #if IS_LINUX if you think that's clearer. We can > revisit that if and when some other sprouts a similar mmapped sysfs > interface to PCI resources. I have not really looked into the patch... but I did a little compile test on top of r1885. I'll just let the buildbot speak for itself: http://buildbot.flashrom.org/buildresults/flashrom-000164-Zcc/results.txt sparc7 is expected to fail with r1885. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

[PATCH] Acquire I/O privileges only if needed for mmap access to PCI resources
by Ed Swierk 02 Mar '15

02 Mar '15

On Linux, /dev/mem can be used to access PCI device resources without first calling iopl() to obtain I/O privileges. Skipping the iopl() call allows several flashrom programmers to work on a grsecurity kernel with GRKERNSEC_IO=y, which blocks calls to iopl() while permitting selective /dev/mem access. With this patch, pcidev_init() calls rget_io_perms() automatically on non-Linux systems. rget_io_perms() is no longer called explicitly by programmers that use only mmapped access to PCI resources. I have tested this patch on a Debian sid system, Linux 3.14.30 kernel with grsecurity (GRKERNSEC_KMEM=y, GRKERNSEC_IO=y, STRICT_DEVMEM=y), successfully programming the SPI flash on an Intel 10G NIC using the nicintel_spi programmer. I have not tested any other programmers or system configurations. Signed-off-by: Ed Swierk <eswierk(a)skyportsystems.com> --- atavia.c | 3 --- drkaiser.c | 3 --- gfxnvidia.c | 3 --- it8212.c | 3 --- nicintel.c | 6 ------ nicintel_eeprom.c | 3 --- nicintel_spi.c | 3 --- ogp_spi.c | 3 --- pcidev.c | 6 ++++++ satasii.c | 3 --- 10 files changed, 6 insertions(+), 30 deletions(-) diff --git a/atavia.c b/atavia.c index db29eea..1bcdda5 100644 --- a/atavia.c +++ b/atavia.c @@ -143,9 +143,6 @@ int atavia_init(void) } free(arg); - if (rget_io_perms()) - return 1; - dev = pcidev_init(ata_via, PCI_ROM_ADDRESS); /* Acutally no BAR setup needed at all. */ if (!dev) return 1; diff --git a/drkaiser.c b/drkaiser.c index 75cc085..7ccdd07 100644 --- a/drkaiser.c +++ b/drkaiser.c @@ -61,9 +61,6 @@ int drkaiser_init(void) struct pci_dev *dev = NULL; uint32_t addr; - if (rget_io_perms()) - return 1; - dev = pcidev_init(drkaiser_pcidev, PCI_BASE_ADDRESS_2); if (!dev) return 1; diff --git a/gfxnvidia.c b/gfxnvidia.c index 1e5a23a..d1635b0 100644 --- a/gfxnvidia.c +++ b/gfxnvidia.c @@ -82,9 +82,6 @@ int gfxnvidia_init(void) struct pci_dev *dev = NULL; uint32_t reg32; - if (rget_io_perms()) - return 1; - dev = pcidev_init(gfx_nvidia, PCI_BASE_ADDRESS_0); if (!dev) return 1; diff --git a/it8212.c b/it8212.c index 460e820..417ffc7 100644 --- a/it8212.c +++ b/it8212.c @@ -51,9 +51,6 @@ static const struct par_master par_master_it8212 = { int it8212_init(void) { - if (rget_io_perms()) - return 1; - struct pci_dev *dev = pcidev_init(devs_it8212, PCI_ROM_ADDRESS); if (!dev) return 1; diff --git a/nicintel.c b/nicintel.c index 69b40d3..ad8a0b2 100644 --- a/nicintel.c +++ b/nicintel.c @@ -64,12 +64,6 @@ int nicintel_init(void) struct pci_dev *dev = NULL; uintptr_t addr; - /* Needed only for PCI accesses on some platforms. - * FIXME: Refactor that into get_mem_perms/rget_io_perms/get_pci_perms? - */ - if (rget_io_perms()) - return 1; - /* FIXME: BAR2 is not available if the device uses the CardBus function. */ dev = pcidev_init(nics_intel, PCI_BASE_ADDRESS_2); if (!dev) diff --git a/nicintel_eeprom.c b/nicintel_eeprom.c index b5d4202..3aba21d 100644 --- a/nicintel_eeprom.c +++ b/nicintel_eeprom.c @@ -295,9 +295,6 @@ static int nicintel_ee_shutdown(void *eecp) int nicintel_ee_init(void) { - if (rget_io_perms()) - return 1; - struct pci_dev *dev = pcidev_init(nics_intel_ee, PCI_BASE_ADDRESS_0); if (!dev) return 1; diff --git a/nicintel_spi.c b/nicintel_spi.c index 9195c79..fa93d08 100644 --- a/nicintel_spi.c +++ b/nicintel_spi.c @@ -187,9 +187,6 @@ int nicintel_spi_init(void) struct pci_dev *dev = NULL; uint32_t tmp; - if (rget_io_perms()) - return 1; - dev = pcidev_init(nics_intel_spi, PCI_BASE_ADDRESS_0); if (!dev) return 1; diff --git a/ogp_spi.c b/ogp_spi.c index 929ecd9..73993c1 100644 --- a/ogp_spi.c +++ b/ogp_spi.c @@ -125,9 +125,6 @@ int ogp_spi_init(void) } free(type); - if (rget_io_perms()) - return 1; - dev = pcidev_init(ogp_spi, PCI_BASE_ADDRESS_0); if (!dev) return 1; diff --git a/pcidev.c b/pcidev.c index 2c78063..6655987 100644 --- a/pcidev.c +++ b/pcidev.c @@ -165,6 +165,12 @@ static int pcidev_shutdown(void *data) int pci_init_common(void) { +#if IS_LINUX + /* On Linux, I/O privileges are not needed for mmap access to PCI resources in /dev/mem. */ +#else + if (rget_io_perms()) + return 1; +#endif if (pacc != NULL) { msg_perr("%s: Tried to allocate a new PCI context, but there is still an old one!\n" "Please report a bug at flashrom(a)flashrom.org\n", __func__); diff --git a/satasii.c b/satasii.c index 368d7d4..63eb788 100644 --- a/satasii.c +++ b/satasii.c @@ -74,9 +74,6 @@ int satasii_init(void) uint32_t addr; uint16_t reg_offset; - if (rget_io_perms()) - return 1; - dev = pcidev_init(satas_sii, PCI_BASE_ADDRESS_0); if (!dev) return 1; -- 1.9.1

1 0

[PATCH] Chip definition for W29C512A/W29EE512
by Urja Rannikko 02 Mar '15

02 Mar '15

Mine was a Winbond W29EE512P-70 (PLCC32, 5V) found in an RTL8169 network card. I was about to backup the chip when i found out flashrom didnt know of it. The ID for the chip was already in flashchips.h with the name W29C512A and a note for "also W29EE512". I'm assuming they're compatible. Attached are patch for the flashchips.c entry and a write log for 64k random data (proving it is PREW by me as in the patch). I also successfully wrote the original data back into the chip. -- Urja Rannikko

1 0

ANNOUNCE: Release of flashrom 0.9.8
by Stefan Tauner 01 Mar '15

01 Mar '15

Hello, I am happy to announce the release of flashrom version 0.9.8 (r1888). flashrom is a utility for reading, writing, erasing and verifying flash chips. Please see the detailed release notes at http://flashrom.org/Flashrom/0.9.8 for more information. Thanks to everybody for their contributions to this release! We are also working on a new logo for flashrom and would like to hear your opinion on the current proposals. Please rate them at http://epicdecide.com/bac504d1-0061-46c4-ac7c-9beecaba87e0/ thanks! -- Kind regards, Stefan Tauner

1 0

[commit] r1888 - tags/0.9.8
by repository service 01 Mar '15

01 Mar '15

Author: stefanct Date: Sun Mar 1 23:12:16 2015 New Revision: 1888 URL: http://flashrom.org/trac/flashrom/changeset/1888 Log: Tag flashrom 0.9.8. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Added: tags/0.9.8/ - copied from r1887, trunk/

1 0

[commit] r1887 - trunk
by repository service 01 Mar '15

01 Mar '15

Author: stefanct Date: Sun Mar 1 23:05:16 2015 New Revision: 1887 URL: http://flashrom.org/trac/flashrom/changeset/1887 Log: Increase flashrom version number to 0.9.8. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/Makefile Modified: trunk/Makefile ============================================================================== --- trunk/Makefile Sun Mar 1 23:04:38 2015 (r1886) +++ trunk/Makefile Sun Mar 1 23:05:16 2015 (r1887) @@ -386,7 +386,7 @@ # will not require subversion. The downloadable snapshots are already exported. SVNVERSION := $(shell ./util/getrevision.sh -u 2>/dev/null ) -RELEASE := 0.9.8-rc1 +RELEASE := 0.9.8 VERSION := $(RELEASE)-$(SVNVERSION) RELEASENAME ?= $(VERSION)

1 0

[commit] r1886 - trunk
by repository service 01 Mar '15

01 Mar '15

Author: stefanct Date: Sun Mar 1 23:04:38 2015 New Revision: 1886 URL: http://flashrom.org/trac/flashrom/changeset/1886 Log: Add a bunch of new/tested stuff and various small changes 23. Tested mainboards: OK: - Elitegroup GF7050VT-M Reported by Alex - Fujitsu D2724-A1x (used in ESPRIMO E5625) Reported by Rainer Spillmann - Teclast X98 Air 3G Reported by Antonio Ospite Flash chips: - Fix MX25L6405(D) definition by splitting it. Reported by Reggie McMurtrey - Add Macronix MX25L..08E family and rearrange MX25L6436E. - Pm49FL004 to PREW (+EW) Reported by Georg Sauthoff Miscellaneous: - Add board enable for abit KN9 Ultra. - Mark ARM-USB-OCD as working OK. - Use "mobile devices" instead of "laptops" in output. - Tiny other stuff. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/Makefile trunk/board_enable.c trunk/flashchips.c trunk/flashchips.h trunk/ft2232_spi.c trunk/print.c trunk/print_wiki.c Modified: trunk/Makefile ============================================================================== --- trunk/Makefile Thu Feb 19 00:28:30 2015 (r1885) +++ trunk/Makefile Sun Mar 1 23:04:38 2015 (r1886) @@ -1081,6 +1081,6 @@ libpayload: clean make CC="CC=i386-elf-gcc lpgcc" AR=i386-elf-ar RANLIB=i386-elf-ranlib -.PHONY: all install clean distclean compiler hwlibs features export tarball dos featuresavailable +.PHONY: all install clean distclean compiler hwlibs features export tarball djgpp-dos featuresavailable libpayload -include $(OBJS:.o=.d) Modified: trunk/board_enable.c ============================================================================== --- trunk/board_enable.c Thu Feb 19 00:28:30 2015 (r1885) +++ trunk/board_enable.c Sun Mar 1 23:04:38 2015 (r1886) @@ -1099,6 +1099,7 @@ /* * Suited for: * - abit KN8 Ultra: NVIDIA CK804 + * - abit KN9 Ultra: NVIDIA MCP55 */ static int nvidia_mcp_gpio2_lower(void) { @@ -2314,6 +2315,7 @@ {0x8086, 0x2930, 0x147b, 0x1084, 0x11ab, 0x4364, 0x147b, 0x1084, NULL, NULL, NULL, P3, "abit", "IP35", 0, OK, intel_ich_gpio16_raise}, {0x8086, 0x2930, 0x147b, 0x1083, 0x10ec, 0x8167, 0x147b, 0x1083, NULL, NULL, NULL, P3, "abit", "IP35 Pro", 0, OK, intel_ich_gpio16_raise}, {0x10de, 0x0050, 0x147b, 0x1c1a, 0x10de, 0x0052, 0x147b, 0x1c1a, NULL, NULL, NULL, P3, "abit", "KN8 Ultra", 0, NT, nvidia_mcp_gpio2_lower}, + {0x10de, 0x0369, 0x147b, 0x1c20, 0x10de, 0x0360, 0x147b, 0x1c20, "^KN9(NF-MCP55 series)$", NULL, NULL, P3, "abit", "KN9 Ultra", 0, OK, nvidia_mcp_gpio2_lower}, {0x10de, 0x01e0, 0x147b, 0x1c00, 0x10de, 0x0060, 0x147B, 0x1c00, NULL, NULL, NULL, P3, "abit", "NF7-S", 0, OK, nvidia_mcp_gpio8_raise}, {0x10de, 0x02f0, 0x147b, 0x1c26, 0x10de, 0x0260, 0x147b, 0x1c26, NULL, NULL, NULL, P3, "abit", "NF-M2 nView", 0, OK, nvidia_mcp_gpio4_lower}, {0x1106, 0x0691, 0, 0, 0x1106, 0x3057, 0, 0, "(VA6)$", NULL, NULL, P3, "abit", "VA6", 0, OK, via_apollo_gpo4_lower}, Modified: trunk/flashchips.c ============================================================================== --- trunk/flashchips.c Thu Feb 19 00:28:30 2015 (r1885) +++ trunk/flashchips.c Sun Mar 1 23:04:38 2015 (r1886) @@ -6803,12 +6803,14 @@ { .vendor = "Macronix", - .name = "MX25L8005/MX25L8006E/MX25V8005", + .name = "MX25L8005/MX25L8006E/MX25L8008E/MX25V8005", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = MACRONIX_MX25L8005, .total_size = 1024, .page_size = 256, + /* MX25L8006E, MX25L8008E support SFDP */ + /* OTP: 64B total; enter 0xB1, exit 0xC1 (MX25L8006E, MX25L8008E only) */ .feature_bits = FEATURE_WRSR_WREN, .tested = TEST_OK_PREW, .probe = probe_spi_rdid, @@ -6876,13 +6878,13 @@ { .vendor = "Macronix", - .name = "MX25L1605A/MX25L1606E", + .name = "MX25L1605A/MX25L1606E/MX25L1608E", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = MACRONIX_MX25L1605, .total_size = 2048, .page_size = 256, - /* OTP: 64B total; enter 0xB1, exit 0xC1 (MX25L1606E only) */ + /* OTP: 64B total; enter 0xB1, exit 0xC1 (MX25L1606E and MX25L1608E only) */ .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, .tested = TEST_OK_PREW, .probe = probe_spi_rdid, @@ -6909,7 +6911,7 @@ .printlock = spi_prettyprint_status_register_bp3_srwd, /* MX25L1605A bp2 only */ .unlock = spi_disable_blockprotect_bp3_srwd, .write = spi_chip_write_256, - .read = spi_chip_read, /* Fast read (0x0B) supported */ + .read = spi_chip_read, /* Fast read (0x0B) supported (MX25L1608E supports dual-I/O read) */ .voltage = {2700, 3600}, }, @@ -6941,7 +6943,7 @@ .block_erase = spi_block_erase_c7, }, }, - .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6: Continuously Program (CP) mode */ + .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6: Continuously Program (CP) mode, for 73E is quad enable */ .unlock = spi_disable_blockprotect_bp3_srwd, .write = spi_chip_write_256, .read = spi_chip_read, /* Fast read (0x0B), dual I/O supported */ @@ -7084,7 +7086,7 @@ .block_erase = spi_block_erase_c7, }, }, - .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6: CP mode */ + .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6: continuously program mode */ .unlock = spi_disable_blockprotect_bp3_srwd, .write = spi_chip_write_256, .read = spi_chip_read, /* Fast read (0x0B) and dual I/O supported */ @@ -7093,7 +7095,7 @@ { .vendor = "Macronix", - .name = "MX25L3206E", + .name = "MX25L3206E/MX25L3208E", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = MACRONIX_MX25L3205, @@ -7207,14 +7209,14 @@ { .vendor = "Macronix", - .name = "MX25L6405(D)", + .name = "MX25L6405", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = MACRONIX_MX25L6405, .total_size = 8192, .page_size = 256, - /* MX25L6405D has 64B of OTP; enter 0xB1, exit 0xC1 */ - .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + /* Has an additional 512B EEPROM sector */ + .feature_bits = FEATURE_WRSR_WREN, .tested = TEST_OK_PREW, .probe = probe_spi_rdid, .probe_timing = TIMING_ZERO, @@ -7234,22 +7236,22 @@ .block_erase = spi_block_erase_c7, } }, - .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6 has different meanings */ + .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6: error flag */ .unlock = spi_disable_blockprotect_bp3_srwd, .write = spi_chip_write_256, - .read = spi_chip_read, + .read = spi_chip_read, /* Fast read (0x0B) supported */ .voltage = {2700, 3600}, }, { .vendor = "Macronix", - .name = "MX25L6406E/MX25L6436E", + .name = "MX25L6405D", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = MACRONIX_MX25L6405, .total_size = 8192, .page_size = 256, - /* OTP: 06E 64B/36E 512B total; enter 0xB1, exit 0xC1 */ + /* OTP: 64B total; enter 0xB1, exit 0xC1 */ .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, .tested = TEST_OK_PREW, .probe = probe_spi_rdid, @@ -7270,16 +7272,56 @@ .block_erase = spi_block_erase_c7, } }, - .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6 for 36E is quad enable */ + .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6: continuously program mode */ .unlock = spi_disable_blockprotect_bp3_srwd, .write = spi_chip_write_256, - .read = spi_chip_read, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O read (0xBB) supported */ .voltage = {2700, 3600}, }, { .vendor = "Macronix", - .name = "MX25L6445E/MX25L6465E/MX25L6473E", + .name = "MX25L6406E/MX25L6408E", + .bustype = BUS_SPI, + .manufacture_id = MACRONIX_ID, + .model_id = MACRONIX_MX25L6405, + .total_size = 8192, + .page_size = 256, + /* MX25L6406E supports SFDP */ + /* OTP: 06E 64B total; enter 0xB1, exit 0xC1 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_OK_PREW, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 2048} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {64 * 1024, 128} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 128} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {8 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {8 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp3_srwd, + .unlock = spi_disable_blockprotect_bp3_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B), dual I/O read supported */ + .voltage = {2700, 3600}, + }, + + { + .vendor = "Macronix", + .name = "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, .model_id = MACRONIX_MX25L6405, @@ -10126,9 +10168,9 @@ .total_size = 512, .page_size = 64 * 1024, .feature_bits = FEATURE_REGISTERMAP | FEATURE_EITHER_RESET, - .tested = TEST_OK_PR, + .tested = TEST_OK_PREW, .probe = probe_jedec, - .probe_timing = TIMING_ZERO, /* routine is wrapper to probe_jedec (pm49fl00x.c) */ + .probe_timing = TIMING_ZERO, .block_erasers = { { Modified: trunk/flashchips.h ============================================================================== --- trunk/flashchips.h Thu Feb 19 00:28:30 2015 (r1885) +++ trunk/flashchips.h Sun Mar 1 23:04:38 2015 (r1886) @@ -470,10 +470,10 @@ #define MACRONIX_MX25L1005 0x2011 /* Same as MX25L1005C, MX25L1006E */ #define MACRONIX_MX25L2005 0x2012 /* Same as MX25L2005C, MX25L2006E */ #define MACRONIX_MX25L4005 0x2013 /* Same as MX25L4005A, MX25L4005C, MX25L4006E */ -#define MACRONIX_MX25L8005 0x2014 /* Same as MX25V8005, MX25L8006E, FIXME: MX25L8073E (4k 0x20) */ -#define MACRONIX_MX25L1605 0x2015 /* MX25L1605 (64k 0x20); MX25L1605A/MX25L1606E (4k 0x20, 64k 0x52); MX25L1605D/MX25L1608D/MX25L1673E (4k 0x20) */ -#define MACRONIX_MX25L3205 0x2016 /* MX25L3205, MX25L3205A (64k 0x20); MX25L3205D/MX25L3208D (4k 0x20); MX25L3206E (4k 0x20, 64k 0x52); MX25L3273E (4k 0x20, 32k 0x52) */ -#define MACRONIX_MX25L6405 0x2017 /* MX25L6405, MX25L6405D (64k 0x20); MX25L6406E/MX25L6436E (4k 0x20); MX25L6445E/MX25L6465E/MX25L6473E (4k 0x20, 32k 0x52) */ +#define MACRONIX_MX25L8005 0x2014 /* Same as MX25V8005, MX25L8006E, MX25L8008E, FIXME: MX25L8073E (4k 0x20) */ +#define MACRONIX_MX25L1605 0x2015 /* MX25L1605 (64k 0x20); MX25L1605A/MX25L1606E/MX25L1608E (4k 0x20, 64k 0x52); MX25L1605D/MX25L1608D/MX25L1673E (4k 0x20) */ +#define MACRONIX_MX25L3205 0x2016 /* MX25L3205, MX25L3205A (64k 0x20); MX25L3205D/MX25L3208D (4k 0x20); MX25L3206E/MX25L3208E (4k 0x20, 64k 0x52); MX25L3273E (4k 0x20, 32k 0x52) */ +#define MACRONIX_MX25L6405 0x2017 /* MX25L6405, MX25L6405D (64k 0x20); MX25L6406E/MX25L6408E (4k 0x20); MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E (4k 0x20, 32k 0x52) */ #define MACRONIX_MX25L12805D 0x2018 /* MX25L12805D (no 32k); MX25L12865E, MX25L12835F, MX25L12845E (32k 0x52) */ #define MACRONIX_MX25L25635F 0x2019 /* Same as MX25L25639F, but the latter seems to not support REMS */ #define MACRONIX_MX25L1635D 0x2415 Modified: trunk/ft2232_spi.c ============================================================================== --- trunk/ft2232_spi.c Thu Feb 19 00:28:30 2015 (r1885) +++ trunk/ft2232_spi.c Sun Mar 1 23:04:38 2015 (r1886) @@ -67,7 +67,7 @@ {FTDI_VID, AMONTEC_JTAGKEY_PID, OK, "Amontec", "JTAGkey"}, {GOEPEL_VID, GOEPEL_PICOTAP_PID, OK, "GOEPEL", "PicoTAP"}, {FIC_VID, OPENMOKO_DBGBOARD_PID, OK, "FIC", "OpenMoko Neo1973 Debug board (V2+)"}, - {OLIMEX_VID, OLIMEX_ARM_OCD_PID, NT, "Olimex", "ARM-USB-OCD"}, + {OLIMEX_VID, OLIMEX_ARM_OCD_PID, OK, "Olimex", "ARM-USB-OCD"}, {OLIMEX_VID, OLIMEX_ARM_TINY_PID, OK, "Olimex", "ARM-USB-TINY"}, {OLIMEX_VID, OLIMEX_ARM_OCD_H_PID, OK, "Olimex", "ARM-USB-OCD-H"}, {OLIMEX_VID, OLIMEX_ARM_TINY_H_PID, OK, "Olimex", "ARM-USB-TINY-H"}, Modified: trunk/print.c ============================================================================== --- trunk/print.c Thu Feb 19 00:28:30 2015 (r1885) +++ trunk/print.c Sun Mar 1 23:04:38 2015 (r1886) @@ -480,9 +480,9 @@ programmer_table[PROGRAMMER_INTERNAL].name); print_supported_chipsets(); msg_ginfo("\n"); - print_supported_boards_helper(boards_known, "boards"); + print_supported_boards_helper(boards_known, "mainboards"); msg_ginfo("\n"); - print_supported_boards_helper(laptops_known, "laptops"); + print_supported_boards_helper(laptops_known, "mobile devices"); #endif for (i = 0; i < PROGRAMMER_INVALID; i++) { const struct programmer_entry prog = programmer_table[i]; @@ -535,6 +535,7 @@ B("abit", "IP35 Pro", OK, NULL, NULL), B("abit", "IS-10", BAD, NULL, "Reported by deejkuba(a)aol.com to flashrom(a)coreboot.org, no public archive. Missing board enable and/or M50FW040 unlocking. May work now."), B("abit", "KN8 Ultra", OK, NULL, NULL), + B("abit", "KN9 Ultra", OK, NULL, NULL), B("abit", "NF-M2 nView", OK, NULL, NULL), B("abit", "NF-M2S", OK, NULL, NULL), B("abit", "NF7-S", OK, NULL, NULL), @@ -774,6 +775,7 @@ B("Elitegroup", "GeForce6100PM-M2 (V3.0)", OK, NULL, NULL), B("Elitegroup", "GeForce6100SM-M", OK, NULL, NULL), B("Elitegroup", "GeForce7050M-M (V2.0)", OK, "http://www.ecs.com.tw/ECSWebSite/Product/Product_Detail.aspx?DetailID=865&M…", NULL), + B("Elitegroup", "GF7050VT-M", OK, NULL, NULL), B("Elitegroup", "GF7100PVT-M3 (V1.0)", OK, NULL, NULL), B("Elitegroup", "GF8200A", OK, NULL, NULL), B("Elitegroup", "K7S5A", OK, NULL, NULL), @@ -803,7 +805,8 @@ B("Foxconn", "P55MX", OK, "http://www.foxconnchannel.com/ProductDetail.aspx?T=motherboard&U=en-us00004…", "Needs the MFG jumper to be set correctly before flashing to enable the Flash Descriptor Override Strap."), B("Foxconn", "Q45M", BAD, "http://www.foxconnchannel.com/ProductDetail.aspx?T=Motherboard&U=en-us00005…", "Probing works (Hardware sequencing, 4096 kB, SPI), but parts of the flash are problematic: descriptor is r/o (conforming to ICH reqs), ME is locked."), B("Freetech", "P6F91i", OK, "http://web.archive.org/web/20010417035034/http://www.freetech.com/prod/P6F9…", NULL), - B("Fujitsu", "D3041-A1", OK, NULL, "Used in ESPRIMO P2560, contains an Atmel AT26DF081A."), + B("Fujitsu", "D2724-A1x", OK, NULL, "Used in ESPRIMO E5625."), + B("Fujitsu", "D3041-A1x", OK, NULL, "Used in ESPRIMO P2560, contains an Atmel AT26DF081A."), B("Fujitsu-Siemens", "CELSIUS W410", BAD, "ftp://ftp.ts.fujitsu.com/pub/mainboard-oem-sales/Products/Mainboards/Indust…", "Mainboard model is D3062-A1. Probing works (Macronix MX25L6405, 8192 kB, SPI), but parts of the flash are problematic: descriptor is r/o (conforming to ICH reqs), ME is locked."), B("Fujitsu-Siemens", "ESPRIMO P5915", OK, "http://uk.ts.fujitsu.com/rl/servicesupport/techsupport/professionalpc/ESPRI…", "Mainboard model is D2312-A2."), B("GIGABYTE", "GA-2761GXDK", OK, "http://www.computerbase.de/news/hardware/mainboards/amd-systeme/2007/mai/gi…", NULL), @@ -1144,6 +1147,7 @@ B("IBM/Lenovo", "ThinkPad 240", BAD, "http://www.stanford.edu/~bresnan//tp240.html", "Seems to (partially) work at first, but one block/sector cannot be written which then leaves you with a bricked laptop. Maybe this can be investigated and fixed in software later."), B("IBM/Lenovo", "3000 V100 TF05Cxx", OK, "http://www5.pc.ibm.com/europe/products.nsf/products?openagent&brand=Lenovo3…", NULL), //B("MSI", "GT60-2OD", OK, "http://www.msi.com/product/nb/GT60_2OD.html", NULL), requires layout patches + B("Teclast", "X98 Air 3G", OK, NULL, NULL), #endif {0}, Modified: trunk/print_wiki.c ============================================================================== --- trunk/print_wiki.c Thu Feb 19 00:28:30 2015 (r1885) +++ trunk/print_wiki.c Sun Mar 1 23:04:38 2015 (r1886) @@ -133,15 +133,15 @@ } #if CONFIG_INTERNAL == 1 -static const char laptop_intro[] = "\n== Supported laptops/notebooks ==\n\n\ -In general, flashing laptops is more difficult because laptops\n\n\ +static const char laptop_intro[] = "\n== Supported mobile devices (laptops, tablets etc.) ==\n\n\ +In general, flashing mobile devices is more difficult because they\n\n\ * often use the flash chip for stuff besides the BIOS,\n\ * often have special protection stuff which has to be handled by flashrom,\n\ * often use flash translation circuits which need drivers in flashrom.\n\n\ <div style=\"margin-top:0.5em; padding:0.5em 0.5em 0.5em 0.5em; \ background-color:#ff6666; align:right; border:1px solid #000000;\">\n\ '''IMPORTANT:''' At this point we recommend to '''not''' use flashrom on \ -untested laptops unless you have a means to recover from a flashing that goes \ +untested mobile devices unless you have a means to recover from a flashing that goes \ wrong (a working backup flash chip and/or good soldering skills).\n</div>\n"; static void print_supported_chipsets_wiki(int cols) @@ -275,10 +275,10 @@ static void print_supported_boards_wiki(void) { printf("%s", board_intro); - print_supported_boards_wiki_helper("boards", 2, boards_known); + print_supported_boards_wiki_helper("mainboards", 2, boards_known); printf("%s", laptop_intro); - print_supported_boards_wiki_helper("laptops", 1, laptops_known); + print_supported_boards_wiki_helper("mobile devices", 1, laptops_known); } #endif

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom