SST49LF160C in Wyse S10
by Michał Witek
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.
3 months
Dual boot MCU
by Stuart Johnson
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)!
3 months
probleme read flashrom
by sebchami＠gmx.com
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
3 months, 1 week
buildbot.flashrom.org
by Сергій Новосад
Hello! buildbot subdomain not responding, cant download flashrom for DOS
3 months, 1 week
Wont flash bios
by Frei Bjerkestrand
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!
3 months, 2 weeks
Re: Wont flash bios
by Angel Pons
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
>
3 months, 2 weeks
[announce] flashrom 1.0.1-rc2
by Nico Huber
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...
If there is no further issue, the release is due next week.
Best regards,
Nico
3 months, 3 weeks
