<div dir="ltr"><div>Antonio, seems you have purchased typical Chineese VT6421 card with fake ROM.</div><div>VT6421 supports only LPC chips. Nowadays China manufacturers simply utilizes old parallel flash chips by this manner. Look thoroughly, this IC, most likely, even not connected to flash chip interface pins of VT6421 (sometimes it even soldered only on corner pins).</div><div><br></div><div>Look with Google translate on this thread: <a href="http://forum.ixbt.com/topic.cgi?id=11:38403">http://forum.ixbt.com/topic.cgi?id=11:38403</a>, with this key post: <a href="http://forum.ixbt.com/topic.cgi?id=11:38403:488#488">http://forum.ixbt.com/topic.cgi?id=11:38403:488#488</a>.</div><div>There's enthusiast who developed flash tool and heavily modified RAID BIOS and explored Chinese flash chip phenomenon. There are also described flash addressing issues. It's possible to desolder fake chip, add required few component and set real working BIOS chip.</div><div>Actually, I done all that, soldered IC socket for BIOs chip and nowadays searching for supported LPC flash chip.</div><div><br></div><div>===================================</div><div>Message: 2<br> Date: Tue, 5 Apr 2016 14:01:43 +0200<br> From: "Antonio Estrada Respeto" <<a href="mailto:aestradarespeto@gmail.com">aestradarespeto@gmail.com</a>><br> To: <<a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a>><br> Subject: Re: [flashrom] VT6421 sata card with sst39Vf512 eprom<br> Message-ID: <6FBFE9CEFEF54581B7BA6A024BA7C6B3@Asrock960gm><br> Content-Type: text/plain; format=flowed; charset="UTF-8";<br> reply-type=original<br><br> Thank you for your support.<br><br> I have tried to take the output file as you request, but no luck. I always<br> start freedos in my usb sdcard boot choosing the number 3 option, then input<br> cswdpr0, and then execute flashrom comand. But if I try to make -o<br> logfilename.txt, the system refuses to save the file (it says that the file<br> does not exists). If I do not execute cswdpr0 at first time, always have a<br> disk write error. I suppose it will be related to the file log error.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Best regards,<br>Max Arephin.<br></div></div></div>
<br><div class="gmail_quote">2016-04-05 20:05 GMT+03:00 <span dir="ltr"><<a href="mailto:flashrom-request@flashrom.org" target="_blank">flashrom-request@flashrom.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send flashrom mailing list submissions to<br>
<a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://www.flashrom.org/mailman/listinfo/flashrom" target="_blank" rel="noreferrer">https://www.flashrom.org/mailman/listinfo/flashrom</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:flashrom-request@flashrom.org">flashrom-request@flashrom.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:flashrom-owner@flashrom.org">flashrom-owner@flashrom.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of flashrom digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [PATCH] 4 byte address mode for Macronix MX25L25735F<br>
(Peter Martini)<br>
2. Re: VT6421 sata card with sst39Vf512 eprom<br>
(Antonio Estrada Respeto)<br>
3. Re: MX25L6445E erase and write failed! (The Raven)<br>
4. Adding support for MX25L6455EMI (The Raven)<br>
5. Adding some functionality to the FTDI driver<br>
(Salvador Eduardo Tropea)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 5 Apr 2016 05:06:56 -0400<br>
From: Peter Martini <<a href="mailto:petercmartini@gmail.com">petercmartini@gmail.com</a>><br>
To: Tim Chick <<a href="mailto:Tim.Chick@mediatek.com">Tim.Chick@mediatek.com</a>><br>
Cc: David Hendricks <<a href="mailto:dhendrix@google.com">dhendrix@google.com</a>>, "<a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a>"<br>
<<a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a>><br>
Subject: Re: [flashrom] [PATCH] 4 byte address mode for Macronix<br>
MX25L25735F<br>
Message-ID:<br>
<<a href="mailto:CAFyW6MS_YkaA2_wM2H8RCeSHK2xDAFjEdCFyHv55_%2BTtMdw%2BNA@mail.gmail.com">CAFyW6MS_YkaA2_wM2H8RCeSHK2xDAFjEdCFyHv55_+TtMdw+NA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi all,<br>
<br>
I'd asked about support for the MX25L25635E earlier on this list [<br>
<a href="https://www.flashrom.org/pipermail/flashrom/2015-September/013855.html" target="_blank" rel="noreferrer">https://www.flashrom.org/pipermail/flashrom/2015-September/013855.html</a>],<br>
and have confirmed with the patches referenced there that I can read and<br>
flash my chip. I'll try this patch tonight when I get home and report<br>
back; I'd love to see this support main-lined.<br>
<br>
Peter<br>
<br>
On Tue, Apr 5, 2016 at 3:18 AM, Tim Chick <<a href="mailto:Tim.Chick@mediatek.com">Tim.Chick@mediatek.com</a>> wrote:<br>
<br>
> Hi David,<br>
><br>
><br>
><br>
> There was a mistake in the logic, which I have corrected.<br>
><br>
><br>
><br>
> I was also asked by someone else on the list if it worked with the<br>
> MX25L25635F, which is 32Mbytes, but uses 3-byte addressing by default.<br>
><br>
><br>
><br>
> So I made the attached changes, which switch the chip to 4-byte mode. It<br>
> also has some dedicated 4-byte commands, and a BAR register, but it seemed<br>
> easiest to just use what I had tested for the MX25L25735F. I can?t actually<br>
> test the MX25L25635F though, as I don?t have one.<br>
><br>
><br>
><br>
> Thanks,<br>
> Tim<br>
><br>
><br>
><br>
><br>
><br>
> *From:* David Hendricks [mailto:<a href="mailto:dhendrix@google.com">dhendrix@google.com</a>]<br>
> *Sent:* 04 April 2016 23:21<br>
> *To:* Tim Chick<br>
> *Cc:* <a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a><br>
> *Subject:* Re: [flashrom] [PATCH] 4 byte address mode for Macronix<br>
> MX25L25735F<br>
><br>
><br>
><br>
> On Thu, Mar 31, 2016 at 8:21 AM, Tim Chick <<a href="mailto:Tim.Chick@mediatek.com">Tim.Chick@mediatek.com</a>> wrote:<br>
><br>
> Hi List,<br>
><br>
><br>
><br>
> Flashrom would not detect this chip. When the definition was added,<br>
> everything failed as the chip only supports 4 byte address operation.<br>
><br>
><br>
><br>
> Interesting - I didn't know such chips existed. The ones I've used have<br>
> backwards-compatible commands that support 3-byte addresses. FYI - Some<br>
> other high-capacity chips have 4-byte address enable bit in a config<br>
> register that will make the usual read/write/erase instructions accept 4<br>
> byte addresses. And yet other large chips have alternative instructions<br>
> that function the same but only accept a 4-byte address.<br>
><br>
><br>
><br>
> The attached patch adds 4 byte address support for 4 byte only chips, as<br>
> determined by the JEDEC flash parameter table, and support for this chip<br>
> specifically.<br>
><br>
><br>
><br>
> I?ve only allowed it to work with the SPI_CONTROLLER_FT2232 controller, as<br>
> that is the only one I have to test.<br>
><br>
><br>
><br>
> I?ve also only ported spi_block_erase_20 ? the other block erase functions<br>
> will fail.<br>
><br>
><br>
><br>
> Please let me know what you think!<br>
><br>
><br>
><br>
> Good stuff! FWIW, I have a work-in-progress patch on <a href="http://chromium.org" target="_blank" rel="noreferrer">chromium.org</a> (<br>
> <a href="https://chromium-review.googlesource.com/#/c/323359/" target="_blank" rel="noreferrer">https://chromium-review.googlesource.com/#/c/323359/</a>) for the other types<br>
> of high-capacity flash chips. I've tested on a Spansion S25FS256 using<br>
> linux_spi and ft2232. It needs a lot of clean-up, but might be of help.<br>
> Most of the changes were to convert read/write/erase functions to use<br>
> allocated buffers whose length depends on whether we're using a 3- or<br>
> 4-byte address.<br>
><br>
><br>
><br>
> I'll borrow some ideas from your patch as well to support the "4-byte<br>
> address only" chips.<br>
><br>
><br>
><br>
> --<br>
><br>
> David Hendricks (dhendrix)<br>
> Systems Software Engineer, Google Inc.<br>
><br>
> ************* Email Confidentiality Notice ********************<br>
> The information contained in this e-mail message (including any<br>
> attachments) may be confidential, proprietary, privileged, or otherwise<br>
> exempt from disclosure under applicable laws. It is intended to be<br>
> conveyed only to the designated recipient(s). Any use, dissemination,<br>
> distribution, printing, retaining or copying of this e-mail (including its<br>
> attachments) by unintended recipient(s) is strictly prohibited and may<br>
> be unlawful. If you are not an intended recipient of this e-mail, or believe<br>
> that you have received this e-mail in error, please notify the sender<br>
> immediately (by replying to this e-mail), delete any and all copies of<br>
> this e-mail (including any attachments) from your system, and do not<br>
> disclose the content of this e-mail to any other person. Thank you!<br>
><br>
><br>
> _______________________________________________<br>
> flashrom mailing list<br>
> <a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a><br>
> <a href="https://www.flashrom.org/mailman/listinfo/flashrom" target="_blank" rel="noreferrer">https://www.flashrom.org/mailman/listinfo/flashrom</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://www.flashrom.org/pipermail/flashrom/attachments/20160405/922e248f/attachment-0001.html" target="_blank" rel="noreferrer">http://www.flashrom.org/pipermail/flashrom/attachments/20160405/922e248f/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 5 Apr 2016 14:01:43 +0200<br>
From: "Antonio Estrada Respeto" <<a href="mailto:aestradarespeto@gmail.com">aestradarespeto@gmail.com</a>><br>
To: <<a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a>><br>
Subject: Re: [flashrom] VT6421 sata card with sst39Vf512 eprom<br>
Message-ID: <6FBFE9CEFEF54581B7BA6A024BA7C6B3@Asrock960gm><br>
Content-Type: text/plain; format=flowed; charset="UTF-8";<br>
reply-type=original<br>
<br>
Thank you for your support.<br>
<br>
I have tried to take the output file as you request, but no luck. I always<br>
start freedos in my usb sdcard boot choosing the number 3 option, then input<br>
cswdpr0, and then execute flashrom comand. But if I try to make -o<br>
logfilename.txt, the system refuses to save the file (it says that the file<br>
does not exists). If I do not execute cswdpr0 at first time, always have a<br>
disk write error. I suppose it will be related to the file log error.<br>
<br>
-----Mensaje original-----<br>
From: Stefan Tauner<br>
Sent: Monday, April 04, 2016 8:24 PM<br>
To: Antonio Estrada Respeto<br>
Cc: <a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a><br>
Subject: Re: [flashrom] VT6421 sata card with sst39Vf512 eprom<br>
<br>
On Mon, 4 Apr 2016 14:01:35 +0200<br>
"Antonio Estrada Respeto" <<a href="mailto:aestradarespeto@gmail.com">aestradarespeto@gmail.com</a>> wrote:<br>
<br>
> I have tried the below flashrom option (code tested) in order to find a<br>
> right response on my no name VT6421A pci sata card, but no luck.<br>
> Environment is Freedos in an usb boot sdcard device in a standard PC.<br>
> Address was from 0xffff0000 to others. The card is found by flashrom at<br>
> 1106:3249 BDF 02:0b.0 . The card has an Eprom flashable sst39Vf512 at is<br>
> printed in top of it. Final messages are:<br>
><br>
> Requested bar is of type rom.<br>
> Error: No suported PCI found.<br>
> Error: Program initialization failed.<br>
><br>
><br>
> I managed flashrom to work with my 3C905TX and do it in the same<br>
> environment as a charm. I know VT6421A hardware is very tricky depending<br>
> on every pci maker. The final goal is to flash a 64k boot rom ins this<br>
> card. Any help will be wellcome.<br>
><br>
> Thanks in advance.<br>
><br>
> The code tested:<br>
><br>
> flashrom ?p atavia offset=(different address) ?V<br>
<br>
Please post a log file. You can generate it with "-o logfilename.txt".<br>
<br>
--<br>
Kind regards/Mit freundlichen Gr??en, Stefan Tauner<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 5 Apr 2016 14:57:26 +0200<br>
From: The Raven <<a href="mailto:originalraven@hotmail.com">originalraven@hotmail.com</a>><br>
To: Urja Rannikko <<a href="mailto:urjaman@gmail.com">urjaman@gmail.com</a>>, <a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a><br>
Subject: Re: [flashrom] MX25L6445E erase and write failed!<br>
Message-ID: <BLU437-SMTP994D4E3F5AD35128DA7899B89E0@phx.gbl><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi again<br>
<br>
I think the problem was that this (my) chips are defective. :-(<br>
Tested now some of them and only two are not working as they should.<br>
<br>
So i think this case can be closed.<br>
<br>
THX<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 5 Apr 2016 16:47:42 +0200<br>
From: The Raven <<a href="mailto:originalraven@hotmail.com">originalraven@hotmail.com</a>><br>
To: <a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a><br>
Subject: [flashrom] Adding support for MX25L6455EMI<br>
Message-ID: <BLU437-SMTP39870E76A80C056D9BDA0DB89E0@phx.gbl><br>
Content-Type: text/plain; charset="iso-8859-15"<br>
<br>
Hi<br>
<br>
I have two of those chips and added support for them.<br>
This chip looks similar to the "MX25L6406E", so i took this part of code<br>
and modified it to fit the MX25L6455EMI.<br>
<br>
I have tested all erase modes (logs available if needed).<br>
spi_block_erase_20<br>
spi_block_erase_52<br>
spi_block_erase_d8<br>
spi_block_erase_60<br>
spi_block_erase_c7<br>
<br>
I am not a coder and it's years ago since my last patch. So sorry for<br>
not posting a patch. :-(<br>
<br>
Here are my modifications (are the correct?):<br>
<br>
File flashchips.h<br>
#define MACRONIX_MX25L6455EMI 0x2617 /* MX25L6455EMI (4k 0x20) */<br>
<br>
File flashchips.c<br>
{<br>
.vendor = "Macronix",<br>
.name = "MX25L6455EMI",<br>
.bustype = BUS_SPI,<br>
.manufacture_id = MACRONIX_ID,<br>
.model_id = MACRONIX_MX25L6455EMI,<br>
.total_size = 8192,<br>
.page_size = 256,<br>
.feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP,<br>
.tested = TEST_OK_PREW,<br>
.probe = probe_spi_rdid,<br>
.probe_timing = TIMING_ZERO,<br>
.block_erasers =<br>
{<br>
{<br>
.eraseblocks = { {4 * 1024, 2048} },<br>
.block_erase = spi_block_erase_20,<br>
}, {<br>
.eraseblocks = { {64 * 1024, 128} },<br>
.block_erase = spi_block_erase_52,<br>
}, {<br>
.eraseblocks = { {64 * 1024, 128} },<br>
.block_erase = spi_block_erase_d8,<br>
}, {<br>
.eraseblocks = { {8 * 1024 * 1024, 1} },<br>
.block_erase = spi_block_erase_60,<br>
}, {<br>
.eraseblocks = { {8 * 1024 * 1024, 1} },<br>
.block_erase = spi_block_erase_c7,<br>
}<br>
},<br>
.printlock = spi_prettyprint_status_register_bp3_srwd,<br>
.unlock = spi_disable_blockprotect_bp3_srwd,<br>
.write = spi_chip_write_256,<br>
.read = spi_chip_read, /* Fast read (0x0B), dual I/O read<br>
supported */<br>
.voltage = {2700, 3600},<br>
},<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 5 Apr 2016 13:50:02 -0300<br>
From: Salvador Eduardo Tropea <<a href="mailto:salvador@inti.gob.ar">salvador@inti.gob.ar</a>><br>
To: <a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a><br>
Subject: [flashrom] Adding some functionality to the FTDI driver<br>
Message-ID: <<a href="mailto:5703ECBA.7000809@inti.gob.ar">5703ECBA.7000809@inti.gob.ar</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
Hi!<br>
<br>
flashrom is a very nice tool. I'm using it to configure Lattice iCE40<br>
FPGAs. These FPGAs uses an SPI configuration memory (M25P10-A in my case).<br>
To communicate with the flash I'm using an FTDI 2232H cable (my own<br>
version, supports 0.9 to 5 V signals).<br>
The software provided by Lattice works. But I had problems with the<br>
command line version of the tool (the GUI is fine).<br>
So I searched for solutions and found flashrom.<br>
I was able to flash the chip and start the FPGA without problems.<br>
Flashrom is really fast and very easy to use.<br>
Now I want to avoid some annoying details, and I thought about adding a<br>
couple of new options to flashrom.<br>
<br>
My problem is that I need to control a system reset line. I can't access<br>
the SPI flash if the FPGA isn't in reset state (is directly connected to<br>
the SPI flash).<br>
It means that I must assert the reset line, do all the flashrom stuff<br>
and then deassert reset. This is quite easy to implement. In fact I<br>
could add a new "cable" to the ftdi.c file. But this won't solve similar<br>
problems. So I was thinking about adding options to the FTDI driver to<br>
control the initial and final state of the FTDI I/O lines. This is a<br>
little bit more complex, but will add support for a lot of situations.<br>
<br>
So my questions are:<br>
1) Is this kind of addition desired.<br>
2) Which way is preferred? simple/limited, complex/versatile.<br>
<br>
Regards, SET<br>
<br>
--<br>
Ing. Salvador Eduardo Tropea <a href="http://utic.inti.gob.ar/" target="_blank" rel="noreferrer">http://utic.inti.gob.ar/</a><br>
INTI - Micro y Nanoelectr?nica (CMNB) <a href="http://www.inti.gob.ar/" target="_blank" rel="noreferrer">http://www.inti.gob.ar/</a><br>
Unidad T?cnica Sistemas Inteligentes Av. General Paz 5445<br>
Tel: (+54 11) 4724 6300 ext. 6919 San Mart?n - B1650KNA<br>
FAX: (+54 11) 4754 5194 Buenos Aires * Argentina<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
flashrom mailing list<br>
<a href="mailto:flashrom@flashrom.org">flashrom@flashrom.org</a><br>
<a href="https://www.flashrom.org/mailman/listinfo/flashrom" target="_blank" rel="noreferrer">https://www.flashrom.org/mailman/listinfo/flashrom</a><br>
<br>
------------------------------<br>
<br>
End of flashrom Digest, Vol 83, Issue 4<br>
***************************************<br>
</blockquote></div><br></div>