flashrom

flashrom@flashrom.org

5 participants
9161 discussions

SST49LF160C in Wyse S10
by Michał Witek 28 Mar '19

28 Mar '19

Hi. I just successfully flashed SST49LF160C on a Wyse S10 terminal and it works fine, so it looks like the chip is fully supported. I'm letting You know, because there are some questions marks in "supported hardware" table near this one. root@OpenWrt:/# flashrom -p internal -w /tmp/2rom.rom -c SST49LF160C flashrom v1.0 on Linux 4.14.95 (i586) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. No DMI table found. Found chipset "AMD CS5536". Enabling flash write... OK. Found SST flash chip "SST49LF160C" (2048 kB, LPC) mapped at physical address 0xffe00000. === This flash part has status UNTESTED for operations: 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 old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.

1 0

Dual boot MCU
by Stuart Johnson 22 Mar '19

22 Mar '19

I have an MCU that can boot from two locations of it's flash. The flash is 2097152 bytes, and the MCU will boot from location 0 or half way. So I created a layout file, like so: 00000000:0000fffff bank0 00100000:0001fffff bank1 But flashrom is demanding the image to be written is the full 2097152 bytes. What am I missing? flashrom -p .... --layout my_layout --image bank0 -w flash.bin Error: Image size (1048576 B) doesn't match the flash chip's size (2097152 B)!

1 0

BIOS Rom for DX79SI
by Adee Bin Shahid 19 Mar '19

19 Mar '19

Sir, I wish to know if flashrom has support for Intel DX79SI motherboard, since I couldn't find the board enlisted on the flashrom website. However, I did find the link below, and I want to verify. https://mail.coreboot.org/pipemail/flashrom/2013-March/010653.html I shall be entirely grateful. Regards, Adee Bin Shahid

1 0

probleme read flashrom
by sebchami＠gmx.com 15 Mar '19

15 Mar '19

Hello, I'm tried to read bios of PCB Western Digital to write it on a new PCB. But I have a problem. I use Ubuntu OS version 16.04. This is the error message what I have I write the command "sudo flashrom --programmer ch341a_spi -r new.bin : before this command, I have installed package with the command "sudo apt install flashrom" ************** itr@itr-K52Je:~$ sudo flashrom --programmer ch341a_spi -r new.bin flashrom v0.9.9-rc1-r1942 on Linux 4.4.0-142-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ch341a_spi. === This flash part has status NOT WORKING 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! Read is not working on this chip. Aborting. *************************** Can you help me, please, Thanks you Sebastien

2 1

buildbot.flashrom.org
by Сергій Новосад 15 Mar '19

15 Mar '19

Hello! buildbot subdomain not responding, cant download flashrom for DOS

1 0

report: Winbond flash chip "W25Q32.V" is in an unknown state.
by Владимир Суворов 12 Mar '19

12 Mar '19

Reporting (see screenshot), bios was flashed correctly and motherboard is now [image: Report W25Q32V.png] working.

2 1

Wont flash bios
by Frei Bjerkestrand 12 Mar '19

12 Mar '19

I have an ch341a programmer and an W25Q128.W Winbond Chip, im trying to flash a custom bios where I just change the serial numbers. Flashing the backup bios works but flashing any other roms ends up in an error mess. I have tried to just erase it with -E but with no luck. ------------------------------------------------------------------------------------ > sudo flashrom -p ch341a_spi -w freiZeroed flashrom v1.0 on Linux 4.18.0-15-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 ch341a_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! Block protection could not be disabled! Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00200000! Expected=0xff, Found=0x5f, failed byte count from 0x00200000-0x00200fff: 0x2bb ERASE FAILED!

2 2

Re: Wont flash bios
by Angel Pons 12 Mar '19

12 Mar '19

Hello, Your reply did not reach the mailing list. Please use "Reply to all" so that your messages can reach more people than just me. On Tue, Mar 12, 2019, 09:06 Frei Bjerkestrand <frei.bjerkestrand(a)hotmail.no wrote: > No I'm pretty sure the 1.8V is connected. Should I try to disassemble the > programmer and the 1.8V converter and assemble it again? > So you are using a 1.8V converter between the programmer and the chip? Regarding the original issue: If you can not change any bytes, I would suspect the flash chip is write-protected. Check its datasheet, it is likely pin 3 is somehow pulled low (write-protect pin is usually active when low). Regards, Angel Pons >

1 0

[announce] flashrom 1.0.1-rc2
by Nico Huber 07 Mar '19

07 Mar '19

Hey folks, so here's another RC for flashrom 1.0.1. Single change since RC1: * a3db7ed5 Fix erasing of unaligned regions This never worked correctly from the beginning. We completely erased every block that touched an included layout region. Now, we restore surrounding data in case a block expands beyond the region. 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-rc2.t… If there is no further issue, the release is due next week. Best regards, Nico

1 0

[announce] flashrom 1.0.1-rc1
by Nico Huber 04 Mar '19

04 Mar '19

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

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom