What version of flashrom do you have? It looks like this might be the bug that was introduced in 1.5.0 and fixed in 1.5.1.
On Fri, Dec 13, 2024 at 2:46 AM Chris Andrew cjhandrew@gmail.com wrote:
Hi, guys.
I'm trying to update the firmware for my Toshiba Swanky. I've done this several times before, without issue, but have got an error, this time. Can you tell me what you may need, to help troubleshoot this?
*My machine:*
System: Host: swanky Kernel: 6.12.4-arch1-1 arch: x86_64 bits: 64 Desktop: Xfce v: 4.18.1 Distro: EndeavourOS Machine: Type: Laptop System: GOOGLE product: Swanky v: 1.0 serial: 5F239563C Mobo: GOOGLE model: Swanky v: 1.0 serial: N/A UEFI: coreboot v: MrChromebox-4.22.4 date: 04/16/2024 Battery: ID-1: BAT0 charge: 33.1 Wh (97.6%) condition: 33.9/44.2 Wh (76.7%) CPU: Info: dual core model: Intel Celeron N2840 bits: 64 type: MCP cache: L2: 1024 KiB
*The command I used, today:*
[chris@swanky ~]$ cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh
*Some of the output:*
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). Skipping writeprotect-based unlocking for read/verify operations. Block protection is disabled. Reading ich descriptor... read_flash: region (00000000..0x7fffff) is readable, reading range (00000000..0x000fff). done. Assuming chipset 'Baytrail'. Added layout entry 00000000 - 00000fff named fd Added layout entry 00200000 - 007fffff named bios Added layout entry 00001000 - 001fffff named me Using region: "bios". coreboot last image size (not ROM size) is 8388608 bytes. Manufacturer: Google Mainboard ID: Swanky This coreboot image matches this mainboard. spi_read_register: read from register 2 not supported by programmer
I hope this helps,
Chris (chris_debian) _______________________________________________ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-leave@flashrom.org