flashrom

flashrom@flashrom.org

5 participants
9161 discussions

MX25L25635E / 4 byte addressing
by Peter Martini 15 Sep '15

15 Sep '15

Hello, I've checked out master from the flashrom svn repo, compiled, and was able to see my chip (MX25L25635E). The id wasn't recognized, but after a quick patch to copy a MX25L128... to ..L256.., I got it to successfully read the first 16MB of the chip - however, I can't get any further than that, because changing the values in the table to the right values moves me from 3 byte addressing to 4 byte addressing territory (if I understand this correctly), and it looks like there aren't any patches merged for that yet. Is there a patch set actively in the works? (I saw some activity around this from January, from this link http://patchwork.coreboot.org/patch/4272/, but I'm not sure where that ended up). Thanks! Peter

1 0

Re: [flashrom] Contribution: option to disable read_all_first
by Willy Tarreau 14 Sep '15

14 Sep '15

Hi David, On Mon, Sep 14, 2015 at 11:10:31AM -0700, David Hendricks wrote: > Hi Willy, > You might be interested in another approach that is used in the chromium > branch <https://chromium.googlesource.com/chromiumos/third_party/flashrom>. > The "--diff" longopt allows the user to supply a file to diff against the > -w argument. This is useful in cases where the user wishes to skip the > initial read step, and flashrom will figure out which blocks need to be > erased and written thereby eliminating unnecessary erase/write operations > as well. > > There is some documentation for it here: > https://sites.google.com/a/chromium.org/dev/chromium-os/packages/cros-flash… Thank you I'll take a look at it, it can indeed be another solution. The only thing is that it requires the creation of an extra file and I tend to find that it's not always convenient to have to create files for known patterns. However I think that it would be possible based on your approach to provide an option to replace the file with a known pattern for some cases (eg: full of 0xff or full of 0x00, which could be called "assume-clean" or "assume-dirty"), which would achieve the same result and at the same time not change the spirit of your latest work. Best regards, Willy

2 1

Contribution: option to disable read_all_first
by Willy Tarreau 14 Sep '15

14 Sep '15

Hello, I was bothered by having to read all the contents of an empty flash before programming just a boot loader to it. It's particularly long when using a buspirate board. I looked into the code to see how to bypass this and discovered it was already planned but not implemented due to the (presumably) complex API of the doit() function. I took a different route : I'm using 3 different write levels in write_it: - normal write (read first) - trusted write (no need to read but still erase) - fully trusted write (flash assumed to be clean) These ones are set using a new "-t" flag for which I have even updated the man page and indicated that it's not recommended. It worked well for me so I'm sending the patches assuming they'll be useful for someone else. BTW, to give you a bit more context, I was writing a 8MB flash to upgrade a small router from its 4MB one, so I just had to add 4MB of \xff after the existing image before flashing it. Best regards, Willy

2 1

flashrom can successfully read the BIOS image of my Amilo Xi3650 laptop
by Elmar Stellnberger 14 Sep '15

14 Sep '15

Lately I have tried > flashrom -p internal:laptop=force_I_want_a_brick --read Xi3650.rom on my Fujitsu Siemens Amilo Xi 3650 laptop and it has worked quite well. ... Found chipset "Intel ICH9M-E". Found Winbond flash chip "W25X16" (2048 kB, SPI) at physical address 0xffe00000. > sha256sum Xi3650.rom 8c5095d38bffe9b87d481ba8da395e48d9dcfadd43176979fd69e5da249b3763 Xi3650.rom BIOS (according to dmidecode) is Vendor: Phoenix Version: 1.0H-1646-0024 Release Date: 04/15/2010 I would love to see it under 'supported boards' in the future. More information can be found in the attachements.

1 0

Success: ASRock ION 330HT-BD
by Stefan Tauner 13 Sep '15

13 Sep '15

This is a small Atom-based media center from 2009. The board name is AMCP7AION-HT. I have successfully updated from the initial 1.00 to the last (and latest) version 1.20 and will add it myself to the wiki. ;) The -BD suffix is only indicating that there is a blueray player in the case. The mainboard and firmware is probably the same. http://www.asrock.com/nettop/NVIDIA/ION%20330HT-BD/ -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Foxconn H61MXL-K verbose flashrom output
by Ryan Solomon 10 Sep '15

10 Sep '15

1 0

SST49LF016C: Supermicro X7DWT successfully reflashed
by Steven Stremciuc 10 Sep '15

10 Sep '15

The Supermicro X7DWT motherboard is not listed on the flashrom supported hardware page, and the SST49LF016C chip has an "?" for erase and write status. I successfully reflashed the chip using flashrom, and thought I would send you a note so you can update the supported hardware list, if you would like. This board(s) was in a Dell C6100 XS23-SB. Thanks, Steven Stremciuc

1 0

Re: [flashrom] Teensy ISP on Synology mainboard
by Urja Rannikko 31 Aug '15

31 Aug '15

