flashrom

flashrom@flashrom.org

5 participants
9161 discussions

[commit] r1889 - trunk
by repository service 04 Apr '15

04 Apr '15

Author: stefanct Date: Fri Apr 3 23:29:04 2015 New Revision: 1889 URL: http://flashrom.org/trac/flashrom/changeset/1889 Log: Add support for more GigaDevice GD25LQ chips. Namely GD25LQ40, GD25LQ80, GD25LQ16, GD25LQ64(B), GD25LQ128. Signed-off-by: Roman Titov <titovroman(a)gmail.com> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/flashchips.c Modified: trunk/flashchips.c ============================================================================== --- trunk/flashchips.c Sun Mar 1 23:12:16 2015 (r1888) +++ trunk/flashchips.c Fri Apr 3 23:29:04 2015 (r1889) @@ -5466,6 +5466,123 @@ { .vendor = "GigaDevice", + .name = "GD25LQ40", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ40, + .total_size = 512, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 128} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 16} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 8} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {512 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {512 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", + .name = "GD25LQ80", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ80, + .total_size = 1024, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 256} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 32} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 16} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {1 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {1 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", + .name = "GD25LQ16", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ16, + .total_size = 2048, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 512} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 64} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 32} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", .name = "GD25LQ32", .bustype = BUS_SPI, .manufacture_id = GIGADEVICE_ID, @@ -5499,8 +5616,86 @@ .printlock = spi_prettyprint_status_register_bp4_srwd, .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ .write = spi_chip_write_256, - .read = spi_chip_read, - .voltage = {1700, 1950}, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", + .name = "GD25LQ64(B)", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ64, + .total_size = 8192, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 2048} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 256} }, + .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_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, + }, + + { + .vendor = "GigaDevice", + .name = "GD25LQ128", + .bustype = BUS_SPI, + .manufacture_id = GIGADEVICE_ID, + .model_id = GIGADEVICE_GD25LQ128, + .total_size = 16384, + .page_size = 256, + /* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 4096} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 512} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 256} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {16 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {16 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_bp4_srwd, + .unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 0x35) */ + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */ + .voltage = {1695, 1950}, }, {

1 0

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

03 Apr '15

On Sat, 14 Mar 2015 14:40:37 +0000 Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > On 8 March 2015 at 04:48, Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > > On 8 March 2015 at 00:46, Steven Honeyman <stevenhoneyman(a)gmail.com> wrote: > > > > ...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. > > OK, I finally got chance to make a little adapter board for > buspirate->soic16 spi... success! > It would seem that a set of ~20cm BP wires are too long for this to > work reliably, because with the adapter it worked first/every time: > > (the two other identical files came from a 'universal programmer' and > its own software) > […] > 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. > > > $ md5sum *.bin* > 6d7cf06448bd5ea941a4b458b6067e5f 25l6445.bin > 6d7cf06448bd5ea941a4b458b6067e5f 25l6465.bin > 6d7cf06448bd5ea941a4b458b6067e5f flashrom_mx23l6454.bin > 6d7cf06448bd5ea941a4b458b6067e5f flashrom_mx23l6454.bin2 Thanks for the update. I have marked the flash chip as tested and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Support for AT25080
by Roy Krikke 03 Apr '15

03 Apr '15

