April 2018 - flashrom - mail.coreboot.org

Re: [flashrom] New SPI NOR Flash product Support
by Stefan Tauner Aug. 15, 2019

Aug. 15, 2019

On Mon, 9 May 2016 20:46:18 -0700 David Hendricks <dhendrix(a)google.com> wrote: > Hi Victor, > From Flashrom's software perspective all chips with the same ID are > indistinguishable. > > Part number often includes characteristics such as package and thermal > tolerance which do not affect software compatibility. However, we will add the new names to the in-program (and hence wiki) database so that this new information becomes public. Thanks for the heads up, Victor. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

4 4

80/100/132 column line width policy
by Carl-Daniel Hailfinger Dec. 15, 2018

Dec. 15, 2018

Hi, we're hitting the 80 column limit in our code in ways which actually reduce readability for the code. Examples are various multiline messages and complicated nested code where refactoring to a separate function doesn't make sense. Keeping the old 80 column limit is not really an option anymore. Standard terminal sizes have one of 80, 100 or 132 columns. Given the monitor resolutions many people have nowadays, I think it is safe to say that you can fit two xterms with 100 columns horizonally next to each other. 100 columns should also be sufficient for a msg_p* of roughly 80 columns of text. 132 columns provide more leeway, but IMHO that would be too wide for good readability (and my screen can't fit two xterms side-by-side anymore). Of course some files have sections where any column limit is not acceptable (board lists etc.), but the column limit violations should be limited to the affected file sections, not whole files. Comments? I'd like to get this decided today or tomorrow so we know where we need line breaks in Stefan Tauner's new struct flashchip patch. Regards, Carl-Daniel -- http://www.hailfinger.org/

7 9

FOSDEM Hardware Enablement Devroom
by Paul Kocialkowski Dec. 4, 2018

Dec. 4, 2018

A Hardware Enablement devroom will be taking place at FOSDEM this year, on Sunday 10 December 2017. This newly-created devroom is the result of 3 proposals that were merged together. It is co-organized by several individuals. The devroom covers all aspects related to hardware enablement and support with free software, including aspects related to boot software, firmwares, drivers and userspace tools and adaptation. Proposals for talks related to these topics are welcome and can be submitted until Sunday 26 November 2017 via the pentabarf interface. Short talks are encouraged over longer ones in order to cover a wide range of topics. The announcement for the devroom, that contains all the useful information, was published at: https://lists.fosdem.org/pipermail/fosdem/2017-October/002649.html Cheers and see you at FOSDEM! -- Paul Kocialkowski, developer of free digital technology and hardware support Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/

3 3

Re: [flashrom] FAILED: Soraka DVT1
by David Hendricks April 27, 2018

April 27, 2018

Hello Hongxia, Were you able to get in touch with someone on the chromiumos team? It appears that you attempted to write the entire firmware ROM, but it failed to write the flash descriptor region. You should target the region(s) you want updated using the -i option, along with --fast-verify, so that flashrom does not attempt to write and verify regions that it might not have access to. On Mon, Apr 23, 2018 at 11:54 PM, Gao, HongxiaX <hongxiax.gao(a)intel.com> wrote: > Hi, > > > > It is failed on my board when flashing firmware R68 10599. Can you help me > on it? > > > > *HW:* Soraka DVT1 > > > > *Issue description:* > > Flash firmware 10431 without any problems, but it is failed when flashing > firmware R68 10599. Steps are: > > > > 1. Download firmware R68 10599 > <https://www.google.com/chromeos/partner/fe/#download:event=IMAGE_DOWNLOAD&u…>, > then extract it. > > 2. Enter board terminal > > localhost /home # flashrom -w 10599/image.bin > > flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 > (x86_64) > > flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 > (x86_64) > > Calibrating delay loop... OK. > > coreboot table found at 0x7aac5000. > > WARNING: SPI Configuration Lockdown activated. > > Erasing and writing flash chip... Verifying flash... VERIFY FAILED at > 0x00000081! Expected=0xff, Read=0x0b, failed byte count from > 0x00000000-0x00ffffff: 0x9 > > 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 > > > > 3. Try to update firmware > > localhost /home/10599 # chromeos-firmwareupdate -m autoupdate > > Starting Google_Soraka firmware updater v4 (autoupdate)... > > - Updater package: [Google_Soraka.10431.32.0 / > EC:soraka_v1.1.8047-2c5917d7d] > > - Current system: [RO:Google_Soraka.10431.32.0 , > ACT:Google_Soraka.10431.32.0 / EC:soraka_v1.1.8047-2c5917d7d] > > - Write protection: Hardware: ON, Software: Main=off > > * invoke: flashrom -p host -r _current/bios.bin > > RO Contents are different. > > autoupdate(recovery): update RO+RW > > * invoke: flashrom -p host --fast-verify -w bios.bin > > autoupdate(recovery): update ec/RO+RW > > * invoke: flashrom -p ec --fast-verify -w ec.bin > > autoupdate(recovery): EC may be restored or updated in next boot. > > Firmware update (autoupdate) completed. > > > > 4. Reboot the board, then power off and power on > > 5. Flash fw 10599 again > > localhost /home # flashrom -w 10599/image.bin > > flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 > (x86_64) > > flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 > (x86_64) > > Calibrating delay loop... OK. > > coreboot table found at 0x7aac5000. > > WARNING: SPI Configuration Lockdown activated. > > Erasing and writing flash chip... Verifying flash... VERIFY FAILED at > 0x00000081! Expected=0xff, Read=0x0b, failed byte count from > 0x00000000-0x00ffffff: 0x9 > > 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 > > > > > > Thanks > > > > Br, > > Hongxia > > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom >

1 0

Re: [flashrom] Flash support FT25H04
by Balázs Vinarz April 26, 2018

April 26, 2018

Sorry, I made a mistake when applying the patch. So the patch works with read, erase and write functions. 2018-04-26 11:34 GMT+02:00 Balázs Vinarz <vinibali1(a)gmail.com>: > Hello there! > > I have the following chip: FT25H04. This is not yet supported even with > the following: patch > <https://raw.githubusercontent.com/tomaskovacik/kicad-library/master/library…>. > Can I help you anyhow to let this type supported? > > Regards >

1 0

Flash support FT25H04
by Balázs Vinarz April 26, 2018

April 26, 2018

Hello there! I have the following chip: FT25H04. This is not yet supported even with the following: patch <https://raw.githubusercontent.com/tomaskovacik/kicad-library/master/library…>. Can I help you anyhow to let this type supported? Regards

1 0

FAILED: Soraka DVT1
by Gao, HongxiaX April 24, 2018

April 24, 2018

Hi, It is failed on my board when flashing firmware R68 10599. Can you help me on it? HW: Soraka DVT1 Issue description: Flash firmware 10431 without any problems, but it is failed when flashing firmware R68 10599. Steps are: 1. Download firmware R68 10599<https://www.google.com/chromeos/partner/fe/#download:event=IMAGE_DOWNLOAD&u…>, then extract it. 2. Enter board terminal localhost /home # flashrom -w 10599/image.bin flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 (x86_64) flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 (x86_64) Calibrating delay loop... OK. coreboot table found at 0x7aac5000. WARNING: SPI Configuration Lockdown activated. Erasing and writing flash chip... Verifying flash... VERIFY FAILED at 0x00000081! Expected=0xff, Read=0x0b, failed byte count from 0x00000000-0x00ffffff: 0x9 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 3. Try to update firmware localhost /home/10599 # chromeos-firmwareupdate -m autoupdate Starting Google_Soraka firmware updater v4 (autoupdate)... - Updater package: [Google_Soraka.10431.32.0 / EC:soraka_v1.1.8047-2c5917d7d] - Current system: [RO:Google_Soraka.10431.32.0 , ACT:Google_Soraka.10431.32.0 / EC:soraka_v1.1.8047-2c5917d7d] - Write protection: Hardware: ON, Software: Main=off * invoke: flashrom -p host -r _current/bios.bin RO Contents are different. autoupdate(recovery): update RO+RW * invoke: flashrom -p host --fast-verify -w bios.bin autoupdate(recovery): update ec/RO+RW * invoke: flashrom -p ec --fast-verify -w ec.bin autoupdate(recovery): EC may be restored or updated in next boot. Firmware update (autoupdate) completed. 4. Reboot the board, then power off and power on 5. Flash fw 10599 again localhost /home # flashrom -w 10599/image.bin flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 (x86_64) flashrom v0.9.9 : cfd7dfc : Apr 06 2018 05:12:10 UTC on Linux 4.4.128 (x86_64) Calibrating delay loop... OK. coreboot table found at 0x7aac5000. WARNING: SPI Configuration Lockdown activated. Erasing and writing flash chip... Verifying flash... VERIFY FAILED at 0x00000081! Expected=0xff, Read=0x0b, failed byte count from 0x00000000-0x00ffffff: 0x9 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 Thanks Br, Hongxia

1 0

Re: [flashrom] WinBond Chip Support
by Nico Huber April 17, 2018

April 17, 2018

Hi Jordan, On 17.04.2018 14:40, Jordan Hill wrote: > Hello there, > > I have a Dell Inspiron 5559 Laptop which contains a Winbond 25Q128FVSQ > Chip. I tried running flashrom natively on the laptop and got the usual EC > warning so i stopped there. I then desoldered the SMD chip off the > motherboard and hooked it up to a RPI and connected it through the SPI > protocol. Flashrom then recognized it as a "Generic" flash chip and would > not allow the data to be read as it was still unrecognized. did you connect all input pins of the flash chip? A common error is to leave /HOLD and /WP floating. But they need a defined state. /HOLD has to be pulled up (towards VCC). /WP up too (might as well be down depen- ding on the chip's configuration, but up always works). Nico

1 0

WinBond Chip Support
by Jordan Hill April 17, 2018

April 17, 2018

Hello there, I have a Dell Inspiron 5559 Laptop which contains a Winbond 25Q128FVSQ Chip. I tried running flashrom natively on the laptop and got the usual EC warning so i stopped there. I then desoldered the SMD chip off the motherboard and hooked it up to a RPI and connected it through the SPI protocol. Flashrom then recognized it as a "Generic" flash chip and would not allow the data to be read as it was still unrecognized. Unfortunately I do not have any logs. I believe that this chip is on the list of supported hardware yet it was not recognized in flashrom. I am using the latest version as of April 18th 2018. Any suggestions or help would be appreciated. Thank You

1 0

Re: [flashrom] no spi flash IS25LP128
by Nico Huber April 17, 2018

April 17, 2018

On 16.04.2018 05:07, 山中老虎 wrote: > no spi flash IS25LP128 This chip is supported on our master branch only. You'd have to clone the repository and build flashrom yourself, see [1]. Nico PS. Please don't send unnecessary large attachments to the mailing list. [1] https://flashrom.org/Downloads

1 0