I successfully flashed my device using this command—thank you! sudo flashrom -p raiden_debug_spi:target=AP -c "GD25B128B/GD25Q128B" -w coreboot_edk2-atlas-mrchromebox_20260409.rom
On Sat, May 2, 2026 at 12:11 PM wcrvf <[email protected]> wrote: > Hello flashrom team, > > i don't know how to deal with it > > I am reporting a flash failure on a Google Pixelbook Go (Board Name: > ATLAS). [System Info] - Device: Google Pixelbook Go (ATLAS) - Environment: > ChromeOS Developer Mode / Ubuntu (Linux 6.14.0) - Programmer: internal - > Hardware WP: Disabled via SuzyQable (Cr50 CCD opened, FlashAP Always) > [Error Description] While attempting to flash the Full ROM firmware, I > encountered the following errors: 1. Warning: Setting BIOS Control at 0xdc > from 0x8b to 0x89 failed. 2. SPI Configuration is locked down. 3. FREG0 > (Descriptor) and FREG2 (ME) are locked. 4. "Opaque flash chip" detected, WP > operations not implemented. [Attached Log] (Please find the attached > /tmp/flashrom.log for detailed output) It seems the Intel Kaby Lake chipset > is locking the SPI configuration, preventing flashrom from performing > erase/write operations even with hardware write-protect disabled via CCD. > Regards, > > Thanks > > > > ChromeOS Device Firmware Utility Script [2026-04-30] > (c) Mr Chromebox <[email protected]> > ********************************************************* > ** Device: Google Pixelbook Go > ** Board Name: ATLAS > ** Platform: Intel KabyLake > ** Fw Type: Full ROM / UEFI > ** Fw Ver: MrChromebox-4.22.2-5-g822782a1001 (02/13/2024) > ** Update Available (04/09/2026) > ** Fw WP: Disabled > ********************************************************* > ** [WP] 1) Install/Update UEFI (Full ROM) Firmware > ** [WP] 2) Restore Stock Firmware > ** 3) Backup Current Firmware > ** [WP] 4) Flash Custom Firmware > ** 5) Set Hardware ID (HWID) > ** C) Clear UEFI NVRAM > ********************************************************* > Select a numeric menu option or > R to reboot P to poweroff Q to quit > 1 > > Install/Update UEFI Full ROM Firmware > > IMPORTANT: flashing the firmware has the potential to brick your device, > requiring relatively inexpensive hardware and some technical knowledge to > recover.Not all boards can be tested prior to release, and even then slight > differences in hardware can lead to unforseen failures. > If you don't have the ability to recover from a bad flash, you're taking a > risk. > > You have been warned. > > Do you wish to continue? [y/N] y > > > Downloading Full ROM firmware > (coreboot_edk2-atlas-mrchromebox_20260409.rom) > > ############################################################################################################################################################################## > 100.0% > ############################################################################################################################################################################## > 100.0% > > Creating device HWID from board name > > Persisting device HWID > > VPD extracted from current firmware > > Disabling software write-protect and clearing the WP range > > Installing Full ROM firmware (may take up to 90s) > > Error running cmd: /tmp/flashrom -p internal:boardmismatch=force > --use-first-chip --ifd -i bios -N -w > coreboot_edk2-atlas-mrchromebox_20260409.rom >/dev/null 2>&1 -o > /tmp/flashrom.l > og > > Press enter to view the flashrom log file, then space for next page, q to > quit > > > > > > FAILED at 0x00c00000! Expected=0xff, Found=0x5f, failed byte count from > 0x00c00000-0x00c00fff: 0x1dc > ERASE FAILED! > Erase/write done from 200000 to ffffff > Write Failed!Uh oh. Erase/write failed. > Your flash chip is in an unknown state. > Get help on IRC (see https://www.flashrom.org/Contact) or mail > [email protected] with the subject "FAILED: <your board > name>"!------------------------------------------------------------------------------- > DO NOT REBOOT OR POWEROFF! > Restoring PCI config space for 00:1f:5 reg 0xdc > >
_______________________________________________ flashrom mailing list -- [email protected] To unsubscribe send an email to [email protected]