I know C coding and I also know some thing or two about hardware. But tip on how to add this specific device to flashrom are welcome. On 18-3-2015 22:42, Idwer Vollering wrote: > 2015-03-18 22:24 GMT+01:00 Roy Krikke <roykrikke(a)gmail.com>: >> Hello, >> >> I have compiled the latest version of flashrom (flashrom v0.9.8-r1887) and >> hoped to flash my AT25080. But without suc6. > flashrom does not (yet) support this chip. We like patches :) > >> I have connected a new AT25080 to a Raspberry Pi and hoped to flash the >> device with in system programming (ISP) mode. >> >> First erasing the device with sudo flashrom -E -V -p >> linux_spi:dev=/dev/spidev0.0 > The command line command looks just fine, but flashrom doesn't support > this particular flash chip, > >> No luke :( >> >> snapshot of flashrom below: >> Probing for Generic unknown SPI chip (RDID), 0 kB: RDID byte 0 parity >> violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 >> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi. >> Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x0, >> id2 0x0 >> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI). >> === >> This flash part has status NOT WORKING for operations: PROBE READ ERASE >> WRITE >> The test status of this chip may have been updated in the latest development >> version of flashrom. If you are running the latest development version, >> please email a report to flashrom(a)flashrom.org if any of the above >> operations >> work correctly for you with this flash chip. Please include the flashrom log >> file for all operations you tested (see the man page for details), and >> mention >> which mainboard or programmer you tested in the subject line. >> Thanks for your help! >> Read is not working on this chip. Aborting. >> >> Any kind of help is welcome, tips on how best to proceed! >> >> >> Thank you very much, >> >> Roy >> >> >> >> My previous post >> -------------------------------------------------------------------------------- >> Hello, >> >> Is there support for the AT25080B device from ATMEL? It is not in the >> supported device list. >> >> http://www.atmel.com/Images/Atmel-5228-SEEPROM-AT25080B-160B-Datasheet.pdf >> >> Need to flash the AT25080B which is connected to a 82574L from intel. There >> are two 82574L with two AT25080B on my board. If I read from the first >> AT25080B the data is fine and I can also flash is. But the second one is not >> working at all. >> >> I compared/checked the SPI communication of the first one with the second >> one. This looks the same. So I thought maybe the second AT25080B is broken. >> After replacing it, still the same result. >> >> I hope to get is to work if I could flash is not by the SPI interface of the >> 82574L, but by an in system programming (ISP). Example shown in >> http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf >> >> Any kind of help is welcome. >> >> Thanks, >> >> Roy >> >> >> >> >> _______________________________________________ >> flashrom mailing list >> flashrom(a)flashrom.org >> http://www.flashrom.org/mailman/listinfo/flashrom > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

3 4

Re: [flashrom] Flashrom not finding BIOS flash on HP DL585 G2
by Stefan Tauner 03 Apr '15

03 Apr '15

On Thu, 19 Mar 2015 21:27:18 +0000 Paul Lalonde <Paul.Lalonde(a)telecomcomputer.com> wrote: > Unless there is another way to perform a BIOS flash backup of an HP ProLiant DL585 G2 server, I'd like to use flashrom for this. > > Results of flashrom -V -p internal, lspci, and superiotool are attached. Hi, I think you have found an old but still unsupported flash chip in that server. From some lines in the log output I think it is plausible that it is a Macronix MX29LV320DT or MX29LV321DT. It would be great if you could verify that visually if that's possible. I can probably add support for the chip without too much problems... but I am not sure if you would want to test it on that hardware if it is somewhat important to you...? :) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Nec/Renesas 78k0s flash programming?
by Stefan Tauner 03 Apr '15

03 Apr '15

On Mon, 30 Mar 2015 15:56:06 +0000 Riccardo Delpopolo Carciopolo <rdelpopolo(a)gmail.com> wrote: > Hi, > I've used flashrom with pickit2 in past. > I'm a newbie but I'd like to add support for this MCUs by myself. > On Internet exist some parallel programmer but I want to program a 78k0s > flash my with the uart protocol. > We're can I start from? > It requires some vpp pulses to enable the uart programming mode. I don't think that flashrom is the right tool for the job of writing the flash memory of a microcontroller. Usually there are dedicated tools for this... but I guess the 78k0s are not really popular? You can of course use flashrom or at least its serial.c as a base for your tool. The protocol seems to be documented in a public application note: http://documentation.renesas.com/doc/DocumentServer/U17739EJ3V0AN00.pdf I am not sure about pulses thing. AFAICT the flash mode is enabled if FLMD0 is high when reset is released. I am however unsure if the following pulses on the same pin (FLMD0) are to be output by the programmer or are a way for the chip to indicate how it needs to be accessed... the language in the AN is abysmal. I would apply VCC to FLMD0 on reset release with a pull-up resistor and measure if the chip outputs anything on the port... Anyway this is rather off-topic... good luck with your project! -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Linux Raspberry PI B - Spansion FL256S
by Stefan Tauner 02 Apr '15

