flashrom November 2017

flashrom@flashrom.org

23 participants
40 discussions

flashrom not "seeing" W25Q128FV
by Yaron Shragai 20 Nov '17

20 Nov '17

Hello, I am trying to use flashrom to program a Winbond W25Q128FV chip, on a Supermicro X10DRT-L mobo, with a Dediprog SF 100. I am running flashrom from an Ubuntu VM on a Win10 laptop as well as from a Minnowboard Max system running Ubuntu. I am running flashrom v0.9.9-rc1-r1942, installed via apt. I am connecting to the chip via a SOIC clip. I should note that I have looked at the product support data on the flashrom web site. It lists full support for the W25Q128FV. It does not list the X10DRT-L mobo. flashrom almost never "sees" the flash chip (output: "No EEPROM/flash device found."). I say "almost", b/c it did see it a couple of times (out of, I would say, ~100 tries) - which was enough for me to read out the pre-existing content, and write to it an image that has effectively bricked it. :-) So, now I'm trying to flash the pre-existing content back... (There is no documented way to force the X10DRT-L to use the recovery block, and I have yet to find an undocumented way...) I have tried with the system board plugged in and unplugged, and with and without connecting the VCC pin to the programmer. I have been using these two command lines, at various times: flashrom -p dediprog flashrom -p dediprog:voltage=3.5 When I add -VVV, the following relevant lines appear in the output: Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region: mapping W25Q128.V from 0x00000000ff000000 to 0x0000000000000000 dediprog_spi_send_command, writecnt=1, readcnt=3 RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff programmer_unmap_flash_region: unmapped 0x0000000000000000 ...and further down... Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: dediprog_spi_send_command, writecnt=1, readcnt=3 RDID returned 0xff 0xff 0xff. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff One more datapoint: When I connect my laptop -> Dediprog -> to the flash chip on the Minnowboard Max (Micron 25Q064A), it does recognize the chip. Any advice would be appreciated! Thanks, Yaron

1 0

Re: [flashrom] working board - elitegroup P6STMT
by Nico Huber 20 Nov '17

20 Nov '17

Hi Branden, On 10.11.2017 19:20, Branden Waldner wrote: > Attached are more log files that the Board Testing HOWTO wiki entry asks for. > > The board name from dmidecode seems to just be the chipset name, sis > 630, rather then the actual board name. Hopefully there is still > something to identify the board with autodetect. Thanks for reporting, I've filed a patch [1] to mark SiS 630 as tested. Though, I don't understand what you want to have auto-detected? From the logs I grasp, that you didn't have to identify anything manually. Nico [1] https://review.coreboot.org/22522

2 1

Re: [flashrom] Addenum12/11/2017 problem when flashing p5b-deluxe : mb marked ok but can't flash
by Nico Huber 19 Nov '17

19 Nov '17

On 12.11.2017 15:17, Marc wrote: > Now using the -VVV option : > > Bonjour everybody, > > May I get your advices ? > > ... > Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000 > /dev/mem mmap failed: Operation not permitted That's a common issue also mentioned in our FAQ [1]. Linux limits access to the hardware. Try booting with iomem=relaxed in your kernel command line. Nico [1] https://www.flashrom.org/FAQ > FAILED! > FATAL ERROR! > Error: Programmer initialization failed. > > > I have bios 0506 and want to write the 1238. > > ONLY EMAIL COMMUNICATION PLEASE. > > Thanks for your attention. > > Gégé >

1 0

Patch to add Librem 15 laptop to flashrom whitelist
by Harry Prevor 19 Nov '17

19 Nov '17

Attached is a patch to whitelist the Librem 15 laptop on flashrom, so that I don't have to write "force_I_want_a_brick" every time I use it. I also added the laptop's info to print.c so it shows up as a supported device. This is my first ever patch, so please let me know if there is anything missing or that I can do to improve it! Added as per this PureOS bug: https://tracker.pureos.net/T170 P.S. Please CC me on any replies as I am not receiving messages from this list. Thanks! -- Harry Prevor http://habs.sdf.org/

3 2

Re: [flashrom] winbond 25q128jvfm
by Nico Huber 19 Nov '17

19 Nov '17

Hi Ron, On 17.11.2017 18:49, ron minnich wrote: > any suggestions on making this part work? I have not done this in a while. its brother 25Q128*F*V is already supported (as W25Q128.V, where . is a wildcard, alas, not matching the *J*V). I'd start by copying the W25Q128.V entry in flashchips.c as W28Q128JV and adding its id to flashchips.h (should be 0x7018). Then carefully compare the copied infos to the new chip's datasheet (instruction table should be most useful) before giving it a shot ;) Nico

1 0

Re: [flashrom] Compiling from source on Chromebook:GalliumOS - can't get libusb?
by Nico Huber 19 Nov '17

19 Nov '17

Hi Anders, On 11.11.2017 17:27, Anders Nelson wrote: > Hi again, > > I don't see details on what image file formats are supported - does > Flashrom use only binary files? yes, that's right, conversion from other formats is out of flashrom's scope. > I see the ROM layout file explanation so I guess I can use that but it > would be nice to use an Intel HEX format if possible. There are already tools to convert such formats to binary and we have no intention to include something like this. Flashrom's task is simply to synchronize the flash chip's contents with those of a file. Though, I'd understand if you miss support to pipe the output of a conversion into flashrom. Nico

2 1

Move PicKit2 form libusb0 to libusb
by tgotic 18 Nov '17

18 Nov '17

Hi, Recently I tried to use flashrom with PicKit2 on Windows. I was unable to get it working with various libusb0 dll's, so I rewrote pickit2_spi.c to use libusb (form libusb.info). Since other external USB programmers use libusb, flashrom doesn't depend on obsolete libusb0 anymore. Please find attached new pickit2_spi.c, patch for Makefile, and a result of write operation. Signed-off-by: Tomislav Gotić <tgotic(a)gmail.com>

1 0

non-working board - asus p2-99 - failed to detect chip
by Branden Waldner 18 Nov '17

18 Nov '17

Flashrom isn't able to detect the flash chip on this board. I've tried while running factory asus p2-99 firmware, with p2b firmware, and with coreboot. This board seems use the same pcb layout as the p2b, but with 440zx northbridge whichs supports only 2 ram slots instead of 3 and with the hardware monitor chip being optional. The vendor aflash tool works while running an asus bios - both p2-99 and p2b, but not with coreboot. I've tried using the piix gpo board enable function on all possible gpos - high and low, but didn't get anywhere, besides finding out gpo0 is the fan. Since the original p2b testing seems to be fairly old - and this board is basically the same - should I test an old version of flashrom? I was going to try 0.9.0, but it does not build nicely, it stops with compiler warnings. Probably could still build it with some cflag adjustments, but I wasn't sure if that was the only problem. I'm mostly just posting this to be compete about it, though any recommendations would be appreciated. ps. The old post I had about a P4S5MG/GL+ board with SiS 650 chipset not working turned out to be the flash chip failing. Figured I might as well mention it.

1 0

spi_send_command invoked on a few chips that don't look to support it
by Kevin Shelton 17 Nov '17

17 Nov '17

Hello, on a board with a GD25Q127C/GD25Q128C and a board with a W25Q128FW, I've observed the below from flashrom --wp-status output: WP: write protect range: spi_send_command called, but SPI is unsupported on this hardware. Please report a bug at flashrom(a)flashrom.org Let me know how I can help.

1 0

winbond 25q128jvfm
by ron minnich 17 Nov '17

17 Nov '17

any suggestions on making this part work? I have not done this in a while.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom November 2017