Hi all,
after a quiet week with the RC1, I'm happy to announce flashprog v1.1.
This release brings a progress bar (--progress), support for Dediprog
SF700 and SF600Plus-G2 programmers, and some more additions, fixes and
tunings. You can find the full release notes on the wiki [1].
The code is available through the v1.1 tag and as a tarball [2].
Happy flashing,
Nico
[1] https://flashprog.org/wiki/Flashprog/v1.1
[2] https://flashprog.org/releases/flashprog-v1.1.tar.bz2
Hi all,
I'm glad to announce a new release candidate v1.1-rc1. 55 commits
went into it, during a little more than four months. The most pro-
minent changes are:
* The `serprog' protocol now supports multiple CS lines. Which can
be selected from the command line if the programmer supports it.
* `serprog' driver now synchronizes more reliably after an aborted
run and without the initial 1s delay.
* We got rid of spurious attempts to memory map SPI flash chips by
default. This was mostly visible with the `internal' programmer
on AMD machines and `serprog' combined with big flash chips that
just couldn't be mapped.
* The CLI has a new `--progress' switch, finally(!) which makes it
show progress bars for read/erase/write. Some programmer drivers
were adapted to allow finer progress reporting.
* The Dediprog SF600Plus-G2 (tested) and SF700 (untested) program-
mers are supported now.
And there were more, smaller changes and refactorings all over the
place.
As usual, the code is available through the tag `v1.1-rc1', and as
tarball[1]. Please grab it! test it!
Cheers,
Nico
[1] https://flashprog.org/releases/flashprog-v1.1-rc1.tar.bz2
Hi,
we found two regressions related to the Dediprog driver and large
flash chips. There'll be a small maintenance release to fix them.
The code of the release candidate is available through the tag
`v1.0.2-rc1` and as a tarball[1].
Cheers,
Nico
[1] https://flashprog.org/releases/flashprog-v1.0.2-rc1.tar.bz2
Hi,
after a quiet test period, RC1 became the release. v1.0.1 fixes building
our `linux_gpio_spi' driver with newer versions of libgpiod.
Find more about it here:
https://flashprog.org/wiki/Flashprog/v1.0.1
Cheers,
Nico
Hi all,
flashprog has fallen behind with libgpiod compatibility. As it changed
the API with version 2.0, which already ships with at least Fedora and
ArchLinux. So we'll have a small maintenance release to include a new
libgpiod bit-banging driver that uses the new API.
The code is available through the tag `v1.0.1-rc1` and as a tarball[1].
As there are no other changes, only users of the linux_gpio_spi driver
would have to test anything.
Cheers,
Nico
[1] https://flashprog.org/releases/flashprog-v1.0.1-rc1.tar.bz2
Hello,
Please find enclosed the log describing the successful probe / read / flash
/ erase operations on a W25Q256JVEQ chip using the ch341a_spi programmer.
Best regards,
Hi all,
I'm happy to announce flashprog v1.0, our very first release. See the
full release notes[1] for more details and ways to download the source
code.
The most prominent change is the introduction of a new algorithm for
erase-function selection from last year's GSoC. Which should provide
a nice speed-up when operations are not limited by reading speed.
Overall, this might be our fastest version so far :)
Development already continued. A progress bar (finally!) and a CLI to
control write-protection of SPI flashes are in the queue. Let's see
what will make it into the next release.
Best,
Nico
[1] https://flashprog.org/wiki/Flashprog/v1.0
Hi all,
glad to announce that the first flashprog release candidate is tagged :)
Biggest change since flashrom-stable v1.1 is the integration of Aarya's
2022 GSoC work: a new core algorithm for the erase-function selection.
Otherwise, a small workaround to avoid MTD as internal programmer on x86
was merged, beside a few smaller cosmetic and build related things.
We'll let the ink on the RC dry for at least three days. You are of
course encouraged to test it with your flashing setup, especially
with the internal programmer. But keep a backup, so if something
goes wrong, you can recover with an older version.
The source code is available through the usual channels, on GitHub:
https://github.com/SourceArcade/flashprog/releases/tag/v1.0-rc1
and of course in the main Git repo
https://review.sourcearcade.org/plugins/gitiles/flashprog/+/refs/tags/v1.0-…
Tarballs can also be downloaded here
https://flashprog.org/releases/
Cheers,
Nico
Hi everybody!
as you may know already, flashrom-stable was removed from
review.coreboot.org a while ago. flashrom-stable was a short-
lived semi-fork, based on flashrom v1.2 [1].
The effort to keep developing a stable flash programming tool
for everyone, however, shall continue. I have hence renamed
flashrom-stable to *flashprog*. Now it's definitely a fork.
The main reason for the fork is that I saw the flashrom master
(now main) branch to become unmaintainable. Probably because
we merged too much code together, without actually managing to
work together on a product.
Beside names, I tried to keep everything as usual. There's
a wiki (slowly filled with contents from the old one)
https://flashprog.org/
an IRC channel
#flashprog on libera.chat
and a mailing list, of course
flashprog(a)flashprog.org
managed at
https://mail.sourcearcade.org/postorius/lists/flashprog.flashprog.org/
Review continues on a Gerrit instance, albeit on
https://review.sourcearcade.org/
And you can clone the repository from a GitHub mirror
https://github.com/SourceArcade/flashprog.git
Now that all this is done, I hope to return to work on the
source code again. There are still many patches open that were
pending for flashrom-stable. And it looks like the next release
candidate is only one commit away :)
So stay tuned!
Nico
[1]
https://mail.coreboot.org/hyperkitty/list/flashrom-stable@flashrom.org/thre…
