flashrom December 2022

flashrom@flashrom.org

14 participants
17 discussions

Why start over ( was Re: Starting over; how would you do it?)
by Nico Huber 13 Dec '22

13 Dec '22

Hi Richard, opening a new thread. Let's not derail the existing one before anything was discussed ;) On 19.11.22 21:18, Richard Hughes wrote: > On Sat, 19 Nov 2022 at 17:17, Nico Huber <nico.h(a)gmx.de> wrote: >> I've been thinking more and more about returning to a stable flashrom >> branch lately > > I'm missing the "why". To get back to work. To create something sustainable. As you and many others suggest, I also would like to have a branch that can be kept in a releasable state. First, we need a branch that is in a releasable state. You may have missed the decisions around the 1.3.x branch. The idea seems to be to clean things up on that release branch and for the time being do nothing about the open issues on the master branch. To me that's yet another sign that the current master branch is at a dead end. Nico

3 5

Contributing in GSOC 2023
by ABHISHEK TIWARI 10 Dec '22

10 Dec '22

Hello, I am a full-stack developer looking for organisations to contribute to this summer(GSOC 2023). If you allow me, I would love to contribute to this project's UI/UX part. I have experience I react.js and web development-related technologies, and I am an open-source contributor too, and a contributor of layer5.io and meshery.io. Waiting for your reply Thanks Abhishek Tiwari

1 0

gerrit settings
by Evan Benn 08 Dec '22

08 Dec '22

Hello, https://review.coreboot.org/admin/repos/flashrom,general https://gerrit-review.googlesource.com/Documentation/config-project-config.… I believe some small QOL improvements can be made in the flashrom settings: receive.requireSignedOffBy I think we can set this to true, I have been nagged by Ed enough times to remember to do this. 'Submit type' aka submit.action We use 'cherry pick'. This means each patch in a series says 'merge conflict' because it is being cherry picked without it's parent. It is tedious to submit a chain of patches (I hear) as each needs to wait for HEAD to sync and become the parent commit. The gerrit docs recommend NOT using cherry pick, and using 'rebase always' instead. Can we give it a try? https://gerrit-review.googlesource.com/Documentation/config-project-config.… "the rebase always action can be considered similar to the cherry pick action, but with the important distinction that rebase always does not ignore dependencies, which is why using the rebase always action should be preferred over the cherry pick submit action." Thanks Evan

1 0

unknown 25VG32 + ft2232h
by Arne Jansen 07 Dec '22

07 Dec '22

Hi, I encountered a flash chip that is not known to flashrom. I built flashrom from git, HEAD 153359935aa5. Write reported a fail, the other operations suceeded. Command line was: LD_LIBRARY_PATH=/home/arne/libftdi/build/src/libftdi.so.2 /home/arne/flashrom/flashrom -p ft2232_spi:type=2232H,port=A -w rv901_orig_rom.bin on arch linux (i needed build libftdi from source due to missing symbols in libusb). The datasheet for the chip is probably https://semic-boutique.com/wp-content/uploads/2016/05/ZB25VQ32.pdf Attached are the -VV logs for id, erase, write and read. Repeating write always fail in different places. -Arne

1 1

Project Proposal For GSOC 2023
by Yashashvi Mann 06 Dec '22

06 Dec '22

Respected Sir/Mam, My name is Yashashvi Mann and I am currently an undergraduate in Delhi technological University. I am a GSOC 2023 enthusiast. I have knowledge of HTML, CSS, Java script, Tailwind and React. I believe that I can contribute to the improvement of UI/UX of the flashrom website by specifically making the web site more user friendly and also ADC compliant by adding accesibility plugins as the current website framework majorly lacks it. I can provide more in depth information to it but not sure whom to contact for me to start? If you could guide me, I will be very grateful. Hope to hear from you soon. Regards.

1 0

GD25LQ128C/D error
by Tim Tech 02 Dec '22

02 Dec '22

Hello, I have flashed this chip in the past but suddenly I keep getting this error when writing/verification. I tried two separate flashrom versions, I'll post both error messages below: agimb@agimb-electro:~$ sudo ./flashrom -p ch341a_spi -w rom.rom flashrom v1.2-99-gfbb2b25f61 on Linux 5.15.0-53-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 GigaDevice flash chip "GD25LQ128C/GD25LQ128D" (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! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00002fc3! Expected=0x44, Found=0x04, failed byte count from 0x00000000-0x00ffffff: 0x83 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! ----------------------------------------------------------------------------------------------------------------------- sudo ./flashrom -p ch341a_spi -w rom.rom flashrom v1.2-1028-gbd8a02de6c on Linux 5.15.0-53-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 GigaDevice flash chip "GD25LQ128C/GD25LQ128D/GD25LQ128E" (16384 kB, SPI) on ch341a_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x000168e3! Expected=0x57, Found=0x17, failed byte count from 0x00000000-0x00ffffff: 0x37 Your flash chip is in an unknown state. Please report this to the mailing list at flashrom(a)flashrom.org or on IRC (see https://www.flashrom.org/Contact for details), thanks! Thank you, Tim

2 1

flashrom dev meeting notes week 48/2022
by Felix Singer 01 Dec '22

01 Dec '22

# 30th November, 21:00 - 22:00 UTC+0 Attendees: Anastasia, Felix, Evan, Arthur ## Decision summary * Discussing the remaining issues from the 1.3 tracking ticket, all comments/updates are in the bugtracker * Meeting on 28th December will be canceled ## Agenda * [aklm] Lets go through bugs in the release list [https://ticket.coreboot.org/issues/353](https://ticket.coreboot.org/issues/… * We went through the bugs, end result: * 3 are on aklm * [https://ticket.coreboot.org/issues/354](https://ticket.coreboot.org/issues/… add a paragraph to README for RC1. * [https://ticket.coreboot.org/issues/356](https://ticket.coreboot.org/issues/… check with teammate(s) how is it going * [https://ticket.coreboot.org/issues/372](https://ticket.coreboot.org/issues/… finish two patches which are under review at the moment * 3 are on Felix * [https://ticket.coreboot.org/issues/374](https://ticket.coreboot.org/issues/… check with teammate, response needed * [https://ticket.coreboot.org/issues/375](https://ticket.coreboot.org/issues/… check with teammate, response needed * [https://ticket.coreboot.org/issues/408](https://ticket.coreboot.org/issues/… either do it quickly or re-link to 1.4 * We have some little number of patches to merge as of topic for_1.3.x and once it’s merged we can put a RC1 tag. After the tag is done, send an announcement on the mailing list. * Before 16 December (inclusive) aklm can send an announcement. If it happens later in December, Felix and Angel would need to do it. * Meeting on 28 Dec we cancel (holidays!!)

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom December 2022