02 Apr '15

On Thu, 2 Apr 2015 16:16:38 +0200 Pascal de Marichalar <pascal.demarichalar(a)gmail.com> wrote: > Hi, > > I use the latest version of flashrom from github: "flashrom v0.9.8-r1887 on > Linux 3.18.10+ (armv6l)" that I had built on a Raspberry PI B. When I run > the command line "flashrom -p linux_spi:dev=/dev/spidev0.0" to probe a SPI > Flash memory chip soldered on a board (I use a a clip test probe) I get the > message: 'Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on > linux_spi.' > The Flash chip is a 32 MB Spansion memory. On the chip is written « > FL256SAIF00 SPANSION ». I have attached the output log from flashrom. Flash chips >16MB are not supported yet, but there are some patches you might want to look at, see http://patchwork.coreboot.org/project/flashrom/list/ -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Linux Raspberry PI B - Spansion FL256S
by Pascal de Marichalar 02 Apr '15

02 Apr '15

Hi, I use the latest version of flashrom from github: "flashrom v0.9.8-r1887 on Linux 3.18.10+ (armv6l)" that I had built on a Raspberry PI B. When I run the command line "flashrom -p linux_spi:dev=/dev/spidev0.0" to probe a SPI Flash memory chip soldered on a board (I use a a clip test probe) I get the message: 'Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi.' The Flash chip is a 32 MB Spansion memory. On the chip is written « FL256SAIF00 SPANSION ». I have attached the output log from flashrom. Thanks, Best regards, Pascal de Marichalar

1 0

Nec/Renesas 78k0s flash programming?
by Riccardo Delpopolo Carciopolo 30 Mar '15

30 Mar '15

Hi, I've used flashrom with pickit2 in past. I'm a newbie but I'd like to add support for this MCUs by myself. On Internet exist some parallel programmer but I want to program a 78k0s flash my with the uart protocol. We're can I start from? It requires some vpp pulses to enable the uart programming mode. Thabk you for help

1 0

W836xx: Lancer 5A2: flashrom -V
by Henrik Stokseth 29 Mar '15

29 Mar '15

if you want me to run additional tests on this new lenovo g50-70 laptop mail me privately. got some developer experience. HTH === flashrom v0.9.8-r1887 on Linux 3.19.0-10-generic (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.9.2, little endian Command line (3 args): ./flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 3072M loops per second, 10 myus = 10 us, 100 myus = 107 us, 1000 myus = 1000 us, 10000 myus = 10406 us, 4 myus = 6 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Notebook" Laptop detected via DMI. DMI string system-manufacturer: "LENOVO" DMI string system-product-name: "20351" DMI string system-version: "Lenovo G50-70" DMI string baseboard-manufacturer: "LENOVO" DMI string baseboard-product-name: "Lancer 5A2" DMI string baseboard-version: "31900058STD" 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: 85. Please send the output of "flashrom -V -p internal" 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 ITE EC, ID 0x8586, Rev 0x06 on port 0x4e. ====

1 0

W836xx: To be filled by O.E.M.: flashrom -V
by Florian Schroeter 29 Mar '15

29 Mar '15

Dear flashrom Developers, I am writing you because I want to set up a proper Linux on my Laptop, which I imported from china. It's clearly an imitation of some Acer Aspire One Model. When I got it, the packaging was labeled as "Spire One"... W-Lan and Bluetooth, sound, battery state and brightness controls as well as function keys seem to work under windows but not under Linux. I guess the ACPI tables provided by the hardware do poorly support any OS different from Microsoft Windows. I had hoped that a BIOS update could maybe fix the buggy ACPI tables but wasn't able to update the bios using flashrom. As suggested by your tool I'll put the verbose output of flashrom into the attachment. Kind regards Florian Schröter

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom