flashrom

flashrom@flashrom.org

1 participants
9182 discussions

flashrom meeting notes 17.08.2023
by Anastasia Klimchuk 17 Aug '23

17 Aug '23

# 17th August 2023, 6.00-7.00am UTC+0 Attendees: Joursoir, Stefan, Anastasia ## Decision summary * logo files will be copied from flashrom-media to flashrom repo (into doc/ to display on website) * enable Gerrit feature to not submit with unresolved comments ## Agenda * [aklm] is it okay to copy the logo from one repo to another and add it to new website? Any licensing considerations? * copy the whole logo directory from media repository to docs * include svg in color on the page * licence is CC BY-ND 4.0 [https://github.com/flashrom/flashrom-media/blob/master/logo/COPYING](https:… so all good * What is the normal release process? what do we do for v1.4? * when all that is needed for rc1 is ready, put the tag v1.4_rc1 on master * then freeze the master for new features for 1 month, announce on mailing list * code reviews can continue, just not merging * do the testing * fix bugs if discovered, put v1.4_rc2, .... rcN * at the end of 1 month (hopefully bugs are fixed), put v1.4 on master, and then branch v1.4 * and then unfreeze, and merge everything that was waiting * [aklm] we need more people to subscribe to flashchips.c. I did already. We have contributors adding chips, and marking chips as tested, and they may not know whom to add as reviewer. [https://review.coreboot.org/q/status:open+project:flashrom+flashchips](http… * like this [https://review.coreboot.org/c/flashrom/+/75895](https://review.coreboot.org… * * let's add gerrit feature "do not submit with unresolved comments". it makes life easier for people who submit patches. * yes, lets add this feature * Joursoir: get a warning (do NOT restrict) if 24 hours have not passed. Is it possible? -- Anastasia.

1 0

Re: ISSI Flash parts request to be added
by Johnny Chien 15 Aug '23

15 Aug '23

Hi Everyone, The links provided to us are no longer working. Please help advise if there were new links setup or it this is a temporary issue and we should check back again. Johnny Chien Integrated Silicon Solution, Inc. Phone: 408.969.4647 Mobile: 408.786.8210 Fax: 408.969.4747 Email: Jchien(a)issi.com<mailto:Jchien@issi.com> Follow us on Twitter Hi Johnny, I couldn't connect the link, https://www.flashrom.org/Development_Guidelines#Adding/reviewing_a_new_flas… with the error below. Maybe the link was changed. Also the links below. [cid:image002.png@01D9C60E.013F0790] To send a patch you need to follow the guidelines here https://www.flashrom.org/Development_Guidelines#Patch_submission --> with the same error above. In addition, read specifically the section about adding a new chip https://www.flashrom.org/Development_Guidelines#Adding/reviewing_a_new_flas… --> with the same error above. One more document is about building flashrom from source https://doc.flashrom.org/dev_guide/building_from_source.html --> with the message below (unsupported protocol). [cid:image003.png@01D9C60E.013F0790] Can you please get the latest information about the links above through your contact in FalshRom? From: Peter Marheine <pmarheine(a)chromium.org<mailto:pmarheine@chromium.org>> Sent: Thursday, May 25, 2023 5:50 PM To: Johnny Chien <jchien(a)issi.com<mailto:jchien@issi.com>> Cc: flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> Subject: Re: [flashrom] ISSI Flash parts request to be added The tips at https://www.flashrom.org/Development_Guidelines#Adding/reviewing_a_new_flas… will probably help you get started; if the chips you want to add support for are similar to already-supported chips it should be easy to add the new ones, but as long as they don't have any very unusual behavior there shouldn't be anything difficult about it. On Tue, May 23, 2023 at 11:53 AM Johnny Chien <jchien(a)issi.com<mailto:jchien@issi.com>> wrote: Hi FlashROM, We have a customer who pointed us to your organization. They asked if we could get more of our SPI NOR flash supported. Do you have a contact or person who would be able to guide us in this activity? We see the following parts supported here: [cid:image004.png@01D9C60E.013F0790] Johnny Chien Integrated Silicon Solution, Inc. Phone: 408.969.4647<tel:(408)%20969-4647> Mobile: 408.786.8210<tel:(408)%20786-8210> Fax: 408.969.4747<tel:(408)%20969-4747> Email: Jchien(a)issi.com<mailto:Jchien@issi.com> Follow us on Twitter _______________________________________________ flashrom mailing list -- flashrom(a)flashrom.org<mailto:flashrom@flashrom.org> To unsubscribe send an email to flashrom-leave(a)flashrom.org<mailto:flashrom-leave@flashrom.org> ________________________________ This email has been scanned for spam and viruses. Click here<https://securemail.cloud-protect.net/index01.php?mod_id=11&mod_option=logit…> to report this email as spam.

2 4

Missing chip definition for ZD25WQ80Y
by a.b.c＠ntlworld.com 12 Aug '23

12 Aug '23

ZD25WQ80Y Hope this info is of use

1 0

Re: HP 11 G5 EE - WP disable failure
by Peter Marheine 09 Aug '23

09 Aug '23

You don't need to cut any tracks, and that might not even do what you want because there probably isn't a pull-up or -down on the WP signal so it would be left floating in an indeterminate state. It looks like your Meep uses battery presence for WP, so disconnecting the battery should be all you need to do in order to temporarily disable hardware write protection. On Thu, Aug 10, 2023 at 11:16 AM E239 76BF <e23976bf(a)gmail.com> wrote: > I think the apparent thin link might be on the other side of the board. I > need to extract the board to confirm this, cut it and try again. > I'm a hardware tech with 40 yrs experience, so no issue. Just > unfamiliar with ChromeOS. > Need to remove the board. But it's the only IT platform I have. > Learned ChromeOS, Time to go back to linux. > > > On Thu, 10 Aug 2023 at 13:01, Peter Marheine <pmarheine(a)chromium.org> > wrote: > >> > Note: hardware status register protection is enabled. The chip's WP# >> pin must be set to an inactive voltage level to be able to change the WP >> settings. >> >> You need to disable hardware write protect: >> https://chromium.googlesource.com/chromiumos/docs/+/master/write_protection… >> >> On Tue, Aug 8, 2023 at 1:02 PM E239 76BF <e23976bf(a)gmail.com> wrote: >> >>> Glenn in Wellington, New Zealand >>> I know little about ChromeOS, but am moderately comfortable with Linux. >>> Got this machine two months ago (because I lost all my gear in a big >>> fire 11 weeks ago) and having learned ChromeOS, I'm now ready to return to >>> the comfort of a linux environment. >>> >>> Verbose output : >>> >>> # flashrom --wp-disable -V >>> flashrom 68022911 on Linux 4.14.313-20323-gc32c2d54e434 (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). >>> flashrom was built with LLVM Clang 16.0.0 >>> (/var/tmp/portage/sys-devel/llvm-16.0_pre484197_p20230405-r7/work/llvm-16.0_pre484197_p20230405/clang >>> 2916b99182752b1aece8cc4479d8d6a20b5e02da), little endian >>> Command line (2 args): flashrom --wp-disable -V >>> Using default programmer "internal" with arguments "". >>> Acquiring lock (timeout=180 sec)... >>> Opened file lock "/run/lock/firmware_utility_lock" >>> Lock acquired. >>> Initializing internal programmer >>> /sys/class/mtd/mtd0 does not exist >>> Found candidate at: 00000500-00000528 >>> Found coreboot table at 0x00000500. >>> Found candidate at: 00000000-000005cc >>> Found coreboot table at 0x00000000. >>> coreboot table found at 0x79b2a000. >>> coreboot header(24) checksum: a42a table(1460) checksum: c446 entries: 45 >>> Vendor ID: Google, part ID: Meep >>> Using Internal DMI decoder. >>> DMI string chassis-type: "Laptop" >>> Laptop detected via DMI. >>> DMI string system-manufacturer: "HP" >>> DMI string system-product-name: "Meep" >>> DMI string system-version: "rev7" >>> DMI string baseboard-manufacturer: "HP" >>> DMI string baseboard-product-name: "Meep" >>> DMI string baseboard-version: "rev7" >>> Found chipset "Intel Gemini Lake" with PCI ID 8086:3197. >>> 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... BIOS_SPI_BC = 0x9: BIOS Interface Lock-Down: >>> disabled, Boot BIOS Straps: 0x0 (SPI) >>> Top Swap: not enabled >>> SPI Read Configuration: prefetching enabled, caching enabled, >>> BIOS_CNTL = 0x09: BIOS Lock Enable: disabled, BIOS Write Enable: enabled >>> SPIBAR = 0x00007bd11ce10000 (phys = 0xc1121000) >>> 0x04: 0x6000 (HSFS) >>> HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=0, SCIP=0, FDOPSS=1, FDV=1, >>> FLOCKDN=0 >>> Programming OPCODES... done >>> 0x06: 0x020c (HSFC) >>> HSFC: FGO=0, FCYCLE=2, FDBC=2, SME=0 >>> 0x0c: 0x00000000 (DLOCK) >>> DLOCK: BMWAG_LOCKDN=0, BMRAG_LOCKDN=0, SBMWAG_LOCKDN=0, SBMRAG_LOCKDN=0, >>> PR0_LOCKDN=0, PR1_LOCKDN=0, PR2_LOCKDN=0, PR3_LOCKDN=0, >>> PR4_LOCKDN=0, >>> SSEQ_LOCKDN=0 >>> 0x50: 0x000042c3 (FRAP) >>> BMWAG 0x00, BMRAG 0x00, BRWA 0x42, BRRA 0xc3 >>> 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) >>> is read-only. >>> 0x58: 0x0f7e0001 FREG1: BIOS region (0x00001000-0x00f7efff) is >>> read-write. >>> 0x68: 0x0fff0f7f FREG5: Device Expansion region (0x00f7f000-0x00ffffff) >>> is locked. >>> 0x7C: 0x7fff7fff FREG10: unknown region (0x07fff000-0x07ffffff) has >>> unknown permissions. >>> 0x80: 0x7fff7fff FREG11: unknown region (0x07fff000-0x07ffffff) has >>> unknown permissions. >>> 0xE0: 0x7fff7fff FREG12: unknown region (0x07fff000-0x07ffffff) has >>> unknown permissions. >>> 0xE4: 0x7fff7fff FREG13: unknown region (0x07fff000-0x07ffffff) has >>> unknown permissions. >>> 0xE8: 0x7fff7fff FREG14: unknown region (0x07fff000-0x07ffffff) has >>> unknown permissions. >>> 0xEC: 0x7fff7fff FREG15: unknown region (0x07fff000-0x07ffffff) has >>> unknown permissions. >>> 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. >>> 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. >>> 0xa0: 0xc0 (SSFS) >>> SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 >>> 0xa1: 0xfe0000 (SSFC) >>> SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=6 >>> 0xa4: 0x5006 (PREOP) >>> 0xa6: 0x463b (OPTYPE) >>> 0xa8: 0x05200302 (OPMENU) >>> 0xac: 0xc79f0190 (OPMENU+4) >>> 0xc4: 0xb1d82024 (LVSCC) >>> LVSCC: BES=0x0, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 >>> 0xc8: 0x00002000 (UVSCC) >>> UVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x20 >>> Enabling hardware sequencing by default for >>> Apollo/Gemini/Jasper/Elkhart/Meteor Lake. >>> OK. >>> The following protocols are supported: Programmer-specific. >>> Probing for Programmer Opaque flash chip, 0 kB: Hardware sequencing >>> reports 1 attached SPI flash chip with a density of 16384 kB. >>> HSFC: FGO=1, FCYCLE=2, FDBC=2, SME=0 >>> Chip identified: GD25LQ128C/GD25LQ128D/GD25LQ128E >>> Added layout entry 00000000 - 00ffffff named complete flash >>> Found GigaDevice flash chip "GD25LQ128C/GD25LQ128D/GD25LQ128E" (16384 >>> kB, Programmer-specific) on internal. >>> Found GigaDevice flash chip "GD25LQ128C/GD25LQ128D/GD25LQ128E" (16384 >>> kB, Programmer-specific). >>> 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). >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> ich_hwseq_read_status: only supports STATUS1 >>> wp_read_register: read from register 2 not is supported by programmer, >>> writeprotect operations will assume it contains 0x00. >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> ich_hwseq_read_status: only supports STATUS1 >>> wp_read_register: read from register 2 not is supported by programmer, >>> writeprotect operations will assume it contains 0x00. >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> ich_hwseq_read_status: only supports STATUS1 >>> wp_read_register: read from register 2 not is supported by programmer, >>> writeprotect operations will assume it contains 0x00. >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> ich_hwseq_read_status: only supports STATUS1 >>> wp_read_register: read from register 2 not is supported by programmer, >>> writeprotect operations will assume it contains 0x00. >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> ich_hwseq_read_status: only supports STATUS1 >>> wp_read_register: read from register 2 not is supported by programmer, >>> writeprotect operations will assume it contains 0x00. >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> ich_hwseq_read_status: only supports STATUS1 >>> wp_read_register: read from register 2 not is supported by programmer, >>> writeprotect operations will assume it contains 0x00. >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> Writing status register >>> HSFC: FGO=1, FCYCLE=3, FDBC=0, SME=0 >>> ich_hwseq_read_status: only supports STATUS1 >>> wp_read_register: read from register 2 not is supported by programmer, >>> writeprotect operations will assume it contains 0x00. >>> Reading Status register >>> HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 >>> write_wp_bits: wp_verify failed: reg:1 actual:0xb4 expected:0x34 >>> ich_hwseq_read_status: only supports STATUS1 >>> wp_read_register: read from register 2 not is supported by programmer, >>> writeprotect operations will assume it contains 0x00. >>> Failed to apply new WP settings: unexpected WP configuration read back >>> from chip >>> Note: hardware status register protection is enabled. The chip's WP# pin >>> must be set to an inactive voltage level to be able to change the WP >>> settings. >>> Restoring MMIO space at 0x7bd11ce10084 >>> Restoring MMIO space at 0x7bd11ce100ac >>> Restoring MMIO space at 0x7bd11ce100a8 >>> Restoring MMIO space at 0x7bd11ce100a6 >>> Restoring MMIO space at 0x7bd11ce100a4 >>> _______________________________________________ >>> flashrom mailing list -- flashrom(a)flashrom.org >>> To unsubscribe send an email to flashrom-leave(a)flashrom.org >>> >>

