AT25SF041 chip support

[adam]

Hello,

I'm trying to manage AT25SF041 using FT4232 MiniModule programmer. I'm 
using flashrom v1.0 on Linux 4.15.0-42-generic (x86_64) compiled from 
sources. Trying to erase chip at first and get this output:

./flashrom -p ft2232_spi:type=4232H,port=A -Ef

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) on ft2232_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 [e-mail] 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. Continuing anyway.
flashrom has no read function for this flash chip.
Aborting.
Your flash chip is in an unknown state.
Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail [e-mail], thanks!

According to https://www.flashrom.org/Supported_hardware page, this chip 
should be fully supported.
Please advice.

Thank you,
Adam

[adam]

Build details atteched

Adam

On 12/4/18 8:26 AM, adam wrote:
> Hello,
>
> I'm trying to manage AT25SF041 using FT4232 MiniModule programmer. I'm 
> using flashrom v1.0 on Linux 4.15.0-42-generic (x86_64) compiled from 
> sources. Trying to erase chip at first and get this output:
>
> ./flashrom -p ft2232_spi:type=4232H,port=A -Ef
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) on ft2232_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 [e-mail] 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. Continuing anyway.
> flashrom has no read function for this flash chip.
> Aborting.
> Your flash chip is in an unknown state.
> Please report this on IRC at chat.freenode.net (channel #flashrom) or
> mail [e-mail], thanks!
>
> According to https://www.flashrom.org/Supported_hardware page, this 
> chip should be fully supported.
> Please advice.
>
> Thank you,
> Adam

[Nico Huber]

Hello Adam,

On 04.12.18 08:26, adam wrote:
> Hello,
>
> I'm trying to manage AT25SF041 using FT4232 MiniModule programmer. I'm
> using flashrom v1.0 on Linux 4.15.0-42-generic (x86_64) compiled from
> sources. Trying to erase chip at first and get this output:
>
> ./flashrom -p ft2232_spi:type=4232H,port=A -Ef

forcing erase is futile, flashrom shouldn't ever do that.
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) on ft2232_spi.

This is likely a physical issue with your hardware setup. SPI is not
a bus where you can just plug things together like USB for instance.
Signal integrity is a delicate thing with SPI.

An easy workaround is often to lower the transfer speed. For your
programmer there's a divisor option. IIRC add `,divisor=6` to the
programmer argument (valid divisors are equal numbers >= 2, the base
frequency is 60MHz so 6 means 10MHz SPI clock).

If that doesn't help, please attach a log file (add `-o logfile.txt`
to your flashrom command line) to your next email. And tell us more
about your hardware setup (e.g. how the flash chip is connected, what
else is connected, is the chip on some kind of mainboard etc.).

Hope that helps,
Nico

[adam]

Hello Nico,

Thank you for the reply.

I have looked at the SPI communication using logic analyzer and it 
doesn't look bad. I have slower SPI clock by adding divisor=6 and even 
went down to 12 and it didn't helped.
It looks like on the capture below.

I have checked what verbose output will tell me and there is valid JEDEC 
read from the chip next to the probes but it looks like there is no 
probe for the AT25SF041.

Here is the grep for AT25 from the verbose output.

./flashrom -p ft2232_spi:type=4232H,divisor=12,port=A -V | grep AT25
Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 
0x1f, id2 0x8401
Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff
Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff
Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 0xff
Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff
Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff
Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401
Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x1f, 
id2 0x8401

I'm also attaching the logfile.

My hardware is basically a clone of the following spectral sensor board 
from the Sparkfun: 
https://cdn.sparkfun.com/assets/a/e/7/7/a/Qwiic_Spectral_Sensor-AS726x_v10.p...

Best regards,
Adam

