flashrom June 2019

flashrom@flashrom.org

13 participants
17 discussions

Flash chip in unknown state!
by Max Bell 08 Jun '19

08 Jun '19

Hello, Ijust discovered this project and thought I would try it out on a spare Gigabye GA-N3050-D3P board that I had in storage. Unfortunately, flashing the modified image back to the board fails during the verify step. The same thing happens when I attempt to write the original BIOS back to the board, so I'm stuck with a presumably bricked board. Below is (I hope) all the relevant information you need. I've also attached the original and modified BIOS images. Board: Gigabye GA-N3050-D3P Chip: MX25U6435F (8192 kB) Flashrom ver: 1.0.1 Using Raspberry Pi and Pomona 5252 for SPI interface Verifying flash... FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0xc0d48 Your flash chip is in an unknown state. Thanks, Max Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Re: N25Q128A
by Buhrow, Simon 06 Jun '19

06 Jun '19

I found the error: I had a signal integrity problem. The chip now is detected correctly as N25Q128..3E . All commands execute correctly. So please forget my las mail/post as the chip is already in the flashrom database and working fine!! (as my N25Q128A is a N25Q128..3E ) Sorry! Simon

1 0

about ASUS H110M-E M.2 board with GD25B128CPIG 16MB bios chip
by Pavel Sayekat 06 Jun '19

06 Jun '19

Dear FlashromTeam, if it helps any, (ASUS-H110M-E M.2 board with GD25B128CPIG 16MB bios chip) flashrom -p internal flashrom v1.1-rc1-6-g7eb38aa on Linux 5.1.6-gnu-1 (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 chipset "Intel H110". This chipset is marked as untested. If you are using an up-to-date version of 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... Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0xdc from 0xaa to 0x89 failed. New value is 0xaa. SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only. FREG2: Management Engine region (0x00001000-0x0027ffff) is read-only. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME for details. At least some flash regions are write protected. For write operations, you should use a flash layout and include only writable regions. See manpage for more details. Enabling hardware sequencing because some important opcode is locked. PROBLEMS, continuing anyway Found Programmer flash chip "Opaque flash chip" (16384 kB, Programmer-specific) mapped at physical address 0x0000000000000000. No operations were specified.

1 1

Erase/write fail, could you help me?
by William Schmitt 04 Jun '19

04 Jun '19

I believe the chip is proprerly connected, i guess its a code problem, but if isnt, then its the chip... Could you guys help me? This is the log from terminal: sudo flashrom -p serprog:dev=/dev/ttyACM0:115200,spispeed=100k -w BIOS.FI [sudo] senha para wizogales: flashrom v0.9.9-r1954 on Linux 4.9.0-9-amd64 (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. serprog: Programmer name is "frser-duino" serprog: requested mapping AT45CS1282 is incompatible: 0x1080000 bytes at 0x00000000fef80000. Found Macronix flash chip "MX25L4005(A/C)/MX25L4006E" (512 kB, SPI) on serprog. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x0000fffd! Expected=0xff, Found=0xfc, failed byte count from 0x0000f000-0x0000ffff: 0x3 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0x5c0c ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x0000fff4! Expected=0xff, Found=0xfe, failed byte count from 0x00000000-0x0000ffff: 0xc ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0xa0, failed byte count from 0x00000000-0x0007ffff: 0x7659a ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0007ffff: 0x765b5 ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has changed. 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!

1 0

Supprot new St95XXx series
by evrinoma＠gmail.com 04 Jun '19

04 Jun '19

Hi Tell me, please, how to post a patch? I added support ST95XXX chips. I've done tested, all chip-sets reads , erases, writes and verifies successfully. Only st95xxxA125 series chipsets respond to RDID request, what why force key logic was improve. chip-set STM95080 STM95160 STM95320 STM95640 STM95128 STM95256

2 2

N25Q128A
by Buhrow, Simon 04 Jun '19

04 Jun '19

Hi, see attached files for success in probe, read and erase for the N25Q128A Flash from Micron. Write-cmd fails. See write_flash.log for details. I will investigate it the next weeks. Any suggestions are welcome. Regards, Simon PS: @Nico Huber: Thanks for your mail. I got the aforementioned error solved: I had a bad formatted hyphen at the '-w' parameter. (As I copied the command from a notepad on my windows system) -----Ursprüngliche Nachricht----- Von: Nico Huber <nico.h(a)gmx.de> Gesendet: Montag, 3. Juni 2019 17:27 An: Buhrow, Simon <simon.buhrow(a)sieb-meyer.de> Betreff: Re: N25Q128A Hello Simon, your mail got filtered because of its size, we have a limit of 256KiB. If you could send your modification as a `diff`, that would be nice. Have a look here, for more instructions: https://flashrom.org/Development_Guidelines Regarding your error: > Error: Extra parameter found. > Please run "flashrom --help" for usage info. I've no idea what could have caused it. You can add `-o logfile.txt` to your flashrom command and attach the resulting log file to your mail. Maybe it can tell us more. Regards, Nico

1 0

[announce] flashrom 1.1-rc2
by Nico Huber 03 Jun '19

03 Jun '19

Hello flashrom friends, after an unannounced rc1, we now have a `v1.1-rc2` in Git. During the 1.5 years since v1.0, we have merged SPI 4-byte address support, about half a dozen new programmers and a lot of flash chips. Preliminary release notes can be found at [1], and the full list of supported hardware at [2]. Happy testing! If you don't use Git, you can find a tarball at [3]. Best regards, Nico [1] https://flashrom.org/Flashrom/1.1 [2] https://flashrom.org/Flashrom/1.1/Supported_Hardware [3] https://review.coreboot.org/cgit/flashrom.git/snapshot/flashrom-1.1-rc2.tar…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom June 2019