- flashrom - mail.coreboot.org

Unable to read “Boyamicro” SPI chip.
by Frankie LEE (HTX) 22 Apr '22

22 Apr '22

Hi, Unable to read “Boyamicro” SPI chip? Any workaround? Thanks. ============================================================================================== ack@ack:~$ flashrom -p ft2232_spi:type=2232H,port=B,divisor=4 -r firmware.bin flashrom v1.2 on Linux 5.13.0-40-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 Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ft2232_spi. === This flash part has status NOT WORKING 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<mailto:flashrom@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! Read is not working on this chip. Aborting.

1 0

flashrom dev meeting notes 21.04.22
by Felix Singer 21 Apr '22

21 Apr '22

# 21th April 2022, 6:00 - 7:00 am UTC+0 Attendees: Thomas, David, Edward, Nico, Anastasia, Nikolai ## Decisions Summary * Anastasia will be doing next release. She has never done release before, and needs help from more experienced people. ## Agenda * [FelixS] Redmine is ready to use * If you wonder, new registrations require an unlock by an administrator. This is to prevent spamming and bots. Maybe we can work out something better in the future. * I added additional fields to issues, so that important information is easily visible. For example affected hardware, affected OS, affected version. Please tell me if you find these useful or if you need other fields, trackers, .. * aklm: let’s start using, I will try to create an account and see how it goes * [FelixS] Created a proposal for closing GitHub issues and pull requests automatically * Closes newly created issues and pull requests and adds a comment using GitHub Actions hook. Old issues and pull requests stay untouched. * [flashrom patch](https://review.coreboot.org/c/flashrom/+/63671), based on GitHub Actions hook and [repo- lockdown](https://github.com/dessant/repo-lockdown). * My playground [https://github.com/felixsinger/awesome-repo](https://github.com/felixsinger… * [Nico] ChromeOS fork and attempted convergence * (in case witnesses of that time are present) What led to the fork? * [PatrickG] Velocity requirements: stuff needed to happen to make progress on the products using flashrom and it didn’t happen in time. Not much of a problem when it’s temporary but stuff just piled up over time. * Nico: lots of things went wrong. And it took around 8 months to converge * David: Fork happened when Carl-Daniel was the maintainer, and he was really busy. Tools were worse that time. * We had irreconcilable differences at that time * Edward: Stefan asked me to unfork flashrom. I had to work out how things were done, how to re-write parts of the system. It was just me, on my own, no other resources. I took upstream and tried to make chrome os work with upstream. Except for a few patches: mapping hack inside of sb600spi, I am trying to chase AMD to get documentation , so that I can improve it. * David: Timer stuff I was trying to deal locally. There were a bunch of things that had to be dealt locally. * David: It was uglier downstream than it should have been. Trying to minimize the number of hacks. There are things that can be tr * Edward: Where we are today: I was trying to have a team for flashrom, to spend dedicated time to work on flashrom. We had good results on that, but it takes time. Hard to allocate people. * (in case somebody knows) What is Google’s current strategy to avoid repeating mistakes of the past? * [PatrickG] Generally CrOS is willing to go upstream-first (as with coreboot) after divergence has been resolved. Depends on the upstream, so probably need to work on the questions raised by Edward et al. * [Nico] Upstream-first of a dominant vendor made it harder for others to work upstream on coreboot. It’s not what I had in mind, but this would be repeating a mistake, IMHO. * Nico: There were very good and very bad contributions during last years * Edward: how do you quantify that nothing is happening? * Nico : sb600 is bricking machines , but nothing is happening * Edward: maybe it is a visibility problem, also some things are really hard * Nico: maybe devs in google need to talk to each other? * Edward: original patch came from AMD, not from google * Nico: if it takes a long time to find a solution, maybe just revert? * Edward: we didn’t know it would take so long * David: board bringup. There is 3-4 months time before chromebooks get into users hands, and then bugs get filed. Bugs in the code which is 6 months old, but people are already reassigned to other tasks. * Edward: maybe have a parameter which turns on the behaviour, default is turned off. The problem exists, but it is not trivial. * Nico: The problem with the “upstream-first” idea: when something is not trivial, you push it upstream first, and then try to figure out how to fix it. * Edward: that was exceptional situation, it is better now * Nico: most of the issues in the list are from google. When someone looks at the code, it is clear that code it is not understood. * Edward: we opened issues about non-documented programmer, and added documentation * Nico: one of the drivers is mixing all layers of flashrom. * Nikolai: what are concerns with the code? We will try to remove them. * Edward: The datasheet was in mandarin, and lots of questions were discussed in mandarin with the vendor. Vendors were not giving documentation, despite us asking them many times. * Nico: Who is doing reviews for google? We need reviewers who know all layers of flashrom. * David: Can we simplify the process of adding a new chipset? So that it would be easier to contribute without introducing bugs? * Thomas: It would be nice to have more structure in the code repository. It is hard to understand where the code needs to go. Having a specific place for every component is a good idea * David : flash.h and flashrom.c are dumping grounds * Anastasia: Nico do you think it is possible so that we all work together normally and peacefully? If we resolve issues from the past, and also write guidelines so that new issues won’t appear and development goes normally? >> Yes it is possible. * Let's make a release! * Nico: I spent a lot of time on this already, I can’t spend even more time. Anyone else? * Nikolai: What if the vendor does not give documentation, do you think it’s better to have a driver which is not documented, or no driver at all? * David: for early chromebooks , drivers were not documented. That’s why an option was called “I want brick” * Edward: some of the changes in the chromium tree we are not sending upstream, because there is no documentation * Nikolai: Can we have a flag for situations like sb600spi ? Finer granularity than the whole driver. Feature flags? * Nico: other people work on the sb600spi code, affects everyone who works on the code. * Edward: something similar in kernel hardware quark framework. * Nico: this needs documentation, whatever is needed to understand the quark. Man pages are for the users, but there also should be documentation for developers. In what product is this chip? You can document what you know * [dhendrix] Is this the kind of finger pointing that Edward mentioned above? At this point, CrOS has proved more than happy to move upstream. The Github mirror is probably more of a concern. Perhaps upstream should consider how to get developers to choose upstream rather than the Github mirror or some other fork. * [Nico] Pointing at Google, actually. If one company forks and later wants their code upstream without proper review, something seems wrong. As if they never reflected on the problems. * [aklm] I am not sure we are on the same page on what are “mistakes of the past”. Everyone has their own idea on what the mistakes were. I can start from myself. From my observations, converging the code was considered a purely technical task, and so it was done as a technical task. However, converging the code means converging the people/the teams, converging very different workflows and work cultures. This does not seem to be thought through or ever discussed, and to me this is a mistake. * [quasisec] I am also unclear how CrOS convergence had really much of an impact on upstream considering >99% of the work was adjusting the CrOS fork to realign with upstream. Only an extremely small amount of alignment was in the form of upstream commits, e.g., missing raiden_debug and some unfortunate part of sb600spi. Is there a specific area that stands out? * [Nico] No idea if related to the original reasons for the fork, but that the convergence is stalling new releases for years stands out pretty much. * Anastasia: We currently have more GSOC project proposals than mentors (5 vs 3). If someone wants to be a mentor, it is not too late. Contact Anastasia or Felix.

1 0

[GSoC 2022] Restructure Shutdown Function
by Joursoir 13 Apr '22

13 Apr '22

Good day, I am a student and very interested in flashrom. I fit the description of experienced C programmer. Open-source and low-level programming are my interests. I already have real experience with flashrom (CH341A programmer + chip "MX25L6436E") and want to become a GSoC 2022 contributor in this project. I find the "Restructure Shutdown Function" project interestring to me. But right now it has no mentors. Maybe someone from the mailing can help me. I have gone through sources and understand how things are now. The project description says "have a defined shutdown function in the programmer API". But we already have it. It's programmer_shutdown(). Or no? The first and easiest thing that comes to my mind is to refuse using callbacks and use enums, thusly: enum shutdown_func { SERPROG = 1 << 0, SPI = 1 << 1, ... }; int programmer_shutdown(enum shutdown_func execfunc) { ... if(execfunc & SERPROG) ret |= serprog_shutdown(...); if(execfunc & SPI) { /* the problem is that SPI programmers have own shutdown funcs, like dlc5_shutdown, byteblaster_shutdown, stlinkv3_spi_shutdown, so use struct spi_master, that contains shutdown callback */ ret |= spi_master_shutdown(...); } ... } This system has disadvantages, but it'll make easier to track the code flow. What are the potential problems in this implementation? What's with struct flashrom_programmer? Is not implemented yet? I would appreciate any feedback. -- Joursoir

3 15

Future of DirectHW
by Thomas Heijligen 12 Apr '22

12 Apr '22

Hi, is there someone in the flashrom community who has worked with DirectHW and knows if it's still working on supported MacOS systems? I want to figure out how to deal with it in the future of flashrom. -- Thomas

3 5

Couldn't parse the descriptor?
by Pete Smith 12 Apr '22

12 Apr '22

I'm using a Raspberry Pi Zero and SOIC clip to communicate with a MX25L12873F chip, using flashrom built from master branch (1b1066e). Reading the chip is working fine, no matter how many times I do a read operation, the resulting firmware image is correct. However, I'm unable to write to the chip: ======================================================================== flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1000 -c \ MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F \ -w firmware.bin --ifd -i fd -i bios -i me --noverify-all -VVV -o out.log Initializing linux_spi programmer Using device /dev/spidev0.0 Using 1000kHz clock get_max_kernel_buf_size: Using value from \ /sys/module/spidev/parameters/bufsiz as max buffer size. linux_spi_init: max_kernel_buf_size: 4096 The following protocols are supported: SPI. Probing for Macronix \ MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F, \ 16384 kB: programmer_map_flash_region: mapping \ MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F from \ 0xff000000 to 0x00000000 RDID returned 0xc2 0x20 0x18. compare_id: id1 0xc2, id2 0x2018 Added layout entry 00000000 - 00ffffff named complete flash Found Macronix flash chip \ "MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F" \ (16384 kB, SPI) on linux_spi. Chip status register is 0x7c. Chip status register: Status Register Write Disable (SRWD, SRP, ...) \ is not set Chip status register: Bit 6 is set Chip status register: Block Protect 3 (BP3) is set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set programmer_unmap_flash_region: unmapped 0x00000000 This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to \ completely clone the contents of this chip (see man page for details). programmer_map_flash_region: mapping \ MX25L12833F/MX25L12835F/MX25L12845E/MX25L12865E/MX25L12873F from \ 0xff000000 to 0x00000000 Some block protection in effect, disabling... \ Block protection could not be disabled! Chip status register is 0x7c. Chip status register: Status Register Write Disable (SRWD, SRP, ...) \ is not set Chip status register: Bit 6 is set Chip status register: Block Protect 3 (BP3) is set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Reading ich descriptor... done. layout_from_ich_descriptors():1367, returned with value -1. Couldn't parse the descriptor! Illegal instruction ======================================================================== On an identical system, I have been using the flashrom internal programmer to write the same firmware image without any errors parsing the descriptor. Any ideas why this happens? I'm a doing something wrong? Thanks. Best regards, Pete Smith

2 6

Invitation: Flashrom Dev Meeting (monthly) @ Every 2 weeks from 8am to 9am on Thursday (CEST) (flashrom@flashrom.org)
by felix.singer12＠gmail.com 11 Apr '22

11 Apr '22

You have been invited to the following event. Title: Flashrom Dev Meeting (monthly) Monthly meeting of Flashrom project developers. Meeting notes doc: https://docs.google.com/document/d/18qKvEbfPszjsJJGJhwi8kRVDUG3GZ… When: Every 2 weeks from 8am to 9am on Thursday Central European Time - Berlin Joining info: 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 Calendar: flashrom(a)flashrom.org Who: * aklm(a)chromium.org- creator * felix.singer12(a)gmail.com * david.hendricks(a)gmail.com * quasisec(a)google.com * nico.h(a)gmx.de * Martin Roth * 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 Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=MmVscGY2cjNsdTZw… Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account flashrom(a)flashrom.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively, you can sign up for a Google Account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organiser and be added to the guest list, invite others regardless of their own invitation status or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Board Testing - ASRock TRX40 Creator
by Dario Dorando 09 Apr '22

09 Apr '22

Hey folks, I've tested compatibility of this tool with my mainboard today. Boardname: ASRock TRX40 Creator Vendor website: http://www.asrock.com/mb/AMD/TRX40%20Creator/#Specification Flash-chip: Winbond 25Q128FWSQ - 16MBSuperI/O: nuvoTon NCT6683D-T For the folks interested - A webpage with amazingly detailed photos of that mainboard, including chips and whatnot: https://news.xfastest.com/review/review-03/72941/asrock-trx40-creator-revie… Note that this page is currently down for me, but you can still access it via the wayback machine. Commands ran: sudo flashrom/flashrom -r biosdump.bin -p internal # Note that TRX4CTR1.70 is the rom file that's freely downloadable from ASRock's website. binwalk -W -i TRX4CTR1.70 biosdump.bin > binwalk_diff.txt # Since I'm not really fond of firmware file layouts yet, somebody who's smarter than me might want to verify whether # the differences are mainly due to different bios configs and hardware I've added into my system,# or if some firmware section got omitted on read. more binwalk_diff.txt | grep 0x0 | wc -l # This command showed '17430'. Since binwalk shows 16 bytes per line, there should be about 34kb of differences in binary. # Flashed back the official rom, since I don't really trust the read one. sudo flashrom/flashrom -p internal -w TRX4CTR1.70 # The output from that is in the attached file. sudo flashrom/flashrom -p internal -V lspci -nnvvxxxsuperiotool -deV Flashing the machine with the stock rom did work as well! - Dario

1 0

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

07 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 07 Apr '22

07 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 07 Apr '22

07 Apr '22

3 2

GSOC 2022
by Wynn K 07 Apr '22

07 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

Sharing info about flashrom HW seq code refactoring https://review.coreboot.org/q/topic:PCH_HW_SEQ_Cleanup
by Subrata Banik 31 Mar '22

31 Mar '22

Hello Team, Hope you are doing well. I would like bring this activity in your notice https://review.coreboot.org/q/topic:PCH_HW_SEQ_Cleanup and seek help to review the code. The reason for this refactoring of HW sequencing SPI driver code are: 1. We (Chrome OS team) recently ran into a firmware update issue on dogfooders (test device utilise by real users and share feedback) systems, where the attempt to perform SPI flash update operation from host-cpu (using underlying flashrom utility) is silently failing. Furthermore, we debug the issue with help of Intel and figure out the problem is related to multiple master is accessing the SPI flash and operation triggered by host-cpu side using flashrom (write and erase operation) is getting timed out (due to given lesser timeout boundary) due to underlying SPI bus is occupied by other master. This is the special case, starting from Tiger Lake Chrome Platform, where we have enable the PVAP (Protected Audio Video Path) which request CSE to perform some erase and write operation as needed. Now an attempt to perform firmware update from host-cpu side might coincide with the CSE performing SPI operations. The recommendation that coming out from Intel is to account the multiple master SPI operation while we are issuing the timeout from flashrom side. We are also expecting a doc update from Intel to share the exact timeout calculation (although I have attempted to document that early here https://review.coreboot.org/c/flashrom/+/62867/1/ichspi.c#35). 2. Maintain the code symmetry between coreboot and flashrom SPI hardware sequencing operations. From the testing side, I have tested this code on Alderlake `Brya`, Tigerlake `volteer` and Kabylake `eve` devices, and looking for help from community to check on other systems as well (if possible). Furthermore, I have attempted to increase the timeout which won't impact the flashrom performance on the older and/or existing systems. Looking forward for your help on this request. Thanks, Subrata

3 7

Inquiry about a required task for GSOC.
by Israa Odeh 31 Mar '22

31 Mar '22

Dear Flashrom Org, While I was looking for a GSOC contribution that appeals to my interests and attracts my attention. I noticed your GSOC project ideas for Flashrom, and specifically, the task labeled as "Modernize the flashrom website", which I found quite interesting. Generally, I enjoy web development using CSS, HTML, JavaScript, and PHP, and I'm willing to learn new skills, work with various frameworks, and learn about other helping platforms to enhance my abilities. However, I would like to gain more details about what this project idea requires in minute details so that I could prepare an appropriate proposal and a good plan if it is suitable to me. Please Kindly, provide me with additional information about the requirements. Examples of a bunch of details that I need to know: - Who will be the mentors? (This isn't clarified for each task separately). - What are the expected outcomes you hope to accomplish with this task? - Do you mean specifically that you need to improve the front-end? (Is it specifically a front-end improvement?) - Must the design be responsive? - Are there any predetermined languages or frameworks to use? - Could you clarify what do you mean by saying "However, we have to find out what we need and which framework supports what. Then, various frameworks need to be evaluated and we need a plan on how to migrate to the new site." I'd appreciate hearing the required details from you. Kind Regards Israa Odeh. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

2 1

SPI flashing is the future! :-)
by Stefan Zett 27 Mar '22

27 Mar '22

Hi, i am no developer and spi flashing is very interesting for me. Please can someone write a short explanation about the status registers and block protect? Just for the usual hacker. Thanks Stefan

1 0

Board Asus P7P55D-E Chipset intel P55 reading works
by Stefan Zett 26 Mar '22

26 Mar '22

sudo flashrom -V -p internal -c "MX25L1605" -r 4d.rom flashrom v1.2 on Linux 5.4.0-91-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.6.4, GCC 9.2.1 20200304, little endian Command line (7 args): flashrom -V -p internal -c MX25L1605 -r 4d.rom Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). 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: "System manufacturer" DMI string system-product-name: "System Product Name" DMI string system-version: "System Version" DMI string baseboard-manufacturer: "ASUSTeK Computer INC." DMI string baseboard-product-name: "P7P55D-E" DMI string baseboard-version: "Rev 1.xx" Found chipset "Intel P55" with PCI ID 8086:3b02. 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 GCS = 0xc65: BIOS Interface Lock-Down: enabled, Boot BIOS Straps: 0x3 (SPI) Top Swap: not enabled 0x7fffffff/0x7fffffff FWH IDSEL: 0x0 0x7fffffff/0x7fffffff FWH IDSEL: 0x0 0x7fffffff/0x7fffffff FWH IDSEL: 0x1 0x7fffffff/0x7fffffff FWH IDSEL: 0x1 0x7fffffff/0x7fffffff FWH IDSEL: 0x2 0x7fffffff/0x7fffffff FWH IDSEL: 0x2 0x7fffffff/0x7fffffff FWH IDSEL: 0x3 0x7fffffff/0x7fffffff FWH IDSEL: 0x3 0x7fffffff/0x7fffffff FWH IDSEL: 0x4 0x7fffffff/0x7fffffff FWH IDSEL: 0x5 0x7fffffff/0x7fffffff FWH IDSEL: 0x6 0x7fffffff/0x7fffffff FWH IDSEL: 0x7 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode enabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled 0x7fffffff/0x7fffffff FWH decode disabled Maximum FWH chip size: 0x100000 bytes SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x0b: BIOS Lock Enable: enabled, BIOS Write Enable: enabled Warning: Setting Bios Control at 0xdc from 0x0a to 0x09 failed. New value is 0x0b. SPIBAR = 0x00007fc4c1fbd000 + 0x3800 0x04: 0x6008 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=1, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=0 Programming OPCODES... done 0x06: 0x0000 (HSFC) HSFC: FGO=0, FCYCLE=0, FDBC=0, SME=0 0x50: 0x0000ffff (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0xff, BRRA 0xff 0x54: 0x000f0000 FREG0: Flash Descriptor region (0x00000000-0x0000ffff) is read-write. 0x58: 0x01ff0000 FREG1: BIOS region (0x00000000-0x001fffff) is read-write. 0x5C: 0x002f0010 FREG2: Management Engine region (0x00010000-0x0002ffff) is read-write. 0x64: 0x01ff0050 FREG4: Platform Data region (0x00050000-0x001fffff) is read-write. 0x90: 0x04 (SSFS) SSFS: SCIP=0, FDONE=1, FCERR=0, AEL=0 0x91: 0xf87f10 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=1, DBC=63, SME=0, SCF=0 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05200302 (OPMENU) 0x9c: 0xc79f0190 (OPMENU+4) 0xa0: 0x00000000 (BBAR) 0xc4: 0x00000000 (LVSCC) LVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0, VCL=0 0xc8: 0x00002001 (UVSCC) UVSCC: BES=0x1, WG=0, WSR=0, WEWS=0, EO=0x20 0xd0: 0x00000000 (FPB) OK. The following protocols are supported: FWH, SPI. Probing for Macronix MX25L1605, 2048 kB: probe_spi_rdid_generic: id1 0xc2, id2 0x2015 Found Macronix flash chip "MX25L1605" (2048 kB, SPI) mapped at physical address 0x00000000ffe00000. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Reading flash... done. Restoring MMIO space at 0x7fc4c1fc08a0 Restoring MMIO space at 0x7fc4c1fc0874 Restoring MMIO space at 0x7fc4c1fc089c Restoring MMIO space at 0x7fc4c1fc0898 Restoring MMIO space at 0x7fc4c1fc0896 Restoring MMIO space at 0x7fc4c1fc0894 Restoring PCI config space for 00:1f:0 reg 0xdc

1 0

flashrom and ASUS PRIME_X370-PRO
by Andrew Grzegorek 26 Mar '22

26 Mar '22

sudo flashrom --programmer internal flashrom v1.2 on Linux 5.11.22-100.fc32.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). Found chipset "AMD FP4". Enabling flash write... FCH device found but SMBus revision 0x59 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 No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. ----------------------------------------------------- lspci -nnvx 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex [1022:1450] Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: fast devsel 00: 22 10 50 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit [1022:1451] Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: fast devsel, IRQ 27 Capabilities: <access denied> 00: 22 10 51 14 00 04 10 00 00 00 06 08 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 00 00 00 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 0 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 1 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe900000-fe9fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 53 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 f1 01 00 00 20: 90 fe 90 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 2 Bus: primary=00, secondary=02, subordinate=09, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fe400000-fe6fffff [size=3M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 53 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 02 09 00 e1 e1 00 20 20: 40 fe 60 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 12 00 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] DeviceName: Onboard IGD Flags: fast devsel, IOMMU group 3 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 4 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge [1022:1453] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 30, IOMMU group 5 Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0 I/O behind bridge: 0000d000-0000dfff [size=4K] Memory behind bridge: fe800000-fe8fffff [size=1M] Prefetchable memory behind bridge: 00000000e0000000-00000000efffffff [size=256M] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 53 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 0a 0a 00 d1 d1 00 20 20: 80 fe 80 fe 01 e0 f1 ef 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 1a 00 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 6 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 7 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 8 Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe100000-fe3fffff [size=3M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 54 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 0b 0b 00 f1 01 00 00 20: 10 fe 30 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Flags: fast devsel, IOMMU group 9 00: 22 10 52 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B [1022:1454] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 32, IOMMU group 10 Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe700000-fe7fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 54 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 0c 0c 00 f1 01 00 00 20: 70 fe 70 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 12 00 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 59) Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: 66MHz, medium devsel, IOMMU group 11 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00: 22 10 0b 79 03 04 20 02 59 00 05 0c 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 11 00: 22 10 0e 79 0f 00 20 02 51 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1460] Flags: fast devsel, IOMMU group 12 00: 22 10 60 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1461] Flags: fast devsel, IOMMU group 12 00: 22 10 61 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1462] Flags: fast devsel, IOMMU group 12 00: 22 10 62 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1463] Flags: fast devsel, IOMMU group 12 Kernel driver in use: k10temp Kernel modules: k10temp 00: 22 10 63 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1464] Flags: fast devsel, IOMMU group 12 00: 22 10 64 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1465] Flags: fast devsel, IOMMU group 12 00: 22 10 65 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1466] Flags: fast devsel, IOMMU group 12 00: 22 10 66 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 [1022:1467] Flags: fast devsel, IOMMU group 12 00: 22 10 67 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] (prog-if 02 [NVM Express]) Subsystem: Samsung Electronics Co Ltd Device [144d:a801] Flags: bus master, fast devsel, latency 0, IRQ 70, NUMA node 0, IOMMU group 13 Memory at fe900000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: nvme Kernel modules: nvme 00: 4d 14 08 a8 06 04 10 00 00 02 08 01 10 00 00 00 10: 04 00 90 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 4d 14 01 a8 30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 00 00 02:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset USB 3.1 xHCI Controller [1022:43b9] (rev 02) (prog-if 30 [XHCI]) Subsystem: ASMedia Technology Inc. Device [1b21:1142] Flags: bus master, fast devsel, latency 0, IRQ 25, IOMMU group 14 Memory at fe6a0000 (64-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: xhci_hcd 00: 22 10 b9 43 06 04 10 00 02 30 03 0c 10 00 80 00 10: 04 00 6a fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 21 1b 42 11 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00 02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset SATA Controller [1022:43b5] (rev 02) (prog-if 01 [AHCI 1.0]) Subsystem: ASMedia Technology Inc. Device [1b21:1062] Flags: bus master, fast devsel, latency 0, IRQ 42, IOMMU group 14 Memory at fe680000 (32-bit, non-prefetchable) [size=128K] Expansion ROM at fe600000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: ahci 00: 22 10 b5 43 06 04 10 00 02 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 68 fe 00 00 00 00 21 1b 62 10 30: 00 00 60 fe 50 00 00 00 00 00 00 00 0a 02 00 00 02:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] X370 Series Chipset PCIe Upstream Port [1022:43b0] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 33, IOMMU group 14 Bus: primary=02, secondary=03, subordinate=09, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fe400000-fe5fffff [size=2M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b0 43 07 04 10 00 02 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 02 03 09 00 e1 e1 00 00 20: 40 fe 50 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0f 03 12 00 03:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 14 Bus: primary=03, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 04 04 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 12 00 03:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 35, IOMMU group 14 Bus: primary=03, secondary=05, subordinate=05, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 05 05 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0f 01 12 00 03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 37, IOMMU group 14 Bus: primary=03, secondary=06, subordinate=06, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 06 06 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 12 00 03:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 38, IOMMU group 14 Bus: primary=03, secondary=07, subordinate=07, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: fe500000-fe5fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 07 07 00 f1 01 00 00 20: 50 fe 50 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 12 00 03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 39, IOMMU group 14 Bus: primary=03, secondary=08, subordinate=08, sec-latency=0 I/O behind bridge: 0000e000-0000efff [size=4K] Memory behind bridge: fe400000-fe4fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 08 08 00 e1 e1 00 00 20: 40 fe 40 fe f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 0f 01 12 00 03:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 14 Bus: primary=03, secondary=09, subordinate=09, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: [disabled] Prefetchable memory behind bridge: [disabled] Capabilities: <access denied> Kernel driver in use: pcieport 00: 22 10 b4 43 07 04 10 00 02 00 04 06 10 00 01 00 10: 00 00 00 00 00 00 00 00 03 09 09 00 f1 01 00 00 20: f0 ff 00 00 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 05 01 12 00 07:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller [1b21:1343] (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:86f2] Flags: bus master, fast devsel, latency 0, IRQ 25, IOMMU group 14 Memory at fe500000 (64-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: xhci_hcd 00: 21 1b 43 13 06 04 10 00 00 30 03 0c 10 00 00 00 10: 04 00 50 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 f2 86 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 01 00 00 08:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:85f0] Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 14 Memory at fe400000 (32-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=32] Memory at fe420000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: igb Kernel modules: igb 00: 86 80 39 15 07 04 10 00 03 00 00 02 10 00 00 00 10: 00 00 40 fe 00 00 00 00 01 e0 00 00 00 00 42 fe 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 f0 85 30: 00 00 00 00 40 00 00 00 00 00 00 00 0f 01 00 00 0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] [1002:6613] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:8094] Flags: bus master, fast devsel, latency 0, IRQ 97, IOMMU group 15 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at fe800000 (64-bit, non-prefetchable) [size=256K] I/O ports at d000 [size=256] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon Kernel modules: radeon, amdgpu 00: 02 10 13 66 07 04 10 00 87 00 00 03 10 00 80 00 10: 0c 00 00 e0 00 00 00 00 04 00 80 fe 00 00 00 00 20: 01 d0 00 00 00 00 00 00 00 00 00 00 62 14 94 80 30: 00 00 84 fe 48 00 00 00 00 00 00 00 0e 01 00 00 0a:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] [1002:aab0] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:aab0] Flags: bus master, fast devsel, latency 0, IRQ 99, IOMMU group 15 Memory at fe860000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 02 10 b0 aa 07 04 10 00 00 00 03 04 10 00 80 00 10: 04 00 86 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 b0 aa 30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 02 00 00 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a] Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a] Flags: fast devsel, IOMMU group 16 Capabilities: <access denied> 00: 22 10 5a 14 00 00 10 00 00 00 00 13 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 5a 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 00 00 00 0b:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor [1022:1456] Flags: bus master, fast devsel, latency 0, IRQ 72, IOMMU group 17 Memory at fe200000 (32-bit, non-prefetchable) [size=1M] Memory at fe300000 (32-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: ccp Kernel modules: ccp 00: 22 10 56 14 06 04 10 00 00 00 80 10 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 20 fe 00 00 00 00 20: 00 00 00 00 00 00 30 fe 00 00 00 00 22 10 56 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 02 00 00 0b:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller [1022:145f] (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: bus master, fast devsel, latency 0, IRQ 61, IOMMU group 18 Memory at fe100000 (64-bit, non-prefetchable) [size=1M] Capabilities: <access denied> Kernel driver in use: xhci_hcd 00: 22 10 5f 14 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 10 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 47 87 30: 00 00 00 00 48 00 00 00 00 00 00 00 0f 03 00 00 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455] Subsystem: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function [1022:1455] Flags: fast devsel, IOMMU group 19 Capabilities: <access denied> 00: 22 10 55 14 00 00 10 00 00 00 00 13 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 55 14 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 00 00 00 0c:00.2 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Device [1043:8747] Flags: bus master, fast devsel, latency 0, IRQ 44, IOMMU group 20 Memory at fe708000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: ahci 00: 22 10 01 79 07 04 10 00 51 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 80 70 fe 00 00 00 00 43 10 47 87 30: 00 00 00 00 48 00 00 00 00 00 00 00 0f 02 00 00 0c:00.3 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller [1022:1457] Subsystem: ASUSTeK Computer Inc. Device [1043:8733] Flags: bus master, fast devsel, latency 0, IRQ 101, IOMMU group 21 Memory at fe700000 (32-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 22 10 57 14 06 04 10 00 00 00 03 04 10 00 80 00 10: 00 00 70 fe 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 33 87 30: 00 00 00 00 48 00 00 00 00 00 00 00 05 03 00 00 ----------------------------------------------------- Best Regards, Andrew

1 0

Re: Questions About Flashrom Of Gsoc
by Anastasia Klimchuk 25 Mar '22

25 Mar '22

Hi Hui, First of all, I wanted to say, you replied to me only and not to the mailing list (and I only noticed now). Most likely you clicked the "Reply" button instead of "Reply All". I am adding the mailing list back, but for future please keep in mind to Reply All. The most important reason is that if you send your questions to the mailing list, then everyone in our community can help you! Which is really good. You will have various questions, and you never know who is the best person to answer. So, pay attention that the mailing list is on the To line ;) Some things I can answer: >> The platform Gerrit is mentioned in the "Development Guidelines." All I know about it is that it is a code management tool. Are there any tutorial videos or articles that I can use to learn more about Gerrit? Gerrit is also a code review tool. Gerrit has an official website with lots of presentations, look here https://www.gerritcodereview.com/presentations.html , hopefully that's useful! >> I went to GitHub's official Flashrom mirror. You can browse all code on GitHub, no problem, and yes it can be a convenient way to browse. Just keep in mind GitHub is a mirror, so that's pretty much only for browsing code. When you start with trying to make changes by yourself, you need to set up flashrom git repository locally. When you come to that point, open https://review.coreboot.org/admin/repos/flashrom and choose your desired method to clone the repository. Supported methods are HTTPS and SSH. The same method will also be used when you push your changes to Gerrit later. >> My current devices are a Windows 11 laptop (processor 11370H, Tiger Lake-H35) and a Mac. Is it possible for me to try out some patches on my computer? Also, could you provide me with any resources or introductions to chip packaging (DIP32, PLCC32, DIP8...)? I am wondering if someone else can take these questions? We need community help on this :) Thanks! On Thu, Mar 10, 2022 at 6:59 AM Hui Xiang <zavier2001(a)outlook.com> wrote: > Dear Anastasia, > > > > Thank you for your response. I read the "Contributor Guidelines" and have > some questions. > > > > >> "work with our git repository." > > I went to GitHub's official Flashrom mirror. The repository contains a > large number of files. Which file would you recommend I start with if I > want to familiarize myself with the current codes on GitHub? The platform > Gerrit is mentioned in the "Development Guidelines." All I know about it is > that it is a code management tool. Are there any tutorial videos or > articles that I can use to learn more about Gerrit? > > > > >> "downloaded and built flashrom as well as applied some patches." > > My current devices are a Windows 11 laptop (processor 11370H, Tiger > Lake-H35) and a Mac. Is it possible for me to try out some patches on my > computer? Also, could you provide me with any resources or introductions to > chip packaging (DIP32, PLCC32, DIP8...)? I looked them up on Google, but > there is not much information about them. > > > > >> "Check Easy projects or ask for simple tasks on the mailing list or on > IRC." > > I went to the "Easy projects" page and decided to start my job with "Find > chips without voltage data." What can I do about it? Could you provide me > with any tips and advice? Thank you very much. > > > > I joined the IRC channel through Libera. Chat. My nickname is Hui_Xiang. > Is it necessary for me to install an IRC client on my computer? Thank you > for looking into this for me. I appreciate it. > > > > Best Regards, > > Hui > > > > > > *From:* Anastasia Klimchuk <aklm(a)chromium.org> > *Sent:* 09 March 2022 01:50 > *To:* flashrom(a)flashrom.org; Hui Xiang <zavier2001(a)outlook.com> > *Subject:* Re: [flashrom] Questions About Flashrom Of Gsoc > > > > Hello Hui, > > Nice to meet you! Great to know that you are interested to work with us > this Summer of Code! > > It is very good that you looked into the list of project ideas and are > interested in one of them, and your experience in C is very relevant. > > > What resources can I use to learn more about it? > > First thing, please have a read of our Contributor Guidelines > https://www.flashrom.org/GSoC especially the “Contributor commitments & > requirements” section, and see if you can gradually start with p.1 “Prior > to project acceptance, you need to demonstrate that you can work with the > flashrom codebase”. It is important that you complete all steps from 1 to 5. > Definitely tell us how it goes! You can reply to this email, tell us what > steps you did successfully, or if not, what are the problems. > > Also look into the “How to contact us” section, join our IRC channel and > say hello! :) > > Just in case, if you haven’t read these already, here are official > guidelines for gsoc program: > https://google.github.io/gsocguides/student/ > Rules https://summerofcode.withgoogle.com/rules (at least check p.7 from > here) > > > What skills do I need to improve to get accepted from Flashrom? > > For the project you are interested in, good knowledge of C language is a > critical skill. > > Thank you! > > Anastasia. > > > -- Anastasia.

3 7

flashrom dev meeting notes 23.03.22
by Felix Singer 24 Mar '22

24 Mar '22

# Decisions on 23th March 2022: * Meeting times from not until November will alternate between two different times (to be voted upon) so that no one group will be excluded from every meeting. Time1 is EU+AU, Time2 is EU+US. * In the short term, any money collected for the Flashrom project, will be given to the coreboot project. coreboot will maintain a ledger for flashrom money. * We want a single build system (either Make or Meson). Anastasia will set up a separate meeting to discuss the “Makefile vs Meson” topic. * Next meeting will be in 2 weeks since there's still so much on the agenda. # 23th March 2022, 21:00-22:00 UTC+0 **Attendees: **Thomas, Michal, Felix, Anastasia, David, Nico, Patrick, Edward, Martin, Carl-Daniel **Agenda:** * [FelixS] Before we start discussing new topics, anything we need to discuss from the last meeting? * Leadership question is relevant to the item below, about fiscal sponsorship * [aklm] Reminder: daylight saving time is approaching. Next time we will use this time (21.00-22.00 UTC+0) in November. * For the next occurrence of dev meeting, Felix will send a poll to vote on days/times for the interval Apr-Sept. * In October we can have a vacation from each other (because there is a month diff when DST happens in different locations). * Martin: Can we have a schedule where the bad time rotates? So one out of every 3 times is poor for 1 group, but better for the other two. * Will do alternating times until november. Alternating between EU+AU and EU+US. * [Martinr] Should flashrom look for a fiscal sponsor so that it can accept donations? * [aklm] (possibly related) As an organization we can get some money per successful gsoc project (around 500 USD IIRC). Where do we put it? A bank account? * That's exactly the issue. In the past, before coreboot joined the SFC, the coreboot project had no way to accept donations, so the money was just donated directly to the SFC. By joining a fiscal sponsor, that allows money to be donated to the flashrom project to be used for purchasing test equipment, boards, servers, or whatever is needed. * [https://opensource.com/article/19/1/fiscal-sponsors-open-source](https://op… * [aklm] I just (10/03) got this comms from gsoc orgs: “For orgs who need to change their financial details for GSoC 2022, the deadline to have all of your Payoneer account information completed is July 15, 2022 as described in the Program Rules. We will not pay out stipends to any orgs who miss this hard deadline. We'll send more details about receiving stipends etc. in May so you'll have 2 months to get everything in order.” * It takes a long time to join a fiscal sponsor, so if flashrom is going to join a group, we're probably looking at 2023. * [FelixS] Since there is no legal entity around flashrom, we would have to create one first or a private person needs to take the money for now. In any case, this brings a lot of complicated implications and work (e.g. taxes). Can we just transfer the money to coreboot? * Since flashrom currently shares the coreboot infrastructure, in the short term, combining the financial interests makes sense. In the long term, we might want to look at having the projects be more separate, and getting a fiscal sponsorship for flashrom itself. * aklm will ask gsoc organizers on a mailing list, to get official reply whether 2 orgs can have the same account. * [Patrick] SFC needs some point of contact that can make decisions (e.g. about spending project money), so that's where the "leadership" thing came from in coreboot. They also strongly suggest to have at least 3 people and to avoid having outsized impact of any particular company contributing which informed how we defined our leadership group make up. * [aklm] Meson and Makefile. For upstream, Makefile is officially supported and used by developers, Meson is only used for unit tests. For chromium, Meson is officially supported and used for everything, including tests. Logically, these two should be in sync, since they are building the same code. Each side is interested in one build system (the one they are using). Can we join forces and keep two build systems in sync? * [FelixS] Thomas is about cleaning up both build systems and bringing them closer. * [Thomas] I’m working on getting the Makefile in a readable and usable state. A lot of configuration was / is done by C preprocessor macros. I’m trying to get rid of those. Since the meson.build is mostly a copy of the Makefile I want to update it when the Makefile is in a good shape. Currently the meson.build lags support for non Linux systems. I personally would prefer meson as a single build system, but we are not at this point yet. * [Edward and Martin] we need to test builds in both build systems until a single build system is selected. * [David] Are there any fundamental differences between the two build systems that cannot be resolved? We need to do gap analysis * [FelixS] I think Thomas mentioned a few things that can’t be done with Meson, or which are harder to do, but AFAIK he is working on it adding this functionality to upstream Meson. * [aklm] Do we all agree that we ideally have one build system? * YES! * Why did googlers decide to use meson? * [Edward] we want to use libflashrom instead of subprocessing, and that was supported well by meson. Also I have experience with both, and IMO meson is easier to maintain. Makefile is more ugly to do configurations for boards. * [Nico] secunet uses it in combination with FILO for firmware updates * [Thomas] I did lots of readability improvements and rework, but would like to switch to meson completely. It would be good to work with google to implement meson as the primary (and eventually only) build system. * Aklm to set up meeting (in 2 weeks from now) about meson and Makefile work, google will happily join this effort. Aklm is a google point of contact for the effort. * [Nico] Is meson capable of doing everything that Makefile is doing? Is ninja available on all platforms? * [CDH] if everything works for meson, I have no preference. But if not everything is working, then everyone will be unhappy. * [David] if we can cross-compile to DOS with meson, that would be a POC * [aklm] we do cross-compile with meson, just not for DOS * [Edward] How do we make it easy for new contributors to get involved in the project and grow the community to have more resources? * Improvements to community guidelines, * Improvements to developer documentation and expectations, * Convey appreciation to contributors and make them feel like no contribution is too small, * [aklm] Good news: this is exactly what we are doing right now! Literally, all of that starting from “How do we make it easy ….” to “.... no contribution is too small”. Importantly, these are not just words, but _lots of tasks to be done._ Since we got accepted to gsoc, already 6 people contacted us, they want to contribute. I really encourage everyone who can, to talk, respond to people, answer their questions, review their patches. I can quote myself from a previous meeting: “If you want to help and don’t know what to do, contact Anastasia or Felix.” * [dhendrix] Better automation. Git precommit hooks for style checks, etc. so that we don't waste review time telling newcomers where to put their braces, how to write a commit message, etc. * [FelixS] In my opinion, the website needs to be reworked. From my view, it’s not really inviting or motivating to read it. Also, many texts are outdated. * [David] What do we do about the GitHub mirror? Many issues and pull requests there, people are waiting for responses. * Edward suggests using [PRBot](https://github.com/ajdlinux/PRBot) * Martin: Do we want to add checks similar to coreboot's linters to the jenkins build? * Edward: Clang-format would be good. * [dhendrix]: revisit [https://review.coreboot.org/c/flashrom/+/44095](https://review.coreboot.org… ? * CDH: An automated message is much better than nothing. We need some sort of onboarding, and onboarding is always hard. * [aklm] Easy projects page, we need more easy projects for new people, please add if you have ideas. * [Nico] we have checkpatch set up for coreboot, I think this is a good thing, * [Martin] I think I can set this up. * [Martin] I can set up scan-build too * [Edward] we can display coverage in gerrit, contributors will see the progress for the changes in their patch? * [Thomas] note: tests are only for meson * [Martinr] The tests need to generate an output file, and a gerrit plugin needs to be added. coreboot currently has the files output, but the plugin isn't integrated yet. * [Felix] upstream pull requests as easy projects? * [Nico] These are not very easy projects, but there are unmerged patches on [patchwork](https://patchwork.coreboot.org/project/flashrom/list). We can see if there is some useful stuff there.

1 0

flashrom dev meeting notes 9.03.22
by Felix Singer 24 Mar '22

24 Mar '22

# Decisions 9th March 2022 * Will make this meeting bi-weekly until we've worked our way through the issues listed here. # 9th March 2022, 21:00-22:00 UTC+0 Attendees: Anastasia Klimchuk, Felix Singer, Thomas Heijligen, Stefan Reinauer, Edward O’Callaghan, Maciej Pijanowski, Miklos Marton, Martin Roth, Nico, Carl-Daniel, Piotr, Angel Pons Agenda: * [FelixS] First flashrom meeting. Let’s introduce ourselves and say what we are working on at flashrom. * [FelixS] flashrom has been accepted to GSoC * [GSoC project page](https://summerofcode.withgoogle.com/programs/2022/organizations/flash… ) * [Official announcement](https://mail.coreboot.org/hyperkitty/list/flashrom@flashrom.o… ) * Current tasks? What is left to do? * [aklm] Respond to GSoC candidates, help and guide them * [aklm] Help improve [Development Guidelines](https://www.flashrom.org/Development_Guidelines), [Easy Projects](https://www.flashrom.org/Easy_projects) pages. * If you want to help and don’t know what to do, contact Anastasia or Felix. * [Martinr] Who is the flashrom leadership and how is that decided? * [Nico] For the last years this was rather implicitly who was maintaining the code to be safe and sound. And helping users on IRC and the ML and such. * Is this how the project wants to continue? It seems somewhat disorganized. Just because someone is a good coder doesn't necessarily make them a good leader. * Who decides "safe and sound"? Are there any metrics for this? * The coreboot project has 3 people who actually make the decisions. This was set up when we joined the SFC. Also the 3 leaders need to be from different companies. * SFC has a requirement that organisation defines its leadership. What exactly the leadership is, it is up to organisation, but there should be some leadership". And that's how coreboot got leadership: coreboot wanted to join SFC, so needed to define leadership. * Which means, if flashrom wants to join SFC we need leadership too * Nico: In the past there wasn't much to decide, so there was no need for official leadership. * [Anastasia] We need someone to make decisions after a discussion on the mailing list if there isn't a clear direction. * [Edward] Some kind of election process, [Martin] organized the vote system for coreboot. * [Nico] There are currently two different projects in one repo, so if the leadership picks one, there might end up being two projects? * [Martinr] How are decisions made in the flashrom project? In this meeting, on the mailing list, something else? * [Nico] So far for smaller topics on IRC. For bigger topics, I suggest the mailing list. * [Thomas and Felix] Before deciding on leadership we need to talk more to each other. This is the first meeting we see each other and talk. We need to talk more about development, code, need to know more what we are doing. * Conclusion: let’s everyone think about it and continue discussion later. Topic added to Ongoing Items. * [Martin/Nico] Should we split flashrom into two separate projects? * Nico when I started, the project was for everyone, and stability was a priority. * Now we're trying to add the google fork, which has different objectives. * Edward: This isn't a different objective. * Quality is degrading. * Is code even tested? * Edward: yes, there's a strong emphasis on testing and improving tests. * Felix: what is tested? Is this unit testing? * Google tests any paths that they have available for testing. * Intel, AMD, Linux, mtd, Dediprog, raiden debug. * In the past, we kept all the code working for generic systems, so when support was added for a chip, it works for all of them, or bails out early. * New code is for specific boards, but not documented * [Martin] So let's focus on testing and make stability branches. * Nico: There's nobody to do that testing. * Felix: with the jenkins replacement, I'm thinking about how to add hardware tests as a part of the CI. * Miklos: There was someone who had boards with spi roms on boards with multiplexers for testing. \ Referred to this [document about the Chromium team’s hardware test setup.](https://docs.google.com/document/d/1IoBR7rHXJFiahC6dGnNKqaNFfg-q89_… ) * [Edward] Exactly this has come up between a discussion originally Martin and latter with Nikolai Artemiev to get CI coverage for writeprotect changes. * [Edward] We need to document testing what testing is done on the wiki. * Google is working on testing and making sure that the tests can be run by anyone. * [Edward]: First part of this is upstream-first unit-testing efforts, second part harder. * [Edward]: We need to get boards hooked for E2E tests, looking at what is happening for coreboot CI? * [Piotr] aklm on IRC just received commit rights without any previous discussion [[1]](https://matrix.to/#/!SAlNdlJiEjYGbpbVfu:libera.chat/$eKIApfMuImHqA9T0TowmUaTylyfJAOWTn9iK0q7itQk?via=matrix.org&via=libera.chat&via=nixos.dev ) * [Martinr] Anastasia has earned her commit rights with 125 commits over the past 2 years, more than anyone else. She is active in the community. She has done more than 82 reviews, more than anyone but Angel, Edward, and Nico. If she doesn't deserve her commit rights, Angel, Edward and Nico are the only ones who do. The discussion about commit rights is listed below, but as mentioned there, IMO, Thomas is the only other person who has earned commit rights. * [Nico] Edward’s history in the project is quite unique. He got the submit rights before he landed a single patch and with close to 0 prior activity in the project. So we can’t really put him above or below anyone in this matter. * We can absolutely look at commits and reviews that he's done since then. * [Nico] I don’t think we can decide this matter simply on the amount of patches / reviews. * [Martin] So what are your thoughts on how people should get +2? Is this also the "safe and sound" rule? You don't give any suggestions here. * [Piotr] How to get patch submitting rights in flashrom? We have 4 patches in +2 for some time: [[1]](https://review.coreboot.org/c/flashrom/+/55713/), [[2]](https://review.coreboot.org/c/flashrom/+/55714), [[3]](https://review.coreboot.org/c/flashrom/+/55714), [[4]](https://review.coreboot.org/c/flashrom/+/55848/) * Current Submitters * Anastasia Klimchuk * Angel Pons * Carl-Daniel Hailfinger * David Hendricks * Edward O'Callaghan * Idwer Vollering * Nico Huber * Patrick Georgi * Stefan T * Urja Rannikko * The only other person that has a significant number of commits in the last 5 years is Thomas Heijligen with 83 commits since July 2019. Thomas seems like a good candidate for getting submit rights. * What are the criteria for giving someone +2? When is someone ready, and who makes that decision? * coreboot has a relatively loose criteria for adding people, but decisions are made by the leadership. * Felix: Change the process about how patches are merged * Maybe require 2 +2s? * In case patches are merged too early, request that patches stay on gerrit for greater than 2 days or so? * [Carl-Daniel] We have different strategies, availability. Reviews are harder than writing code. We need to give people time to do reviews. Maybe we need to give 2 weeks time for reviewers. Unless some really bad bug which kills machines. * We have different modes of working on code, different goals. * Nico: 2 weeks is probably too long. * [Angel] too many patches sometimes, too little time. Very stressful. Patches pile up, not enough time to review and respond to everything. A feeling that if I miss something and do not respond in time then things will go wrong (e.g. errors missed during review). * [Anastasia] maybe if reviewer is busy, they can send a message to gerrit saying “sorry I am busy for next X weeks, I will get back to you after X weeks, thanks”, and this gives information to patch owner. Makes a big difference.

1 0

Flashrom Dev Meeting once a month?
by Anastasia Klimchuk 22 Mar '22

22 Mar '22

Hello Everyone, One good idea came up recently: to organize a “Flashrom Developers Meeting” so that we can talk to each other, discuss current development and future plans! The idea is, specifically, to have it regularly - and once a month seems just about right. The attendance will be, obviously, entirely optional, however one thing is important: to take notes from what has been discussed (and notes should be public). The main two questions are: when? (time) and which software to use. Time is a tricky question, and it depends on who is going to attend the meeting. We can optimize either for EU-US or for EU-AU. I can say for sure, we have at least one person from AU who is going to attend ;) (that’s me). If it turns out that we have people all over the planet who want to attend, and there is no one time that suits all, then as a plan B we can alternate between two options. That will be time1 and time2 alternating. Software. What do people use and like? I am used to Google Meet, and don’t know much about other options. What do people think of the idea? Let’s discuss! -- Anastasia.

