This is just a follow up email. I was wondering what the status is of
support for the EN25S64 bios chip. I have tried to flash it many times and
it always fails. See my message below for more details.
I would like to help out with any testing for this chip, however if I don't
hear back from you soon, I will probably be returning the laptop I have
which contains the EN25S64 chip.
On Oct 4, 2015 6:22 PM, "Kyle Stanevich" <kstanevich(a)imsa.edu> wrote:
> I am still having trouble flashing the EN25S64 chip on my Lenovo N21
> chromebook. I have connected a raspberry pi to the EN25S64 on the Lenovo
> N21 motherboard chip via this clip (
> On the raspberry pi (which is running raspbian) I run the command "sudo
> ./flashrom -VVV -p linux_spi:dev=/dev/spidev0.0 -w ~/Downloads/bios.bin". I
> have removed the write protect screw, but I don't think that matters
> because I am connecting to the chip directly.
> I have tried to compile google's (chromiumos') version of flashrom, but I
> could not get it to compile due to many errors. Therefore, I am using the
> latest version of flashrom which compiles fine.
> It seams to me that the problem is there is something not working
> correctly writing/erasing/reading to the chip. Erase functions 1 through 3
> all fail when using the command shown above. It hangs up on erase function
> 2 for a very long time. I had to run it overnight until erase function 2
> failed. I have tried running the same command again, and it is currently
> still stuck at "Trying erase function 2... 0x000000-0x7fffff:E". It has
> been stuck at this line for 16 hours, with the raspberry pi at 100% cpu
> usage the entire time.
> The line "This flash part has status UNTESTED for operations: PROBE READ
> ERASE WRITE" indicates to me that this chip has not yet been tested. I
> would like to help out with testing for this chip since I have one and have
> the hardware required to flash it. What can I do to help out?
> Kyle Stanevich
> On Sat, Oct 3, 2015 at 3:56 PM, Stefan Tauner <
> stefan.tauner(a)alumni.tuwien.ac.at> wrote:
>> On Sat, 3 Oct 2015 10:13:36 -0700
>> Kyle Stanevich <kstanevich(a)imsa.edu> wrote:
>> > Hi,
>> > I have attached all the output from my command line. Hopefully it will
>> > be useful for you.
>> > Do you think that I will ever have a chance to flash this chip, or
>> > should I go and buy another laptop?
>> first of all you should not reboot before fixing the issue.
>> If you made a backup first, you should try to write that instead.
>> If that works you are at least safe...
>> I am not familiar with the N21 but you probably have to disable a write
>> protection. Also, chromebooks work best with google's (chromiumos')
>> version of flashrom.
>> Kind regards/Mit freundlichen Grüßen, Stefan Tauner
I have used the same patch set on trunk to flash W25Q256 (WSON version).
I still need to build a system to check what was actually written.
(I'll try to flash Openwrt to the chip and run in on a MT7620 with
If there is anything I can do to move this along, please let me know.
On 21-9-2015 14:59, Peter Martini wrote:
> On Tue, Sep 15, 2015 at 3:12 AM, Stefan Tauner
> <mailto:email@example.com>> wrote:
> On Tue, 15 Sep 2015 02:26:39 -0400
> Peter Martini <petercmartini(a)gmail.com
> <mailto:firstname.lastname@example.org>> wrote:
> > 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?
> Nope, there isn't, at least nothing that I know about or that will hit
> vanilla flashrom soon.
> Kind regards/Mit freundlichen Grüßen, Stefan Tauner
> Thanks for the quick reply. I did some digging, and found a patch set
> from January, resurrected and forward ported to the current tip of
> flashrom on github.com/petermartini/flashrom
> <http://github.com/petermartini/flashrom>, and confirmed it worked well
> enough that it worked on my chipset.
> This was Boris' work, and I guess it was incomplete / petered out before
> being committed; does it ring any bells?
> It seems the thread petered out around
> I'm happy to help, if I can, get that patch set merged in if there's
> work to be done on it so I can upstream my chipset's specs.
> flashrom mailing list
On Sat, 3 Oct 2015 10:13:36 -0700
Kyle Stanevich <kstanevich(a)imsa.edu> wrote:
> I have attached all the output from my command line. Hopefully it will
> be useful for you.
> Do you think that I will ever have a chance to flash this chip, or
> should I go and buy another laptop?
first of all you should not reboot before fixing the issue.
If you made a backup first, you should try to write that instead.
If that works you are at least safe...
I am not familiar with the N21 but you probably have to disable a write
protection. Also, chromebooks work best with google's (chromiumos')
version of flashrom.
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
I have attached all the output from my command line. Hopefully it will
be useful for you.
Do you think that I will ever have a chance to flash this chip, or
should I go and buy another laptop?