1 0

HP 11 G5 EE - WP disable failure
by E239 76BF 09 Aug '23

09 Aug '23

Glenn in Wellington, New Zealand I know little about ChromeOS, but am moderately comfortable with Linux. Got this machine two months ago (because I lost all my gear in a big fire 11 weeks ago) and having learned ChromeOS, I'm now ready to return to the comfort of a linux environment. Verbose output : # flashrom --wp-disable -V flashrom 68022911 on Linux 4.14.313-20323-gc32c2d54e434 (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). flashrom was built with LLVM Clang 16.0.0 (/var/tmp/portage/sys-devel/llvm-16.0_pre484197_p20230405-r7/work/llvm-16.0_pre484197_p20230405/clang 2916b99182752b1aece8cc4479d8d6a20b5e02da), little endian Command line (2 args): flashrom --wp-disable -V Using default programmer "internal" with arguments "". Acquiring lock (timeout=180 sec)... Opened file lock "/run/lock/firmware_utility_lock" Lock acquired. Initializing internal programmer /sys/class/mtd/mtd0 does not exist Found candidate at: 00000500-00000528 Found coreboot table at 0x00000500. Found candidate at: 00000000-000005cc Found coreboot table at 0x00000000. coreboot table found at 0x79b2a000. coreboot header(24) checksum: a42a table(1460) checksum: c446 entries: 45 Vendor ID: Google, part ID: Meep Using Internal DMI decoder. DMI string chassis-type: "Laptop" Laptop detected via DMI. DMI string system-manufacturer: "HP" DMI string system-product-name: "Meep" DMI string system-version: "rev7" DMI string baseboard-manufacturer: "HP" DMI string baseboard-product-name: "Meep" DMI string baseboard-version: "rev7" Found chipset "Intel Gemini Lake" with PCI ID 8086:3197. 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... BIOS_SPI_BC = 0x9: BIOS Interface Lock-Down: disabled, Boot BIOS Straps: 0x0 (SPI) Top Swap: not enabled SPI Read Configuration: prefetching enabled, caching enabled, BIOS_CNTL = 0x09: BIOS Lock Enable: disabled, BIOS Write Enable: enabled SPIBAR = 0x00007bd11ce10000 (phys = 0xc1121000) 0x04: 0x6000 (HSFS) HSFS: FDONE=0, FCERR=0, AEL=0, BERASE=0, SCIP=0, FDOPSS=1, FDV=1, FLOCKDN=0 Programming OPCODES... done 0x06: 0x020c (HSFC) HSFC: FGO=0, FCYCLE=2, FDBC=2, SME=0 0x0c: 0x00000000 (DLOCK) DLOCK: BMWAG_LOCKDN=0, BMRAG_LOCKDN=0, SBMWAG_LOCKDN=0, SBMRAG_LOCKDN=0, PR0_LOCKDN=0, PR1_LOCKDN=0, PR2_LOCKDN=0, PR3_LOCKDN=0, PR4_LOCKDN=0, SSEQ_LOCKDN=0 0x50: 0x000042c3 (FRAP) BMWAG 0x00, BMRAG 0x00, BRWA 0x42, BRRA 0xc3 0x54: 0x00000000 FREG0: Flash Descriptor region (0x00000000-0x00000fff) is read-only. 0x58: 0x0f7e0001 FREG1: BIOS region (0x00001000-0x00f7efff) is read-write. 0x68: 0x0fff0f7f FREG5: Device Expansion region (0x00f7f000-0x00ffffff) is locked. 0x7C: 0x7fff7fff FREG10: unknown region (0x07fff000-0x07ffffff) has unknown permissions. 0x80: 0x7fff7fff FREG11: unknown region (0x07fff000-0x07ffffff) has unknown permissions. 0xE0: 0x7fff7fff FREG12: unknown region (0x07fff000-0x07ffffff) has unknown permissions. 0xE4: 0x7fff7fff FREG13: unknown region (0x07fff000-0x07ffffff) has unknown permissions. 0xE8: 0x7fff7fff FREG14: unknown region (0x07fff000-0x07ffffff) has unknown permissions. 0xEC: 0x7fff7fff FREG15: unknown region (0x07fff000-0x07ffffff) has unknown permissions. 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. 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. 0xa0: 0xc0 (SSFS) SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0 0xa1: 0xfe0000 (SSFC) SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=6 0xa4: 0x5006 (PREOP) 0xa6: 0x463b (OPTYPE) 0xa8: 0x05200302 (OPMENU) 0xac: 0xc79f0190 (OPMENU+4) 0xc4: 0xb1d82024 (LVSCC) LVSCC: BES=0x0, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1 0xc8: 0x00002000 (UVSCC) UVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x20 Enabling hardware sequencing by default for Apollo/Gemini/Jasper/Elkhart/Meteor Lake. OK. The following protocols are supported: Programmer-specific. Probing for Programmer Opaque flash chip, 0 kB: Hardware sequencing reports 1 attached SPI flash chip with a density of 16384 kB. HSFC: FGO=1, FCYCLE=2, FDBC=2, SME=0 Chip identified: GD25LQ128C/GD25LQ128D/GD25LQ128E Added layout entry 00000000 - 00ffffff named complete flash Found GigaDevice flash chip "GD25LQ128C/GD25LQ128D/GD25LQ128E" (16384 kB, Programmer-specific) on internal. Found GigaDevice flash chip "GD25LQ128C/GD25LQ128D/GD25LQ128E" (16384 kB, Programmer-specific). 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). Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 ich_hwseq_read_status: only supports STATUS1 wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00. Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 ich_hwseq_read_status: only supports STATUS1 wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00. Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 ich_hwseq_read_status: only supports STATUS1 wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00. Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 ich_hwseq_read_status: only supports STATUS1 wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00. Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 ich_hwseq_read_status: only supports STATUS1 wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00. Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 ich_hwseq_read_status: only supports STATUS1 wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00. Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 Writing status register HSFC: FGO=1, FCYCLE=3, FDBC=0, SME=0 ich_hwseq_read_status: only supports STATUS1 wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00. Reading Status register HSFC: FGO=1, FCYCLE=0, FDBC=0, SME=0 write_wp_bits: wp_verify failed: reg:1 actual:0xb4 expected:0x34 ich_hwseq_read_status: only supports STATUS1 wp_read_register: read from register 2 not is supported by programmer, writeprotect operations will assume it contains 0x00. Failed to apply new WP settings: unexpected WP configuration read back from chip Note: hardware status register protection is enabled. The chip's WP# pin must be set to an inactive voltage level to be able to change the WP settings. Restoring MMIO space at 0x7bd11ce10084 Restoring MMIO space at 0x7bd11ce100ac Restoring MMIO space at 0x7bd11ce100a8 Restoring MMIO space at 0x7bd11ce100a6 Restoring MMIO space at 0x7bd11ce100a4

2 1

flashrom meeting notes 03.08.2023
by Anastasia Klimchuk 03 Aug '23

03 Aug '23

# 3th August 2023, 6.00-7.00am UTC+0 Attendees: Stefan, Carl-Daniel, Anastasia ## Decision summary * 3 developers get submit rights: Joursoir (Alexander Goncharov), Peter Marheine, Nikolai Artemiev * document the process of getting commit rights and send for review (todo aklm) ## Agenda * [aklm] I would like to nominate 3 developers to get submit rights: Joursoir (Alexander Goncharov) [authored](https://review.coreboot.org/q/owner:chat@joursoir.net), [reviewed](https://review.coreboot.org/q/reviewer:chat@joursoir.net), Peter Marheine [authored](https://review.coreboot.org/q/owner:pmarheine@chromium.org), [reviewed](https://review.coreboot.org/q/reviewer:pmarheine@chromium.org), Nikolai Artemiev [authored](https://review.coreboot.org/q/owner:nartemiev@google.com), [reviewed](https://review.coreboot.org/q/reviewer:nartemiev@google.com). They all made valuable contributions to flashrom, are on the project for a while already: 1-2-3.... years, currently active, are respected members of the dev community. To be more specific, and formal: we now have the duties documented [https://www.flashrom.org/about_flashrom/team.html](https://www.flashrom.org… and all of them agreed to do the duties. * all approved! * [aklm] ongoing item: "We need to figure out criteria to give people submit rights." Is it done with the Team page describing duties? A missing piece is to describe the process (which currently is: someone nominates you and adds an item to the meeting agenda in advance. whoever comes to the meeting, discusses and decides). So maybe document the process and ongoing item solved? * yes, document the process, send for review (todo aklm) * we can remove ongoing item * the process can be improved later, if any issues are observed. As of today, the process has been working for >1yr, everything seems to go well. * [Carl-Daniel] subject line for meeting notes email says "dev meeting", but there are various questions discussed, not only dev, but also organisational and any misc stuff. * [aklm] we can drop "dev"? that would be "flashrom meeting notes DD.MM.YYYY" * sounds good, drop "dev" from subject line -- Anastasia.

1 0

MCIX MX25L6406E M2I-12G (Acer DAFT3L-Kelia MB 12088-1M)
by Shizeeg Unadequatov 31 Jul '23

31 Jul '23

Board: Acer DAFT3L-Kelia MB 12088-1M Programmer: CH431 (CH341B) OS: NixOS 23.05 (Linux-6.1.39 x86_64) flashrom: v1.3.0 ```sh # command-line: % flashrom -p ch341a_spi -c "MX25L6406E/MX25L6408E" -w 12088-1M\ 48.3KN02.01M\ DAFT3L-KELIA\ MB.BIN ```

1 0

(no subject)
by vanniealdamar 31 Jul '23

31 Jul '23

Unknown flash Chip detected ( eon en25qx128a ) on ch341a bios programmer...any update for this thanks Sent from vivo smartphone

1 0

New flashrom website
by Anastasia Klimchuk 28 Jul '23

28 Jul '23

Good day everyone, Good news for the good day: we are launching the new flashrom website! doc.flashrom.org At the moment it is available by the address doc.flashrom.org, but in the very near future (think of a few weeks) it will move to primary flashrom.org. The reason for this few weeks' interval is to check everything looks good and fix small things. After the new website moves to the primary address, the old wiki website moves to wiki.flashrom.org and will be locked for editing. Wiki will be available as view-only until we migrate all the content. New website is generated by sphinx from sources that are in the tree under doc/ directory. To add or update documentation, you need to send a patch as per usual dev process. Separate wiki account is no longer needed to update the documentation. Everything is set up so that after the patch is merged into documentation, it will appear on the website shortly after. There is a doc on how to add docs with more details: https://doc.flashrom.org/how_to_add_docs.html As you can see, the new website doesn't have all of the pages migrated from the old wiki yet. This is by the plan, we will migrate the pages gradually, hopefully within this year. Everyone is very welcome to join migrating the wiki pages to doc/ files! Especially if there is a page in wiki that you own and can verify the correctness of content. Thanks a lot to everyone who was working on the new website! The idea has been around for a while, and it is so cool to see it happening! -- Anastasia.

2 3

flashrom dev meeting notes 20.07.2023
by Anastasia Klimchuk 28 Jul '23

28 Jul '23

# 20th July 2023, 6.00-7.00am UTC+0 Attendees: Stefan, Edward, Anastasia ## Decision summary * flashrom.org is new, wiki.flashrom.org is old (will be a dedicated post on the ML) ## Agenda * New website: let's do it right now! * Done: flashrom.org is new, wiki.flashrom.org is old, and old one is locked for editing (no edit button anymore) * one thing left: put a red banner on old wiki which says it is retired and locked for editing * aklm to post news on mailing list * Code of conduct patch [https://review.coreboot.org/c/flashrom/+/76455](https://review.coreboot.org… * maybe coreboot can help in the beginning? but longer term we need our own. -- Anastasia.

2 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom