On Mon, 9 May 2016 20:46:18 -0700
David Hendricks <dhendrix(a)google.com> wrote:
> Hi Victor,
> From Flashrom's software perspective all chips with the same ID are
> indistinguishable.
>
> Part number often includes characteristics such as package and thermal
> tolerance which do not affect software compatibility.
However, we will add the new names to the in-program (and hence
wiki) database so that this new information becomes public. Thanks for
the heads up, Victor.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Greetings everyone,
I'm a new member of flashrom mailing list, searching for info pertaining certain external programmer and corresponding 'flashrom' support. I noticed that the official list of supported programmers has not been updated for quite a while (January 2018), so I'd be interested to know if anyone succeeded to make it work - running 'flashrom' on Linux machine, in combination with this tiny programmer:
Product designation: "NANO USB Programmer"
Mfg: HS-TECH R.O.K, Korea
MPN: NANOUSB001
Site: http://shop3.nanobios.cafe24.com/article/download/7/8/?page=1
Programmer's core silicon:
Name: Cypress enCoRe II
Short description: Low Speed USB Peripheral Controller, with 8-bit M8C core.
Chip designation: CY7C63813-PXC
Ref.: https://www.cypress.com/products/encore-ii
USB ID: 04b4:3813
Name: NANO BIOS Programmer
Link: https://usb-ids.gowdy.us/read/UD/04b4/3813
WIN driver: cyusb3.inf (in case it's relevant);
----------------------------------------------------------------------------
I already contacted the guy, who runs the website mentioned above (shop3.nanobios.cafe24.com), and who also sells these programmers on eBay. He responded that in-the-house software, currently "NANO BIOS Programmer v1.1", is the only software that works with their Nano USB Programmer, but he promised to look into possibility, to "run an open platform software" for this programmer, as he elaborated in his response.
Since I have doubts that Windows based programming SW will be ported to Linux, at least not in a foreseeable time window, I would appreciate any useful information, as in - whether this programmer is supported by 'flashrom' project, what needs to be done to make it happen, which Linux distro you're using (in case it matters), etc.
Thank you in advance !
Kind regards,
Bostjan
Hello,
I would like to ask for a support of the chip GigaDevice GD25Q64C. The latest flashrom is able to read the data on the chip but cannot erase nor write. Is this possible to do for the flashrom future updates?
P.S. Here is the data sheet for GD25Q64C >> http://www.elm-tech.com/en/products/spi-flash-memory/gd25q64/gd25q64.pdf
Regards,
Ohm.
Sent from my iPhone
I am having trouble figuring out the correct pinout for the plcc32 chip to
program with the raspberry pi.
Here is the Data sheet
https://datasheetspdf.com/mobile-pdf/574977/SST/SST49LF020A.html
I know that I need to solder to pins VCC, HOLD, WP, GND, SCLK, SO, SI and
CS however I have no idea what pins these are on the datasheet. If you have
any input on this that would be awesome. I am looking to reprogram a bios
on one of these chips
Serious thanks in advanced.
Hello,
right now, I am working on a windows version of Flashrom based on the FTD2XX driver from FTDI instead of libFTDI.
Thus, I would like to know if I should submit a patch such that the ‚ft2232_spi.c‘ can cope with libFTDI and FTD2XX via defines or crate a new driver.
Best regards
Steffen
Dear flashrom followers,
I'm pleased to announce that we released flashrom v1.1 after fixing a
few minor compilation issues in v1.1-rc2.
This is a feature release with a handful of new programmers and lots of
new flash chips including, finally, 4-byte-address SPI flashes. You can
find the complete release notes here:
https://flashrom.org/Flashrom/1.1
The official tarball and signature here:
https://download.flashrom.org/releases/flashrom-v1.1.tar.bz2https://download.flashrom.org/releases/flashrom-v1.1.tar.bz2.asc
Again, the hint for package maintainers: If you don't use Git or don't
override flashrom's version string anyway, avoid the tarballs offered by
tools like Cgit or Github. They don't contain any version information.
Best regards,
Nico
Hi,
I´m using a N25Q128..3E to store a bitstream configuration for an FPGA.
To program the flash I´m using an ftdi2232H chip.
I have two ways how to program the flash (with the same ftdi chip!): Via the JTAG and the FPGA (which first loads a JTAG to SPI converter core to do so) or directly via SPI.
I prefer the last way as it is with less possible error points and I suppose that it should be faster.
My problem:
Programming the flash directly via SPI is much slower than the indirect way through JTAG and the FPGA.
I think that it does not has to do with the SPI clock frequency as it is even slower in indirect case.
But I can observe a significant difference in the Idle time between two SPI sequences/packages.
You can see that at attached screenshots. The idle time (red arrows) is 2 - 4 times longer in direct case (below) than in the indirect (above) (as there are about 16000 SPI sequences it really does matter).
1. I couldn't find any flashrom parameters to change idle time. Is there any?
2. When looking at the source code I found the function call 'ftdi_set_latency_timer' but can´t find the function definition. Does it has to do with the idle time?
3. Which function should I touch to change idle time if there is any to do so?
4. Any other advice about how to change the idle time?
Regards,
Simon
Hi,
sometimes I like to know how long an operation took or when I started programming.
That´s why I added some timestamp printouts.
May be you want to add it to the sources or do it in a more elegant way?
What´s about adding the timestamp printout to msg_cinfo ?
Just a proposal...
Regards,
Simon
Hello List,
i have a bricked TP-Link router with GD25Q32C DIP8-chip, but flashrom
supports only the GD25Q32(B).
I can read this ROM with --force option, but no write :(
What can i do? Whitch other options exitst for me to write to the DIP8-chip?
Thanks,
Christioph
--
Mit freundlichen Grüßen
Christoph Machon
-----BEGIN PGP PUBLIC KEY BLOCK-----
EMail : christoph(a)mach0n.de
GPG Public Key : 0x74D2 5E2E 3D30 9485
Key fingerprint : C33C 5F2F A3C4 3D9E 9319 35D0 74D2 5E2E 3D30 9485
-----END PGP PUBLIC KEY BLOCK-----
