flashrom March 2014

flashrom@flashrom.org

41 participants
124 discussions

[commit] r1767 - trunk
by repository service 17 Mar '14

17 Mar '14

Author: stefanct Date: Mon Mar 17 23:07:29 2014 New Revision: 1767 URL: http://flashrom.org/trac/flashrom/changeset/1767 Log: Add support for Intel 82574L to nicintel_spi.c. Signed-off-by: Bill Paul <wpaul(a)windriver.com> Acked-by: Idwer Vollering <vidwer(a)gmail.com> Modified: trunk/nicintel_spi.c Modified: trunk/nicintel_spi.c ============================================================================== --- trunk/nicintel_spi.c Fri Mar 14 09:10:02 2014 (r1766) +++ trunk/nicintel_spi.c Mon Mar 17 23:07:29 2014 (r1767) @@ -19,10 +19,16 @@ */ /* - * Datasheet: + * Datasheets: * PCI/PCI-X Family of Gigabit Ethernet Controllers Software Developer's Manual * 82540EP/EM, 82541xx, 82544GC/EI, 82545GM/EM, 82546GB/EB, and 82547xx - * http://download.intel.com/design/network/manuals/8254x_GBe_SDM.pdf + * http://www.intel.com/content/www/us/en/ethernet-controllers/pci-pci-x-famil… + * + * PCIe GbE Controllers Open Source Software Developer's Manual + * http://www.intel.com/content/www/us/en/ethernet-controllers/pcie-gbe-contro… + * + * Intel 82574 Gigabit Ethernet Controller Family Datasheet + * http://www.intel.com/content/www/us/en/ethernet-controllers/82574l-gbe-cont… */ #include <stdlib.h> @@ -72,6 +78,7 @@ {PCI_VENDOR_ID_INTEL, 0x1076, OK, "Intel", "82541GI Gigabit Ethernet Controller"}, {PCI_VENDOR_ID_INTEL, 0x107c, OK, "Intel", "82541PI Gigabit Ethernet Controller"}, {PCI_VENDOR_ID_INTEL, 0x10b9, OK, "Intel", "82572EI Gigabit Ethernet Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10d3, OK, "Intel", "82574L Gigabit Ethernet Controller"}, {0}, };

1 0

Re: [flashrom] Erase failed
by Leonardo Pedretti 17 Mar '14

17 Mar '14

Nevermind! I risked downloading and compiling the last build, selected the internal programmer and worked like a charm! Thank you very much!! Best regards! ---------------------------------------------------------------------------------- Leonardo Pedretti Código Dínamo +54 11 50935333 / +54 11 15 35745251 http://www.codigodinamo.com 2014-03-17 15:29 GMT-03:00 Leonardo Pedretti <lpedretti(a)codigodinamo.com>: > Hey! sorry to bother you, i really try to help myself out, but in this > case i lack any knowledge of the details of bios memory management. > I have tried to flash the bios on my k8n Neo4 Platinum pcb v 1.0, the > write started giving errors, output follows... > > flashrom v0.9.2-r1141 on Linux 2.6.32-5-686 (i686), built with libpci > 3.1.7, GCC 4.4.5 20100728 (prerelease), little endian > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > No coreboot table found. > Found chipset "NVIDIA CK804", enabling flash write... OK. > This chipset supports the following protocols: Non-SPI. > Disabling flash write protection for board "MSI K8N Neo4-F"... OK. > Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address > 0xfff80000. > Flash image seems to be a legacy BIOS. Disabling checks. > Writing flash chip... Erasing flash chip... SUCCESS. > Programming page: address: 0x00040000 writing sector at 0xb744d000 failed! > > writing sector at 0xb744d400 failed! > writing sector at 0xb744d800 failed! > writing sector at 0xb744dc00 failed! > address: 0x00041000 writing sector at 0xb744e000 failed! > > writing sector at 0xb744e400 failed! > writing sector at 0xb744e800 failed! > writing sector at 0xb744ec00 failed! > address: 0x00042000 writing sector at 0xb744f000 failed! > > writing sector at 0xb744f400 failed! > writing sector at 0xb744f800 failed! > writing sector at 0xb744fc00 failed! > address: 0x00043000 writing sector at 0xb7450000 failed! > > writing sector at 0xb7450400 failed! > writing sector at 0xb7450800 failed! > writing sector at 0xb7450c00 failed! > address: 0x00044000 writing sector at 0xb7451000 failed! > > writing sector at 0xb7451400 failed! > writing sector at 0xb7451800 failed! > writing sector at 0xb7451c00 failed! > address: 0x00045000 writing sector at 0xb7452000 failed! > > writing sector at 0xb7452400 failed! > writing sector at 0xb7452800 failed! > writing sector at 0xb7452c00 failed! > address: 0x00046000 writing sector at 0xb7453000 failed! > > writing sector at 0xb7453400 failed! > writing sector at 0xb7453800 failed! > writing sector at 0xb7453c00 failed! > address: 0x00047000 writing sector at 0xb7454000 failed! > > writing sector at 0xb7454400 failed! > writing sector at 0xb7454800 failed! > writing sector at 0xb7454c00 failed! > address: 0x00048000 writing sector at 0xb7455000 failed! > > writing sector at 0xb7455400 failed! > writing sector at 0xb7455800 failed! > writing sector at 0xb7455c00 failed! > address: 0x00049000 writing sector at 0xb7456000 failed! > > writing sector at 0xb7456400 failed! > writing sector at 0xb7456800 failed! > writing sector at 0xb7456c00 failed! > address: 0x0004a000 writing sector at 0xb7457000 failed! > > writing sector at 0xb7457400 failed! > writing sector at 0xb7457800 failed! > writing sector at 0xb7457c00 failed! > address: 0x0004b000 writing sector at 0xb7458000 failed! > > writing sector at 0xb7458400 failed! > writing sector at 0xb7458800 failed! > writing sector at 0xb7458c00 failed! > address: 0x0004c000 writing sector at 0xb7459000 failed! > > writing sector at 0xb7459400 failed! > writing sector at 0xb7459800 failed! > writing sector at 0xb7459c00 failed! > address: 0x0004d000 writing sector at 0xb745a000 failed! > > writing sector at 0xb745a400 failed! > writing sector at 0xb745a800 failed! > writing sector at 0xb745ac00 failed! > address: 0x0004e000 writing sector at 0xb745b000 failed! > > writing sector at 0xb745b400 failed! > writing sector at 0xb745b800 failed! > writing sector at 0xb745bc00 failed! > address: 0x0004f000 writing sector at 0xb745c000 failed! > > writing sector at 0xb745c400 failed! > writing sector at 0xb745c800 failed! > writing sector at 0xb745cc00 failed! > address: 0x00050000 writing sector at 0xb745d000 failed! > > writing sector at 0xb745d400 failed! > writing sector at 0xb745d800 failed! > writing sector at 0xb745dc00 failed! > address: 0x00051000 writing sector at 0xb745e000 failed! > > writing sector at 0xb745e400 failed! > writing sector at 0xb745e800 failed! > writing sector at 0xb745ec00 failed! > address: 0x00052000 writing sector at 0xb745f000 failed! > > writing sector at 0xb745f400 failed! > writing sector at 0xb745f800 failed! > writing sector at 0xb745fc00 failed! > address: 0x00053000 writing sector at 0xb7460000 failed! > > writing sector at 0xb7460400 failed! > writing sector at 0xb7460800 failed! > writing sector at 0xb7460c00 failed! > address: 0x00054000 writing sector at 0xb7461000 failed! > > writing sector at 0xb7461400 failed! > writing sector at 0xb7461800 failed! > writing sector at 0xb7461c00 failed! > address: 0x00055000 writing sector at 0xb7462000 failed! > > writing sector at 0xb7462400 failed! > writing sector at 0xb7462800 failed! > writing sector at 0xb7462c00 failed! > address: 0x00056000 writing sector at 0xb7463000 failed! > > writing sector at 0xb7463400 failed! > writing sector at 0xb7463800 failed! > writing sector at 0xb7463c00 failed! > address: 0x00057000 writing sector at 0xb7464000 failed! > > writing sector at 0xb7464400 failed! > writing sector at 0xb7464800 failed! > writing sector at 0xb7464c00 failed! > address: 0x00058000 writing sector at 0xb7465000 failed! > > writing sector at 0xb7465400 failed! > writing sector at 0xb7465800 failed! > writing sector at 0xb7465c00 failed! > address: 0x00059000 writing sector at 0xb7466000 failed! > > writing sector at 0xb7466400 failed! > writing sector at 0xb7466800 failed! > writing sector at 0xb7466c00 failed! > address: 0x0005a000 writing sector at 0xb7467000 failed! > > writing sector at 0xb7467400 failed! > writing sector at 0xb7467800 failed! > writing sector at 0xb7467c00 failed! > address: 0x0005b000 writing sector at 0xb7468000 failed! > > writing sector at 0xb7468400 failed! > writing sector at 0xb7468800 failed! > writing sector at 0xb7468c00 failed! > address: 0x0005c000 writing sector at 0xb7469000 failed! > > writing sector at 0xb7469400 failed! > writing sector at 0xb7469800 failed! > writing sector at 0xb7469c00 failed! > address: 0x0005d000 writing sector at 0xb746a000 failed! > > writing sector at 0xb746a400 failed! > writing sector at 0xb746a800 failed! > writing sector at 0xb746ac00 failed! > address: 0x0005e000 writing sector at 0xb746b000 failed! > > writing sector at 0xb746b400 failed! > writing sector at 0xb746b800 failed! > writing sector at 0xb746bc00 failed! > address: 0x0005f000 writing sector at 0xb746c000 failed! > > writing sector at 0xb746c400 failed! > writing sector at 0xb746c800 failed! > writing sector at 0xb746cc00 failed! > DONE!ss: 0x0007f000 > COMPLETE. > Verifying flash... VERIFY FAILED at 0x00005555! Expected=0xff, Read=0xaa, > failed byte count from 0x00000000-0x0007ffff: 0x1fd7c > Your flash chip is in an unknown state. > Get help on IRC at irc.freenode.net (channel #flashrom) or > mail flashrom(a)flashrom.org! > > ------------------------------------------------------------------------------- > DO NOT REBOOT OR POWEROFF! > > Thanx for any guidance! > > Best regards! > > > ---------------------------------------------------------------------------------- > Leonardo Pedretti > Código Dínamo > +54 11 50935333 / +54 11 15 35745251 > http://www.codigodinamo.com > >

1 0

Erase failed
by Leonardo Pedretti 17 Mar '14

17 Mar '14

Hey! sorry to bother you, i really try to help myself out, but in this case i lack any knowledge of the details of bios memory management. I have tried to flash the bios on my k8n Neo4 Platinum pcb v 1.0, the write started giving errors, output follows... flashrom v0.9.2-r1141 on Linux 2.6.32-5-686 (i686), built with libpci 3.1.7, GCC 4.4.5 20100728 (prerelease), little endian flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. No coreboot table found. Found chipset "NVIDIA CK804", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Disabling flash write protection for board "MSI K8N Neo4-F"... OK. Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000. Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... Erasing flash chip... SUCCESS. Programming page: address: 0x00040000 writing sector at 0xb744d000 failed! writing sector at 0xb744d400 failed! writing sector at 0xb744d800 failed! writing sector at 0xb744dc00 failed! address: 0x00041000 writing sector at 0xb744e000 failed! writing sector at 0xb744e400 failed! writing sector at 0xb744e800 failed! writing sector at 0xb744ec00 failed! address: 0x00042000 writing sector at 0xb744f000 failed! writing sector at 0xb744f400 failed! writing sector at 0xb744f800 failed! writing sector at 0xb744fc00 failed! address: 0x00043000 writing sector at 0xb7450000 failed! writing sector at 0xb7450400 failed! writing sector at 0xb7450800 failed! writing sector at 0xb7450c00 failed! address: 0x00044000 writing sector at 0xb7451000 failed! writing sector at 0xb7451400 failed! writing sector at 0xb7451800 failed! writing sector at 0xb7451c00 failed! address: 0x00045000 writing sector at 0xb7452000 failed! writing sector at 0xb7452400 failed! writing sector at 0xb7452800 failed! writing sector at 0xb7452c00 failed! address: 0x00046000 writing sector at 0xb7453000 failed! writing sector at 0xb7453400 failed! writing sector at 0xb7453800 failed! writing sector at 0xb7453c00 failed! address: 0x00047000 writing sector at 0xb7454000 failed! writing sector at 0xb7454400 failed! writing sector at 0xb7454800 failed! writing sector at 0xb7454c00 failed! address: 0x00048000 writing sector at 0xb7455000 failed! writing sector at 0xb7455400 failed! writing sector at 0xb7455800 failed! writing sector at 0xb7455c00 failed! address: 0x00049000 writing sector at 0xb7456000 failed! writing sector at 0xb7456400 failed! writing sector at 0xb7456800 failed! writing sector at 0xb7456c00 failed! address: 0x0004a000 writing sector at 0xb7457000 failed! writing sector at 0xb7457400 failed! writing sector at 0xb7457800 failed! writing sector at 0xb7457c00 failed! address: 0x0004b000 writing sector at 0xb7458000 failed! writing sector at 0xb7458400 failed! writing sector at 0xb7458800 failed! writing sector at 0xb7458c00 failed! address: 0x0004c000 writing sector at 0xb7459000 failed! writing sector at 0xb7459400 failed! writing sector at 0xb7459800 failed! writing sector at 0xb7459c00 failed! address: 0x0004d000 writing sector at 0xb745a000 failed! writing sector at 0xb745a400 failed! writing sector at 0xb745a800 failed! writing sector at 0xb745ac00 failed! address: 0x0004e000 writing sector at 0xb745b000 failed! writing sector at 0xb745b400 failed! writing sector at 0xb745b800 failed! writing sector at 0xb745bc00 failed! address: 0x0004f000 writing sector at 0xb745c000 failed! writing sector at 0xb745c400 failed! writing sector at 0xb745c800 failed! writing sector at 0xb745cc00 failed! address: 0x00050000 writing sector at 0xb745d000 failed! writing sector at 0xb745d400 failed! writing sector at 0xb745d800 failed! writing sector at 0xb745dc00 failed! address: 0x00051000 writing sector at 0xb745e000 failed! writing sector at 0xb745e400 failed! writing sector at 0xb745e800 failed! writing sector at 0xb745ec00 failed! address: 0x00052000 writing sector at 0xb745f000 failed! writing sector at 0xb745f400 failed! writing sector at 0xb745f800 failed! writing sector at 0xb745fc00 failed! address: 0x00053000 writing sector at 0xb7460000 failed! writing sector at 0xb7460400 failed! writing sector at 0xb7460800 failed! writing sector at 0xb7460c00 failed! address: 0x00054000 writing sector at 0xb7461000 failed! writing sector at 0xb7461400 failed! writing sector at 0xb7461800 failed! writing sector at 0xb7461c00 failed! address: 0x00055000 writing sector at 0xb7462000 failed! writing sector at 0xb7462400 failed! writing sector at 0xb7462800 failed! writing sector at 0xb7462c00 failed! address: 0x00056000 writing sector at 0xb7463000 failed! writing sector at 0xb7463400 failed! writing sector at 0xb7463800 failed! writing sector at 0xb7463c00 failed! address: 0x00057000 writing sector at 0xb7464000 failed! writing sector at 0xb7464400 failed! writing sector at 0xb7464800 failed! writing sector at 0xb7464c00 failed! address: 0x00058000 writing sector at 0xb7465000 failed! writing sector at 0xb7465400 failed! writing sector at 0xb7465800 failed! writing sector at 0xb7465c00 failed! address: 0x00059000 writing sector at 0xb7466000 failed! writing sector at 0xb7466400 failed! writing sector at 0xb7466800 failed! writing sector at 0xb7466c00 failed! address: 0x0005a000 writing sector at 0xb7467000 failed! writing sector at 0xb7467400 failed! writing sector at 0xb7467800 failed! writing sector at 0xb7467c00 failed! address: 0x0005b000 writing sector at 0xb7468000 failed! writing sector at 0xb7468400 failed! writing sector at 0xb7468800 failed! writing sector at 0xb7468c00 failed! address: 0x0005c000 writing sector at 0xb7469000 failed! writing sector at 0xb7469400 failed! writing sector at 0xb7469800 failed! writing sector at 0xb7469c00 failed! address: 0x0005d000 writing sector at 0xb746a000 failed! writing sector at 0xb746a400 failed! writing sector at 0xb746a800 failed! writing sector at 0xb746ac00 failed! address: 0x0005e000 writing sector at 0xb746b000 failed! writing sector at 0xb746b400 failed! writing sector at 0xb746b800 failed! writing sector at 0xb746bc00 failed! address: 0x0005f000 writing sector at 0xb746c000 failed! writing sector at 0xb746c400 failed! writing sector at 0xb746c800 failed! writing sector at 0xb746cc00 failed! DONE!ss: 0x0007f000 COMPLETE. Verifying flash... VERIFY FAILED at 0x00005555! Expected=0xff, Read=0xaa, failed byte count from 0x00000000-0x0007ffff: 0x1fd7c Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org! ------------------------------------------------------------------------------- DO NOT REBOOT OR POWEROFF! Thanx for any guidance! Best regards! ---------------------------------------------------------------------------------- Leonardo Pedretti Código Dínamo +54 11 50935333 / +54 11 15 35745251 http://www.codigodinamo.com

1 0

Sorry for two identical mail from Jinyi Yan
by Allen Yan 17 Mar '14

17 Mar '14

Hi, I'm sorry for that I send two identical mail with subject <[flashrom] GSoC-2014 Flashrom project "Locking and unlocking of access protections of flash chips"> using two different mailbox. >From now on, I would only use "lexkde(a)gmail.com" as the mailbox. Thanks! Jinyi Yan

1 0

[Patch] Add support for Atmel AT25DL161
by Allen Yan 17 Mar '14

17 Mar '14

This patch adds support for Atmel AT25DL161, 2Mbytes SPI flash which look like the low voltage version of Atmel AT25DQ161. It has no pre test for now. Index: flashchips.c =================================================================== --- flashchips.c (Revision 1766) +++ flashchips.c (Arbeitskopie) @@ -1671,77 +1671,114 @@ { .vendor = "Atmel", .name = "AT25DF641(A)", .bustype = BUS_SPI, .manufacture_id = ATMEL_ID, .model_id = ATMEL_AT25DF641, .total_size = 8192, .page_size = 256, .feature_bits = FEATURE_WRSR_WREN, .tested = TEST_OK_PREW, .probe = probe_spi_rdid, .probe_timing = TIMING_ZERO, .block_erasers = { { .eraseblocks = { {4 * 1024, 2048} }, .block_erase = spi_block_erase_20, }, { .eraseblocks = { {32 * 1024, 256} }, .block_erase = spi_block_erase_52, }, { .eraseblocks = { {64 * 1024, 128} }, .block_erase = spi_block_erase_d8, }, { .eraseblocks = { {8 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_60, }, { .eraseblocks = { {8 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_c7, } }, .printlock = spi_prettyprint_status_register_at25df_sec, .unlock = spi_disable_blockprotect_at2x_global_unprotect_sec, .write = spi_chip_write_256, .read = spi_chip_read, .voltage = {2700, 3600}, }, - + { + .vendor = "Atmel", + .name = "AT25DL161", + .bustype = BUS_SPI, + .manufacture_id = ATMEL_ID, + .model_id = ATMEL_AT25DL161, + .total_size = 2048, + .page_size = 256, + /* OTP: 128B total, 64B pre-programmed; read 0x77; write 0x9B */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, + .tested = TEST_UNTESTED, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 512} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 64} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 32} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {2 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_at25df_sec, + .unlock = spi_disable_blockprotect_at2x_global_unprotect_sec, + .write = spi_chip_write_256, + .read = spi_chip_read, + .voltage = {1650, 1950}, + }, { .vendor = "Atmel", .name = "AT25DQ161", .bustype = BUS_SPI, .manufacture_id = ATMEL_ID, .model_id = ATMEL_AT25DQ161, .total_size = 2048, .page_size = 256, /* OTP: 128B total, 64B pre-programmed; read 0x77; write 0x9B */ .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP, .tested = TEST_UNTESTED, .probe = probe_spi_rdid, .probe_timing = TIMING_ZERO, .block_erasers = { { .eraseblocks = { {4 * 1024, 512} }, .block_erase = spi_block_erase_20, }, { .eraseblocks = { {32 * 1024, 64} }, .block_erase = spi_block_erase_52, }, { .eraseblocks = { {64 * 1024, 32} }, .block_erase = spi_block_erase_d8, }, { .eraseblocks = { {2 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_60, }, { .eraseblocks = { {2 * 1024 * 1024, 1} }, .block_erase = spi_block_erase_c7, } }, .printlock = spi_prettyprint_status_register_at25df_sec, .unlock = spi_disable_blockprotect_at2x_global_unprotect_sec, .write = spi_chip_write_256, .read = spi_chip_read, .voltage = {2700, 3600}, },

1 0

GSoC-2014 Flashrom project "Locking and unlocking of access protections of flash chips"
by yanjinyi＠mail.sim.ac.cn 17 Mar '14

17 Mar '14

Hi, I am Jinyi Yan , a second year PhD candidate from Shanghai Institute of Micro-system and Information Technology, Chinese Academy of Sciences. I used to be a mainboard BIOS engineer in ASUS Technology Suzhou Co., Ltd for about two years (2007.7~2009.2). My major now is optoelectronics. But I have a lot of fun while programming, in my heart the working experience of being a BIOS engineer is still very exciting. I think GsoC is a nice platform for me to participate the open source community. When I search the GsoC projects and organizations, the coreboot and flashrom projects are definitely the right choices for me. I have a spare ASUS P5KPL PC at my hand, but the chipset is not in the support list of coreboot project. So I consider the flashrom project is the better choice. I also have a home-made flash programmer based on uspasp. I'd like to choose “Locking and unlocking of access protections of flash chips” for GSoC 2014. Now I'm not very familiar with the program structure of flashrom, so I expect your guidence and hope to contribute for flashrom and coreboot even if my application is not accpeted. Thanks! Look forward to your kind advice! Regards, Jinyi Yan

1 0

Z87 flash not supported flashrom 0.9.6.1+r1563-1
by Rob Whyte 16 Mar '14

16 Mar '14

Hi, as the topic reflects flashrom 0.9.6.1+r1563-1 was unable to flash my Gigabyte Z87m-d3h. Much thanks goes to Carldani on IRC for helping me get my board back to a bootable state. It would be great if the upcoming LTS of Ubuntu, Trusty 14.04 can be upgraded since these boards are common and should be supported out of the box. A great IRC community and my thanks go out to you all for the work that goes in to maintaining and updating Flashrom. For me, being blind and using text to speech I use this tool, I also recommend Flashrom to vinuxproject.org users that are also blind and want an accessible method to flash their chips. Thank you Kind regards Rob Whyte http://www.launchpad.net/~fudge

1 0

ASUS A7V8X-MX board support
by François Revol 14 Mar '14

14 Mar '14

(note I'm not subscribed to the list) This patch adds support for the ASUS A7V8X-MX motherboard. Before, despite being mentionned as supported on http://flashrom.org/Supported_hardware , flashrom failed to detect the flash chip: http://paste.flashrom.org/view.php?id=2041 After, the flash chip is detected: http://paste.flashrom.org/view.php?id=2044 It seems the trick is the same as for the MX-SE variant, which is already in. I didn't try flashing as the only other chip I have doesn't seem to be detected, probably because of incompatible pinout due to it being LPC/FWH instead of parallel. François.

2 3

[PATCH] Add support for 82574L to nicintel_spi.c
by Bill Paul 14 Mar '14

14 Mar '14

I recently found a need to re-flash the option ROM on an Intel 82574L gigabit ethernet card. These are a bit more common these days than the 82571 and 82572 and relatively cheap. It turns out this works with flashrom, but it doesn't detect the PCI ID for the device out of the box. Below is a patch add it to nicintel_spi.c. Note that there are probably other devices in the PRO/1000 family that would work too. Here's an example run with the latest code from svn: [...] flashrom v0.9.7-unknown on FreeBSD 10.0-RELEASE (amd64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. Found Winbond flash chip "W25X40" (512 kB, SPI) on nicintel_spi. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. [...] FreeBSD detects the device as follows: em1@pci0:2:0:0: class=0x020000 card=0xa01f8086 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet I also added links to the Intel PCIe ethernet controllers programming manual and the 82574 datasheet. Incidentally, thanks to everyone involved for their work in this project. It helped me out of a bit of a jam. -Bill Signed-off-by: Bill Paul <wpaul(a)windriver.com> Index: nicintel_spi.c =================================================================== --- nicintel_spi.c (revision 1765) +++ nicintel_spi.c (working copy) @@ -17,14 +17,20 @@ * along with this program; if not, write to the Free Software * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA */ /* - * Datasheet: + * Datasheets: * PCI/PCI-X Family of Gigabit Ethernet Controllers Software Developer's Manual * 82540EP/EM, 82541xx, 82544GC/EI, 82545GM/EM, 82546GB/EB, and 82547xx * http://download.intel.com/design/network/manuals/8254x_GBe_SDM.pdf + * + * PCIe GbE Controllers Open Source Software Developer's Manual + * http://www.intel.com/content/www/us/en/ethernet-controllers/pcie-gbe- controllers-open-source-manual.html + * + * Intel 82574 Gigabit Ethernet Controller Family Datasheet + * http://www.intel.com/content/www/us/en/ethernet-controllers/82574l-gbe- controller-datasheet.html */ #include <stdlib.h> #include <unistd.h> #include "flash.h" @@ -70,10 +76,11 @@ const struct dev_entry nics_intel_spi[] = { {PCI_VENDOR_ID_INTEL, 0x105e, OK, "Intel", "82571EB Gigabit Ethernet Controller"}, {PCI_VENDOR_ID_INTEL, 0x1076, OK, "Intel", "82541GI Gigabit Ethernet Controller"}, {PCI_VENDOR_ID_INTEL, 0x107c, OK, "Intel", "82541PI Gigabit Ethernet Controller"}, {PCI_VENDOR_ID_INTEL, 0x10b9, OK, "Intel", "82572EI Gigabit Ethernet Controller"}, + {PCI_VENDOR_ID_INTEL, 0x10d3, OK, "Intel", "82574L Gigabit Ethernet Controller"}, {0}, }; static void nicintel_request_spibus(void) -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Member of Technical Staff, wpaul(a)windriver.com | Master of Unix-Fu - Wind River Systems ============================================================================= "I put a dollar in a change machine. Nothing changed." - George Carlin =============================================================================

2 1

[commit] r1766 - trunk
by repository service 14 Mar '14

14 Mar '14

Author: stefanct Date: Fri Mar 14 09:10:02 2014 New Revision: 1766 URL: http://flashrom.org/trac/flashrom/changeset/1766 Log: Add board enable for ASUS A7V8X-MX. Use the same trick as for the MX-SE variant. Despite being mentioned as supported on http://flashrom.org/Supported_hardware flashrom fails to detect the flash chip without this. Signed-off-by: François Revol <revol(a)free.fr> Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Modified: trunk/board_enable.c Modified: trunk/board_enable.c ============================================================================== --- trunk/board_enable.c Wed Mar 5 01:16:16 2014 (r1765) +++ trunk/board_enable.c Fri Mar 14 09:10:02 2014 (r1766) @@ -2333,6 +2333,7 @@ {0x8086, 0x2570, 0x1849, 0x2570, 0x8086, 0x24d3, 0x1849, 0x24d0, NULL, NULL, NULL, P3, "ASRock", "775i65G", 0, OK, intel_ich_gpio23_raise}, {0x10DE, 0x0060, 0x1043, 0x80AD, 0x10DE, 0x01E0, 0x1043, 0x80C0, NULL, NULL, NULL, P3, "ASUS", "A7N8X-VM/400", 0, OK, it8712f_gpio12_raise}, {0x1106, 0x3189, 0x1043, 0x807F, 0x1106, 0x3065, 0x1043, 0x80ED, NULL, NULL, NULL, P3, "ASUS", "A7V600-X", 0, OK, it8712f_gpio31_raise}, + {0x1106, 0x3177, 0x1043, 0x80F9, 0x1106, 0x3205, 0x1043, 0x80F9, NULL, NULL, NULL, P3, "ASUS", "A7V8X-MX", 0, OK, w836xx_memw_enable_2e}, {0x1106, 0x3177, 0x1043, 0x80A1, 0x1106, 0x3205, 0x1043, 0x8118, NULL, NULL, NULL, P3, "ASUS", "A7V8X-MX SE", 0, OK, w836xx_memw_enable_2e}, {0x1106, 0x3189, 0x1043, 0x807F, 0x1106, 0x3177, 0x1043, 0x808C, NULL, NULL, NULL, P3, "ASUS", "A7V8X", 0, OK, it8703f_gpio51_raise}, {0x1106, 0x3099, 0x1043, 0x807F, 0x1106, 0x3147, 0x1043, 0x808C, NULL, NULL, NULL, P3, "ASUS", "A7V333", 0, OK, it8703f_gpio51_raise},

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom March 2014