On 12/4/18 9:07 PM, Nico Huber wrote:
> Hello Adam,
>
> On 04.12.18 08:26, adam wrote:
> > Hello,
> >
> > I'm trying to manage AT25SF041 using FT4232 MiniModule programmer. I'm
> > using flashrom v1.0 on Linux 4.15.0-42-generic (x86_64) compiled from
> > sources. Trying to erase chip at first and get this output:
> >
> > ./flashrom -p ft2232_spi:type=4232H,port=A -Ef
>
> forcing erase is futile, flashrom shouldn't ever do that.
> > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> > Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) on ft2232_spi.
>
> This is likely a physical issue with your hardware setup. SPI is not
> a bus where you can just plug things together like USB for instance.
> Signal integrity is a delicate thing with SPI.
>
> An easy workaround is often to lower the transfer speed. For your
> programmer there's a divisor option. IIRC add `,divisor=6` to the
> programmer argument (valid divisors are equal numbers >= 2, the base
> frequency is 60MHz so 6 means 10MHz SPI clock).
>
> If that doesn't help, please attach a log file (add `-o logfile.txt`
> to your flashrom command line) to your next email. And tell us more
> about your hardware setup (e.g. how the flash chip is connected, what
> else is connected, is the chip on some kind of mainboard etc.).
>
> Hope that helps,
> Nico

[adam]

Hi again Nico,

I just realized that there is more recent version on the git repo. I was 
using the one from downloaded tar archive before. Now it looks to work 
fine with AT25SF041.

Thank you,
Adam

On 12/4/18 11:36 PM, adam wrote:
> Hello Nico,
>
> Thank you for the reply.
>
> I have looked at the SPI communication using logic analyzer and it 
> doesn't look bad. I have slower SPI clock by adding divisor=6 and even 
> went down to 12 and it didn't helped.
> It looks like on the capture below.
>
> I have checked what verbose output will tell me and there is valid 
> JEDEC read from the chip next to the probes but it looks like there is 
> no probe for the AT25SF041.
>
> Here is the grep for AT25 from the verbose output.
>
> ./flashrom -p ft2232_spi:type=4232H,divisor=12,port=A -V | grep AT25
> Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x1f, 
> id2 0x8401
> Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 
> 0x1f, id2 0x8401
> Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff
> Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff, id2 0xff
> Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x1f, 
> id2 0x8401
> Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0xff, id2 
> 0xff
> Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff, id2 0xff
> Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff, id2 0xff
> Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x1f, 
> id2 0x8401
> Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x1f, 
> id2 0x8401
>
> I'm also attaching the logfile.
>
> My hardware is basically a clone of the following spectral sensor 
> board from the Sparkfun: 
> https://cdn.sparkfun.com/assets/a/e/7/7/a/Qwiic_Spectral_Sensor-AS726x_v10.p...
>
> Best regards,
> Adam
>
> On 12/4/18 9:07 PM, Nico Huber wrote:
> > Hello Adam,
> >
> > On 04.12.18 08:26, adam wrote:
> > > Hello,
> > >
> > > I'm trying to manage AT25SF041 using FT4232 MiniModule programmer. I'm
> > > using flashrom v1.0 on Linux 4.15.0-42-generic (x86_64) compiled from
> > > sources. Trying to erase chip at first and get this output:
> > >
> > > ./flashrom -p ft2232_spi:type=4232H,port=A -Ef
> >
> > forcing erase is futile, flashrom shouldn't ever do that.
> > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> > > Found Atmel flash chip "unknown Atmel SPI chip" (0 kB, SPI) on ft2232_spi.
> >
> > This is likely a physical issue with your hardware setup. SPI is not
> > a bus where you can just plug things together like USB for instance.
> > Signal integrity is a delicate thing with SPI.
> >
> > An easy workaround is often to lower the transfer speed. For your
> > programmer there's a divisor option. IIRC add `,divisor=6` to the
> > programmer argument (valid divisors are equal numbers >= 2, the base
> > frequency is 60MHz so 6 means 10MHz SPI clock).
> >
> > If that doesn't help, please attach a log file (add `-o logfile.txt`
> > to your flashrom command line) to your next email. And tell us more
> > about your hardware setup (e.g. how the flash chip is connected, what
> > else is connected, is the chip on some kind of mainboard etc.).
> >
> > Hope that helps,
> > Nico