flashrom January 2019

flashrom@flashrom.org

26 participants
24 discussions

Re: [flashrom] Cleanup patches for flashrom
by Nico Huber 02 Jan '19

02 Jan '19

Hi Richard, On 20.12.18 11:11, Richard Hughes wrote: > We're slowly moving towards using libflashrom in fwupd, rather than > exec'ing the flashrom binary and screen scraping. So that it can be > consumed by users easily, I'm tempted to use flashrom as a subproject > to the fwupd project rather than waiting for distros to ship any new > bleeding edge version of flashrom to users. To make some of that > possible, I've fixed up a few of the CI failures we would see in > fwupd, which I've filed as a PR here: > https://github.com/flashrom/flashrom/pull/67 thanks. > > If a GitHub PR isn't how you want these kind of general patches please > let me know. One person already told me that I needed to use Gerrit, When we switched to Gerrit, we decided to still allow patches per email and also on GitHub. Though, all patches have to go through Gerrit in the end as that's where the official repository is. I've never been active on GitHub (my account is only few months old). And the developers that set the flashrom mirror up there obviously had the best intentions (pull requests are mentioned in the project des- cription) but aren't actively reviewing atm. I also can't say anymore that everything on Gerrit gets a review, though smaller changes do. If you'd use Gerrit, you'd hit the remaining active reviewers right in their everyday workflow. > but I'm not overly keen on learning a new process if I can avoid it. > Feedback welcome, thanks. I just tried, it was horrible ;) I just can't find a way to comment on individual commits of your PR (beside commenting inline in the code). I'll leave some comments their and pull those commits that seem ready to go. Nico

2 1

Hardware support
by Waltteri Koskinen 02 Jan '19

02 Jan '19

Hello! I wanted to report that I have successfully probed, read, erased and wrote in this chip https://www.mouser.fi/datasheet/2/308/LE25U40CMD-D-972803.pdf I used raspberry pi 1.gen and linux_spi. Thank you for this fantastic software it saved my pc display. BR. Waltteri Koskinen

1 0

FAILED: Asus Chromebox 3 / CN65 (TEEMO)
by Markku Viholainen 02 Jan '19

02 Jan '19

Hi, do you have any idea what to do with folowing error? ChromeOS Firmware Utility Script [2018-12-30] (c) Mr Chromebox <mrchromebox(a)gmail.com> ********************************************************* ** Device: Asus Chromebox 3 / CN65 (TEEMO) ** CPU Type: Intel KabyLake ** Fw Type: Stock ChromeOS ** Fw WP: Disabled ********************************************************* ** 1) Install/Update RW_LEGACY Firmware ** 2) Install/Update BOOT_STUB Firmware ** [WP] 3) Install/Update Full ROM Firmware ** [WP] 4) Set Boot Options (GBB flags) ** [WP] 5) Set Hardware ID (HWID) ** 6) Remove ChromeOS Bitmaps ** 7) Restore ChromeOS Bitmaps ** 8) Restore Stock BOOT_STUB ** 9) Restore Stock Firmware (full) ********************************************************* Select a menu option or R to reboot P to poweroff Q to quit 3 Install/Update UEFI Full ROM Firmware Standard disclaimer: flashing the firmware has the potential to brick your device, requiring relatively inexpensive hardware and some technical knowledge to recover. You have been warned. Also, flashing Full ROM firmware will remove your ability to run ChromeOS. Do you wish to continue? [y/N] y NOTE: After flashing UEFI firmware, you will need to install a UEFI-compatible OS; ChromeOS will no longer be bootable. UEFI firmware supports Windows and Linux on all devices. Debian/Ubuntu-based distros require a small fix to boot after install -- see https://mrchromebox.tech/#faq for more info. Press Y to continue or any other key to abort. y Create a backup copy of your stock firmware? This is highly recommended in case you wish to return your device to stock configuration/run ChromeOS, or in the (unlikely) event that things go south and you need to recover using an external EEPROM programmer. [Y/n] n Downloading Full ROM firmware (coreboot_tiano-fizz-mrchromebox_20181230.rom) Disabling software write-protect and clearing the WP range Installing Full ROM firmware (may take up to 90s) flashrom v0.9.9 : 266087c : Nov 20 2018 01:07:48 UTC on Linux 4.4.159-15346-gc5e629939ae0 (x86_64) Calibrating delay loop... OK. coreboot table found at 0x7aac2000. WARNING: SPI Configuration Lockdown activated. Erasing and writing flash chip... Verifying flash... VERIFY FAILED at 0x00000086! Expected=0x40, Read=0xc0, failed byte count from 0x00000000-0x00ffffff: 0x2 Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org with FAILED: your board name in the subject line! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! FAILED An error occurred flashing the Full ROM firmware. DO NOT REBOOT! Press [Enter] to return to the main menu.^C +Markku+

1 0

Flashing Asus KGPE-D16 Chip
by Joshua Aspinall 02 Jan '19

02 Jan '19

Hi, I am attempting to write a Libreboot ROM to my BIOS chip. The chip reports as follows: sudo flashrom -p linux_spi:dev=/dev/spidev0.0 'Found Winbond flash chip "W25Q16.V" (2048 kB, SPI) on linux_spi.' All of the online guides show reading the chip before attempting to flash, and confirming that the checksums match. However, when reading the contents of the flash chip, the checksums vary wildly. When attempting to flash the chip with a Libreboot ROM for the board, the erase function fails on all attempts as follows: sudo flashrom --programmer linux_spi:dev=/dev/spidev0.0 --write kgpe-d16_ukqwerty_txtmode.rom flashrom p1.0-141-g9cecc7e on Linux 4.14.79+ (armv6l) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Using default 2000kHz clock. Use 'spispeed' parameter to override. Found Winbond flash chip "W25Q16.V" (2048 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x000007fd! Expected=0xff, Found=0xfe, failed byte count from 0x00000000-0x00007fff: 0x6218 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x000001bb! Expected=0xff, Found=0xfc, failed byte count from 0x00000000-0x0000ffff: 0xbde4 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x001fffff: 0x18a7c0 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000111! Expected=0xff, Found=0xc0, failed byte count from 0x00000000-0x001fffff: 0x18af13 ERASE FAILED! Reading current flash chip contents... done. 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. Checking if anything has changed. Reading current flash chip contents... done. Apparently at least some data has changed. 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! I am trying to determine whether I am doing something incorrectly, or whether the chip is unserviceable and needs to be replaced. Any help/hints would be greatly appreciated! Best Regards, Joshua Aspinall.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom January 2019