5 18

Adding some details to the dev guidelines wiki page
by Nikolai Artemiev 21 Mar '22

21 Mar '22

Hi everyone! As a follow up to https://review.coreboot.org/c/flashrom/+/58477 and https://review.coreboot.org/c/flashrom/+/58480, I want to update the section "Adding/reviewing a new flash chip" of the dev guidelines <http://flashrom.org/Development_Guidelines> with documentation for two new chip data fields that were added: - `.reg_bits` stores information about what configuration bits the chip has and where they are found. For example,`.cmp = {STATUS2, 6, RW}` indicates that the chip has a complement bit (CMP) and it is the 6th bit of the 2nd status register. See `struct reg_bit_info` in flash.h for details on each of the structure's fields. Note that some chips have configuration bits that function like TB/SEC/CMP but are called something else in the datasheet (e.g. BP3/BP4/...). These bits should be assigned to a field according their function and the datasheet name should be noted in a comment, for example: ``` .sec = {STATUS1, 6, RW}, /* Called BP4 in datasheet, acts like SEC */ ``` - `.decode_range` points to a function that determines what protection range will be selected by particular configuration bit values. It is required for writeprotect operations on the chip. Let me know if the text is alright, thanks! Cheers, Nik

2 1

Re: FAILED: Joshua-H61-uATX
by Nico Huber 13 Mar '22

13 Mar '22

Hello Zack, your message got filtered because of the attachment. We have a limit of 200KiB for this mailing list because things are sent to a lot of people. I've scaled the image down. Regarding your problem, I don't think it is IME related. A locked region would already make trouble during the initial read. There are likely additional protections by your BIOS in effect. A full log might give us more information. If you append `-o logfile.txt` to your command that logfile would get written. For the moment I suggest you to try to write a backup back if you made one. It's possible that flashrom didn't write anything, but we don't know. Nico On 13.03.22 03:41, Zack Gibbs wrote: > Motherboard spec: > > https://support.hp.com/us-en/document/c03135925 > > Hello there. I've attempted to flash my bios however I have portions of the IME that are locked. > > At the bottom of the screen is the last command I ran,. > > Thanks for your help, > > Zack Gibbs >

2 1

Request for Assistance with FLASHROM
by Karani Vinay Kumar 13 Mar '22

13 Mar '22

Hello Flashrom team! I'm new to open source and I have some prior knowledge on C programming language. I would like to participate in GSOC with Flashrom. Give me some suggestions to how do I start and work on this.

2 1

Help !
by Guillaume Rallon 11 Mar '22

11 Mar '22

Hello, I request your help for a little problem. I try to unbrick my MSI Gaming 5 Z97 motherboard, using flashrom using a raspberry Pi 4b vi the JSPI1 port. I plugged it like this : Hold 0V o o WP 3.3V x o o o GND CLK o o CS SI-SO o o SO-SI o o VCC The plugin seems to be good as Flashrom detects the chipset as a Winbond W25Q64.V The battery of the mother board is removed, no other external current source plugged. When I launch the writing sequence everything goes flawlessly and the problem appears during the flash verification. I receive this message : Verifying flash... FAILED at 0x00000014! Expected=0x03, Found=0x02, failed byte count from 0x00000000-0x007fffff: 0x3d6c96 Your flash chip is in an unknown state. I tried to put HOLD at 3.3V and let the CMOS battery but it is always the same message. Maybe my chipset has an internal defect ? If yes, I think I can buy a new chip and solder it but it's a brutal solution ;) I would really be pleased if you could give me at least a clue. Best regards Guillaume RALLON The whole messages are below : flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w /home/Yogiadmin/flashrom/E7917IMS.190 flashrom v1.2-644-g79e2bd0 on Linux 5.10.92-v8+ (aarch64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... FAILED at 0x00000014! Expected=0x03, Found=0x02, failed byte count from 0x00000000-0x007fffff: 0x3d6c96 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! -- RALLON Guillaume 19 CHEMIN DE LA RETARDIERE 44700 ORVAULT FRANCE 06 79 69 15 60

2 1

Experimental GD25Q40(B) support
by Wolf Dieter Brandt 09 Mar '22

09 Mar '22

2 1

EN25F10 read/write support log files
by Wolf Dieter Brandt 09 Mar '22

09 Mar '22

Here you go! Thanks fro this great tool!

2 1

Erase Failed - MX25L12805D, MX25L12835F/...
by dean rooney 09 Mar '22

09 Mar '22

Hello, I am trying to fix a bricked motherboard (Z170A Mpower Gaming Titanium). The motherboard does have a MX25L12873F (not seen on your supported list) but does have the MX25L12805D and MX25L12835F/MX25L12845E/MX25L12865E as similar chips. I am using flashrom on a Raspberry Pi 3 and had gotten quite far using the forums until I came across "ERASE FAILED". I am able to read the chip, but I am unable to write as it has this Erase Failed appears every time. I'm not sure if there is a work around. I've seen the -f force erase but I'm not aware how to use this function. Any help would be greatly appreciated. Kind Regards, Dean

2 1

Questions About Flashrom Of Gsoc
by Hui Xiang 08 Mar '22

08 Mar '22

Dear Sir/Madam, I hope you are well today when you receive this email. My name is Hui Xiang, and I am a University of Manchester Electrical and Electronic Engineering student. This summer, I would like to join Google Summer of Code. The Flashrom Project caught my eyes after I went through all the projects of GSoC. In my school project, I am now working on the NUCLEO-F401RE(STM32). I can programme in C and C++, as well as assembly language. From the file of GSoC project ideas, I really like the idea of "Design and implement new CLI based on libflashrom and enhance the API as needed". For the Flashrom project, I would like to make contributions on some API. What resources can I use to learn more about it? What skills do I need to improve to get accepted from Flashrom? Thank you for looking into this for me. Best Regards, Hui

2 1

MT25QU256 Tested/Passed with Olimex ARM-USB-OCD-H
by Shawn Rainey 08 Mar '22

08 Mar '22

Seems to work well with an in-house prototype board + the olimex jtag probe and some hacked in wiring. Log file of a write is attached.

1 0

[MT25QU256] Tested probe, read, write and erase through ft2232_spi programmer
by Charles Parent 08 Mar '22

08 Mar '22

Hello, First thank you a lot for your amazing work on flashrom, I just discovered this software and it saved me a lot of time lately ! I use it to flash a MT25QU256 through a FTDI4233H, and as software is telling me that this chip is labelled as untested I would like to send you the logs showing that it works indeed. Here are logs for both reading and writing / erasing. I also did varius tests, filling the EEPROM with arbitrary values and reading back to see everything was working. Please do not hesitate if you need more details ! Best regards, Charles Parent Software Engineer charles.parent(a)orolia2s.com<mailto:jean-arnold.chenilleau@orolia.com> [cid:755255d5-41f3-4c56-848c-a82a0d12ea1a] France, Sèvres 6, rue Troyon 92310 Sèvres

2 1

Flashrom has been accepted for GSoC 2022
by Anastasia Klimchuk 07 Mar '22

07 Mar '22

Hello Everyone, Breaking news! Flashrom has been accepted as a Mentoring Organization for GSoC 2022! This is amazing news, because for the first time in history, Flashrom is participating in GSoC as independent organisation, has its own Org Admins and an entry in the list of accepted organisations: https://summerofcode.withgoogle.com/programs/2022/organizations Here is Flashrom page: https://summerofcode.withgoogle.com/programs/2022/organizations/flashrom (in case you are wondering, I also have no idea why all the newlines have been removed from the long description :)) What’s going to happen next? Timeline is here https://developers.google.com/open-source/gsoc/timeline Please share the news with everyone, especially with people who may be interested to participate in GSoC as contributors. There are three resources that you can share (each of them or all of them): #1 Flashrom page on GSoC site: https://summerofcode.withgoogle.com/programs/2022/organizations/flashrom #2 Flashrom Contributor guidelines: https://www.flashrom.org/GSoC #3 Our Project Ideas list: https://docs.google.com/document/d/1AxMobB2v8Dv2uUwZPZ_vCmmONYDJuliHcnjfWOs… If you saw my earlier thread on the mailing list “Call for Mentors”, it is not too late to respond! There are many ways you can help (not only by being a mentor), and every help counts, no matter big or small. And it’s never too late if you want to help with something :) Respond to this thread, or respond to “Call for Mentors”, or contact me/aklm, Felix/flx or Angel/hell directly. Finally, I wanted to say thank you to everyone who helped and supported this effort! Your Org Admins, Anastasia, Felix, Angel.

1 0

[RFC] Flashrom Development Guidelines - Patch submission
by Anastasia Klimchuk 07 Mar '22

07 Mar '22

Hello Flashrom community, Recently, we (Anastasia and Felix, your Org Admins) were looking into the Flashrom Dev Guidelines page https://www.flashrom.org/Development_Guidelines#Patch_submission with the main goal to prepare the page for GSoC. Very soon (7th March) the results are announced, and in case Flashrom is accepted, we will suddenly have lots of people (potential contributors) looking into our Dev Guidelines! :) We have a suggestion on how to improve the guidelines. Specifically, this is about the “Patch Submission” section (not the whole guidelines). There are few most important points to address: 1. Update the links, so that they don’t point to instructions from the old coreboot wiki (which explains how to clone coreboot repo). 2. State very clearly that we have a strong preference for Gerrit code reviews (not mailing list reviews). 3. Explain that we don’t look at pull requests on GitHub. The updated version of the “Patch Submission” section that we are suggesting is below. Comments/feedback is welcome, the wording can be changed/improved, as long as the three main points are addressed. Unchanged sections are marked as such. Thank you so much! ----------------------------------------------------------------- *Patch Submission* Coding style (unchanged) Flashrom generally follows Linux kernel style <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Doc…> . The notable exception is the line length limit. Our guidelines are: - 80-columns soft limit for most code and comments. This is to encourage simple design and concise naming. - 112-columns hard limit. Use this to reduce line breaks in cases where they harm grep-ability or overall readability, such as print statements and function signatures. Don't abuse this for long variable/function names or deep nesting. - Tables are the only exception to the hard limit and may be as long as needed for practical purposes. GitHub The official Flashrom mirror on GitHub is: https://github.com/flashrom/flashrom Importantly, GitHub repo is only a mirror, so all changes must go through Gerrit on review.coreboot.org in order to be merged, even small patches such as adding support for a flash chip. For this reason, reviewers do not look at pull requests. Even if pull requests were automatically transferred to Gerrit, requirements such as the #Sign-off Procedure <https://www.flashrom.org/Development_Guidelines#Sign-off_Procedure> still present a problem. The quickest and best way to get your patch reviewed and merged is by sending it to review.coreboot.org. Conveniently, you can use your GitHub, GitLab or Google account as an OAuth2 login method. Please continue reading, the instructions are below. Preparing a patch Before sending a patch for review, put your Signed-off-by line <https://www.flashrom.org/Development_Guidelines#Sign-off_Procedure> in the commit message. Currently there are two ways to send patches for review: 1. Our strong preference, especially for large patches, is via Gerrit on review.coreboot.org <https://review.coreboot.org/#/q/project:flashrom>, i.e. git push origin HEAD:refs/for/master 2. For small patches, with the reviewer’s agreement, there is an option to send via our mailing list <https://www.flashrom.org/Contact#Mailing_List>. When sending a patch via the mailing list, send it in-line instead of as an attachment so that reviewers can easily comment on specific parts of it. However, eventually the reviewer will need to push patch to gerrit anyway. Our guidelines borrow heavily from the coreboot development guidelines <https://doc.coreboot.org/contributing/index.html>, and most of them apply to flashrom as well. The really important part is about the #Sign-off Procedure <https://www.flashrom.org/Development_Guidelines#Sign-off_Procedure>. We try to reuse as much code as possible and create new files only if absolutely needed, so if you find a function somewhere in the tree which already does what you want (even if it is for a totally different chip), please use it. See also Command set secrets <https://www.flashrom.org/Random_notes#Command_set_secrets>. The patch reviews may sound harsh, but please don't get discouraged. We try to merge simple patches after one or two iterations and complicated ones as soon as possible, but we have quite high standards regarding code quality. If you introduce new features (not flash chips, but stuff like partial programming, support for new external programmers, voltage handling, etc) please discuss your plans on the mailing list <https://www.flashrom.org/Contact#Mailing_List> first. That way, we can avoid duplicated work and know about how flashrom internals need to be adjusted and you avoid frustration if there is some disagreement about the design. For patches that modify convoluted tables like struct flashchip flashchips[] in flashchips.c it may make sense to increase the lines of context to include enough information directly in the patch for reviewers (for example to include the chip names when changing other parameters like .voltage). To do this with git use git format-patch -U5 where 5 is an example for the number of lines of context you want. Commit message (unchanged) Commit messages shall have the following format: <component>: Short description (up to 72 characters) This is a long description. Max width of each line in the description is 72 characters. It is separated from the summary by a blank line. You may skip the long description if the short description is sufficient, for example "flashchips: Add FOO25Q128" to add FOO25Q128 chip support. You may have multiple paragraphs in the long description, but please do not write a novel here. For non-trivial changes you must explain what your patch does, why, and how it was tested. TEST=tests that you performed Finally, follow the #Sign-off Procedure <https://www.flashrom.org/Development_Guidelines#Sign-off_Procedure> to add your sign-off! Signed-off-by: Your Name <your@domain> Sign-off Procedure (unchanged) We employ a similar sign-off procedure as the Linux kernel developers <http://web.archive.org/web/20070306195036/http://osdlab.org/newsroom/press_…> do. Add a note such as Signed-off-by: Random J Developer <random(a)developer.example.org> to your email/patch if you agree with the Developer's Certificate of Origin 1.1 printed below. Read this post on the LKML <https://lkml.org/lkml/2004/5/23/10> for rationale (spoiler: SCO). You must use your real name in the Signed-off-by line and in any copyright notices you add. Patches without an associated real name lack provenance and cannot be committed! Developer's Certificate of Origin 1.1: By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it; and (d) In the case of each of (a), (b), or (c), I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license indicated in the file. Note: The Developer's Certificate of Origin 1.1 <http://web.archive.org/web/20070306195036/http://osdlab.org/newsroom/press_…> is licensed under the terms of the Creative Commons Attribution-ShareAlike 2.5 License <http://creativecommons.org/licenses/by-sa/2.5/>. Submitting a patch using GerritSetting up a Gerrit accountAll changes have to go through Gerrit on review.coreboot.org in order to be merged, even small patches such as adding support for a flash chip. Our Gerrit supports multiple authentication methods <https://review.coreboot.org/login> including OAUTH2, e.g. Google, GitHub or GitLab, or also OpenID. 1. Go to https://review.coreboot.org/login and sign in. 2. Edit your settings by clicking on the gear icon in the upper right corner. 3. Set your Gerrit username. 4. Add an email address so that you receive notifications when others commented or reviewed your patch. 5. Add a SSH public key to your account, or click the button to generate an HTTPS password. Preparing your local repository Open https://review.coreboot.org/admin/repos/flashrom and choose your desired method to clone the repository. Supported methods are HTTPS and SSH. The same method will also be used when you push your changes to Gerrit later. Also, make sure to install the Change-Id hook. This generates a unique ID which is appended to your commit message. It is used by Gerrit to identify if a patch with the same ID exists, and if so it will add a new version to it called “patchset”. If you are just about getting a fresh copy of the flashrom repository, then you can use the command which you can find under “Clone with commit-msg hook”. If you have an existing copy of the repository and you need to install the hook afterwards, then you can run this command within your flashrom directory - mkdir -p .git/hooks && curl -Lo `git rev-parse --git-dir`/hooks/commit-msg https://review.coreboot.org/tools/hooks/commit-msg; chmod +x `git rev-parse --git-dir`/hooks/commit-msg) Pushing your patch to Gerrit 1. Check out a new local branch that tracks origin/master: git checkout -b <branch_name> origin/master 2. Do your changes 3. Add your changes using `git add` and create a commit using `git commit -s` 4. Push to gerrit: git push origin HEAD:refs/for/master. - If using HTTPS you will be prompted for the username and password you set in the Gerrit UI. - If successful, the Gerrit URL for your patch will be shown in the output. -- Anastasia.

2 2

FAILED: Chip is in an uknown state!
by Marcel Grant 04 Mar '22

04 Mar '22

Trying to flash Skulls on this X230, but keep getting this error. What am I doing wrong? Please help. Can I turn of computer now? What else can I try? sudo ./skulls.sh -b x230 1) ./x230_coreboot_seabios_74d2218cc7_top.rom 3) Quit 2) ./x230_coreboot_seabios_free_74d2218cc7_top.rom file not specified. Please select a file to flash. Please read the README for details about the differences: 1 x230_coreboot_seabios_74d2218cc7_top.rom: OK input: x230_coreboot_seabios_74d2218cc7_top.rom output: output/x230_coreboot_seabios_74d2218cc7_top_prepared_12mb.rom Warning: Make sure not to power off your computer or interrupt this process in any way! Interrupting this process may result in irreparable damage to your computer! Flash the BIOS now? y/N: y flashrom v1.2 on Linux 5.13.0-30-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Using region: "bios". Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found chipset "Intel QM77". Enabling flash write... Warning: BIOS region SMM protection is enabled! Warning: Setting Bios Control at 0xdc from 0x2a to 0x09 failed. New value is 0x2a. SPI Configuration is locked down. FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only. FREG2: Management Engine region (0x00003000-0x004fffff) is locked. Not all flash regions are freely accessible by flashrom. This is most likely due to an active ME. Please see https://flashrom.org/ME for details. PR1: Warning: 0x00b40000-0x00bfffff is read-only. PR2: Warning: 0x00b10000-0x00b10fff is read-only. PR3: Warning: 0x00ad0000-0x00adefff is read-only. PR4: Warning: 0x00800000-0x00aaffff is read-only. At least some flash regions are read protected. You have to use a flash layout and include only accessible regions. For write operations, you'll additionally need the --noverify-all switch. See manpage for more details. Enabling hardware sequencing due to multiple flash chips detected. OK. Found Programmer flash chip "Opaque flash chip" (12288 kB, Programmer-specific) mapped at physical address 0x0000000000000000. Reading old flash chip contents... done. Erasing and writing flash chip... Transaction error between offset 0x00800000 and 0x00800fff (= 0x00800000 + 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. Your flash chip is in an unknown state. Get help on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with the subject "FAILED: <your board name>"! -------------------------------------------------------------------------------DO NOT REBOOT OR POWEROFF!

1 0

Help
by Amber Lukas 26 Feb '22

26 Feb '22

Trying to disable write protect on Acer Chromebook 15 to set seaBIOS to be default BIOS Get Outlook for Android<https://aka.ms/AAb9ysg>

1 0

Unsupported flash chip
by Jordan Thistle 25 Feb '22

25 Feb '22

Hello, I am using flashrom to read and write from a 16MB chip. I have attached the log for the chip as requested. Thanks, Jordan

1 0

Call for Mentors for GSoC 2022
by Anastasia Klimchuk 21 Feb '22

21 Feb '22