Hi, try to keep it on the mailing list too (i made a mistake of both you and the ML last time...) On Mon, Aug 31, 2015 at 11:56 AM, Guillaume Maugein <guillaume.maugein(a)gmail.com> wrote: > Hi, > > Thanks for the feedback. I'll try to see what I can do with the reset. > > I'll let you know if I can manage to ISP with the teensy, but I don't see > any reason why it could work on an unsoldered chip, but not ISP. Yeah it should work given a short enough cable and an non-interfering target; but as you see that sentence, an unsoldered chip is 0 interference and near-0 "cable" length, so it is a very optimal setup. But i wouldnt have added the little section in the wiki unless i thought it is possible to do ISP with the teensy. > > Maybe I'll try to grip my scope to the signals and see what is going on. > > > If I cannot manage this, would you recommend me buying a bus pirate, or not > ? I have 0 experience with buspirate so i cannot say much (except i've heard it is slow). If you want what other people are suggesting for ISP get a beaglebone black (price: ha..), but in general I'll say if you have measurement tools and can make the NAS not interfere with the ISP the Teensy should be electrically as good as either of those. (As i was investigating whether my statement was true or not, this is what i found: The Teensy (MK20DX256) with "high drive strength" (that is enabled currently in the FW) has a drive strength of 9mA. The BBB has a drive strength (note: just from some forum post) of 4, 6 or 8 mA The buspirate PIC24FJ64 has an asymmetric drive strength of 3mA high 8mA low ) > > 2015-08-31 0:39 GMT+02:00 Urja Rannikko <urjaman(a)gmail.com>: >> >> Hi, >> >> On Sun, Aug 30, 2015 at 6:10 PM, Guillaume Maugein >> <guillaume.maugein(a)gmail.com> wrote: >> > Hey, >> > >> > First of all, thank you for the great work. >> > >> > I am trying to access the Micron N25Q064A13 flash chip on my Synology >> > NAS >> > DS413j. >> > >> > I happen to have a teensy board available at hand, so I programmed it >> > with >> > serprog software, using the instructions to which the flashrom website >> > points to. >> > I am under Xubuntu 15.04, and I installed flashrom from the daily builds >> > ppa. >> > If I remember, the version was 20150705~ubuntu14.04.1. >> >> >> >> xubuntu@xubuntu:~$ flashrom -R >> >> flashrom v0.9.8-unknown on Linux 3.19.0-25-generic (x86_64) >> > >> > >> > >> > I connected the programmer with GND, MISO, MOSI, CLK and CS using grips. >> > As >> > I am ISP, I did not connect the VCC. >> > >> > I double-checked my connections, and they seem to be fine. >> > >> > I start the NAS, and using serial terminal (on a different computer), I >> > stop >> > the boot sequence at uboot prompt. >> > If I flinfo in the uboot, I get the following info : >> > >> >> Marvell>> flinfo >> >> >> >> Bank#1: >> >> Flash Base Address : 0xf8000000 >> >> Flash Model : ST N25Q064 >> >> Manufacturer ID : 0x20 >> >> Device Id : 0xba17 >> >> Sector Size : 64K >> >> Number of sectors : 128 >> >> Page Size : 256 >> >> Write Protection : All >> > >> > >> > While the system is waiting on the prompt, I launch a flashrom command, >> > and >> > the chip is not recognized : >> >> >> >> xubuntu@xubuntu:~$ sudo flashrom -V -p serprog:dev=/dev/ttyACM0:2000000 >> >> flashrom v0.9.8-unknown on Linux 3.19.0-25-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.8.4, little endian >> >> Command line (3 args): flashrom -V -p serprog:dev=/dev/ttyACM0:2000000 >> >> Calibrating delay loop... OS timer resolution is 1 usecs, 1104M loops >> >> per >> >> second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 >> >> myus = >> >> 9998 us, 4 myus = 4 us, OK. >> >> Initializing serprog programmer >> >> Baud rate is 2000000 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 2037 >> >> serprog: Maximum read-n length is 400384 >> >> serprog: Programmer name is "Teensy LPC+SPI" >> >> serprog: Serial buffer size is 2044 >> >> serprog: operation buffer size is 2048 >> >> serprog: Output drivers enabled >> >> The following protocols are supported: SPI. >> >> Probing for {... the list is long ...} >> >> >> >> Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity >> >> violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 >> >> Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity >> >> violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 >> This (0x00 reply) means that there's something wrong with the >> connections/communications. >> My guess is either a wiring problem or the NAS is also driving the >> SPI I/O lines and the Teensy is not strong enough to override (it >> could also be harmful to the chipset if it was). >> >> Maybe try finding a reset line and holding the NAS in reset while >> doing the programming. >> >> Also note that I havent tested the teensy in any ISP application, so >> you're doing something untested. Have fun :) >> >> >> -- >> Urja Rannikko > > -- Urja Rannikko

1 0

Re: [flashrom] Teensy ISP on Synology mainboard
by Urja Rannikko 31 Aug '15

31 Aug '15

Hi, On Sun, Aug 30, 2015 at 6:10 PM, Guillaume Maugein <guillaume.maugein(a)gmail.com> wrote: > Hey, > > First of all, thank you for the great work. > > I am trying to access the Micron N25Q064A13 flash chip on my Synology NAS > DS413j. > > I happen to have a teensy board available at hand, so I programmed it with > serprog software, using the instructions to which the flashrom website > points to. > I am under Xubuntu 15.04, and I installed flashrom from the daily builds > ppa. > If I remember, the version was 20150705~ubuntu14.04.1. >> >> xubuntu@xubuntu:~$ flashrom -R >> flashrom v0.9.8-unknown on Linux 3.19.0-25-generic (x86_64) > > > > I connected the programmer with GND, MISO, MOSI, CLK and CS using grips. As > I am ISP, I did not connect the VCC. > > I double-checked my connections, and they seem to be fine. > > I start the NAS, and using serial terminal (on a different computer), I stop > the boot sequence at uboot prompt. > If I flinfo in the uboot, I get the following info : > >> Marvell>> flinfo >> >> Bank#1: >> Flash Base Address : 0xf8000000 >> Flash Model : ST N25Q064 >> Manufacturer ID : 0x20 >> Device Id : 0xba17 >> Sector Size : 64K >> Number of sectors : 128 >> Page Size : 256 >> Write Protection : All > > > While the system is waiting on the prompt, I launch a flashrom command, and > the chip is not recognized : >> >> xubuntu@xubuntu:~$ sudo flashrom -V -p serprog:dev=/dev/ttyACM0:2000000 >> flashrom v0.9.8-unknown on Linux 3.19.0-25-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.8.4, little endian >> Command line (3 args): flashrom -V -p serprog:dev=/dev/ttyACM0:2000000 >> Calibrating delay loop... OS timer resolution is 1 usecs, 1104M loops per >> second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus = >> 9998 us, 4 myus = 4 us, OK. >> Initializing serprog programmer >> Baud rate is 2000000 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 2037 >> serprog: Maximum read-n length is 400384 >> serprog: Programmer name is "Teensy LPC+SPI" >> serprog: Serial buffer size is 2044 >> serprog: operation buffer size is 2048 >> serprog: Output drivers enabled >> The following protocols are supported: SPI. >> Probing for {... the list is long ...} >> >> Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity >> violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 >> Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity >> violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 This (0x00 reply) means that there's something wrong with the connections/communications. My guess is either a wiring problem or the NAS is also driving the SPI I/O lines and the Teensy is not strong enough to override (it could also be harmful to the chipset if it was). Maybe try finding a reset line and holding the NAS in reset while doing the programming. Also note that I havent tested the teensy in any ISP application, so you're doing something untested. Have fun :) -- Urja Rannikko

1 0

Teensy ISP on Synology mainboard
by Guillaume Maugein 30 Aug '15

30 Aug '15

Hey, First of all, thank you for the great work. I am trying to access the Micron N25Q064A13 flash chip on my Synology NAS DS413j. I happen to have a teensy board available at hand, so I programmed it with serprog software, using the instructions to which the flashrom website points to. I am under Xubuntu 15.04, and I installed flashrom from the daily builds ppa. If I remember, the version was 20150705~ubuntu14.04.1. > xubuntu@xubuntu:~$ flashrom -R > flashrom v0.9.8-unknown on Linux 3.19.0-25-generic (x86_64) > I connected the programmer with GND, MISO, MOSI, CLK and CS using grips. As I am ISP, I did not connect the VCC. I double-checked my connections, and they seem to be fine. I start the NAS, and using serial terminal (on a different computer), I stop the boot sequence at uboot prompt. If I flinfo in the uboot, I get the following info : Marvell>> flinfo > > Bank#1: > Flash Base Address : 0xf8000000 > Flash Model : ST N25Q064 > Manufacturer ID : 0x20 > Device Id : 0xba17 > Sector Size : 64K > Number of sectors : 128 > Page Size : 256 > Write Protection : All While the system is waiting on the prompt, I launch a flashrom command, and the chip is not recognized : > xubuntu@xubuntu:~$ sudo flashrom -V -p serprog:dev=/dev/ttyACM0:2000000 > flashrom v0.9.8-unknown on Linux 3.19.0-25-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.8.4, little endian > Command line (3 args): flashrom -V -p serprog:dev=/dev/ttyACM0:2000000 > Calibrating delay loop... OS timer resolution is 1 usecs, 1104M loops per > second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus > = 9998 us, 4 myus = 4 us, OK. > Initializing serprog programmer > Baud rate is 2000000 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 2037 > serprog: Maximum read-n length is 400384 > serprog: Programmer name is "Teensy LPC+SPI" > serprog: Serial buffer size is 2044 > serprog: operation buffer size is 2048 > serprog: Output drivers enabled > The following protocols are supported: SPI. > Probing for {... the list is long ...} Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: RDID byte 0 parity > violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 > Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: RDID byte 0 parity > violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 > Probing for {... the list continues ...} > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > serprog: Output drivers disabled > Do you guys have any idea of what could I try next ? I'm stuck there... Thanks for any help you could provide. G.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom