Hi,
Has anyone done support for an MX25L12835F?
Thanks, Tony
On Wed, 5 Mar 2014 20:08:23 -0800 Tony Li tony.li@tony.li wrote:
Hi,
Has anyone done support for an MX25L12835F?
Not yet, thanks for bringing that up. I think basic operations could be supported by the definition of the old MX25L12805 chip. flashrom should detect it as such an work out of the box if I have not overlooked something.
On May 3, 2014, at 6:05 AM, Stefan Tauner stefan.tauner@alumni.tuwien.ac.at wrote:
Has anyone done support for an MX25L12835F?
Not yet, thanks for bringing that up. I think basic operations could be supported by the definition of the old MX25L12805 chip. flashrom should detect it as such an work out of the box if I have not overlooked something.
So far it seems to be happier with probe_spi_rems, but I’ve only been able to do limited testing.
Tony
On Sat, 3 May 2014 07:27:26 -0700 Tony Li tony.li@tony.li wrote:
So far it seems to be happier with probe_spi_rems, but I’ve only been able to do limited testing.
Could you please elaborate on that and/or post the verbose log of vanilla flashrom probing for the chip?
The datasheet says that it should reply to rdid (as done by probe_spi_rdid()) with 0xC2 0x20 0x18 which is matching flashrom's definition of "MX25L12805(D)".
The datasheet says that it should reply to rdid (as done by probe_spi_rdid()) with 0xC2 0x20 0x18 which is matching flashrom's definition of "MX25L12805(D)".
Which it does. However, in the hope of getting automatic clean identification, I’ve shifted to probe_spi_rems, which it seems to respond to. Unfortunately, this still isn’t enough for automatic identification.
Tony
On Sat, 3 May 2014 09:27:59 -0700 Tony Li tony.li@tony.li wrote:
The datasheet says that it should reply to rdid (as done by probe_spi_rdid()) with 0xC2 0x20 0x18 which is matching flashrom's definition of "MX25L12805(D)".
Which it does. However, in the hope of getting automatic clean identification, I’ve shifted to probe_spi_rems, which it seems to respond to. Unfortunately, this still isn’t enough for automatic identification.
I see... I will hopefully rewrite the probing algorithm completely this summer, so don't bother too much :) We will have to combine results for multiple opcodes to derive good matches.