Good Day Flashrom People! As you might know already, we are currently preparing an application for GSoC 2022 (also known as Google Summer of Code, FAQ <https://developers.google.com/open-source/gsoc/faq>). We have gathered a list of Project Ideas, and it's time to call for Mentors! If you are interested in being a Mentor, please let us know. If you want to help, but not sure you can be a Mentor yourself, you can be a secondary Mentor. Or you can help by doing code reviews. Have a look into our Projects ideas, are you interested to Mentor one of these projects? https://docs.google.com/document/d/1AxMobB2v8Dv2uUwZPZ_vCmmONYDJuliHcnjfWOs… Or maybe you have another project idea that you want to mentor? Great! GSoC runs by a timeline https://developers.google.com/open-source/gsoc/timeline, check that dates are OK for you. How to let us know if you are interested: Reply All to this email. If you are in doubt, you can contact me (Anastasia/aklm) directly. Some more useful information: Mentor responsibilities (short) https://developers.google.com/open-source/gsoc/help/responsibilities#mentor… Mentor guides (long, lots of details) https://google.github.io/gsocguides/mentor/ If you have any questions, you are welcome to ask! ;) Your GSoC Org Admin, Anastasia.

6 9

Application for GSoC 2022
by Anastasia Klimchuk 17 Feb '22

17 Feb '22

Hello Everyone, I am planning to submit Flashrom’s GSoC application within the next few days. Here are the most important resources that we have prepared for application: Projects Ideas https://docs.google.com/document/d/1AxMobB2v8Dv2uUwZPZ_vCmmONYDJuliHcnjfWOs… Project Proposal Template https://docs.google.com/document/d/1DSg1FykuI7Z3JDY1Qtk8C6JjvpsYISMEwyV4932… Contributors Info and Guidelines https://www.flashrom.org/GSoC All these are resources for potential contributors, so that’s public and links can be shared with anyone interested. Application asks for *links* to resources, so we can modify/improve the content at any point, even after the app is submitted. We do want the resources to look nice when applying, of course :) but we can do modifications even later. Let me know if you have feedback/suggestions, thank you! -- Anastasia.

1 1

Report about RedmiBook 14 II
by Maxim Klimenko Sergievich 15 Feb '22

15 Feb '22

[root@mksredmibook14ii max]# flashrom --programmer internal flashrom v1.2 on Linux 5.16.9-arch1-1 (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... Disabling write protection of flash addresses from 0xff73a000 to 0xff78dbff failed. Disabling read write protection of flash addresses from 0xfff30000 to 0xfff7cfff failed. FCH device found but SMBus revision 0x51 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. [root@mksredmibook14ii max]# lspci -nnvx 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630] Subsystem: Xiaomi Device [1d72:1951] Flags: fast devsel 00: 22 10 30 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631] Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ -2147483648 Capabilities: [40] Secure device <?> Capabilities: [64] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00: 22 10 31 16 04 00 10 00 00 00 06 08 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 40 00 00 00 00 00 00 00 ff 01 00 00 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Flags: fast devsel, IOMMU group 0 00: 22 10 32 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Flags: fast devsel, IOMMU group 1 00: 22 10 32 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632] Flags: fast devsel, IOMMU group 2 00: 22 10 32 16 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 26, IOMMU group 2 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00001000-00001fff [size=4K] Memory behind bridge: d0100000-d04fffff [size=4M] Prefetchable memory behind bridge: 000000fce0000000-000000fcf01fffff [size=258M] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: pcieport 00: 22 10 35 16 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 11 11 00 00 20: 10 d0 40 d0 01 e0 11 f0 fc 00 00 00 fc 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 02 00 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 27, IOMMU group 2 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: d0000000-d00fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot-), MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: pcieport 00: 22 10 35 16 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00 00 00 00 02 02 00 f1 01 00 00 20: 00 d0 00 d0 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 02 00 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51) Subsystem: Xiaomi Device [1d72:1951] Flags: 66MHz, medium devsel, IOMMU group 3 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00: 22 10 0b 79 03 04 20 02 51 00 05 0c 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 3 00: 22 10 0e 79 0f 00 20 02 51 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0 [1022:1448] Flags: fast devsel, IOMMU group 4 00: 22 10 48 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1 [1022:1449] Flags: fast devsel, IOMMU group 4 00: 22 10 49 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2 [1022:144a] Flags: fast devsel, IOMMU group 4 00: 22 10 4a 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3 [1022:144b] Flags: fast devsel, IOMMU group 4 Kernel driver in use: k10temp Kernel modules: k10temp 00: 22 10 4b 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4 [1022:144c] Flags: fast devsel, IOMMU group 4 00: 22 10 4c 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5 [1022:144d] Flags: fast devsel, IOMMU group 4 00: 22 10 4d 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6 [1022:144e] Flags: fast devsel, IOMMU group 4 00: 22 10 4e 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7 [1022:144f] Flags: fast devsel, IOMMU group 4 00: 22 10 4f 14 00 00 00 00 00 00 00 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 2 Memory at fce0000000 (64-bit, prefetchable) [size=256M] Memory at fcf0000000 (64-bit, prefetchable) [size=2M] I/O ports at 1000 [size=256] Memory at d0400000 (32-bit, non-prefetchable) [size=512K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=4 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: amdgpu Kernel modules: amdgpu 00: 02 10 36 16 07 04 10 08 c3 00 00 03 10 00 80 00 10: 0c 00 00 e0 fc 00 00 00 0c 00 00 f0 fc 00 00 00 20: 01 10 00 00 00 00 40 d0 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 01 00 00 01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637] Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ 65, IOMMU group 2 Memory at d04c8000 (32-bit, non-prefetchable) [size=16K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 02 10 37 16 06 04 10 00 00 00 03 04 10 00 80 00 10: 00 80 4c d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 02 00 00 01:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df] Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ 59, IOMMU group 2 Memory at d0300000 (32-bit, non-prefetchable) [size=1M] Memory at d04cc000 (32-bit, non-prefetchable) [size=8K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=2 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: ccp Kernel modules: ccp 00: 22 10 df 15 06 04 10 08 00 00 80 10 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 30 d0 00 00 00 00 20: 00 00 00 00 00 c0 4c d0 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 03 00 00 01:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639] (prog-if 30 [XHCI]) Subsystem: Xiaomi Device [1d72:1951] Flags: fast devsel, IRQ 32, IOMMU group 2 Memory at d0100000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 39 16 03 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 10 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 04 00 00 01:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639] (prog-if 30 [XHCI]) Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 2 Memory at d0200000 (64-bit, non-prefetchable) [size=1M] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=8 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00: 22 10 39 16 07 04 10 00 00 30 03 0c 10 00 80 00 10: 04 00 20 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 01 00 00 01:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ 63, IOMMU group 2 Memory at d0480000 (32-bit, non-prefetchable) [size=256K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x 00: 22 10 e2 15 06 04 10 00 01 00 80 04 10 00 80 00 10: 00 00 48 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 02 00 00 01:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ 66, IOMMU group 2 Memory at d04c0000 (32-bit, non-prefetchable) [size=32K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00: 22 10 e3 15 06 04 10 00 00 00 03 04 10 00 80 00 10: 00 00 4c d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 03 00 00 02:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 81) (prog-if 01 [AHCI 1.0]) Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 2 Memory at d0001000 (32-bit, non-prefetchable) [size=2K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [d0] SATA HBA v1.0 Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express Capabilities: [400] Data Link Feature <?> Capabilities: [410] Physical Layer 16.0 GT/s <?> Capabilities: [440] Lane Margining at the Receiver <?> Kernel driver in use: ahci 00: 22 10 01 79 07 04 10 00 81 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 10 00 d0 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 01 00 00 02:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 81) (prog-if 01 [AHCI 1.0]) Subsystem: Xiaomi Device [1d72:1951] Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 2 Memory at d0000000 (32-bit, non-prefetchable) [size=2K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [d0] SATA HBA v1.0 Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: ahci 00: 22 10 01 79 07 04 10 00 81 01 06 01 10 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 d0 00 00 00 00 72 1d 51 19 30: 00 00 00 00 48 00 00 00 00 00 00 00 ff 02 00 00

1 1

GigaDevice flash chip "GD25Q40(B)" flash successful w/ ch341a
by Bryan S 13 Feb '22

13 Feb '22

sudo flashrom --force --programmer ch341a_spi -w gb56c flashrom v1.2 on Linux 5.11.0-7633-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 "GD25Q40(B)" (512 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... VERIFIED. Have used your tool to rescue many things with my handy ch341a Thank you for your work.

1 0

programmer ch341a_spi chip ESMT F25L32PA report
by Oleg Ivanov 10 Feb '22

10 Feb '22

READ: flashrom v1.2 on Linux 5.15.5-arch1-1 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.6.4, GCC 9.3.0, little endian Command line (7 args): flashrom -p ch341a_spi -V -c F25L32PA -r test.bin Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing ch341a_spi programmer Device revision is 3.0.4 The following protocols are supported: SPI. Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x8c, id2 0x2016 Found ESMT flash chip "F25L32PA" (4096 kB, SPI) on ch341a_spi. Chip status register is 0x1c. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 is not set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). === 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! Some block protection in effect, disabling... disabled. Reading flash... done. ERASE: flashrom v1.2 on Linux 5.15.5-arch1-1 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.6.4, GCC 9.3.0, little endian Command line (6 args): flashrom -p ch341a_spi -V -c F25L32PA -E Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing ch341a_spi programmer Device revision is 3.0.4 The following protocols are supported: SPI. Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x8c, id2 0x2016 Found ESMT flash chip "F25L32PA" (4096 kB, SPI) on ch341a_spi. Chip status register is 0x00. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). === 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! Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:E, 0x001000-0x001fff:E, 0x002000-0x002fff:E, 0x003000-0x003fff:E, 0x004000-0x004fff:E, 0x005000-0x005fff:E, 0x006000-0x006fff:E, 0x007000-0x007fff:E, 0x008000-0x008fff:E, 0x009000-0x009fff:E, 0x00a000-0x00afff:E, 0x00b000-0x00bfff:E, 0x00c000-0x00cfff:E, 0x00d000-0x00dfff:E, 0x00e000-0x00efff:E, 0x00f000-0x00ffff:E, 0x010000-0x010fff:E, 0x011000-0x011fff:E, 0x012000-0x012fff:E, 0x013000-0x013fff:E, 0x014000-0x014fff:E, 0x015000-0x015fff:E, 0x016000-0x016fff:E, 0x017000-0x017fff:E, 0x018000-0x018fff:E, 0x019000-0x019fff:E, 0x01a000-0x01afff:E, 0x01b000-0x01bfff:E, 0x01c000-0x01cfff:E, 0x01d000-0x01dfff:E, 0x01e000-0x01efff:E, 0x01f000-0x01ffff:E, 0x020000-0x020fff:E, 0x021000-0x021fff:E, 0x022000-0x022fff:E, 0x023000-0x023fff:E, 0x024000-0x024fff:E, 0x025000-0x025fff:E, 0x026000-0x026fff:E, 0x027000-0x027fff:E, 0x028000-0x028fff:E, 0x029000-0x029fff:E, 0x02a000-0x02afff:E, 0x02b000-0x02bfff:E, 0x02c000-0x02cfff:E, 0x02d000-0x02dfff:E, 0x02e000-0x02efff:E, 0x02f000-0x02ffff:E, 0x030000-0x030fff:E, 0x031000-0x031fff:E, 0x032000-0x032fff:E, 0x033000-0x033fff:E, 0x034000-0x034fff:E, 0x035000-0x035fff:E, 0x036000-0x036fff:E, 0x037000-0x037fff:E, 0x038000-0x038fff:E, 0x039000-0x039fff:E, 0x03a000-0x03afff:E, 0x03b000-0x03bfff:E, 0x03c000-0x03cfff:E, 0x03d000-0x03dfff:E, 0x03e000-0x03efff:E, 0x03f000-0x03ffff:E, 0x040000-0x040fff:E, 0x041000-0x041fff:E, 0x042000-0x042fff:E, 0x043000-0x043fff:E, 0x044000-0x044fff:E, 0x045000-0x045fff:E, 0x046000-0x046fff:E, 0x047000-0x047fff:E, 0x048000-0x048fff:E, 0x049000-0x049fff:E, 0x04a000-0x04afff:E, 0x04b000-0x04bfff:E, 0x04c000-0x04cfff:E, 0x04d000-0x04dfff:E, 0x04e000-0x04efff:E, 0x04f000-0x04ffff:E, 0x050000-0x050fff:E, 0x051000-0x051fff:E, 0x052000-0x052fff:E, 0x053000-0x053fff:E, 0x054000-0x054fff:E, 0x055000-0x055fff:E, 0x056000-0x056fff:E, 0x057000-0x057fff:E, 0x058000-0x058fff:E, 0x059000-0x059fff:E, 0x05a000-0x05afff:E, 0x05b000-0x05bfff:E, 0x05c000-0x05cfff:E, 0x05d000-0x05dfff:E, 0x05e000-0x05efff:E, 0x05f000-0x05ffff:E, 0x060000-0x060fff:E, 0x061000-0x061fff:E, 0x062000-0x062fff:E, 0x063000-0x063fff:E, 0x064000-0x064fff:E, 0x065000-0x065fff:E, 0x066000-0x066fff:E, 0x067000-0x067fff:E, 0x068000-0x068fff:E, 0x069000-0x069fff:E, 0x06a000-0x06afff:E, 0x06b000-0x06bfff:E, 0x06c000-0x06cfff:E, 0x06d000-0x06dfff:E, 0x06e000-0x06efff:E, 0x06f000-0x06ffff:E, 0x070000-0x070fff:E, 0x071000-0x071fff:E, 0x072000-0x072fff:E, 0x073000-0x073fff:E, 0x074000-0x074fff:E, 0x075000-0x075fff:E, 0x076000-0x076fff:E, 0x077000-0x077fff:E, 0x078000-0x078fff:E, 0x079000-0x079fff:E, 0x07a000-0x07afff:E, 0x07b000-0x07bfff:E, 0x07c000-0x07cfff:E, 0x07d000-0x07dfff:E, 0x07e000-0x07efff:E, 0x07f000-0x07ffff:E, 0x080000-0x080fff:E, 0x081000-0x081fff:E, 0x082000-0x082fff:E, 0x083000-0x083fff:E, 0x084000-0x084fff:E, 0x085000-0x085fff:E, 0x086000-0x086fff:E, 0x087000-0x087fff:E, 0x088000-0x088fff:E, 0x089000-0x089fff:E, 0x08a000-0x08afff:E, 0x08b000-0x08bfff:E, 0x08c000-0x08cfff:E, 0x08d000-0x08dfff:E, 0x08e000-0x08efff:E, 0x08f000-0x08ffff:E, 0x090000-0x090fff:E, 0x091000-0x091fff:E, 0x092000-0x092fff:E, 0x093000-0x093fff:E, 0x094000-0x094fff:E, 0x095000-0x095fff:E, 0x096000-0x096fff:E, 0x097000-0x097fff:E, 0x098000-0x098fff:E, 0x099000-0x099fff:E, 0x09a000-0x09afff:E, 0x09b000-0x09bfff:E, 0x09c000-0x09cfff:E, 0x09d000-0x09dfff:E, 0x09e000-0x09efff:E, 0x09f000-0x09ffff:E, 0x0a0000-0x0a0fff:E, 0x0a1000-0x0a1fff:E, 0x0a2000-0x0a2fff:E, 0x0a3000-0x0a3fff:E, 0x0a4000-0x0a4fff:E, 0x0a5000-0x0a5fff:E, 0x0a6000-0x0a6fff:E, 0x0a7000-0x0a7fff:E, 0x0a8000-0x0a8fff:E, 0x0a9000-0x0a9fff:E, 0x0aa000-0x0aafff:E, 0x0ab000-0x0abfff:E, 0x0ac000-0x0acfff:E, 0x0ad000-0x0adfff:E, 0x0ae000-0x0aefff:E, 0x0af000-0x0affff:E, 0x0b0000-0x0b0fff:E, 0x0b1000-0x0b1fff:E, 0x0b2000-0x0b2fff:E, 0x0b3000-0x0b3fff:E, 0x0b4000-0x0b4fff:E, 0x0b5000-0x0b5fff:E, 0x0b6000-0x0b6fff:E, 0x0b7000-0x0b7fff:E, 0x0b8000-0x0b8fff:E, 0x0b9000-0x0b9fff:E, 0x0ba000-0x0bafff:E, 0x0bb000-0x0bbfff:E, 0x0bc000-0x0bcfff:E, 0x0bd000-0x0bdfff:E, 0x0be000-0x0befff:E, 0x0bf000-0x0bffff:E, 0x0c0000-0x0c0fff:E, 0x0c1000-0x0c1fff:E, 0x0c2000-0x0c2fff:E, 0x0c3000-0x0c3fff:E, 0x0c4000-0x0c4fff:E, 0x0c5000-0x0c5fff:E, 0x0c6000-0x0c6fff:E, 0x0c7000-0x0c7fff:E, 0x0c8000-0x0c8fff:E, 0x0c9000-0x0c9fff:E, 0x0ca000-0x0cafff:E, 0x0cb000-0x0cbfff:E, 0x0cc000-0x0ccfff:E, 0x0cd000-0x0cdfff:E, 0x0ce000-0x0cefff:E, 0x0cf000-0x0cffff:E, 0x0d0000-0x0d0fff:E, 0x0d1000-0x0d1fff:E, 0x0d2000-0x0d2fff:E, 0x0d3000-0x0d3fff:E, 0x0d4000-0x0d4fff:E, 0x0d5000-0x0d5fff:E, 0x0d6000-0x0d6fff:E, 0x0d7000-0x0d7fff:E, 0x0d8000-0x0d8fff:E, 0x0d9000-0x0d9fff:E, 0x0da000-0x0dafff:E, 0x0db000-0x0dbfff:E, 0x0dc000-0x0dcfff:E, 0x0dd000-0x0ddfff:E, 0x0de000-0x0defff:E, 0x0df000-0x0dffff:E, 0x0e0000-0x0e0fff:E, 0x0e1000-0x0e1fff:E, 0x0e2000-0x0e2fff:E, 0x0e3000-0x0e3fff:E, 0x0e4000-0x0e4fff:E, 0x0e5000-0x0e5fff:E, 0x0e6000-0x0e6fff:E, 0x0e7000-0x0e7fff:E, 0x0e8000-0x0e8fff:E, 0x0e9000-0x0e9fff:E, 0x0ea000-0x0eafff:E, 0x0eb000-0x0ebfff:E, 0x0ec000-0x0ecfff:E, 0x0ed000-0x0edfff:E, 0x0ee000-0x0eefff:E, 0x0ef000-0x0effff:E, 0x0f0000-0x0f0fff:E, 0x0f1000-0x0f1fff:E, 0x0f2000-0x0f2fff:E, 0x0f3000-0x0f3fff:E, 0x0f4000-0x0f4fff:E, 0x0f5000-0x0f5fff:E, 0x0f6000-0x0f6fff:E, 0x0f7000-0x0f7fff:E, 0x0f8000-0x0f8fff:E, 0x0f9000-0x0f9fff:E, 0x0fa000-0x0fafff:E, 0x0fb000-0x0fbfff:E, 0x0fc000-0x0fcfff:E, 0x0fd000-0x0fdfff:E, 0x0fe000-0x0fefff:E, 0x0ff000-0x0fffff:E, 0x100000-0x100fff:E, 0x101000-0x101fff:E, 0x102000-0x102fff:E, 0x103000-0x103fff:E, 0x104000-0x104fff:E, 0x105000-0x105fff:E, 0x106000-0x106fff:E, 0x107000-0x107fff:E, 0x108000-0x108fff:E, 0x109000-0x109fff:E, 0x10a000-0x10afff:E, 0x10b000-0x10bfff:E, 0x10c000-0x10cfff:E, 0x10d000-0x10dfff:E, 0x10e000-0x10efff:E, 0x10f000-0x10ffff:E, 0x110000-0x110fff:E, 0x111000-0x111fff:E, 0x112000-0x112fff:E, 0x113000-0x113fff:E, 0x114000-0x114fff:E, 0x115000-0x115fff:E, 0x116000-0x116fff:E, 0x117000-0x117fff:E, 0x118000-0x118fff:E, 0x119000-0x119fff:E, 0x11a000-0x11afff:E, 0x11b000-0x11bfff:E, 0x11c000-0x11cfff:E, 0x11d000-0x11dfff:E, 0x11e000-0x11efff:E, 0x11f000-0x11ffff:E, 0x120000-0x120fff:E, 0x121000-0x121fff:E, 0x122000-0x122fff:E, 0x123000-0x123fff:E, 0x124000-0x124fff:E, 0x125000-0x125fff:E, 0x126000-0x126fff:E, 0x127000-0x127fff:E, 0x128000-0x128fff:E, 0x129000-0x129fff:E, 0x12a000-0x12afff:E, 0x12b000-0x12bfff:E, 0x12c000-0x12cfff:E, 0x12d000-0x12dfff:E, 0x12e000-0x12efff:E, 0x12f000-0x12ffff:E, 0x130000-0x130fff:E, 0x131000-0x131fff:E, 0x132000-0x132fff:E, 0x133000-0x133fff:E, 0x134000-0x134fff:E, 0x135000-0x135fff:E, 0x136000-0x136fff:E, 0x137000-0x137fff:E, 0x138000-0x138fff:E, 0x139000-0x139fff:E, 0x13a000-0x13afff:E, 0x13b000-0x13bfff:E, 0x13c000-0x13cfff:E, 0x13d000-0x13dfff:E, 0x13e000-0x13efff:E, 0x13f000-0x13ffff:E, 0x140000-0x140fff:E, 0x141000-0x141fff:E, 0x142000-0x142fff:E, 0x143000-0x143fff:E, 0x144000-0x144fff:E, 0x145000-0x145fff:E, 0x146000-0x146fff:E, 0x147000-0x147fff:E, 0x148000-0x148fff:E, 0x149000-0x149fff:E, 0x14a000-0x14afff:E, 0x14b000-0x14bfff:E, 0x14c000-0x14cfff:E, 0x14d000-0x14dfff:E, 0x14e000-0x14efff:E, 0x14f000-0x14ffff:E, 0x150000-0x150fff:E, 0x151000-0x151fff:E, 0x152000-0x152fff:E, 0x153000-0x153fff:E, 0x154000-0x154fff:E, 0x155000-0x155fff:E, 0x156000-0x156fff:E, 0x157000-0x157fff:E, 0x158000-0x158fff:E, 0x159000-0x159fff:E, 0x15a000-0x15afff:E, 0x15b000-0x15bfff:E, 0x15c000-0x15cfff:E, 0x15d000-0x15dfff:E, 0x15e000-0x15efff:E, 0x15f000-0x15ffff:E, 0x160000-0x160fff:E, 0x161000-0x161fff:E, 0x162000-0x162fff:E, 0x163000-0x163fff:E, 0x164000-0x164fff:E, 0x165000-0x165fff:E, 0x166000-0x166fff:E, 0x167000-0x167fff:E, 0x168000-0x168fff:E, 0x169000-0x169fff:E, 0x16a000-0x16afff:E, 0x16b000-0x16bfff:E, 0x16c000-0x16cfff:E, 0x16d000-0x16dfff:E, 0x16e000-0x16efff:E, 0x16f000-0x16ffff:E, 0x170000-0x170fff:E, 0x171000-0x171fff:E, 0x172000-0x172fff:E, 0x173000-0x173fff:E, 0x174000-0x174fff:E, 0x175000-0x175fff:E, 0x176000-0x176fff:E, 0x177000-0x177fff:E, 0x178000-0x178fff:E, 0x179000-0x179fff:E, 0x17a000-0x17afff:E, 0x17b000-0x17bfff:E, 0x17c000-0x17cfff:E, 0x17d000-0x17dfff:E, 0x17e000-0x17efff:E, 0x17f000-0x17ffff:E, 0x180000-0x180fff:E, 0x181000-0x181fff:E, 0x182000-0x182fff:E, 0x183000-0x183fff:E, 0x184000-0x184fff:E, 0x185000-0x185fff:E, 0x186000-0x186fff:E, 0x187000-0x187fff:E, 0x188000-0x188fff:E, 0x189000-0x189fff:E, 0x18a000-0x18afff:E, 0x18b000-0x18bfff:E, 0x18c000-0x18cfff:E, 0x18d000-0x18dfff:E, 0x18e000-0x18efff:E, 0x18f000-0x18ffff:E, 0x190000-0x190fff:E, 0x191000-0x191fff:E, 0x192000-0x192fff:E, 0x193000-0x193fff:E, 0x194000-0x194fff:E, 0x195000-0x195fff:E, 0x196000-0x196fff:E, 0x197000-0x197fff:E, 0x198000-0x198fff:E, 0x199000-0x199fff:E, 0x19a000-0x19afff:E, 0x19b000-0x19bfff:E, 0x19c000-0x19cfff:E, 0x19d000-0x19dfff:E, 0x19e000-0x19efff:E, 0x19f000-0x19ffff:E, 0x1a0000-0x1a0fff:E, 0x1a1000-0x1a1fff:E, 0x1a2000-0x1a2fff:E, 0x1a3000-0x1a3fff:E, 0x1a4000-0x1a4fff:E, 0x1a5000-0x1a5fff:E, 0x1a6000-0x1a6fff:E, 0x1a7000-0x1a7fff:E, 0x1a8000-0x1a8fff:E, 0x1a9000-0x1a9fff:E, 0x1aa000-0x1aafff:E, 0x1ab000-0x1abfff:E, 0x1ac000-0x1acfff:E, 0x1ad000-0x1adfff:E, 0x1ae000-0x1aefff:E, 0x1af000-0x1affff:E, 0x1b0000-0x1b0fff:E, 0x1b1000-0x1b1fff:E, 0x1b2000-0x1b2fff:E, 0x1b3000-0x1b3fff:E, 0x1b4000-0x1b4fff:E, 0x1b5000-0x1b5fff:E, 0x1b6000-0x1b6fff:E, 0x1b7000-0x1b7fff:E, 0x1b8000-0x1b8fff:E, 0x1b9000-0x1b9fff:E, 0x1ba000-0x1bafff:E, 0x1bb000-0x1bbfff:E, 0x1bc000-0x1bcfff:E, 0x1bd000-0x1bdfff:E, 0x1be000-0x1befff:E, 0x1bf000-0x1bffff:E, 0x1c0000-0x1c0fff:E, 0x1c1000-0x1c1fff:E, 0x1c2000-0x1c2fff:E, 0x1c3000-0x1c3fff:E, 0x1c4000-0x1c4fff:E, 0x1c5000-0x1c5fff:E, 0x1c6000-0x1c6fff:E, 0x1c7000-0x1c7fff:E, 0x1c8000-0x1c8fff:E, 0x1c9000-0x1c9fff:E, 0x1ca000-0x1cafff:E, 0x1cb000-0x1cbfff:E, 0x1cc000-0x1ccfff:E, 0x1cd000-0x1cdfff:E, 0x1ce000-0x1cefff:E, 0x1cf000-0x1cffff:E, 0x1d0000-0x1d0fff:E, 0x1d1000-0x1d1fff:E, 0x1d2000-0x1d2fff:E, 0x1d3000-0x1d3fff:E, 0x1d4000-0x1d4fff:E, 0x1d5000-0x1d5fff:E, 0x1d6000-0x1d6fff:E, 0x1d7000-0x1d7fff:E, 0x1d8000-0x1d8fff:E, 0x1d9000-0x1d9fff:E, 0x1da000-0x1dafff:E, 0x1db000-0x1dbfff:E, 0x1dc000-0x1dcfff:E, 0x1dd000-0x1ddfff:E, 0x1de000-0x1defff:E, 0x1df000-0x1dffff:E, 0x1e0000-0x1e0fff:E, 0x1e1000-0x1e1fff:E, 0x1e2000-0x1e2fff:E, 0x1e3000-0x1e3fff:E, 0x1e4000-0x1e4fff:E, 0x1e5000-0x1e5fff:E, 0x1e6000-0x1e6fff:E, 0x1e7000-0x1e7fff:E, 0x1e8000-0x1e8fff:E, 0x1e9000-0x1e9fff:E, 0x1ea000-0x1eafff:E, 0x1eb000-0x1ebfff:E, 0x1ec000-0x1ecfff:E, 0x1ed000-0x1edfff:E, 0x1ee000-0x1eefff:E, 0x1ef000-0x1effff:E, 0x1f0000-0x1f0fff:E, 0x1f1000-0x1f1fff:E, 0x1f2000-0x1f2fff:E, 0x1f3000-0x1f3fff:E, 0x1f4000-0x1f4fff:E, 0x1f5000-0x1f5fff:E, 0x1f6000-0x1f6fff:E, 0x1f7000-0x1f7fff:E, 0x1f8000-0x1f8fff:E, 0x1f9000-0x1f9fff:E, 0x1fa000-0x1fafff:E, 0x1fb000-0x1fbfff:E, 0x1fc000-0x1fcfff:E, 0x1fd000-0x1fdfff:E, 0x1fe000-0x1fefff:E, 0x1ff000-0x1fffff:E, 0x200000-0x200fff:E, 0x201000-0x201fff:E, 0x202000-0x202fff:E, 0x203000-0x203fff:E, 0x204000-0x204fff:E, 0x205000-0x205fff:E, 0x206000-0x206fff:E, 0x207000-0x207fff:E, 0x208000-0x208fff:E, 0x209000-0x209fff:E, 0x20a000-0x20afff:E, 0x20b000-0x20bfff:E, 0x20c000-0x20cfff:E, 0x20d000-0x20dfff:E, 0x20e000-0x20efff:E, 0x20f000-0x20ffff:E, 0x210000-0x210fff:E, 0x211000-0x211fff:E, 0x212000-0x212fff:E, 0x213000-0x213fff:E, 0x214000-0x214fff:E, 0x215000-0x215fff:E, 0x216000-0x216fff:E, 0x217000-0x217fff:E, 0x218000-0x218fff:E, 0x219000-0x219fff:E, 0x21a000-0x21afff:E, 0x21b000-0x21bfff:E, 0x21c000-0x21cfff:E, 0x21d000-0x21dfff:E, 0x21e000-0x21efff:E, 0x21f000-0x21ffff:E, 0x220000-0x220fff:E, 0x221000-0x221fff:E, 0x222000-0x222fff:E, 0x223000-0x223fff:E, 0x224000-0x224fff:E, 0x225000-0x225fff:E, 0x226000-0x226fff:E, 0x227000-0x227fff:E, 0x228000-0x228fff:E, 0x229000-0x229fff:E, 0x22a000-0x22afff:E, 0x22b000-0x22bfff:E, 0x22c000-0x22cfff:E, 0x22d000-0x22dfff:E, 0x22e000-0x22efff:E, 0x22f000-0x22ffff:E, 0x230000-0x230fff:E, 0x231000-0x231fff:E, 0x232000-0x232fff:E, 0x233000-0x233fff:E, 0x234000-0x234fff:E, 0x235000-0x235fff:E, 0x236000-0x236fff:E, 0x237000-0x237fff:E, 0x238000-0x238fff:E, 0x239000-0x239fff:E, 0x23a000-0x23afff:E, 0x23b000-0x23bfff:E, 0x23c000-0x23cfff:E, 0x23d000-0x23dfff:E, 0x23e000-0x23efff:E, 0x23f000-0x23ffff:E, 0x240000-0x240fff:E, 0x241000-0x241fff:E, 0x242000-0x242fff:E, 0x243000-0x243fff:E, 0x244000-0x244fff:E, 0x245000-0x245fff:E, 0x246000-0x246fff:E, 0x247000-0x247fff:E, 0x248000-0x248fff:E, 0x249000-0x249fff:E, 0x24a000-0x24afff:E, 0x24b000-0x24bfff:E, 0x24c000-0x24cfff:E, 0x24d000-0x24dfff:E, 0x24e000-0x24efff:E, 0x24f000-0x24ffff:E, 0x250000-0x250fff:E, 0x251000-0x251fff:E, 0x252000-0x252fff:E, 0x253000-0x253fff:E, 0x254000-0x254fff:E, 0x255000-0x255fff:E, 0x256000-0x256fff:E, 0x257000-0x257fff:E, 0x258000-0x258fff:E, 0x259000-0x259fff:E, 0x25a000-0x25afff:E, 0x25b000-0x25bfff:E, 0x25c000-0x25cfff:E, 0x25d000-0x25dfff:E, 0x25e000-0x25efff:E, 0x25f000-0x25ffff:E, 0x260000-0x260fff:E, 0x261000-0x261fff:E, 0x262000-0x262fff:E, 0x263000-0x263fff:E, 0x264000-0x264fff:E, 0x265000-0x265fff:E, 0x266000-0x266fff:E, 0x267000-0x267fff:E, 0x268000-0x268fff:E, 0x269000-0x269fff:E, 0x26a000-0x26afff:E, 0x26b000-0x26bfff:E, 0x26c000-0x26cfff:E, 0x26d000-0x26dfff:E, 0x26e000-0x26efff:E, 0x26f000-0x26ffff:E, 0x270000-0x270fff:E, 0x271000-0x271fff:E, 0x272000-0x272fff:E, 0x273000-0x273fff:E, 0x274000-0x274fff:E, 0x275000-0x275fff:E, 0x276000-0x276fff:E, 0x277000-0x277fff:E, 0x278000-0x278fff:E, 0x279000-0x279fff:E, 0x27a000-0x27afff:E, 0x27b000-0x27bfff:E, 0x27c000-0x27cfff:E, 0x27d000-0x27dfff:E, 0x27e000-0x27efff:E, 0x27f000-0x27ffff:E, 0x280000-0x280fff:E, 0x281000-0x281fff:E, 0x282000-0x282fff:E, 0x283000-0x283fff:E, 0x284000-0x284fff:E, 0x285000-0x285fff:E, 0x286000-0x286fff:E, 0x287000-0x287fff:E, 0x288000-0x288fff:E, 0x289000-0x289fff:E, 0x28a000-0x28afff:E, 0x28b000-0x28bfff:E, 0x28c000-0x28cfff:E, 0x28d000-0x28dfff:E, 0x28e000-0x28efff:E, 0x28f000-0x28ffff:E, 0x290000-0x290fff:E, 0x291000-0x291fff:E, 0x292000-0x292fff:E, 0x293000-0x293fff:E, 0x294000-0x294fff:E, 0x295000-0x295fff:E, 0x296000-0x296fff:E, 0x297000-0x297fff:E, 0x298000-0x298fff:E, 0x299000-0x299fff:E, 0x29a000-0x29afff:E, 0x29b000-0x29bfff:E, 0x29c000-0x29cfff:E, 0x29d000-0x29dfff:E, 0x29e000-0x29efff:E, 0x29f000-0x29ffff:E, 0x2a0000-0x2a0fff:E, 0x2a1000-0x2a1fff:E, 0x2a2000-0x2a2fff:E, 0x2a3000-0x2a3fff:E, 0x2a4000-0x2a4fff:E, 0x2a5000-0x2a5fff:E, 0x2a6000-0x2a6fff:E, 0x2a7000-0x2a7fff:E, 0x2a8000-0x2a8fff:E, 0x2a9000-0x2a9fff:E, 0x2aa000-0x2aafff:E, 0x2ab000-0x2abfff:E, 0x2ac000-0x2acfff:E, 0x2ad000-0x2adfff:E, 0x2ae000-0x2aefff:E, 0x2af000-0x2affff:E, 0x2b0000-0x2b0fff:E, 0x2b1000-0x2b1fff:E, 0x2b2000-0x2b2fff:E, 0x2b3000-0x2b3fff:E, 0x2b4000-0x2b4fff:E, 0x2b5000-0x2b5fff:E, 0x2b6000-0x2b6fff:E, 0x2b7000-0x2b7fff:E, 0x2b8000-0x2b8fff:E, 0x2b9000-0x2b9fff:E, 0x2ba000-0x2bafff:E, 0x2bb000-0x2bbfff:E, 0x2bc000-0x2bcfff:E, 0x2bd000-0x2bdfff:E, 0x2be000-0x2befff:E, 0x2bf000-0x2bffff:E, 0x2c0000-0x2c0fff:E, 0x2c1000-0x2c1fff:E, 0x2c2000-0x2c2fff:E, 0x2c3000-0x2c3fff:E, 0x2c4000-0x2c4fff:E, 0x2c5000-0x2c5fff:E, 0x2c6000-0x2c6fff:E, 0x2c7000-0x2c7fff:E, 0x2c8000-0x2c8fff:E, 0x2c9000-0x2c9fff:E, 0x2ca000-0x2cafff:E, 0x2cb000-0x2cbfff:E, 0x2cc000-0x2ccfff:E, 0x2cd000-0x2cdfff:E, 0x2ce000-0x2cefff:E, 0x2cf000-0x2cffff:E, 0x2d0000-0x2d0fff:E, 0x2d1000-0x2d1fff:E, 0x2d2000-0x2d2fff:E, 0x2d3000-0x2d3fff:E, 0x2d4000-0x2d4fff:E, 0x2d5000-0x2d5fff:E, 0x2d6000-0x2d6fff:E, 0x2d7000-0x2d7fff:E, 0x2d8000-0x2d8fff:E, 0x2d9000-0x2d9fff:E, 0x2da000-0x2dafff:E, 0x2db000-0x2dbfff:E, 0x2dc000-0x2dcfff:E, 0x2dd000-0x2ddfff:E, 0x2de000-0x2defff:E, 0x2df000-0x2dffff:E, 0x2e0000-0x2e0fff:E, 0x2e1000-0x2e1fff:E, 0x2e2000-0x2e2fff:E, 0x2e3000-0x2e3fff:E, 0x2e4000-0x2e4fff:E, 0x2e5000-0x2e5fff:E, 0x2e6000-0x2e6fff:E, 0x2e7000-0x2e7fff:E, 0x2e8000-0x2e8fff:E, 0x2e9000-0x2e9fff:E, 0x2ea000-0x2eafff:E, 0x2eb000-0x2ebfff:E, 0x2ec000-0x2ecfff:E, 0x2ed000-0x2edfff:E, 0x2ee000-0x2eefff:E, 0x2ef000-0x2effff:E, 0x2f0000-0x2f0fff:E, 0x2f1000-0x2f1fff:E, 0x2f2000-0x2f2fff:E, 0x2f3000-0x2f3fff:E, 0x2f4000-0x2f4fff:E, 0x2f5000-0x2f5fff:E, 0x2f6000-0x2f6fff:E, 0x2f7000-0x2f7fff:E, 0x2f8000-0x2f8fff:E, 0x2f9000-0x2f9fff:E, 0x2fa000-0x2fafff:E, 0x2fb000-0x2fbfff:E, 0x2fc000-0x2fcfff:E, 0x2fd000-0x2fdfff:E, 0x2fe000-0x2fefff:E, 0x2ff000-0x2fffff:E, 0x300000-0x300fff:E, 0x301000-0x301fff:E, 0x302000-0x302fff:E, 0x303000-0x303fff:E, 0x304000-0x304fff:E, 0x305000-0x305fff:E, 0x306000-0x306fff:E, 0x307000-0x307fff:E, 0x308000-0x308fff:E, 0x309000-0x309fff:E, 0x30a000-0x30afff:E, 0x30b000-0x30bfff:E, 0x30c000-0x30cfff:E, 0x30d000-0x30dfff:E, 0x30e000-0x30efff:E, 0x30f000-0x30ffff:E, 0x310000-0x310fff:E, 0x311000-0x311fff:E, 0x312000-0x312fff:E, 0x313000-0x313fff:E, 0x314000-0x314fff:E, 0x315000-0x315fff:E, 0x316000-0x316fff:E, 0x317000-0x317fff:E, 0x318000-0x318fff:E, 0x319000-0x319fff:E, 0x31a000-0x31afff:E, 0x31b000-0x31bfff:E, 0x31c000-0x31cfff:E, 0x31d000-0x31dfff:E, 0x31e000-0x31efff:E, 0x31f000-0x31ffff:E, 0x320000-0x320fff:E, 0x321000-0x321fff:E, 0x322000-0x322fff:E, 0x323000-0x323fff:E, 0x324000-0x324fff:E, 0x325000-0x325fff:E, 0x326000-0x326fff:E, 0x327000-0x327fff:E, 0x328000-0x328fff:E, 0x329000-0x329fff:E, 0x32a000-0x32afff:E, 0x32b000-0x32bfff:E, 0x32c000-0x32cfff:E, 0x32d000-0x32dfff:E, 0x32e000-0x32efff:E, 0x32f000-0x32ffff:E, 0x330000-0x330fff:E, 0x331000-0x331fff:E, 0x332000-0x332fff:E, 0x333000-0x333fff:E, 0x334000-0x334fff:E, 0x335000-0x335fff:E, 0x336000-0x336fff:E, 0x337000-0x337fff:E, 0x338000-0x338fff:E, 0x339000-0x339fff:E, 0x33a000-0x33afff:E, 0x33b000-0x33bfff:E, 0x33c000-0x33cfff:E, 0x33d000-0x33dfff:E, 0x33e000-0x33efff:E, 0x33f000-0x33ffff:E, 0x340000-0x340fff:E, 0x341000-0x341fff:E, 0x342000-0x342fff:E, 0x343000-0x343fff:E, 0x344000-0x344fff:E, 0x345000-0x345fff:E, 0x346000-0x346fff:E, 0x347000-0x347fff:E, 0x348000-0x348fff:E, 0x349000-0x349fff:E, 0x34a000-0x34afff:E, 0x34b000-0x34bfff:E, 0x34c000-0x34cfff:E, 0x34d000-0x34dfff:E, 0x34e000-0x34efff:E, 0x34f000-0x34ffff:E, 0x350000-0x350fff:E, 0x351000-0x351fff:E, 0x352000-0x352fff:E, 0x353000-0x353fff:E, 0x354000-0x354fff:E, 0x355000-0x355fff:E, 0x356000-0x356fff:E, 0x357000-0x357fff:E, 0x358000-0x358fff:E, 0x359000-0x359fff:E, 0x35a000-0x35afff:E, 0x35b000-0x35bfff:E, 0x35c000-0x35cfff:E, 0x35d000-0x35dfff:E, 0x35e000-0x35efff:E, 0x35f000-0x35ffff:E, 0x360000-0x360fff:E, 0x361000-0x361fff:E, 0x362000-0x362fff:E, 0x363000-0x363fff:E, 0x364000-0x364fff:E, 0x365000-0x365fff:E, 0x366000-0x366fff:E, 0x367000-0x367fff:E, 0x368000-0x368fff:E, 0x369000-0x369fff:E, 0x36a000-0x36afff:E, 0x36b000-0x36bfff:E, 0x36c000-0x36cfff:E, 0x36d000-0x36dfff:E, 0x36e000-0x36efff:E, 0x36f000-0x36ffff:E, 0x370000-0x370fff:E, 0x371000-0x371fff:E, 0x372000-0x372fff:E, 0x373000-0x373fff:E, 0x374000-0x374fff:E, 0x375000-0x375fff:E, 0x376000-0x376fff:E, 0x377000-0x377fff:E, 0x378000-0x378fff:E, 0x379000-0x379fff:E, 0x37a000-0x37afff:E, 0x37b000-0x37bfff:E, 0x37c000-0x37cfff:E, 0x37d000-0x37dfff:E, 0x37e000-0x37efff:E, 0x37f000-0x37ffff:E, 0x380000-0x380fff:E, 0x381000-0x381fff:E, 0x382000-0x382fff:E, 0x383000-0x383fff:E, 0x384000-0x384fff:E, 0x385000-0x385fff:E, 0x386000-0x386fff:E, 0x387000-0x387fff:E, 0x388000-0x388fff:E, 0x389000-0x389fff:E, 0x38a000-0x38afff:E, 0x38b000-0x38bfff:E, 0x38c000-0x38cfff:E, 0x38d000-0x38dfff:E, 0x38e000-0x38efff:E, 0x38f000-0x38ffff:E, 0x390000-0x390fff:E, 0x391000-0x391fff:E, 0x392000-0x392fff:E, 0x393000-0x393fff:E, 0x394000-0x394fff:E, 0x395000-0x395fff:E, 0x396000-0x396fff:E, 0x397000-0x397fff:E, 0x398000-0x398fff:E, 0x399000-0x399fff:E, 0x39a000-0x39afff:E, 0x39b000-0x39bfff:E, 0x39c000-0x39cfff:E, 0x39d000-0x39dfff:E, 0x39e000-0x39efff:E, 0x39f000-0x39ffff:E, 0x3a0000-0x3a0fff:E, 0x3a1000-0x3a1fff:E, 0x3a2000-0x3a2fff:E, 0x3a3000-0x3a3fff:E, 0x3a4000-0x3a4fff:E, 0x3a5000-0x3a5fff:E, 0x3a6000-0x3a6fff:E, 0x3a7000-0x3a7fff:E, 0x3a8000-0x3a8fff:E, 0x3a9000-0x3a9fff:E, 0x3aa000-0x3aafff:E, 0x3ab000-0x3abfff:E, 0x3ac000-0x3acfff:E, 0x3ad000-0x3adfff:E, 0x3ae000-0x3aefff:E, 0x3af000-0x3affff:E, 0x3b0000-0x3b0fff:E, 0x3b1000-0x3b1fff:E, 0x3b2000-0x3b2fff:E, 0x3b3000-0x3b3fff:E, 0x3b4000-0x3b4fff:E, 0x3b5000-0x3b5fff:E, 0x3b6000-0x3b6fff:E, 0x3b7000-0x3b7fff:E, 0x3b8000-0x3b8fff:E, 0x3b9000-0x3b9fff:E, 0x3ba000-0x3bafff:E, 0x3bb000-0x3bbfff:E, 0x3bc000-0x3bcfff:E, 0x3bd000-0x3bdfff:E, 0x3be000-0x3befff:E, 0x3bf000-0x3bffff:E, 0x3c0000-0x3c0fff:E, 0x3c1000-0x3c1fff:E, 0x3c2000-0x3c2fff:E, 0x3c3000-0x3c3fff:E, 0x3c4000-0x3c4fff:E, 0x3c5000-0x3c5fff:E, 0x3c6000-0x3c6fff:E, 0x3c7000-0x3c7fff:E, 0x3c8000-0x3c8fff:E, 0x3c9000-0x3c9fff:E, 0x3ca000-0x3cafff:E, 0x3cb000-0x3cbfff:E, 0x3cc000-0x3ccfff:E, 0x3cd000-0x3cdfff:E, 0x3ce000-0x3cefff:E, 0x3cf000-0x3cffff:E, 0x3d0000-0x3d0fff:E, 0x3d1000-0x3d1fff:E, 0x3d2000-0x3d2fff:E, 0x3d3000-0x3d3fff:E, 0x3d4000-0x3d4fff:E, 0x3d5000-0x3d5fff:E, 0x3d6000-0x3d6fff:E, 0x3d7000-0x3d7fff:E, 0x3d8000-0x3d8fff:E, 0x3d9000-0x3d9fff:E, 0x3da000-0x3dafff:E, 0x3db000-0x3dbfff:E, 0x3dc000-0x3dcfff:E, 0x3dd000-0x3ddfff:E, 0x3de000-0x3defff:E, 0x3df000-0x3dffff:E, 0x3e0000-0x3e0fff:E, 0x3e1000-0x3e1fff:E, 0x3e2000-0x3e2fff:E, 0x3e3000-0x3e3fff:E, 0x3e4000-0x3e4fff:E, 0x3e5000-0x3e5fff:E, 0x3e6000-0x3e6fff:E, 0x3e7000-0x3e7fff:E, 0x3e8000-0x3e8fff:E, 0x3e9000-0x3e9fff:E, 0x3ea000-0x3eafff:E, 0x3eb000-0x3ebfff:E, 0x3ec000-0x3ecfff:E, 0x3ed000-0x3edfff:E, 0x3ee000-0x3eefff:E, 0x3ef000-0x3effff:E, 0x3f0000-0x3f0fff:E, 0x3f1000-0x3f1fff:E, 0x3f2000-0x3f2fff:E, 0x3f3000-0x3f3fff:E, 0x3f4000-0x3f4fff:E, 0x3f5000-0x3f5fff:E, 0x3f6000-0x3f6fff:E, 0x3f7000-0x3f7fff:E, 0x3f8000-0x3f8fff:E, 0x3f9000-0x3f9fff:E, 0x3fa000-0x3fafff:E, 0x3fb000-0x3fbfff:E, 0x3fc000-0x3fcfff:E, 0x3fd000-0x3fdfff:E, 0x3fe000-0x3fefff:E, 0x3ff000-0x3fffff:E Erase/write done. READ AFTER ERASE: all OK, chip dump contains 0xFF only WRITE: flashrom v1.2 on Linux 5.15.5-arch1-1 (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.6.4, GCC 9.3.0, little endian Command line (7 args): flashrom -p ch341a_spi -V -c F25L32PA -w test.bin Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing ch341a_spi programmer Device revision is 3.0.4 The following protocols are supported: SPI. Probing for ESMT F25L32PA, 4096 kB: probe_spi_rdid_generic: id1 0x8c, id2 0x2016 Found ESMT flash chip "F25L32PA" (4096 kB, SPI) on ch341a_spi. Chip status register is 0x00. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Bit 6 is not set Chip status register: Bit 5 is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). === 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... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:W, 0x002000-0x002fff:W, 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:W, 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W, 0x020000-0x020fff:W, 0x021000-0x021fff:W, 0x022000-0x022fff:W, 0x023000-0x023fff:W, 0x024000-0x024fff:W, 0x025000-0x025fff:W, 0x026000-0x026fff:W, 0x027000-0x027fff:W, 0x028000-0x028fff:W, 0x029000-0x029fff:W, 0x02a000-0x02afff:W, 0x02b000-0x02bfff:W, 0x02c000-0x02cfff:W, 0x02d000-0x02dfff:W, 0x02e000-0x02efff:W, 0x02f000-0x02ffff:W, 0x030000-0x030fff:W, 0x031000-0x031fff:W, 0x032000-0x032fff:W, 0x033000-0x033fff:W, 0x034000-0x034fff:W, 0x035000-0x035fff:W, 0x036000-0x036fff:W, 0x037000-0x037fff:W, 0x038000-0x038fff:W, 0x039000-0x039fff:W, 0x03a000-0x03afff:W, 0x03b000-0x03bfff:W, 0x03c000-0x03cfff:W, 0x03d000-0x03dfff:W, 0x03e000-0x03efff:W, 0x03f000-0x03ffff:W, 0x040000-0x040fff:W, 0x041000-0x041fff:W, 0x042000-0x042fff:W, 0x043000-0x043fff:W, 0x044000-0x044fff:W, 0x045000-0x045fff:W, 0x046000-0x046fff:W, 0x047000-0x047fff:W, 0x048000-0x048fff:W, 0x049000-0x049fff:W, 0x04a000-0x04afff:W, 0x04b000-0x04bfff:W, 0x04c000-0x04cfff:W, 0x04d000-0x04dfff:W, 0x04e000-0x04efff:W, 0x04f000-0x04ffff:W, 0x050000-0x050fff:W, 0x051000-0x051fff:W, 0x052000-0x052fff:W, 0x053000-0x053fff:W, 0x054000-0x054fff:W, 0x055000-0x055fff:W, 0x056000-0x056fff:W, 0x057000-0x057fff:W, 0x058000-0x058fff:W, 0x059000-0x059fff:W, 0x05a000-0x05afff:W, 0x05b000-0x05bfff:W, 0x05c000-0x05cfff:W, 0x05d000-0x05dfff:W, 0x05e000-0x05efff:W, 0x05f000-0x05ffff:W, 0x060000-0x060fff:W, 0x061000-0x061fff:W, 0x062000-0x062fff:W, 0x063000-0x063fff:W, 0x064000-0x064fff:W, 0x065000-0x065fff:W, 0x066000-0x066fff:W, 0x067000-0x067fff:W, 0x068000-0x068fff:W, 0x069000-0x069fff:W, 0x06a000-0x06afff:W, 0x06b000-0x06bfff:W, 0x06c000-0x06cfff:W, 0x06d000-0x06dfff:W, 0x06e000-0x06efff:W, 0x06f000-0x06ffff:W, 0x070000-0x070fff:W, 0x071000-0x071fff:W, 0x072000-0x072fff:W, 0x073000-0x073fff:W, 0x074000-0x074fff:W, 0x075000-0x075fff:W, 0x076000-0x076fff:W, 0x077000-0x077fff:W, 0x078000-0x078fff:W, 0x079000-0x079fff:W, 0x07a000-0x07afff:W, 0x07b000-0x07bfff:W, 0x07c000-0x07cfff:W, 0x07d000-0x07dfff:W, 0x07e000-0x07efff:W, 0x07f000-0x07ffff:W, 0x080000-0x080fff:W, 0x081000-0x081fff:W, 0x082000-0x082fff:W, 0x083000-0x083fff:W, 0x084000-0x084fff:W, 0x085000-0x085fff:W, 0x086000-0x086fff:W, 0x087000-0x087fff:W, 0x088000-0x088fff:W, 0x089000-0x089fff:W, 0x08a000-0x08afff:W, 0x08b000-0x08bfff:W, 0x08c000-0x08cfff:W, 0x08d000-0x08dfff:W, 0x08e000-0x08efff:W, 0x08f000-0x08ffff:W, 0x090000-0x090fff:W, 0x091000-0x091fff:W, 0x092000-0x092fff:W, 0x093000-0x093fff:W, 0x094000-0x094fff:W, 0x095000-0x095fff:W, 0x096000-0x096fff:W, 0x097000-0x097fff:W, 0x098000-0x098fff:W, 0x099000-0x099fff:W, 0x09a000-0x09afff:W, 0x09b000-0x09bfff:W, 0x09c000-0x09cfff:W, 0x09d000-0x09dfff:W, 0x09e000-0x09efff:W, 0x09f000-0x09ffff:W, 0x0a0000-0x0a0fff:W, 0x0a1000-0x0a1fff:W, 0x0a2000-0x0a2fff:W, 0x0a3000-0x0a3fff:W, 0x0a4000-0x0a4fff:W, 0x0a5000-0x0a5fff:W, 0x0a6000-0x0a6fff:W, 0x0a7000-0x0a7fff:W, 0x0a8000-0x0a8fff:W, 0x0a9000-0x0a9fff:W, 0x0aa000-0x0aafff:W, 0x0ab000-0x0abfff:W, 0x0ac000-0x0acfff:W, 0x0ad000-0x0adfff:W, 0x0ae000-0x0aefff:W, 0x0af000-0x0affff:W, 0x0b0000-0x0b0fff:W, 0x0b1000-0x0b1fff:W, 0x0b2000-0x0b2fff:W, 0x0b3000-0x0b3fff:W, 0x0b4000-0x0b4fff:W, 0x0b5000-0x0b5fff:W, 0x0b6000-0x0b6fff:W, 0x0b7000-0x0b7fff:W, 0x0b8000-0x0b8fff:W, 0x0b9000-0x0b9fff:W, 0x0ba000-0x0bafff:W, 0x0bb000-0x0bbfff:W, 0x0bc000-0x0bcfff:W, 0x0bd000-0x0bdfff:W, 0x0be000-0x0befff:W, 0x0bf000-0x0bffff:W, 0x0c0000-0x0c0fff:W, 0x0c1000-0x0c1fff:W, 0x0c2000-0x0c2fff:W, 0x0c3000-0x0c3fff:W, 0x0c4000-0x0c4fff:W, 0x0c5000-0x0c5fff:W, 0x0c6000-0x0c6fff:W, 0x0c7000-0x0c7fff:W, 0x0c8000-0x0c8fff:W, 0x0c9000-0x0c9fff:W, 0x0ca000-0x0cafff:W, 0x0cb000-0x0cbfff:W, 0x0cc000-0x0ccfff:W, 0x0cd000-0x0cdfff:W, 0x0ce000-0x0cefff:W, 0x0cf000-0x0cffff:W, 0x0d0000-0x0d0fff:W, 0x0d1000-0x0d1fff:W, 0x0d2000-0x0d2fff:W, 0x0d3000-0x0d3fff:W, 0x0d4000-0x0d4fff:W, 0x0d5000-0x0d5fff:W, 0x0d6000-0x0d6fff:W, 0x0d7000-0x0d7fff:W, 0x0d8000-0x0d8fff:W, 0x0d9000-0x0d9fff:W, 0x0da000-0x0dafff:W, 0x0db000-0x0dbfff:W, 0x0dc000-0x0dcfff:W, 0x0dd000-0x0ddfff:W, 0x0de000-0x0defff:W, 0x0df000-0x0dffff:W, 0x0e0000-0x0e0fff:W, 0x0e1000-0x0e1fff:W, 0x0e2000-0x0e2fff:W, 0x0e3000-0x0e3fff:W, 0x0e4000-0x0e4fff:W, 0x0e5000-0x0e5fff:W, 0x0e6000-0x0e6fff:W, 0x0e7000-0x0e7fff:W, 0x0e8000-0x0e8fff:W, 0x0e9000-0x0e9fff:W, 0x0ea000-0x0eafff:W, 0x0eb000-0x0ebfff:W, 0x0ec000-0x0ecfff:W, 0x0ed000-0x0edfff:W, 0x0ee000-0x0eefff:W, 0x0ef000-0x0effff:W, 0x0f0000-0x0f0fff:W, 0x0f1000-0x0f1fff:W, 0x0f2000-0x0f2fff:W, 0x0f3000-0x0f3fff:W, 0x0f4000-0x0f4fff:W, 0x0f5000-0x0f5fff:W, 0x0f6000-0x0f6fff:W, 0x0f7000-0x0f7fff:W, 0x0f8000-0x0f8fff:W, 0x0f9000-0x0f9fff:W, 0x0fa000-0x0fafff:W, 0x0fb000-0x0fbfff:W, 0x0fc000-0x0fcfff:W, 0x0fd000-0x0fdfff:W, 0x0fe000-0x0fefff:W, 0x0ff000-0x0fffff:W, 0x100000-0x100fff:W, 0x101000-0x101fff:W, 0x102000-0x102fff:W, 0x103000-0x103fff:W, 0x104000-0x104fff:W, 0x105000-0x105fff:W, 0x106000-0x106fff:W, 0x107000-0x107fff:W, 0x108000-0x108fff:W, 0x109000-0x109fff:W, 0x10a000-0x10afff:W, 0x10b000-0x10bfff:W, 0x10c000-0x10cfff:W, 0x10d000-0x10dfff:W, 0x10e000-0x10efff:W, 0x10f000-0x10ffff:W, 0x110000-0x110fff:W, 0x111000-0x111fff:W, 0x112000-0x112fff:W, 0x113000-0x113fff:W, 0x114000-0x114fff:W, 0x115000-0x115fff:W, 0x116000-0x116fff:W, 0x117000-0x117fff:W, 0x118000-0x118fff:W, 0x119000-0x119fff:W, 0x11a000-0x11afff:W, 0x11b000-0x11bfff:W, 0x11c000-0x11cfff:W, 0x11d000-0x11dfff:W, 0x11e000-0x11efff:W, 0x11f000-0x11ffff:W, 0x120000-0x120fff:W, 0x121000-0x121fff:W, 0x122000-0x122fff:W, 0x123000-0x123fff:W, 0x124000-0x124fff:W, 0x125000-0x125fff:W, 0x126000-0x126fff:W, 0x127000-0x127fff:W, 0x128000-0x128fff:W, 0x129000-0x129fff:W, 0x12a000-0x12afff:W, 0x12b000-0x12bfff:W, 0x12c000-0x12cfff:W, 0x12d000-0x12dfff:W, 0x12e000-0x12efff:W, 0x12f000-0x12ffff:W, 0x130000-0x130fff:W, 0x131000-0x131fff:W, 0x132000-0x132fff:W, 0x133000-0x133fff:W, 0x134000-0x134fff:W, 0x135000-0x135fff:W, 0x136000-0x136fff:W, 0x137000-0x137fff:W, 0x138000-0x138fff:W, 0x139000-0x139fff:W, 0x13a000-0x13afff:W, 0x13b000-0x13bfff:W, 0x13c000-0x13cfff:W, 0x13d000-0x13dfff:W, 0x13e000-0x13efff:W, 0x13f000-0x13ffff:W, 0x140000-0x140fff:W, 0x141000-0x141fff:W, 0x142000-0x142fff:W, 0x143000-0x143fff:W, 0x144000-0x144fff:W, 0x145000-0x145fff:W, 0x146000-0x146fff:W, 0x147000-0x147fff:W, 0x148000-0x148fff:W, 0x149000-0x149fff:W, 0x14a000-0x14afff:W, 0x14b000-0x14bfff:W, 0x14c000-0x14cfff:W, 0x14d000-0x14dfff:W, 0x14e000-0x14efff:W, 0x14f000-0x14ffff:W, 0x150000-0x150fff:W, 0x151000-0x151fff:W, 0x152000-0x152fff:W, 0x153000-0x153fff:W, 0x154000-0x154fff:W, 0x155000-0x155fff:W, 0x156000-0x156fff:W, 0x157000-0x157fff:W, 0x158000-0x158fff:W, 0x159000-0x159fff:W, 0x15a000-0x15afff:W, 0x15b000-0x15bfff:W, 0x15c000-0x15cfff:W, 0x15d000-0x15dfff:W, 0x15e000-0x15efff:W, 0x15f000-0x15ffff:W, 0x160000-0x160fff:W, 0x161000-0x161fff:W, 0x162000-0x162fff:W, 0x163000-0x163fff:W, 0x164000-0x164fff:W, 0x165000-0x165fff:W, 0x166000-0x166fff:W, 0x167000-0x167fff:W, 0x168000-0x168fff:W, 0x169000-0x169fff:W, 0x16a000-0x16afff:W, 0x16b000-0x16bfff:W, 0x16c000-0x16cfff:W, 0x16d000-0x16dfff:W, 0x16e000-0x16efff:W, 0x16f000-0x16ffff:W, 0x170000-0x170fff:W, 0x171000-0x171fff:W, 0x172000-0x172fff:W, 0x173000-0x173fff:W, 0x174000-0x174fff:W, 0x175000-0x175fff:W, 0x176000-0x176fff:W, 0x177000-0x177fff:W, 0x178000-0x178fff:W, 0x179000-0x179fff:W, 0x17a000-0x17afff:W, 0x17b000-0x17bfff:W, 0x17c000-0x17cfff:W, 0x17d000-0x17dfff:W, 0x17e000-0x17efff:W, 0x17f000-0x17ffff:W, 0x180000-0x180fff:W, 0x181000-0x181fff:W, 0x182000-0x182fff:W, 0x183000-0x183fff:W, 0x184000-0x184fff:W, 0x185000-0x185fff:W, 0x186000-0x186fff:W, 0x187000-0x187fff:W, 0x188000-0x188fff:W, 0x189000-0x189fff:W, 0x18a000-0x18afff:W, 0x18b000-0x18bfff:W, 0x18c000-0x18cfff:W, 0x18d000-0x18dfff:W, 0x18e000-0x18efff:W, 0x18f000-0x18ffff:W, 0x190000-0x190fff:W, 0x191000-0x191fff:W, 0x192000-0x192fff:W, 0x193000-0x193fff:W, 0x194000-0x194fff:W, 0x195000-0x195fff:W, 0x196000-0x196fff:W, 0x197000-0x197fff:W, 0x198000-0x198fff:W, 0x199000-0x199fff:W, 0x19a000-0x19afff:W, 0x19b000-0x19bfff:W, 0x19c000-0x19cfff:W, 0x19d000-0x19dfff:W, 0x19e000-0x19efff:W, 0x19f000-0x19ffff:W, 0x1a0000-0x1a0fff:W, 0x1a1000-0x1a1fff:W, 0x1a2000-0x1a2fff:W, 0x1a3000-0x1a3fff:W, 0x1a4000-0x1a4fff:W, 0x1a5000-0x1a5fff:W, 0x1a6000-0x1a6fff:W, 0x1a7000-0x1a7fff:W, 0x1a8000-0x1a8fff:W, 0x1a9000-0x1a9fff:W, 0x1aa000-0x1aafff:W, 0x1ab000-0x1abfff:W, 0x1ac000-0x1acfff:W, 0x1ad000-0x1adfff:W, 0x1ae000-0x1aefff:W, 0x1af000-0x1affff:W, 0x1b0000-0x1b0fff:W, 0x1b1000-0x1b1fff:W, 0x1b2000-0x1b2fff:W, 0x1b3000-0x1b3fff:W, 0x1b4000-0x1b4fff:W, 0x1b5000-0x1b5fff:W, 0x1b6000-0x1b6fff:W, 0x1b7000-0x1b7fff:W, 0x1b8000-0x1b8fff:W, 0x1b9000-0x1b9fff:W, 0x1ba000-0x1bafff:W, 0x1bb000-0x1bbfff:W, 0x1bc000-0x1bcfff:W, 0x1bd000-0x1bdfff:W, 0x1be000-0x1befff:W, 0x1bf000-0x1bffff:W, 0x1c0000-0x1c0fff:W, 0x1c1000-0x1c1fff:W, 0x1c2000-0x1c2fff:W, 0x1c3000-0x1c3fff:W, 0x1c4000-0x1c4fff:W, 0x1c5000-0x1c5fff:W, 0x1c6000-0x1c6fff:W, 0x1c7000-0x1c7fff:W, 0x1c8000-0x1c8fff:W, 0x1c9000-0x1c9fff:W, 0x1ca000-0x1cafff:W, 0x1cb000-0x1cbfff:W, 0x1cc000-0x1ccfff:W, 0x1cd000-0x1cdfff:W, 0x1ce000-0x1cefff:W, 0x1cf000-0x1cffff:W, 0x1d0000-0x1d0fff:W, 0x1d1000-0x1d1fff:W, 0x1d2000-0x1d2fff:W, 0x1d3000-0x1d3fff:W, 0x1d4000-0x1d4fff:W, 0x1d5000-0x1d5fff:W, 0x1d6000-0x1d6fff:W, 0x1d7000-0x1d7fff:W, 0x1d8000-0x1d8fff:W, 0x1d9000-0x1d9fff:W, 0x1da000-0x1dafff:W, 0x1db000-0x1dbfff:W, 0x1dc000-0x1dcfff:W, 0x1dd000-0x1ddfff:W, 0x1de000-0x1defff:W, 0x1df000-0x1dffff:W, 0x1e0000-0x1e0fff:W, 0x1e1000-0x1e1fff:W, 0x1e2000-0x1e2fff:W, 0x1e3000-0x1e3fff:W, 0x1e4000-0x1e4fff:W, 0x1e5000-0x1e5fff:W, 0x1e6000-0x1e6fff:W, 0x1e7000-0x1e7fff:W, 0x1e8000-0x1e8fff:W, 0x1e9000-0x1e9fff:W, 0x1ea000-0x1eafff:W, 0x1eb000-0x1ebfff:W, 0x1ec000-0x1ecfff:W, 0x1ed000-0x1edfff:W, 0x1ee000-0x1eefff:W, 0x1ef000-0x1effff:W, 0x1f0000-0x1f0fff:W, 0x1f1000-0x1f1fff:W, 0x1f2000-0x1f2fff:W, 0x1f3000-0x1f3fff:W, 0x1f4000-0x1f4fff:W, 0x1f5000-0x1f5fff:W, 0x1f6000-0x1f6fff:W, 0x1f7000-0x1f7fff:W, 0x1f8000-0x1f8fff:W, 0x1f9000-0x1f9fff:W, 0x1fa000-0x1fafff:W, 0x1fb000-0x1fbfff:W, 0x1fc000-0x1fcfff:W, 0x1fd000-0x1fdfff:W, 0x1fe000-0x1fefff:W, 0x1ff000-0x1fffff:W, 0x200000-0x200fff:W, 0x201000-0x201fff:W, 0x202000-0x202fff:W, 0x203000-0x203fff:W, 0x204000-0x204fff:W, 0x205000-0x205fff:W, 0x206000-0x206fff:W, 0x207000-0x207fff:W, 0x208000-0x208fff:W, 0x209000-0x209fff:W, 0x20a000-0x20afff:W, 0x20b000-0x20bfff:W, 0x20c000-0x20cfff:W, 0x20d000-0x20dfff:W, 0x20e000-0x20efff:W, 0x20f000-0x20ffff:W, 0x210000-0x210fff:W, 0x211000-0x211fff:W, 0x212000-0x212fff:W, 0x213000-0x213fff:W, 0x214000-0x214fff:W, 0x215000-0x215fff:W, 0x216000-0x216fff:W, 0x217000-0x217fff:W, 0x218000-0x218fff:W, 0x219000-0x219fff:W, 0x21a000-0x21afff:W, 0x21b000-0x21bfff:W, 0x21c000-0x21cfff:W, 0x21d000-0x21dfff:W, 0x21e000-0x21efff:W, 0x21f000-0x21ffff:W, 0x220000-0x220fff:W, 0x221000-0x221fff:W, 0x222000-0x222fff:W, 0x223000-0x223fff:W, 0x224000-0x224fff:W, 0x225000-0x225fff:W, 0x226000-0x226fff:W, 0x227000-0x227fff:W, 0x228000-0x228fff:W, 0x229000-0x229fff:W, 0x22a000-0x22afff:W, 0x22b000-0x22bfff:W, 0x22c000-0x22cfff:W, 0x22d000-0x22dfff:W, 0x22e000-0x22efff:W, 0x22f000-0x22ffff:W, 0x230000-0x230fff:W, 0x231000-0x231fff:W, 0x232000-0x232fff:W, 0x233000-0x233fff:W, 0x234000-0x234fff:W, 0x235000-0x235fff:W, 0x236000-0x236fff:W, 0x237000-0x237fff:W, 0x238000-0x238fff:W, 0x239000-0x239fff:W, 0x23a000-0x23afff:W, 0x23b000-0x23bfff:W, 0x23c000-0x23cfff:W, 0x23d000-0x23dfff:W, 0x23e000-0x23efff:W, 0x23f000-0x23ffff:W, 0x240000-0x240fff:W, 0x241000-0x241fff:W, 0x242000-0x242fff:W, 0x243000-0x243fff:W, 0x244000-0x244fff:W, 0x245000-0x245fff:W, 0x246000-0x246fff:W, 0x247000-0x247fff:W, 0x248000-0x248fff:W, 0x249000-0x249fff:W, 0x24a000-0x24afff:W, 0x24b000-0x24bfff:W, 0x24c000-0x24cfff:W, 0x24d000-0x24dfff:W, 0x24e000-0x24efff:W, 0x24f000-0x24ffff:W, 0x250000-0x250fff:W, 0x251000-0x251fff:W, 0x252000-0x252fff:W, 0x253000-0x253fff:W, 0x254000-0x254fff:W, 0x255000-0x255fff:W, 0x256000-0x256fff:W, 0x257000-0x257fff:W, 0x258000-0x258fff:W, 0x259000-0x259fff:W, 0x25a000-0x25afff:W, 0x25b000-0x25bfff:W, 0x25c000-0x25cfff:W, 0x25d000-0x25dfff:W, 0x25e000-0x25efff:W, 0x25f000-0x25ffff:W, 0x260000-0x260fff:W, 0x261000-0x261fff:W, 0x262000-0x262fff:W, 0x263000-0x263fff:W, 0x264000-0x264fff:W, 0x265000-0x265fff:W, 0x266000-0x266fff:W, 0x267000-0x267fff:W, 0x268000-0x268fff:W, 0x269000-0x269fff:W, 0x26a000-0x26afff:W, 0x26b000-0x26bfff:W, 0x26c000-0x26cfff:W, 0x26d000-0x26dfff:W, 0x26e000-0x26efff:W, 0x26f000-0x26ffff:W, 0x270000-0x270fff:W, 0x271000-0x271fff:W, 0x272000-0x272fff:W, 0x273000-0x273fff:W, 0x274000-0x274fff:W, 0x275000-0x275fff:W, 0x276000-0x276fff:W, 0x277000-0x277fff:W, 0x278000-0x278fff:W, 0x279000-0x279fff:W, 0x27a000-0x27afff:W, 0x27b000-0x27bfff:W, 0x27c000-0x27cfff:W, 0x27d000-0x27dfff:W, 0x27e000-0x27efff:W, 0x27f000-0x27ffff:W, 0x280000-0x280fff:W, 0x281000-0x281fff:W, 0x282000-0x282fff:W, 0x283000-0x283fff:W, 0x284000-0x284fff:W, 0x285000-0x285fff:W, 0x286000-0x286fff:W, 0x287000-0x287fff:W, 0x288000-0x288fff:W, 0x289000-0x289fff:W, 0x28a000-0x28afff:W, 0x28b000-0x28bfff:W, 0x28c000-0x28cfff:W, 0x28d000-0x28dfff:W, 0x28e000-0x28efff:W, 0x28f000-0x28ffff:W, 0x290000-0x290fff:W, 0x291000-0x291fff:W, 0x292000-0x292fff:W, 0x293000-0x293fff:W, 0x294000-0x294fff:W, 0x295000-0x295fff:W, 0x296000-0x296fff:W, 0x297000-0x297fff:W, 0x298000-0x298fff:W, 0x299000-0x299fff:W, 0x29a000-0x29afff:W, 0x29b000-0x29bfff:W, 0x29c000-0x29cfff:W, 0x29d000-0x29dfff:W, 0x29e000-0x29efff:W, 0x29f000-0x29ffff:W, 0x2a0000-0x2a0fff:W, 0x2a1000-0x2a1fff:W, 0x2a2000-0x2a2fff:W, 0x2a3000-0x2a3fff:W, 0x2a4000-0x2a4fff:W, 0x2a5000-0x2a5fff:W, 0x2a6000-0x2a6fff:W, 0x2a7000-0x2a7fff:W, 0x2a8000-0x2a8fff:W, 0x2a9000-0x2a9fff:W, 0x2aa000-0x2aafff:W, 0x2ab000-0x2abfff:W, 0x2ac000-0x2acfff:W, 0x2ad000-0x2adfff:W, 0x2ae000-0x2aefff:W, 0x2af000-0x2affff:W, 0x2b0000-0x2b0fff:W, 0x2b1000-0x2b1fff:W, 0x2b2000-0x2b2fff:W, 0x2b3000-0x2b3fff:W, 0x2b4000-0x2b4fff:W, 0x2b5000-0x2b5fff:W, 0x2b6000-0x2b6fff:W, 0x2b7000-0x2b7fff:W, 0x2b8000-0x2b8fff:W, 0x2b9000-0x2b9fff:W, 0x2ba000-0x2bafff:W, 0x2bb000-0x2bbfff:W, 0x2bc000-0x2bcfff:W, 0x2bd000-0x2bdfff:W, 0x2be000-0x2befff:W, 0x2bf000-0x2bffff:W, 0x2c0000-0x2c0fff:W, 0x2c1000-0x2c1fff:W, 0x2c2000-0x2c2fff:W, 0x2c3000-0x2c3fff:W, 0x2c4000-0x2c4fff:W, 0x2c5000-0x2c5fff:W, 0x2c6000-0x2c6fff:W, 0x2c7000-0x2c7fff:W, 0x2c8000-0x2c8fff:W, 0x2c9000-0x2c9fff:W, 0x2ca000-0x2cafff:W, 0x2cb000-0x2cbfff:W, 0x2cc000-0x2ccfff:W, 0x2cd000-0x2cdfff:W, 0x2ce000-0x2cefff:W, 0x2cf000-0x2cffff:W, 0x2d0000-0x2d0fff:W, 0x2d1000-0x2d1fff:W, 0x2d2000-0x2d2fff:W, 0x2d3000-0x2d3fff:W, 0x2d4000-0x2d4fff:W, 0x2d5000-0x2d5fff:W, 0x2d6000-0x2d6fff:W, 0x2d7000-0x2d7fff:W, 0x2d8000-0x2d8fff:W, 0x2d9000-0x2d9fff:W, 0x2da000-0x2dafff:W, 0x2db000-0x2dbfff:W, 0x2dc000-0x2dcfff:W, 0x2dd000-0x2ddfff:W, 0x2de000-0x2defff:W, 0x2df000-0x2dffff:W, 0x2e0000-0x2e0fff:W, 0x2e1000-0x2e1fff:W, 0x2e2000-0x2e2fff:W, 0x2e3000-0x2e3fff:W, 0x2e4000-0x2e4fff:W, 0x2e5000-0x2e5fff:W, 0x2e6000-0x2e6fff:W, 0x2e7000-0x2e7fff:W, 0x2e8000-0x2e8fff:W, 0x2e9000-0x2e9fff:W, 0x2ea000-0x2eafff:W, 0x2eb000-0x2ebfff:W, 0x2ec000-0x2ecfff:W, 0x2ed000-0x2edfff:W, 0x2ee000-0x2eefff:W, 0x2ef000-0x2effff:W, 0x2f0000-0x2f0fff:W, 0x2f1000-0x2f1fff:W, 0x2f2000-0x2f2fff:W, 0x2f3000-0x2f3fff:W, 0x2f4000-0x2f4fff:W, 0x2f5000-0x2f5fff:W, 0x2f6000-0x2f6fff:W, 0x2f7000-0x2f7fff:W, 0x2f8000-0x2f8fff:W, 0x2f9000-0x2f9fff:W, 0x2fa000-0x2fafff:W, 0x2fb000-0x2fbfff:W, 0x2fc000-0x2fcfff:W, 0x2fd000-0x2fdfff:W, 0x2fe000-0x2fefff:W, 0x2ff000-0x2fffff:W, 0x300000-0x300fff:W, 0x301000-0x301fff:W, 0x302000-0x302fff:W, 0x303000-0x303fff:W, 0x304000-0x304fff:W, 0x305000-0x305fff:W, 0x306000-0x306fff:W, 0x307000-0x307fff:W, 0x308000-0x308fff:W, 0x309000-0x309fff:W, 0x30a000-0x30afff:W, 0x30b000-0x30bfff:W, 0x30c000-0x30cfff:W, 0x30d000-0x30dfff:W, 0x30e000-0x30efff:W, 0x30f000-0x30ffff:W, 0x310000-0x310fff:W, 0x311000-0x311fff:W, 0x312000-0x312fff:W, 0x313000-0x313fff:W, 0x314000-0x314fff:W, 0x315000-0x315fff:W, 0x316000-0x316fff:W, 0x317000-0x317fff:W, 0x318000-0x318fff:W, 0x319000-0x319fff:W, 0x31a000-0x31afff:W, 0x31b000-0x31bfff:W, 0x31c000-0x31cfff:W, 0x31d000-0x31dfff:W, 0x31e000-0x31efff:W, 0x31f000-0x31ffff:W, 0x320000-0x320fff:W, 0x321000-0x321fff:W, 0x322000-0x322fff:W, 0x323000-0x323fff:W, 0x324000-0x324fff:W, 0x325000-0x325fff:W, 0x326000-0x326fff:W, 0x327000-0x327fff:W, 0x328000-0x328fff:W, 0x329000-0x329fff:W, 0x32a000-0x32afff:W, 0x32b000-0x32bfff:W, 0x32c000-0x32cfff:W, 0x32d000-0x32dfff:W, 0x32e000-0x32efff:W, 0x32f000-0x32ffff:W, 0x330000-0x330fff:W, 0x331000-0x331fff:W, 0x332000-0x332fff:W, 0x333000-0x333fff:W, 0x334000-0x334fff:W, 0x335000-0x335fff:W, 0x336000-0x336fff:W, 0x337000-0x337fff:W, 0x338000-0x338fff:W, 0x339000-0x339fff:W, 0x33a000-0x33afff:W, 0x33b000-0x33bfff:W, 0x33c000-0x33cfff:W, 0x33d000-0x33dfff:W, 0x33e000-0x33efff:W, 0x33f000-0x33ffff:W, 0x340000-0x340fff:W, 0x341000-0x341fff:W, 0x342000-0x342fff:W, 0x343000-0x343fff:W, 0x344000-0x344fff:W, 0x345000-0x345fff:W, 0x346000-0x346fff:W, 0x347000-0x347fff:W, 0x348000-0x348fff:W, 0x349000-0x349fff:W, 0x34a000-0x34afff:W, 0x34b000-0x34bfff:W, 0x34c000-0x34cfff:W, 0x34d000-0x34dfff:W, 0x34e000-0x34efff:W, 0x34f000-0x34ffff:W, 0x350000-0x350fff:W, 0x351000-0x351fff:W, 0x352000-0x352fff:W, 0x353000-0x353fff:W, 0x354000-0x354fff:W, 0x355000-0x355fff:W, 0x356000-0x356fff:W, 0x357000-0x357fff:W, 0x358000-0x358fff:W, 0x359000-0x359fff:W, 0x35a000-0x35afff:W, 0x35b000-0x35bfff:W, 0x35c000-0x35cfff:W, 0x35d000-0x35dfff:W, 0x35e000-0x35efff:W, 0x35f000-0x35ffff:W, 0x360000-0x360fff:W, 0x361000-0x361fff:W, 0x362000-0x362fff:W, 0x363000-0x363fff:W, 0x364000-0x364fff:W, 0x365000-0x365fff:W, 0x366000-0x366fff:W, 0x367000-0x367fff:W, 0x368000-0x368fff:W, 0x369000-0x369fff:W, 0x36a000-0x36afff:W, 0x36b000-0x36bfff:W, 0x36c000-0x36cfff:W, 0x36d000-0x36dfff:W, 0x36e000-0x36efff:W, 0x36f000-0x36ffff:W, 0x370000-0x370fff:W, 0x371000-0x371fff:W, 0x372000-0x372fff:W, 0x373000-0x373fff:W, 0x374000-0x374fff:W, 0x375000-0x375fff:W, 0x376000-0x376fff:W, 0x377000-0x377fff:W, 0x378000-0x378fff:W, 0x379000-0x379fff:W, 0x37a000-0x37afff:W, 0x37b000-0x37bfff:W, 0x37c000-0x37cfff:W, 0x37d000-0x37dfff:W, 0x37e000-0x37efff:W, 0x37f000-0x37ffff:W, 0x380000-0x380fff:W, 0x381000-0x381fff:W, 0x382000-0x382fff:W, 0x383000-0x383fff:W, 0x384000-0x384fff:W, 0x385000-0x385fff:W, 0x386000-0x386fff:W, 0x387000-0x387fff:W, 0x388000-0x388fff:W, 0x389000-0x389fff:W, 0x38a000-0x38afff:W, 0x38b000-0x38bfff:W, 0x38c000-0x38cfff:W, 0x38d000-0x38dfff:W, 0x38e000-0x38efff:W, 0x38f000-0x38ffff:W, 0x390000-0x390fff:W, 0x391000-0x391fff:W, 0x392000-0x392fff:W, 0x393000-0x393fff:W, 0x394000-0x394fff:W, 0x395000-0x395fff:W, 0x396000-0x396fff:W, 0x397000-0x397fff:W, 0x398000-0x398fff:W, 0x399000-0x399fff:W, 0x39a000-0x39afff:W, 0x39b000-0x39bfff:W, 0x39c000-0x39cfff:W, 0x39d000-0x39dfff:W, 0x39e000-0x39efff:W, 0x39f000-0x39ffff:W, 0x3a0000-0x3a0fff:W, 0x3a1000-0x3a1fff:W, 0x3a2000-0x3a2fff:W, 0x3a3000-0x3a3fff:W, 0x3a4000-0x3a4fff:W, 0x3a5000-0x3a5fff:W, 0x3a6000-0x3a6fff:W, 0x3a7000-0x3a7fff:W, 0x3a8000-0x3a8fff:W, 0x3a9000-0x3a9fff:W, 0x3aa000-0x3aafff:W, 0x3ab000-0x3abfff:W, 0x3ac000-0x3acfff:W, 0x3ad000-0x3adfff:W, 0x3ae000-0x3aefff:W, 0x3af000-0x3affff:W, 0x3b0000-0x3b0fff:W, 0x3b1000-0x3b1fff:W, 0x3b2000-0x3b2fff:W, 0x3b3000-0x3b3fff:W, 0x3b4000-0x3b4fff:W, 0x3b5000-0x3b5fff:W, 0x3b6000-0x3b6fff:W, 0x3b7000-0x3b7fff:W, 0x3b8000-0x3b8fff:W, 0x3b9000-0x3b9fff:W, 0x3ba000-0x3bafff:W, 0x3bb000-0x3bbfff:W, 0x3bc000-0x3bcfff:W, 0x3bd000-0x3bdfff:W, 0x3be000-0x3befff:W, 0x3bf000-0x3bffff:W, 0x3c0000-0x3c0fff:W, 0x3c1000-0x3c1fff:W, 0x3c2000-0x3c2fff:W, 0x3c3000-0x3c3fff:W, 0x3c4000-0x3c4fff:W, 0x3c5000-0x3c5fff:W, 0x3c6000-0x3c6fff:W, 0x3c7000-0x3c7fff:W, 0x3c8000-0x3c8fff:W, 0x3c9000-0x3c9fff:W, 0x3ca000-0x3cafff:W, 0x3cb000-0x3cbfff:W, 0x3cc000-0x3ccfff:W, 0x3cd000-0x3cdfff:W, 0x3ce000-0x3cefff:W, 0x3cf000-0x3cffff:W, 0x3d0000-0x3d0fff:W, 0x3d1000-0x3d1fff:W, 0x3d2000-0x3d2fff:W, 0x3d3000-0x3d3fff:W, 0x3d4000-0x3d4fff:W, 0x3d5000-0x3d5fff:W, 0x3d6000-0x3d6fff:W, 0x3d7000-0x3d7fff:W, 0x3d8000-0x3d8fff:W, 0x3d9000-0x3d9fff:W, 0x3da000-0x3dafff:W, 0x3db000-0x3dbfff:S, 0x3dc000-0x3dcfff:S, 0x3dd000-0x3ddfff:S, 0x3de000-0x3defff:S, 0x3df000-0x3dffff:S, 0x3e0000-0x3e0fff:S, 0x3e1000-0x3e1fff:S, 0x3e2000-0x3e2fff:S, 0x3e3000-0x3e3fff:S, 0x3e4000-0x3e4fff:S, 0x3e5000-0x3e5fff:S, 0x3e6000-0x3e6fff:S, 0x3e7000-0x3e7fff:S, 0x3e8000-0x3e8fff:S, 0x3e9000-0x3e9fff:S, 0x3ea000-0x3eafff:S, 0x3eb000-0x3ebfff:S, 0x3ec000-0x3ecfff:S, 0x3ed000-0x3edfff:S, 0x3ee000-0x3eefff:S, 0x3ef000-0x3effff:S, 0x3f0000-0x3f0fff:S, 0x3f1000-0x3f1fff:S, 0x3f2000-0x3f2fff:S, 0x3f3000-0x3f3fff:S, 0x3f4000-0x3f4fff:S, 0x3f5000-0x3f5fff:S, 0x3f6000-0x3f6fff:S, 0x3f7000-0x3f7fff:S, 0x3f8000-0x3f8fff:S, 0x3f9000-0x3f9fff:S, 0x3fa000-0x3fafff:S, 0x3fb000-0x3fbfff:S, 0x3fc000-0x3fcfff:S, 0x3fd000-0x3fdfff:S, 0x3fe000-0x3fefff:S, 0x3ff000-0x3fffff:S Erase/write done. Verifying flash... VERIFIED.

