Hi,
Debug log file attached and generated by using the "--output" flag when reading(-r) the flash via:
# flashrom -p serprog:dev=/dev/ttyACM0,spispeed=32M -r flash.bin
Flashrom version, built from git checkout.
Version:
# flashrom --version
flashrom 1.4.0-devel (git:v1.2-1388-gbb8e6f90) on Linux 6.6.10-gentoo (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Please reach out to me if you require anything else.
Thank you,
Brendan
Hi
As requested, please find the two logs files for extract and write on the ASRock AB350MPRO4. One for reading BIOS 4.70 and the other for writing 7.40
I hope this helps,
Erik
RecveryErik@Eriks-iMac flashrom % sudo flashrom -w AB35PR47.40 -p ch341a_spi -o AB350PROM4_4.70_write_w.log
flashrom v1.3.0 on Darwin 19.6.0 (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
libusb: info [darwin_detach_kernel_driver] no capture entitlements. may not be able to detach the kernel driver for this device
Found Macronix flash chip "MX25U12835F" (16384 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(a)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 old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.
This is the flash rom:
https://datasheet.lcsc.com/lcsc/2109132030_FUDAN-MICRO-FM25Q128A-SOB-T-G_C9…
SFDP has autodetected a flash chip which is not natively supported by
flashrom yet.
All standard operations (read, verify, erase and write) should work, but to
support all possible features we need to add them manually.
You can help us by mailing us the output of the following command to
flashrom(a)flashrom.org:
'flashrom -VV [plus the -p/--programmer parameter]'
Thanks for your help!
Added layout entry 00000000 - 00ffffff named complete flash
Found Unknown flash chip "SFDP-capable chip" (16384 kB, SPI) on serprog.
Probing for AMIC unknown AMIC SPI chip, 0 kB: RDID byte 0 parity violation.
compare_id: id1 0x00, id2 0x00
Probing for Atmel unknown Atmel SPI chip, 0 kB: compare_id: id1 0xa1, id2
0x4018
Probing for Eon unknown Eon SPI chip, 0 kB: compare_id: id1 0xa1, id2 0x4018
Probing for Macronix unknown Macronix SPI chip, 0 kB: compare_id: id1 0xa1,
id2 0x4018
Probing for PMC unknown PMC SPI chip, 0 kB: compare_id: id1 0xa1, id2 0x4018
Probing for SST unknown SST SPI chip, 0 kB: compare_id: id1 0xa1, id2 0x4018
Probing for ST unknown ST SPI chip, 0 kB: compare_id: id1 0xa1, id2 0x4018
Probing for Sanyo unknown Sanyo SPI chip, 0 kB: compare_id: id1 0xa1, id2
0x4018
Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: compare_id:
id1 0xa1, id2 0x4018
Probing for Generic unknown SPI chip (RDID), 0 kB: compare_id: id1 0xa1,
id2 0x4018
Probing for Generic unknown SPI chip (REMS), 0 kB: compare_id: id1 0xa1,
id2 0x17
Found Unknown flash chip "SFDP-capable chip" (16384 kB, 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(a)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... Error: invalid response 0x00 from device (to command 0x13)
Read operation failed!
FAILED.
I was trying to record a bios on the motherboard machinist X99 PR9
with the Chipset B85 and a Xeon E5 2650V4. I will leave the log below
but i wish anyone could give me instructions about how can i help this
motherboard recorder/flash to get support.
root@archiso ~ # flashrom --programmer internal -c "Opaque flash chip"
-w backup.
bin
flashrom v1.2 on Linux 6.6.3-arch1-1 (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).
Opened /dev/mtd0 successfully
Found Programmer flash chip "Opaque flash chip" (16384 kB,
Programmer-specific) m
apped at physical address 0x0000000000000000.
Reading old flash chip contents... done.
Erasing and writing flash chip... linux_mtd_erase: ioctl: Unknown error 524
Reading current flash chip contents... done. Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
Looking for another erase function.
No usable erase functions left.
FAILED!
Uh oh. Erase/write failed. Checking if anything has changed.
Reading current flash chip contents... done.
Good, writing to the flash chip apparently didn't do anything.
This means we have to add special support for your board, programmer or flash
chip. Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom(a)flashrom.org, thanks!
-------------------------------------------------------------------------------
You may now reboot or simply leave the machine running.
flashrom --programmer internal -c "Opaque flash chip" -w backup.bin
0.11s user 1
2.93s system 99% cpu 13.051 total
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…