LOG:
root@g50-70:~/flashrom/flashrom# ./flashrom --programmer ch341a_spi -w /tmp/test.bin
flashrom v1.1-rc1-124-ga9d6d1a on Linux 4.9.0-9-amd64 (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 Winbond flash chip "W25Q32.V" (4096 kB, SPI) on ch341a_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... FAILED at 0x00007100! Expected=0x23, Found=0xff, failed byte count from 0x00000000-0x003fffff: 0xcf6
Your flash chip is in an unknown state.
Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom(a)flashrom.org, thanks!
LOG:
root@g50-70:~/flashrom/flashrom# ./flashrom --programmer ch341a_spi -w
/tmp/test.bin
flashrom v1.1-rc1-124-ga9d6d1a on Linux 4.9.0-9-amd64 (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 Winbond flash chip "W25Q32.V" (4096 kB, SPI) on ch341a_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... FAILED at 0x00007100! Expected=0x23, Found=0xff,
failed byte count from 0x00000000-0x003fffff: 0xcf6
Your flash chip is in an unknown state.
Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom(a)flashrom.org, thanks!
Hi! Here is the flashrom log. Thank you for this wonderful tool and support.
BIOS chip is MX25U12873F.
My motherboard model is MSI A320M PRO VH-PLUS
https://pastebin.com/raw/0f2PXpex
Regards,
Ghil
Sehr geehrte Damen und Herren,
wir benötigen eine aktuelle BIOS-Version wie oben angegeben. Zur Zeit ist
unserer Stand vom 23.07.2012
Mit freundlichen Grüßen
Rolf Isler
Kontaktdaten: 272343309@11082010-255A auto-id-projekt Fa. Rolf Isler
Neue Straße 65, 04451 Borsdorf (bei Leipzig)
Tel.: +49 (34291) - 86681 Fax: +49 (34291) - 88844
E-Mail: < <mailto:info@auto-id-projekt.de> mailto:info@auto-id-projekt.de>
Internet: < <http://www.auto-id-projekt.de/> http://www.auto-id-projekt.de/>
Steuernummer: 238/235/01137
UST-ID: DE 174403676
Hi,
At FOSDEM on sunday the 2nd of february 2020, there will be another
hardware enablement DevRoom. URL: https://fosdem.org/2020/
This devroom covers topics related to hardware support and enablement
with free software. It includes the following topics:
* peripheral/controller firmwares
* hw support and drivers in bootloaders
* kernel drivers and hardware interfaces
* hardware-related adaptation in operating systems
* tools for firmware flashing
* tools for low-level development
FOSDEM is very much an open source community event, please refrain from
turning in a talk that is meant to be purely corporate or a product
commercial. Also, this is a highly technical devroom on a conference
aimed at developers and advanced users, so only submit a talk on a
subject you actually are involved with. Finally, this devrooms focus is
the technical aspects of the hardware and its enablement in free
projects, rather than the specific applications and use cases that
benefit from it.
With the return of the Embedded and Automotive DevRoom, we have the
ability to schedule full hour talks again, and to go in-depth. If you
however only need half an hour, then this is of course also possible.
Talk Submission:
The venerable pentabarf system will once again be used for talk
submission.
https://penta.fosdem.org/submission/FOSDEM20
When in pentabarf, spend some time on the abstract and description, for
both the event and the speaker. The abstract should be a shortened
description, and the event abstract will sometimes even be printed
directly in the booklet. BUT, on the website the abstract is immediately
followed by the full description. If your abstract is fully descriptive,
while terse, you might get away with just the abstract. As soon as your
talk is scheduled by the devroom managers, you can see the result of
your handiwork on the main website.
Please re-use your old pentabarf account instead of creating a new one:
lost password: https://penta.fosdem.org/user/forgot_password
Talks are either 50 minutes or 20 minutes long, plus 5 minutes for
questions.
All talks will be recorded, and will be streamed out live, and will
later be made available as CC-BY, sometimes minutes after your talk has
finished.
As for deadlines, the fosdem organizers want to have a finished schedule
by the 15th of december, but do not count on that deadline, there are
only a limited number of slots available. Given my belatedness in
sending out this CFP, i might get a few more days if i am really really
nice to the core FOSDEM organizers, but again, do not count on that
(extra hugs only go so far when you're built like i am).
On your personal page:
* General:
* First and last name
* Nickname
* Image
* Contact:
* email address
* mobile number (this is a very hard requirement as there will be no
other reliable form of emergency communication on the day)
* Description:
* Abstract
* Description
Create an event:
* On the General page:
* Event title
* Event subtitle.
* Track: Hardware Enablement Devroom
* Event type: Lecture (talk) or Meeting (BoF)
* Persons:
* Add yourself as speaker.
* Description:
* Abstract:
* Full Description
* Schedule:
* select your preferred talk length, either 55 or 25 minutes.
* Links:
* Add relevant links.
The mobile phone number is the hardest requirement, so you can be
contacted on-the-day when something comes up. Speakers will all receive
my mobile number in return.
Neither email nor phonenumber are publicy visible, nor will this
information be used for anything outside of devroom organization. After
your talk has been scheduled, i usually only send out a single email
with some organizational details in the days before the event.
Everything else can be ignored or will be filled in by me or the FOSDEM
organizers.
I will be keeping a keen eye on your submissions and will come back with
further questions or make small fixes as needed. Feel free to poke me
with any questions or anything, both on irc (libv@freenode) and on
email (hardware-devroom-manager(a)fosdem.org).
That's about it. Hope to see you all at FOSDEM :)
Luc Verhaegen.
> As the subject line states, here is the output of 'flashrom -VV -p ch341a_spi':
>
> flashrom v1.1 on Linux 5.0.0-37-generic (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.5.2, GCC 7.4.0, little endian
> Command line (3 args): flashrom -VV -p ch341a_spi
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Initializing ch341a_spi programmer
> Device revision is 3.0.4
> The following protocols are supported: SPI.
> Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
>
> ....
>
> SFDP number of parameter headers is 2 (NPH = 1).
>
> SFDP parameter table header 0/1:
> ID 0x00, version 1.0
> Length 36 B, Parameter Table Pointer 0x000030
> Parsing JEDEC flash parameter table...
> 3-Byte only addressing.
> Status register is non-volatile and the standard does not allow vendors to tell us whether EWSR/WREN is needed for status register writes - assuming EWSR.
> Write chunk size is at least 64 B.
> Flash chip size is 8192 kB.
> Block eraser 0: 2048 x 4096 B with opcode 0x20
> Tried to add a duplicate block eraser: 2048 x 4096 B with opcode 0x20.
> Block eraser 1: 256 x 32768 B with opcode 0x52
> Block eraser 2: 128 x 65536 B with opcode 0xd8
> done.
>
> SFDP parameter table header 1/1:
> ID 0x20, version 1.0
> Length 16 B, Parameter Table Pointer 0x000060
> ===
> 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!
> ===
> Found Unknown flash chip "SFDP-capable chip" (8192 kB, SPI) on ch341a_spi.
> Probing for AMIC unknown AMIC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for Atmel unknown Atmel SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for Eon unknown Eon SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for Macronix unknown Macronix SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for PMC unknown PMC SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for SST unknown SST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for ST unknown ST SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for Sanyo unknown Sanyo SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for Generic unknown SPI chip (RDID), 0 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
> Probing for Generic unknown SPI chip (REMS), 0 kB: probe_spi_rems: id1 0x20, id2 0x16
> Found Unknown flash chip "SFDP-capable chip" (8192 kB, SPI).
> No operations were specified.
>
Maybe I am mistaken, but I have not seen the actual partnumber of the
chip in the mail. Do you have opportunity to test read/write/earse
functions?
Br,
Miklos
hi there at flashrom.org, while following the procedure described in
https://ostoday.org/linux/how-to-boot-ubuntu-from-usb-on-chromebook.html
to'install the https://johnlewis.ie/Chromebook-ROMs/ for my baywell
gnawty not yet listed in
https://johnlewis.ie/custom-Chromebook-firmware/rom-download/ and
hopefully not bricked i am told by flashrom itself that i am supposed
to report a bug in flashrom:
INPUT REQUIRED: About to flash your gnawty's RW_LEGACY slot, repeat
'If this bricks my gnawty, on my head be it!' observing exact case
and punctuation: If this bricks my gnawty, on my head be it!
+ echo ''
+ [[ If this bricks my gnawty, on my head be it! != \I\f\ \t\h\i\s\
\b\r\i\c\k\s\ \m\y\ \g\n\a\w\t\y\,\ \o\n\ \m\y\ \h\e\a\d\ \b\e\ \i\t\!
]]
+ sudo flashrom -w -i RW_LEGACY:legacy-seabios-baywell-latest.cbfs
flashrom v0.9.9 : 35f1c70c : Sep 12 2019 16:01:11 UTC on Linux
4.4.190-16770-gb3c36ab5af98 (x86_64)
flashrom v0.9.9 : 35f1c70c : Sep 12 2019 16:01:11 UTC on Linux
4.4.190-16770-gb3c36ab5af98 (x86_64)
Calibrating delay loop... OK.
coreboot table found at 0x7ae6e000.
Found chipset "Intel Baytrail-M". Enabling flash write... SPI
Configuration is locked down.
OK.
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Trying to unmap a nonexisting mapping!
Please report a bug at flashrom(a)flashrom.org
Block protection could not be disabled!
spi_write_cmd failed during command execution at address 0x0
spi_simple_write_cmd failed during command execution
spi_simple_write_cmd failed during command execution
Erasing and writing flash chip... Verifying flash... VERIFIED.
SUCCESS
+ readonly AREA
+ readonly R_OR_W
+ echo '
INFO: Good, your gnawty'\''s RW_LEGACY slot was written successfully.
You can hopefully, safely reboot!
'
INFO: Good, your gnawty's RW_LEGACY slot was written successfully.
You can hopefully, safely reboot!
+ rm_files
+ rm -rf /tmp/flash.crbk.rom
+ exit 0