1 0

ft2232h evaluation board
by sotiris sigkounas 08 Feb '22

08 Feb '22

chip: GigaDevice GD25B256D (recognized as "GD25Q256D") read/write work fine! agg@vm:~$ flashrom -p ft2232_spi:type=2232H,port=A -r read.bin -V >read.log agg@vm:~$ flashrom -p ft2232_spi:type=2232H,port=A -w outimage.bin -V >write.log

1 0

How to obtain a BIOS image from another computer use flashrom？
by zy 29 Jan '22

29 Jan '22

Hi，    I'm a student from China and I've been learning flashrom，So I would like to know whether the flashrom can support extracting BIOS firmware images under Windows 7/10.    If I don't have the Internet（Just LAN），how do I remotely obtain a BIOS image from another computer use flashrom？    Maybe my English not very well. Thank you very much.    Looking forward to your reply.  

4 4

Re: issue
by Mike Banon 29 Jan '22

29 Jan '22

1) Try the shorter cables between a test clip and a programmer. See my notes here at http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate#St… 2) Make sure that your ch341a programmer is good enough. I had to repair a couple of dead-on-arrival ch341a: https://www.reddit.com/r/coreboot/comments/bjygqz/green_ch341a_didnt_work_t… https://www.reddit.com/r/coreboot/comments/defkim/green_ch341a_didnt_work_b… On Sat, Jan 29, 2022 at 6:06 PM John Evacristo <sphinxstudios(a)gmail.com> wrote: > > ch341a_spi and yes In-System Programming with a test clip > > On Sat, Jan 29, 2022, 11:05 PM Mike Banon <mikebdp2(a)gmail.com> wrote: >> >> Please describe your flashing setup in more details. We don't even >> know which programmer you're trying to use, and in what mode? >> (In-System Programming with a test clip?) >> >> On Mon, Jan 24, 2022 at 12:55 AM John Evacristo <sphinxstudios(a)gmail.com> wrote: >> > >> > flashrom v1.2 on Linux 5.11.0-27-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 "MX25L3206E/MX25L3208E" (4096 kB, SPI) on ch341a_spi. >> > Erasing and writing flash chip... FAILED at 0x0001347f! Expected=0xff, Found=0xef, failed byte count from 0x00013000-0x00013fff: 0x7 >> > ERASE FAILED! >> > Looking for another erase function. >> > FAILED at 0x00000098! Expected=0xff, Found=0xfe, failed byte count from 0x00000000-0x0000ffff: 0x4a7f >> > ERASE FAILED! >> > Looking for another erase function. >> > FAILED at 0x00000000! Expected=0xff, Found=0x02, failed byte count from 0x00000000-0x0000ffff: 0x544f >> > ERASE FAILED! >> > Looking for another erase function. >> > FAILED at 0x00000000! Expected=0xff, Found=0xbd, failed byte count from 0x00000000-0x003fffff: 0x3e0c19 >> > ERASE FAILED! >> > Looking for another erase function. >> > FAILED at 0x00000000! Expected=0xff, Found=0xbb, failed byte count from 0x00000000-0x003fffff: 0x3fffea >> > 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! >> > _______________________________________________ >> > flashrom mailing list -- flashrom(a)flashrom.org >> > To unsubscribe send an email to flashrom-leave(a)flashrom.org >> >> >> >> -- >> Best regards, Mike Banon >> Open Source Community Manager of 3mdeb - https://3mdeb.com/ -- Best regards, Mike Banon Open Source Community Manager of 3mdeb - https://3mdeb.com/

1 0

issue
by John Evacristo 29 Jan '22

29 Jan '22

flashrom v1.2 on Linux 5.11.0-27-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 "MX25L3206E/MX25L3208E" (4096 kB, SPI) on ch341a_spi. Erasing and writing flash chip... FAILED at 0x0001347f! Expected=0xff, Found=0xef, failed byte count from 0x00013000-0x00013fff: 0x7 ERASE FAILED! Looking for another erase function. FAILED at 0x00000098! Expected=0xff, Found=0xfe, failed byte count from 0x00000000-0x0000ffff: 0x4a7f ERASE FAILED! Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x02, failed byte count from 0x00000000-0x0000ffff: 0x544f ERASE FAILED! Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0xbd, failed byte count from 0x00000000-0x003fffff: 0x3e0c19 ERASE FAILED! Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0xbb, failed byte count from 0x00000000-0x003fffff: 0x3fffea 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!

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom