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
Hi flashrom fellows,
I've just tagged `v1.0.1-rc1`. This is only a bug-fix release, obviously
the first on our 1.0.x branch. The latest commit is rather new, so
please test! Especially your layout use cases.
During the past year, we've gathered a total of 6 fixes! Namely:
* 6b9e934f linux_spi: Reduce maximum read chunksize
Improves compatibility with older Linux kernels that interpreted the
interface differently.
* 30c4cecd Makefile: Disable `-Werror=deprecated-declarations` on
release branch
Just to be able to compile the 1.0.x branch on newer systems.
* 5639af64 linux_spi: Hardcode default spispeed of 2MHz
Default speed of kernel drivers isn't always sane (any more).
* 993e162d dediprog: Fix small, unaligned reads
An actual bug, discovered during experiments with arbitrary
layouts.
* ec8b8a7f board_enable.c: Fix dmi_match string for ThinkPad X201
Probably just wasn't tested before.
* 69f96f60 Fix verification with sparse layouts
A regression that sneaked into flashrom-1.0: When verifying the
whole flash after a partial write with a sparse layout (i.e.
a layout whose regions don't cover the whole chip), flashrom
tried to verify against the wrong data and failed.
Again, please test. If you don't use Git, you can find a tarball here:
https://review.coreboot.org/cgit/flashrom.git/snapshot/flashrom-1.0.1-rc1.t…
It still passes all my local build tests, see below for a full list.
Best regards,
Nico
Build-tested in Docker images for the following targets:
NetBSD 7.1 amd64
NetBSD 7.1 i386
centos:7.3-aarch64-clean
centos:7.3-amd64-clean
centos:7.2-amd64-clean
fedora:25-x86_64
fedora:24-x86_64
fedora:25-ppc64le
fedora:25-aarch64
debian-debootstrap:ppc64el-stretch
debian-debootstrap:arm64-buster
debian-debootstrap:armhf-stretch
debian-debootstrap:mips-stretch
debian-debootstrap:mipsel-stretch
debian-debootstrap:amd64-sid
debian-debootstrap:amd64-buster
debian-debootstrap:amd64-stretch
debian-debootstrap:i386-sid
debian-debootstrap:i386-buster
debian-debootstrap:i386-stretch
ubuntu-debootstrap:arm64-bionic
ubuntu-debootstrap:arm64-xenial
ubuntu-debootstrap:amd64-bionic
ubuntu-debootstrap:amd64-xenial
ubuntu-debootstrap:i386-bionic
ubuntu-debootstrap:i386-xenial
alpine:aarch64-v3.8
alpine:armhf-v3.8
alpine:amd64-v3.8
alpine:amd64-v3.7
alpine:amd64-v3.6
alpine:i386-v3.8
alpine:i386-v3.7
alpine:i386-v3.6
djgpp:6.1.0
hello ;
by this i report a successful read of Winbond flash chip "W25Q128.W" (16384
kB, SPI)
board : NOKIA phone 3310 (2017) TA-1030
using loader from : https://github.com/xobs/fernly
patch applied to flashrom :
https://github.com/xobs/fernly/blob/master/flashrom-fernvale.patch
thankd:
attached is th log:
-------------------------------------------------------------------------------------------
dr@dr-VirtualBox:~/fernly-master/flashrom-1.0$ sudo ./flashrom --programmer
fernvale_spi:dev=/dev/fernvale --read flash.dat
flashrom v1.0 on Linux 4.15.0-45-generic (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 "W25Q128.W" (16384 kB, SPI) on fernvale_spi.
===
This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
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... done.
I have used following command to program my Acer C720:
./flashrom -p internal:ich_spi_forces=yes -V -N --ifd -i bios -w peppy/coreboot-peppy-seabios-latest.ro m > ferr.txt 2>&1
The eprom chip in this computer is: 25Q64FVSIG and yes I have remover write protection screw.
I have received following response from this flashrom command:---------flashrom v1.0 on Linux 4.9.0-8-amd64 (x86_64)flashrom is free software, get the source code at https://flashrom.org
flashrom was built with libpci 3.5.2, GCC 6.3.0 20170516, little endianCommand line (9 args): ./flashrom -p internal:ich_spi_forces=yes -V -N --ifd -i bios -w peppy/coreboot-peppy-seabios-latest.romUsing clock_gettime for delay loops (clk_id: 1, resolution: 1ns).Initializing internal programmerFound candidate at: 00000500-00000510Found coreboot table at 0x00000500.Found candidate at: 00000000-00000194Found coreboot table at 0x00000000.coreboot table found at 0x7becf000.coreboot header(24) checksum: 72d0 table(404) checksum: f9e3 entries: 10Vendor ID: GOOGLE, part ID: PeppyUsing Internal DMI decoder.DMI string chassis-type: "Desktop"DMI string system-manufacturer: "GOOGLE"DMI string system-product-name: "Peppy"DMI string system-version: "1.0"DMI string baseboard-manufacturer: "GOOGLE"DMI string baseboard-product-name: "Peppy"DMI string baseboard-version: "1.0"Found chipset "Intel Lynx Point LP Mainstream" with PCI ID 8086:9c45.This chipset is marked as untested. If you are using an up-to-date versionof flashrom *and* were (not) able to successfully update your firmware with it,then please email a report to flashrom(a)flashrom.org including a verbose (-V) log.Thank you!Enabling flash write... Root Complex Register Block address = 0xfed1c000Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000/dev/mem mmap failed: Operation not permittedFAILED!FATAL ERROR!Unhandled programmer parameters (possibly due to another failure): ich_spi_forces=yesError: Programmer initialization failed.--------
Also please find attached output of dmidecoed from this C720 computer:
I will appreciate any suggestion.
After a failed HP ME firmware on my HP Z200 the computer did displays a "management platform in manufacturing mode" message during bootup, and when I boot into windows my computer shuts off by itself after about 30 minutes.
After Googling arround i found the some one with exact the same issue see: https://www.win-raid.com/t4165f39-Z-switches-off-after-minutes-unable-to-Ct…
After reading this post i ordered the CH341-A and decided to give a try with the modifed BIOS file made by plutomaniac the 7H3_0122.bin
The only difference with the mainbord of Lost_N_BIOS is the BIOS chip, he does have a winbond W25Q64 and i do have a Macronix MXIC MX25L6445E
I've tried to the flash the Bios with a clip but it failed, therefore i soldered the chip on the adapter and tried to flash it again.
But again i get the error:
FAILED at 0x00000000! Expected=0x00, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x33d731
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!
See attached file for a verbose log file
Can you please help me?
Verzonden vanuit Mail<https://go.microsoft.com/fwlink/?LinkId=550986> voor Windows 10
Help! I was following instructions on this page (
https://kodi.wiki/view/Chromebox) to allow the install of a new OS on my
Chromebox. I've successfully run this on HP Chromeboxes, but this ASUS
Chromebox seems to be giving me fits. It returned the following error
message:
VERIFY FAILED at 0x00000086! Expected=0x40, Read=0xc0, failed byte count
from 0x00000000-0x00ffffff: 0x2
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net (channel #flashrom) or email
flashrom(a)flashrom.org with FAILED: your board name in the subject line!
DO NOT REBOOT OR POWEROFF!
FAILED
--------------------------
An error occurred flashing the Full ROM firmware. DO NOT REBOOT!
I haven't touched it yet so it's still waiting. What can I do to get it
back on track? Please let me know if you need any additional information.
V/R,
-Nathan
Hello all.
Flashing MSI 945GZM6-F succeeded perfectly.
It helped me automatically installing 23 workstations using PXE, while
the previously installed BIOS had a bug in the PXE ROM.
No need to say how happy I am to save all these motherboard. They are
now in use for free by refugees. Obsolete systems for Windows, great
machines for Linux. Another miracle by the open source community.
Many thanks.
Daniel.
--
Daniel Debaste
Avenue des Pléiades, 29
1300 Limal
daniel.debaste(a)gmail.com
010/40.27.98
0486/68.29.97
Hi Sven,
On Sun, Feb 17, 2019 at 11:37 AM Sven AOL <SFrey76225(a)aol.com> wrote:
>
> After replacing the new memory IC, the memory contents are missing. The flashfile is not the "software update file" from the manufacturer of the device. Or is a software update always the whole file written on the IC?
>
Maybe this software update updates only a small part of your device
memory contents - I don't know.
>
> In my repair I downloaded the offered file of the homepage
>
Seems to be a correct approach - maybe someone just made a dump of
complete memory contents and shared it. Have you flashed it already
and is it working?
>
> Do you have a good buy recommendation for a good flash programmer that works well with your software?
>
CH341A USB programmer - it works fine and also very cheap - about $2
or $3 with free shipping from China (e.g. AliExpress) or maybe
slightly more expensive to get it locally. Make sure to get a "green
PCB" version of it and also check that it outputs 3.3V instead of 5V
before using it: there was a small number of (mostly black PCB) CH341A
which gave 5V instead of 3.3V - although it's possible to fix them.
Best regards,
Mike Banon