<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi again Nico,</p>
<p>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.</p>
<p>Thank you,<br>
Adam<br>
</p>
<div class="moz-cite-prefix">On 12/4/18 11:36 PM, adam wrote:<br>
</div>
<blockquote type="cite"
cite="mid:27a94ccc-4335-3b8b-fef5-eeeddf5438f1@o2.pl">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Hello Nico,</p>
<p>Thank you for the reply.<br>
</p>
<p>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.<br>
It looks like on the capture below.<br>
</p>
<p><img src="cid:part1.DB62BC5E.84D7647A@o2.pl" alt="" class=""></p>
<p>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.</p>
<p>Here is the grep for AT25 from the verbose output.<br>
</p>
<p>./flashrom -p ft2232_spi:type=4232H,divisor=12,port=A -V | grep
AT25<br>
Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1
0x1f, id2 0x8401<br>
Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic:
id1 0x1f, id2 0x8401<br>
Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0xff,
id2 0xff<br>
Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0xff,
id2 0xff<br>
Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1
0x1f, id2 0x8401<br>
Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1
0xff, id2 0xff<br>
Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0xff,
id2 0xff<br>
Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0xff,
id2 0xff<br>
Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1
0x1f, id2 0x8401<br>
Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1
0x1f, id2 0x8401</p>
<p>I'm also attaching the logfile.</p>
<p>My hardware is basically a clone of the following spectral
sensor board from the Sparkfun:
<a class="moz-txt-link-freetext"
href="https://cdn.sparkfun.com/assets/a/e/7/7/a/Qwiic_Spectral_Sensor-AS726x_v10.pdf"
moz-do-not-send="true">https://cdn.sparkfun.com/assets/a/e/7/7/a/Qwiic_Spectral_Sensor-AS726x_v10.pdf</a><br>
</p>
<p>Best regards,<br>
Adam<br>
</p>
<div class="moz-cite-prefix">On 12/4/18 9:07 PM, Nico Huber wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5e8bc294-dbc3-5a7e-f1f2-abb88e53c7c5@gmx.de">
<pre class="moz-quote-pre" wrap="">Hello Adam,
On 04.12.18 08:26, adam wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">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
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">forcing erase is futile, flashrom shouldn't ever do that.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">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.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">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
</pre>
</blockquote>
</blockquote>
</body>
</html>