flashrom

flashrom@flashrom.org

3 participants
9189 discussions

EU/AU flashrom dev meeting appointment time change
by Felix Singer 08 Apr '22

08 Apr '22

Hi all, as discussed in the last dev meeting, we can not have one appointment for EU, AU and US people during the time from 1. April until 30. September because of the time change. For this time, we have decided to split the meeting up into one meeting for EU/AU and another one for EU/US and we will alternate between them, so that all groups have a chance to participate. The next meeting will be on 6. April, which will target EU/AU. We created a poll [1] for voting. For EU/AU, we are proposing the following dates (UTC+0): * Monday, Wednesday, Thursday 7:00-8:00 * Monday, Wednesday, Thursday 9:15-10:15 // Felix [1] https://terminplaner4.dfn.de/dBtjEZxKqmcm721C

2 3

flashrom dev meeting notes 7.04.22
by Felix Singer 08 Apr '22

08 Apr '22

# 7th April 2022, 6:00 - 7:00 am UTC+0 Attendees: Martin, Michal, Felix, Anastasia, Nikolai, David, Thomas, Nico, Arthur, Edward ## Decisions Summary * Write a script to email out a summary every weekend. Martin can work on a script. * Gerrit guidelines document. Anastasia will start something. * Start using the redmine bug tracker. There are still issues with it, but we’re going to start using it in its current state and work on it as we go. Felix will work on this. ## Agenda * [FelixS] Hackathons need a reboot. So I’m thinking about doing one. Please share :) * [Poll and some more details](https://terminplaner4.dfn.de/pBooK8FBDlM2zDwa) * Darmstadt, Germany. 10. - 12 June * [Edward] Not every developer has the resources to spend their whole time in IRC and have a spiritual connection with a select few. * How to ensure each code review pass results in a contributor that knows where they stand? - what's next, what's done, when things are going to be merged. * How to avoid walking on eggshells and guessing how to avoid arguments on every contribution but at the same time make tangible progress? * Looks like this topic is closely related to the next one, let's discuss them together? (All notes are done below). * [Edward] How to avoid constant politics in every contribution and instead find a path to allow contributors to not feel ostracized for daring to make a change even when the change may not be useful to others in the immediate sense. * Nikolai: hard to understand whether people are looking at the change, do they have thoughts. Hard to get to know the current status of patch? How to coordinate things? There are many channels? * Nikolai: hard to know whether it is ok. If there is no response, does it mean everything is okay, or no one had a look? * Edward: If people send patches, they need to know what the next step is? * David: gerrit plugin which pings reviewers every 48h ? we need some automation * Edward: observation. Both sides expecting action, or both sides are not sure whose turn? If something is +2 , can it be merged? How to understand that something is ready to merge? * Nikolai: how to ensure there is a consensus? People who are unfamiliar with the process don’t know how to proceed and then give up. * Silicon vendors are unfamiliar with the process. Can they officially support new chips? They attempt to send a patch, and then they are confused on what are next steps. Sometimes good ideas come up in code reviews, and it is not clear who should do that. * David: If adding a new chip requires some refactoring, maybe someone can take that work and do a refactoring? * Edward: We can create a bug in this situation, and prioritize the bug, so that refactor idea is not dropped. * Martin: We need guidelines, maybe “gerrit guidelines”. Coreboot has [https://doc.coreboot.org/contributing/gerrit_guidelines.html](https://doc.c… * Review comments should make clear what is next step * [Edward] How to make the project more accommodating to silicon partners so we can start getting direct support from manufacturers? * Often non-native speakers, * Often not well practiced in free software workflows, * Often need help and guidance to bring them into the fold. * [Edward] How to avoid commits sitting around for years in some weird state between reviewed and unmerged. * Improve project velocity while maintaining stability (improved testing, capture mistakes in tests) * Nico: Can we cherry-pick from coreboot guidelines? Only the bits that apply? * Nico: we can say “write to the mailing list if you don’t know what to do and patch needs attention” * Felix: Can we share the same guidelines as coreboot? We share processes and concepts * Edward: Let's start with our own. Copy-paste and cherry pick model. * Edward: at the end of week an email with the list “everything that has +2”. Martin: We can write it in bash. * [David] We have a GSOC student who wants to do some of the easy projects. Are those projects supposed to be saved for new contributors to have something easy to do? * [Anastasia] The easy projects page needs to be updated, but the projects do need to be done. Since they haven’t been done in 5 years, let’s let the students do them. * [Felix] Employees at companies aren’t interested in doing the easy projects. * [Edward] Let’s adopt the bug tracker and mark bugs as “easy” for people to work on. * [Anastasia] Students should do a single easy project, then move on to a single full project. * [Edward] How to get the mailing list into a usable medium and the code review tools into being for code review only. Move noise to a bug tracker. * Capture ideas in bug tracker. Ideas come up in code reviews, good ideas that need to be done “in a separate patch” and then this is lost. * Felix: some issues left to be configured in the redmine instance. * Nico: we can start using bug tracker with email feature disabled, and then see how it goes. Setup email feature can be the first ticket? * Let’s start using it? * [Edward] How to move to a culture of searched responsibility over constant finger pointing? * Some kind of policy for breakage. * Understanding that software breaks, it is impossible to catch everything in review. * Culture around writing tests and documentation. * Edward: revert policy? Anastasia: There is a thread on mailing list, revert policy is one of the topics

1 0

Join GSoC
by Sayed 08 Apr '22

08 Apr '22

3 2

GSOC 2022
by Wynn K 08 Apr '22

08 Apr '22

Hello, I recently found this project and was wondering if this project was still interested in applicants for the 2022 summer. I was looking into the project ideas and am looking into "Emulate hardware and filesystem in platform-independent way for unit tests" and "Optimize Erase-Function Selection". As many of the projects require programmers, flash chips, and hardware, I was wondering to what extent I would need to have these. I saw the following lists which demonstrate the supported hardware, but I would appreciate it if I could have a more descriptive explanation of what I would need. https://www.flashrom.org/Supported_programmers https://www.flashrom.org/Supported_hardware Additionally, I noticed that some projects want low-level programming, which I would be interested in. However, as I have only a small amount of experience with MIPS, would it not be worthwhile to apply to this position? Thank you for your time

2 1

One Build System Working Group
by Thomas Heijligen 07 Apr '22

07 Apr '22

Hi, As discoursed last dev meeting, we are going to start a working group to adopt meson as single, all cases covering, build system for flashrom. The first step will be to write down all requirements that we need to meet. Therefor, we'll meet today at 8:30 UTC at https://meet.google.com/sag-dyik-bbr and posting the working draft afterwards on the mailing list. The google doc can be visited at any time. https://docs.google.com/document/d/1TVso_VbrLEbGc7BNrYxqlrP8jMxB23TuMqEI3Pn… Please feel free to join the meetings, the next ones will be announced much earlier, add comments to the document or reply to this mail with and question or suggestion. -- Thomas

2 6

ERASE FAILED!
by Pascal Boidart 06 Apr '22

06 Apr '22

Hello Flashrom, I'm on latest Linux Mint. programmer ch341a_spi chip is a Macronix type MX25L6406E I'm trying to erase a chip with: sudo flashrom --programmer ch341a_spi --erase -c "MX25L6406E/MX25L6408E" And I'm getting a erase failed. See log. pascal@pascal-mini:~/Desktop/Flashrom$ sudo flashrom --programmer ch341a_spi --erase -c "MX25L6406E/MX25L6408E" flashrom v1.2 on Linux 5.4.0-107-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 Macronix flash chip "MX25L6406E/MX25L6408E" (8192 kB, SPI) on ch341a_spi. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xfad7 ERASE FAILED! Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xfad7 ERASE FAILED! Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x6b7ef1 ERASE FAILED! Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x6b7ef1 ERASE FAILED! Looking for another erase function. Looking for another erase function. Looking for another erase function. No usable erase functions left. FAILED! 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! Any idea? Thanks Pascal

2 1

Google Summer of Code
by Alp 05 Apr '22

05 Apr '22

1 0

Questions regarding Easy projects
by Prakhar Agrawal 04 Apr '22

04 Apr '22

Hello, Hope you are doing well, I am Prakhar Agrawal, currently pursuing Electronics and Communications Engineering from Amrita Vishwa Vidhyapeetham Amritapuri. (2019-2022). For the past 1 year, I have been working with startups to design and develop low latency embedded devices and have also been actively involved in running and managing the bi0s students club(India's best CTF team) While going through different organizations for GSOC 2022, I found Flashrom, and it caught my interest. I was trying to get familiar with the flashrom code-base through easy projects listed here <https://www.flashrom.org/Easy_projects#Fix_issues_found_by_scan-build> I had a few queries in '*Fix issues found by scan-build':-* - In serprog.c, function static int sp_stream_buffer_op( ), if (!sp) { msg_perr("Error: cannot malloc command buffer\n"); return 1; } sp is a pointer, in which a block of memory is being allocated, but in this function, if (!sp) i.e pointer is not null, i.e the memory has been allocated, then why should there be an error message? - While fixing the error generated from the error report, null was being passed to memcpy, here if (sp_stream_buffer_op(S_CMD_O_EXEC, 0, NULL) != 0) to try and fix this issue, I updated the function definition static int sp_stream_buffer_op(uint8_t cmd, uint32_t parmlen, uint8_t *parms){ uint8_t *sp; if (sp_automatic_cmdcheck(cmd)) return 1; sp = malloc(1 + parmlen); if (!sp) { msg_perr("Error: cannot malloc command buffer\n"); return 1; } sp[0] = cmd; /* * Fixed: Added an If block to check the parameter length, * if parameter length is 0 i.e- param is NULL return 1, * else do memcpy */ if(parmlen==0){ //memcpy(&(sp[1]),0, parmlen); msg_perr("Error: Cannot pass Empty parameter\n"); return 1; } else{ memcpy(&(sp[1]),parms, parmlen); } The above changes fixed the error of null value being passed, but now I am getting a memory leak error. Can someone guide me in the right direction on how to fix it? Hoping for a quick and positive response. Warm Regards Prakhar Agrawal Amritapuri <https://www.amrita.edu/campus/amritapuri> LinkedIn <https://www.linkedin.com/in/prakar-agrawal-984555154/>

2 1

Inquiry about your GSOC idea: 'Modernize the flashrom website'
by Mohit Nehra 01 Apr '22

01 Apr '22

Sir/ Ma'am, I hope you are having a wonderful day, The GSOC project idea 'Modernize the flashrom website' was present in the ideas list a week ago but now it is not visible anymore. Please tell if you have intentionally removed it from the ideas list or there is some bug resulting in its removal. Thank you. Mohit Nehra (An aspiring student/ contributor to flashrom GSOC 2022)

2 2

Gsoc 2022 Proposal help
by Shivesh Chaturvedi 31 Mar '22

31 Mar '22

Sir, My name is Shivesh Chaturvedi, I am a second year undergraduate student of the department of Mechanical Engineering enrolled in its btech course at Indian Institute of Technology, Kharagpur, West Bengal India. I am a resident of Lucknow Uttar Pradesh, India. I had worked on the project Idea of Modernising the UI of FlashRom website. I had now gone through the website nearly 2-3 dozen times and I had found some issues which I thought rectifying would help a lot of new people like me. I had worked on basically 5 main points :- 1. Improvement of UI. 2. Having a basic Tutorial on How to use the Website. 3. Some Pages are too long so the idea is to use their pagination view. 4. Having database support for pages like Supported Devices and other pages also will help to improve the website. 5. Having a community chat box feature will help the users very much. Currently I am trying to use Flashrom, but finding it very difficult as there is no proper tutorial available over the internet. I was attempting to contact using Liber Chat, but there was some miscommunication on the website. As a result, I'm sending a draft proposal to this email. Please Kindly take a look over them and do give me pointers that I am going in the right direction or not. Yours Sincerely Shivesh Chaturvedi (+91) 8840884608

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom