flashrom March 2023

flashrom@flashrom.org

21 participants
27 discussions

Start a nNew thread

Ch341a support on 1.3
by Joe h 17 Mar '23

17 Mar '23

2 1

flashrom & flashrom-stable could/should they share resources?
by Nico Huber 16 Mar '23

16 Mar '23

Hi all, since the idea to create a new project "flashrom-stable" on coreboot.org I was wondering how the two projects could coexist best and if they should share resources like the webpage / wiki. Any thoughts on this? Related: If participating in things like GSoC should we do that together? It seems most topics are applicable to both projects anyway. Cheers, Nico PS. I'll also put this on tomorrows meeting agenda.

1 1

report progress to std
by Saeid Yazdani 15 Mar '23

15 Mar '23

Hi all, Is there a way/switch to write flash progress into std. I want to create a graphical wrapper for flashrom and want to show the progress on the screen. I tried to use different verbose switches but it is kind of not easy to parse.

1 0

flashrom facing error
by Zhai, MingXin (Duke) 15 Mar '23

15 Mar '23

[AMD Official Use Only - General] hi Flashrom owner, I want use this tool on my laptop,but it show error as bellow: could you please give me some suggest? ------------------------------------------------------------------------------------------------ root@TEST-VN:/home/scbu# flashrom -p internal -r 1.bin flashrom v1.2 on Linux 5.19.0-1523438.22.04.amdgpu.amd64 (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). No DMI table found. Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x71 does not match known values. Please report this to flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> and include this log and the output of lspci -nnvx, thanks!. Could not determine chipset generation.PROBLEMS, continuing anyway ======================================================================== You may be running flashrom on an unknown laptop. We could not detect this for sure because your vendor has not set up the SMBIOS tables correctly. Some internal buses have been disabled for safety reasons. You can enforce using all buses by adding -p internal:laptop=this_is_not_a_laptop to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.

1 0

Flashrom fails to update ME on Intel idaville HCC platform
by Stan Jiang 15 Mar '23

15 Mar '23

Hello developer team, On the Intel idaville HCC platform, as long as there are differences in the ME settings between the currently booted BIOS and the image to be updated, the flashrom will prompt that the erase failed when updating the ME This is the platform information I added in chip_enable.c { 0x8086,0x18DC, B_S, NT, "Intel", "idaville", enable_flash_c620}, The attachment is the log of the update success and update failure Do I need to add specific settings for the Intel idaville HCC platform to update the BIOS (ME settings are different)? Thanks. An example of a failed update below: [root@localhost home]# ./flashrom -p internal:boardenable=force -w CB2.1.01.04.bi flashrom unknown on Linux 4.18.0-240.el8.x86_64 (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). No DMI table found. Found chipset "Intel idaville". 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... SPI Configuration is locked down. Enabling hardware sequencing because some important opcode is locked. OK. Found Programmer flash chip "Opaque flash chip" (65536 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Reading old flash chip contents... done. Erasing and writing flash chip... Transaction error between offset 0x00001000 and 0x00001fff (= 0x00001000 + 4095)! Reading current flash chip contents... done. Looking for another erase function. Looking for another erase function. Looking for another erase function. Looking for another erase function. Looking for another erase function. Looking for another erase function. 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. Good, writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this to the mailing list at flashrom(a)flashrom.org or on IRC (see https://www.flashrom.org/Contact for details), thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running. [root@localhost home]#

1 0

failed to write w25q256jw with v1.2-1227
by Eric G 11 Mar '23

11 Mar '23

Hi, My chip is in an unknown state after trying to write. I tried ch341a_spi and linux_spi. I have three log files. https://paste.flashrom.org/view.php?id=3677 https://paste.flashrom.org/view.php?id=3676 https://paste.flashrom.org/view.php?id=3675 Any suggestions on how I can get this to work? Any other testing I can do for the developers? Thank you.

2 1

flashrom dev meeting notes 08.03.2023
by Anastasia Klimchuk 10 Mar '23

10 Mar '23

# 8th March 2023, 21:00 - 22:00 UTC+0 Attendees: Thomas, Prakhar, Anastasia ## Decision summary * We will be using CreativeCommons license for documentation, CC-BY-4.0 * 26th April on this meeting will be a “development guidelines brainstorming session”. Everyone with ideas on how to improve development guidelines is welcome to join. * 3 weeks break for meetings between 22th March and 12th April. And then every 2 weeks as usual. ## Agenda * [aklm] We wanted to have a “development guidelines brainstorming session” after the release. Seems the time has come? We can allocate the next meeting for this? Or maybe the next meeting in April, depending on who wants to join. * Yes we can do it on 26th of April. We can create a doc for brainstorming, and everyone will edit it. Once the text is composed, then it can be added to documentation. * [Thomas] How should we license the new documentation? GPL / CreativeCommons / something else * GPL is optimised for code/software * and then CreativeCommons is for everything, not just code/software * what is the level of CreativeCommons license that would be equivalent to what we have now? CC-BY -> do everything that you want, but have to name the original authors. * [https://doc.coreboot.org/documentation_license.html](https://doc.coreboot.o… coreboot has different license for code vs documentation. * that would enable people to write a tutorial based on new docs. * Do we need to add a line to every doc? * (..|//| #) SPDX-License-Identifier: CC-BY-4.0 * we can add git hook to check for this one line * The one-line can be used for code too, with the existing license. Would save repetition of the same text in every file. * [aklm] can we do a 3 week gap between the last meeting in March and first in April? and then 2 weeks as usual. * Yes, we will have a meeting on the 22nd of March as usual, and then 12th April, and then every 2 weeks as usual. -- Anastasia.

1 0

UEFI password
by Paul Pascut 08 Mar '23

08 Mar '23

Hello, my name is Paul, thank you for the great work you are doing! I have bought an HP laptop (elitebook 840 g2) from a company that sat an administration password on the UEFI. I tried to remove it using the UEFI procedure but it was not enrolled... I tried removing the bios battery but it didn't work... I was wondering if flashing the BIOS chip could reset the password. Do you know if it is possible? do you have any advice how to do it? Best regards, Paul P.S. I have a IC CH341A USB Programmer with the chip clip

2 1

Mother MSI H97 PC Mate
by Guillermo Reisch 08 Mar '23

08 Mar '23

Mother home page https://www.msi.com/Motherboard/H97-PC-Mate SO: Debian SID (x86_64) FlashROM version: guille@goku:~/Desktop/7850v59$ dpkg -l flashrom Deseado=desconocido(U)/Instalar/eliminaR/Purgar/retener(H) | Estado=No/Inst/ficheros-Conf/desempaqUetado/medio-conF/medio-inst(H)/espera- disparo(W)/pendienTe-disparo |/ Err?=(ninguno)/requiere-Reinst (Estado,Err: mayúsc.=malo) ||/ Nombre Versión Arquitectura Descripción +++-==============-============-============- ============================================================= ii flashrom 1.3.0-2 amd64 Identify, read, write, erase, and verify BIOS/ROM/flash chips LOG: guille@goku:~/Desktop/7850v59$ sudo flashrom -p internal -r backup.bin -V flashrom unknown on Linux 6.1.0-5-amd64 (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). flashrom was built with GCC 12.2.0, little endian Command line (5 args): flashrom -p internal -r backup.bin -V Initializing internal programmer /sys/class/mtd/mtd0 does not exist No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Desktop" DMI string system-manufacturer: "MSI" DMI string system-product-name: "MS-7850" DMI string system-version: "1.0" DMI string baseboard-manufacturer: "MSI" DMI string baseboard-product-name: "H97 PC Mate(MS-7850)" DMI string baseboard-version: "1.0" Found chipset "Intel H97" with PCI ID 8086:8cc6. 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... Root Complex Register Block address = 0xfed1c000 Error accessing ICH RCRB, 0x4000 bytes at 0x00000000fed1c000 /dev/mem mmap failed: Operation not permitted FAILED! FATAL ERROR! Error: Programmer initialization failed.

2 3

showing progress or remaining time on stdout
by Sean Dekker 08 Mar '23

08 Mar '23

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom March 2023