flashrom December 2024

flashrom@flashrom.org

5 participants
6 discussions

flashrom point release v1.5.1 is out
by Anastasia Klimchuk 22 Dec '24

22 Dec '24

Good day everyone, We have one more release this year (this is the last one of this year, for sure :)). It contains one bug fix for the bug which was introduced in v1.5.0. Bug fix is also merged into the main branch, so building from the latest source works too. Details: Users with older Intel-based platforms (Broadwell/Braswell and earlier) flashing using the internal programmer option might encounter an ‘Invalid OPCODE’ error when erasing/writing which would lead to an incomplete flash and potentially a bricked device. External flashing was not affected at all. Ticket: https://ticket.coreboot.org/issues/573 Patch: https://review.coreboot.org/c/flashrom/+/85612 Release notes: https://flashrom.org/release_notes/v_1_5.html#version-v1-5-1 Git tag: v1.5.1 (in branch 1.5.x) Tarball: https://download.flashrom.org/releases/flashrom-v1.5.1.tar.xz Signature: https://download.flashrom.org/releases/flashrom-v1.5.1.tar.xz.asc Fingerprint: 6E6E F9A0 BA47 8006 E277 6E4C C037 BB41 3134 D111 Thanks heaps to people who helped to do v1.5.1 to get it ready before holidays break! <3 I wish everyone a nice and happy holidays time. -- Anastasia.

1 0

Reg:libmtd: error!: MEMERASE64 ioctl failed for eraseblocks (mtd0)
by Arvind GP 16 Dec '24

16 Dec '24

Hi All, We are trying to implement the flashrom tool utility on the x86 Elkhart Lake(LEC-EL) platform. In this case, we are facing an issue when trying to erase the BIOS device MTD0. There are 4096 erase blocks available in the mtd0 device, but only 1791 erase blocks we can erase; the remaining blocks are throwing errors, and it shows MEMERASE64 IOCTL FAILED. Please see the below error message and MTD0 device info for your reference. NOTE: Sometimes it works; we can erase the MTD0 device without any error, and we can upgrade/downgrade the BIOS. ERROR MESSAGAE: #sudo flash_erase /dev/mtd0 0 0 Erasing 16384 Kibyte @ 0 -- 0 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 0 (mtd0) error 524 (Unknown error 524) flash_erase: error!: Entering into mtd_erase_multi flash_erase: error!: /dev/mtd0: MTD Erase entire chip failureTrying one by one each sector. error 524 (Unknown error 524) Erasing 4 Kibyte @ 700000 -- 43 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 1792 (mtd0) error 5 (Input/output error) flash_erase: error!: /dev/mtd0: MTD Erase failure error 5 (Input/output error) Erasing 4 Kibyte @ 700000 -- 43 % complete cnt 4096 MTD0 INFO:(sudo mtdinfo /dev/mtd0) Name: BIOS Туре: nor Eraseblock size: 4096 bytes, 4.0 KiB Amount of eraseblocks: 4096 (16777216 bytes, 16.0 MB) Minimum input/output unit size: 1 byte Sub-page size: 1 byte Character device major/minor: 90:0 Bad blocks are allowed: false Device is writable: true Please share your inputs on this. Thanks & Regards, Arvind G P.

4 5

request for support programmer with ch341b
by S. 13 Dec '24

13 Dec '24

flashrom supports only programmers with ch341a, but many programmers sold now have ch341b onboard, pid:vid is then 1a86:5523 tnx in advance Stephan

3 12

HP 11MK G9EE - M44236-001 - "W25Q64JW...M"
by Tim Tech 07 Dec '24

07 Dec '24

Hello, attached are two text documents: output from --wp-disable and output from erase/write - let me know if any other information is needed. Chip in question is "W25Q64JW...M" Thanks, Tim

2 4

Splitting flashchips.c
by Anastasia Klimchuk 06 Dec '24

06 Dec '24

Good day, I wanted to confirm that we are splitting flashchips.c file into separate files per vendor. flashchips.c will still stay in the source code but it will be much smaller and will only contain "generic" chip entries. The patch is here: https://review.coreboot.org/c/flashrom/+/83307 , it will be submitted after v1.5.0 tag is done. The patch will not be included in v1.5.0 release. There will be no changes to the usage, and everything that's supported stays the same. If you are a flashrom user who does not look into source code: this does not affect you at all. If you are working on adding support for a chip model: when the patch is submitted (I will post again) you will need to copy your code from flashchips.c into a vendor-specific file. Thank you! -- Anastasia.

1 1

flashrom release v1.5.0 is out
by Anastasia Klimchuk 05 Dec '24

05 Dec '24

Good day everyone, flashrom release v1.5.0 is out! Tarball: https://download.flashrom.org/releases/flashrom-v1.5.0.tar.xz Signature: https://download.flashrom.org/releases/flashrom-v1.5.0.tar.xz.asc Fingerprint: 6E6E F9A0 BA47 8006 E277 6E4C C037 BB41 3134 D111 Checkout from git repository at https://review.coreboot.org/flashrom.git (tag v1.5.0) Release notes published: https://flashrom.org/release_notes/v_1_5.html It has been only 4 months since previous v1.4.0, and yet we have 91 commits made by 24 authors! Release notes explain the details of what was done, and thanks heaps to all the people who did it, reviewed it, and helped in any way <3 All the patches that have been ready and waiting, will be submitted very soon. -- Anastasia.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom December 2024