February 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. 14, 2018

Dec. 14, 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

Can't Flash on AOpen i965GMt-LA motherboard
by Björn Tantau March 19, 2018

March 19, 2018

Hi! I tried to flash a new BIOS to my AOpen i965GMt-LA motherboard. Reading the ROM worked, but flashing did not. I'll gladly give you more information, just tell me what you need. :-) Cheers, Björn $ sudo flashrom --programmer internal -c "W39V040FA" -w IGC1B.BIN flashrom v0.9.9-rc1-r1942 on Linux 4.4.0-112-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. Found chipset "Intel ICH8M". Enabling flash write... OK. Found Winbond flash chip "W39V040FA" (512 kB, FWH) mapped at physical address 0x00000000fff80000. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x49, failed byte count from 0x00000000-0x00000fff: 0x463 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x49, failed byte count from 0x00000000-0x0000ffff: 0x463 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. FAILED at 0x00000000! Expected=0xff, Found=0x49, failed byte count from 0x00000000-0x0007ffff: 0x60915 ERASE FAILED! 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. Good, writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running.

4 7

Building on Windows with mingw
by Miklos Marton Feb. 28, 2018

Feb. 28, 2018

Hello all, I have tried to build the flashrom with mingw on Windows, but the build process fails with: flash.h:336:1: error: '__MINGW_PRINTF_FORMAT' is an unrecognized format function type [-Werror=format=] __attribute__((format(__MINGW_PRINTF_FORMAT, 2, 3))); I have checked the stdio.h shipped with the mingw installation, but it does not contains the __MINGW_PRINTF_FORMAT macro. I have used the latest available mingw-get-setup, because the 20110530 version (which mentioned in the wiki as known t obe working) segfaults when I select the MSYS Basic System feature. I can build with WARNERROR=no, but some more permanent fix recommentation would be warmly welcome! -- Best regards, Miklos Marton

3 5

Мир вам
by Djamel Kalala Feb. 27, 2018

Feb. 27, 2018

У меня вопрос о программе NANDLite Я хочу сделать одну возможную диаграмму

2 1

Re: [flashrom] Trying to dump the contents of a Micron 25Q064A
by The_Raven Raven Feb. 27, 2018

Feb. 27, 2018

Why you don't connect it directly to the pi? Tow things you can try: 1. Try to read the chip with this parameter: "flashrom -V -p linux_spi:dev=/dev/spidev0.0,spispeed=30000" 2. Connect the chip directly to the pi. Greets Am 26.02.2018 um 22:10 schrieb Tim Elliott: > I have my SPI flash chip connected to a logic level shifter and that > connected to a raspberry pi. I am running flashrom and it will find an > "unknown SPI chip (RDID) (0KB, SPI)". It says that "the flash part has > status NOT WORKING" for operations: PROBE READ ERASE WRITE". Is that > normal that it can talk to it but can't read the contents? > Thanks > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://mail.coreboot.org/mailman/listinfo/flashrom

1 0

PATCH: Adding support for Sanyo "LE25FU206"
by The_Raven Raven Feb. 27, 2018

Feb. 27, 2018

Hi I made a Patch for adding Sanyo "LE25FU206" Chip. Tested (with raspberrypi-linux_spi): - Probing - Reading (i readed the chip 3 times and make a diff, all diffs are same) - Erasing (tested all 3 erase-modes) - Writing data1 - Writing data2 (overwriting) Greets

1 0

Add support new hardware
by Алексей Болдырев Feb. 26, 2018

Feb. 26, 2018

Please add support from: EC ITE IT8586E-LQFP

1 0

Trying to dump the contents of a Micron 25Q064A
by Tim Elliott Feb. 26, 2018

Feb. 26, 2018

I have my SPI flash chip connected to a logic level shifter and that connected to a raspberry pi. I am running flashrom and it will find an "unknown SPI chip (RDID) (0KB, SPI)". It says that "the flash part has status NOT WORKING" for operations: PROBE READ ERASE WRITE". Is that normal that it can talk to it but can't read the contents? Thanks

1 0