flashrom

flashrom@flashrom.org

3 participants
9188 discussions

fultility failures
by Fritz Koenig 25 Apr '23

25 Apr '23

Hi, I ran into the following error message: # futility gbb --set --flash --flags=0x39 INFO: write_system_firmware: flashrom -w <IMAGE> -p host -i GBB FAILED at 0x003f5000! Expected=0xff, Found=0x24, failed byte count from 0x003f5000-0x003f5fff: 0xffd ERASE_FAILED FAILED! Uh oh. Erase/write failed. 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! Is that enough information? Is there something else that I can share?

2 1

AMD FP4 - FCH device found but SMBus revision 0x61 does not match known values.
by Daniel Rozsnyó 25 Apr '23

25 Apr '23

Hi, I have an Epyc 2nd gen (Rome) system and I am getting this error: *portable ~ # flashrom --programmer internal* flashrom v1.2 on Linux 6.1.19-gentoo-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 "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x61 does not match known values. Please report this to flashrom(a)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. Thanks for looking into it, Daniel **

1 0

flashrom reviewers gerrit group
by Anastasia Klimchuk 25 Apr '23

25 Apr '23

Hello flashrom community, This email is about our own gerrit group for flashrom reviewers (people who can approve patches in flashrom tree). The idea has been around and has been discussed in various ways for at least a year, and we decided to go ahead with it some time ago (2 months ago I think). Apologies for the delay, finally this is getting done. "flashrom reviewers" group will have permissions to approve patches (+2 / -1 permissions). For submit rights, things stay the same as they are now, "flashrom developers" group has permissions to submit patches. "flashrom reviewers" group will consist of: the whole "flashrom developers" group and all the people who are in flashrom's MAINTAINERS file. There is no script to sync the gerrit group and file, so that will be a human doing that. Which is actually fine. As a summary why we are doing this, there are few reasons. People in the MAINTAINERS file agreed to take care of some part(s) of flashrom, and do code reviews (thank you <3), and naturally they should be able to say "yes I approve the patch". Initial setup was that coreboot reviewers group was used instead (in the absence of flashrom reviewers). However it is really large (>100 people?) and many of them are not working on flashrom and not planning to. Also doesn't work well the other way around: no way to give permissions to someone who works on flashrom, but not on coreboot. Finally the list of members of those gerrit groups is publicly visible, and therefore is a form of documentation: the list of active code reviewers on flashrom. Coreboot group does not give this information. As this change also impacts coreboot community, I will also send an email to coreboot ML (not done yet). Current status. The group was created around a year ago, I picked it from there and added people from the MAINTAINERS file. I need some time to figure out how to wire it in gerrit :) If you have any last moment concerns of being added to the gerrit group, please let me know (by default I assume you agree). Some people already have approval permissions, so you know the process already. For those who are new and only had +1 before, here is the advice: Please read and re-read the development guidelines (https://www.flashrom.org/Development_Guidelines) especially "Patch submission" and "Reviews". Now you need to take care that they are followed, and sometimes educate new contributors ;) Sign-off line is required for every patch. And also important: remember you are not alone, we are the team. You can always add other reviewers if you think you might need help with the patch. There is no way to give granular permissions to "approve patches for this one programmer", it's all flashrom or nothing. Use your best judgement and see above (add other people if unsure). Give me some time to figure out gerrit configs, and I will update the thread when it's done. Thanks! -- Anastasia.

1 1

Updated invitation: Flashrom Dev Meeting @ Co 2 tyg. od 8am do 9am w: czwartek (CEST) (flashrom@flashrom.org)
by mac.pijanowski＠gmail.com 24 Apr '23

24 Apr '23

This event has been updated Flashrom Dev Meeting Co 2 tyg. od 8am do 9am w: czwartek Czas środkowoeuropejski - Warszawa Join with Google Meet https://meet.google.com/iuf-mtri-zva?hs=224 Join by phone (AU) +61 2 9051 6791 PIN: 304642402 More phone numbers https://tel.meet/iuf-mtri-zva?pin=9271993818880&hs=0 Regular meeting of Flashrom project developers. Meeting notes doc: https://docs.google.com/document/d/18qKvEbfPszjsJJGJhwi8kRVDUG3GZ… Guests aklm(a)chromium.org - creator felix.singer12(a)gmail.com david.hendricks(a)gmail.com quasisec(a)google.com nico.h(a)gmx.de src(a)posteo.de martonmiklosqdev(a)gmail.com piotr.krol(a)3mdeb.com Maciej Pijanowski michal.zygowski(a)3mdeb.com th3fanbus(a)gmail.com stefan.k.reinauer(a)gmail.com nartemiev(a)google.com arthur(a)aheymans.xyz flashrom(a)flashrom.org c-d.hailfinger.devel.2006(a)gmx.net gaumless(a)gmail.com chat(a)joursoir.net aarya.chaumal(a)gmail.com sergii.dmytruk(a)3mdeb.com View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=YThrNDBrb2xiOTdh… Reply for flashrom(a)flashrom.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=YThrNDBrb2xiOTdh… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

Updated invitation: Flashrom Dev Meeting @ Co 2 tyg. od 8am do 9am w: czwartek (CEST) (flashrom@flashrom.org)
by mac.pijanowski＠gmail.com 24 Apr '23

24 Apr '23

1 0

Open source contribution
by Jayant Chauhan 24 Apr '23

24 Apr '23

I failed to meet the GSOC deadline but still, I have quite a bit of practical experience with embedded C and assembly but I want to learn new tech that I am not aware of. So, if you think I have the caliber or if you want to test my knowledge you can take an interview. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

2 1

New Flashrom Leadership
by Stefan Reinauer 23 Apr '23

23 Apr '23

Dear Flashrom Community! Today I have a very exciting update for you: As some of you might have already read the announcements in the last few months, the flashrom project has recently decided to split into two separate directions: flashrom, which will modernize its architecture, focus on contemporary systems, rigorous testing, and serve as a platform for the latest and greatest advancements, and flashrom-stable, which will maintain the proven, slower-paced model and focus on keeping old and beloved programmers and flash chips alive. Nico Huber, who has almost a decade of experience with flashrom, is leading the flashrom-stable project. In our recent monthly flashrom meeting on March 22nd [1], we discussed a new leadership structure for the modern flashrom project. We concluded that Anastasia Klimchuk should lead this project, as she has over two decades of software development experience, including significant contributions to flashrom, and an excellent collaborative leadership style. Anastasia will also establish a leadership group for this project to provide a variety of viewpoints and experiences to support flashrom. I'd like to express my heartfelt gratitude to Anastasia for taking on this challenge. I'd also like to extend a warm thank you to Nico for his unwavering commitment to running flashrom-stable. All the best, Stefan [1] t.ly/3tpo

2 1

flashrom dev meeting notes 13.04.2023
by Anastasia Klimchuk 21 Apr '23

21 Apr '23

# 13th April 2023, 6.00-7.00am UTC+0 Attendees: Alex, Anastasia ## Decision summary * Reminder: next meeting on 27th April we are upgrading Development guidelines ## Agenda * [aklm] What is our procedure to sign the release tarballs? The process for 1.3 was rather chaotic, better have a well-defined process. * How do we validate each other's keys? open question * [heijligen] add Chromebook specific documentation * aklm: maybe we can collect the links to chromebook documentation pages which are publicly visible. It would be good to have a page on the website which is a collection of documentation specific to chromebooks. TODO aklm try to find out. -- Anastasia.

1 0

Unable to build flashrom from git repo without sphinx
by Alex Perez 21 Apr '23

21 Apr '23

Hi there, It doesn’t seem possible to cleanly build flashrom without installing a TON of dependencies. The build assumes sphinx-build is present, and shits a brick once it can’t find it. This is not user-friendly behavior.

5 8

Intel C236 successful write
by Tomas 16 Apr '23

16 Apr '23

Hi, I performed a successful write with "-p internal" on the Intel C236. I atach the output text file. /Tomas

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom