Balazs Vinarz wrote:

Hi there!

Is it possible to implement this feature for Flashrom?
I saw some guy at GitHub raising the same question.
[[[https://github.com/flashrom/flashrom/issues/229]]]
Btw, which tool is supposed to be used for reporting bug, feature request, chip informations etc?

Best regards

Anastasia Klimchuk wrote in #note-1:

Hello Balasz! Sorry for not attending to the ticket for so long.
Progress bar was a long time known open issue, and we even had another ticket for it: https://ticket.coreboot.org/issues/390 (since a while ago as you can see),
but it has been fixed just recently!
So I closed the other ticket and also closing yours.

The feature may get further improvements, however it's working already (manpage https://flashrom.org/classic_cli_manpage.html#options )
If you are building from latest source, you have it already.
Or you can wait (not for long) for the next release.

which tool is supposed to be used for reporting bug, feature request, chip informations etc?

This is the right tool, and you did the right thing. Sorry it was missed :( I don't think the issue would be fixed earlier, but at least I could link you to the other "main" ticket.

Great stuff, thank you!
IIRC on Ubuntu the latest line of the output was updated constantly, but here - on Arch - it prints the string all the time.
`
$ sudo flashrom -p ch341a_spi --progress -r 1.bin
flashrom 1.4.0-devel (git:v1.2-1355-g9ccbf1cf) on Linux (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).

Found Eon flash chip "EN25F80" (1024 kB, SPI) on ch341a_spi.¶

This flash part has status UNTESTED for operations: WP
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 flashrom@flashrom.org 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!
Reading flash... [READ] 0% complete... [READ] 1% complete... [READ] 2% complete... [READ] 3% complete... [READ] 4% complete... [READ] 5% complete... [READ] 6% complete... [READ] 7% complete... [READ] 8% complete... [READ] 9% complete... [READ] 10% complete... [READ] 11% complete... [READ] 12% complete... [READ] 13% complete... [READ] 14% complete... [READ] 15% complete... [READ] 16% complete... [READ] 17% complete... [READ] 18% complete... [READ] 19% complete... [READ] 20% complete... [READ] 21% complete... [READ] 22% complete... [READ] 23% complete... [READ] 24% complete... [READ] 25% complete... [READ] 26% complete... [READ] 27% complete... [READ] 28% complete... [READ] 29% complete... [READ] 30% complete... [READ] 31% complete... [READ] 32% complete... [READ] 33% complete... [READ] 34% complete... [READ] 35% complete... [READ] 36% complete... [READ] 37% complete... [READ] 38% complete... [READ] 39% complete... [READ] 40% complete... [READ] 41% complete... [READ] 42% complete... [READ] 43% complete... [READ] 44% complete... [READ] 45% complete... [READ] 46% complete... [READ] 47% complete... [READ] 48% complete... [READ] 49% complete... [READ] 50% complete... [READ] 51% complete... [READ] 52% complete... [READ] 53% complete... [READ] 54% complete... [READ] 55% complete... [READ] 56% complete... [READ] 57% complete... [READ] 58% complete... [READ] 59% complete... [READ] 60% complete... [READ] 61% complete... [READ] 62% complete... [READ] 63% complete... [READ] 64% complete... [READ] 65% complete... [READ] 66% complete... [READ] 67% complete... [READ] 68% complete... [READ] 69% complete... [READ] 70% complete... [READ] 71% complete... [READ] 72% complete... [READ] 73% complete... [READ] 74% complete... [READ] 75% complete... [READ] 76% complete... [READ] 77% complete... [READ] 78% complete... [READ] 79% complete... [READ] 80% complete... [READ] 81% complete... [READ] 82% complete... [READ] 83% complete... [READ] 84% complete... [READ] 85% complete... [READ] 86% complete... [READ] 87% complete... [READ] 88% complete... [READ] 89% complete... [READ] 90% complete... [READ] 91% complete... [READ] 92% complete... [READ] 93% complete... [READ] 94% complete... [READ] 95% complete... [READ] 96% complete... [READ] 97% complete... [READ] 98% complete... [READ] 99% complete... [READ] 100% complete... done.
`

Aha! :) I see in the output the version is flashrom 1.4.0-devel which means it's at least few months old, so this explains why you see the "old style" output (and it used to display progress for reads only, but you did read).

The latest progress feature which displays for read/erase/write has been very recently submitted, within last week (commits are https://review.coreboot.org/c/flashrom/+/84102 and https://review.coreboot.org/c/flashrom/+/84439).
So on your environment on Arch you can either build from the latest source, or wait for around a month for v1.5 which will include the latest progress bar.
(https://mail.coreboot.org/hyperkitty/list/flashrom@flashrom.org/thread/WM4CFSOMEQ4XIM57HIV7XMW5XXDQL26W/)

Anastasia Klimchuk wrote in #note-3:

Aha! :) I see in the output the version is flashrom 1.4.0-devel which means it's at least few months old, so this explains why you see the "old style" output (and it used to display progress for reads only, but you did read).

The latest progress feature which displays for read/erase/write has been very recently submitted, within last week (commits are https://review.coreboot.org/c/flashrom/+/84102 and https://review.coreboot.org/c/flashrom/+/84439).
So on your environment on Arch you can either build from the latest source, or wait for around a month for v1.5 which will include the latest progress bar.
(https://mail.coreboot.org/hyperkitty/list/flashrom@flashrom.org/thread/WM4CFSOMEQ4XIM57HIV7XMW5XXDQL26W/)

So yes, I just picked the flashrom-git package from Arch Linux's AUR. Thank you again for notifying about this change.
Best regards