flashrom December 2017

flashrom@flashrom.org

21 participants
31 discussions

FAILED: ASUS P8H77-M PRO
by Lyubomyr Lytvynskyy 13 Dec '17

13 Dec '17

Hello. Today I try to flash BIOS on my motherboard to support NVMe devices and get terrible message in log "DO NOT REBOOT OR POWEROFF!" After reading BIOS again I saw that flash contents is not changed. Is it safe to reboot my PC now? Can you suggest how can I flash my BIOS? You can see read and write logs in attachment. Best regards, Lyubomyr

1 0

Re: [flashrom] Varification trouble - flashrom v0.9.9-r1954, Intel I210 NIC over SPI, Microchip SST25VF040B
by Lamont Dean 12 Dec '17

12 Dec '17

Okay, I'm seeing it better now and it isn't removing the block protection. On Tue, Dec 12, 2017 at 10:23 AM, Lamont Dean <lamont.dean(a)imsar.com> wrote: > Hello, > > Flashrom can find the Intel I210 NIC SPI connected to the SST25VF040B > flash chip and seems to program but fails to verify and gave me this email > to write to about it. The output is included below. Before and after a > power cycle the Intel I210 still says its in its unprogrammed state. > > I'd like to program a Microchip SST26VF016B flash in place of the > ...25VF040... but its not on the list so I'm going through the comments I > found on the wedsite Design Guide > <https://www.flashrom.org/Development_Guidelines>. I'm new to Linux and > things so we'll see how it goes. > > Any help you can offer would be greatly appreciated. > > Thanks, > > LaMont Dean > Hardware Engineer > ImSAR, LLC. > > ...flashrom> sudo flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c > SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin > flashrom v0.9.9-r1954 on Linux 4.4.38-tegra (aarch64) > flashrom is free software, get the source code at https://flashrom.org > > flashrom was built with libpci 3.3.1, GCC 5.4.0 20160609, little endian > Command line (7 args): flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c > SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin > Calibrating delay loop... OS timer resolution is 1 usecs, 2531M loops per > second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1001 us, 10000 myus > = 10022 us, 4 myus = 4 us, OK. > Initializing nicintel_spi programmer > Found "Intel Unprogrammed i210 Gigabit Ethernet Controller" (8086:1531, > BDF 01:00.0). > === > This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output > to flashrom(a)flashrom.org if it works for you. Please add the name of your > PCI device to the subject. Thank you for your help! > === > PCI header type 0x00 > Requested BAR is of type MEM, 32bit, not prefetchable > PCI header type 0x00 > Requested BAR is of type MEM, 32bit, not prefetchable > page_size=1000 > pre-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 > post-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 > The following protocols are supported: SPI. > Probing for SST SST25VF040B, 512 kB: programmer_map_flash_region: mapping > SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 > RDID returned 0xbf 0x25 0x8d. probe_spi_rdid_generic: id1 0xbf, id2 0x258d > Found SST flash chip "SST25VF040B" (512 kB, SPI) on nicintel_spi. > Chip status register is 0x1c. > Chip status register: Block Protect Write Disable (BPL) is not set > Chip status register: Auto Address Increment Programming (AAI) is not set > Chip status register: Block Protect 3 (BP3) is not set > Chip status register: Block Protect 2 (BP2) is set > Chip status register: Block Protect 1 (BP1) is set > Chip status register: Block Protect 0 (BP0) is set > Chip status register: Write Enable Latch (WEL) is not set > Chip status register: Write In Progress (WIP/BUSY) is not set > Resulting block protection : all blocks > programmer_unmap_flash_region: unmapped 0x0000000000000000 > programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 > to 0x0000000000000000 > Some block protection in effect, disabling... Block protection could not > be disabled! > Chip status register is 0x1c. > Chip status register: Block Protect Write Disable (BPL) is not set > Chip status register: Auto Address Increment Programming (AAI) is not set > Chip status register: Block Protect 3 (BP3) is not set > Chip status register: Block Protect 2 (BP2) is set > Chip status register: Block Protect 1 (BP1) is set > Chip status register: Block Protect 0 (BP0) is set > Chip status register: Write Enable Latch (WEL) is not set > Chip status register: Write In Progress (WIP/BUSY) is not set > Resulting block protection : all blocks > Reading old flash chip contents... done. > Erasing and writing flash chip... Trying erase function 0... > 0x000000-0x000fff:W, 0x001000-0x001fff:S, 0x002000-0x002fff:W, > 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, > 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, > 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, > 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, > 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, > 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, > 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:W, > 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, > 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, > 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W, 0x020000-0x020fff:W, > 0x021000-0x021fff:W, 0x022000-0x022fff:W, 0x023000-0x023fff:W, > 0x024000-0x024fff:W, 0x025000-0x025fff:W, 0x026000-0x026fff:W, > 0x027000-0x027fff:W, 0x028000-0x028fff:W, 0x029000-0x029fff:W, > 0x02a000-0x02afff:W, 0x02b000-0x02bfff:W, 0x02c000-0x02cfff:W, > 0x02d000-0x02dfff:W, 0x02e000-0x02efff:W, 0x02f000-0x02ffff:W, > 0x030000-0x030fff:W, 0x031000-0x031fff:W, 0x032000-0x032fff:W, > 0x033000-0x033fff:W, 0x034000-0x034fff:W, 0x035000-0x035fff:W, > 0x036000-0x036fff:W, 0x037000-0x037fff:W, 0x038000-0x038fff:S, > 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, > 0x03c000-0x03cfff:W, 0x03d000-0x03dfff:W, 0x03e000-0x03efff:W, > 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, > 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, > 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, > 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, > 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, > 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, > 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, > 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, > 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, > 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, > 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, > 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, > 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, > 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, > 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, > 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, > 0x06f000-0x06ffff:S, 0x070000-0x070fff:S, 0x071000-0x071fff:S, > 0x072000-0x072fff:S, 0x073000-0x073fff:S, 0x074000-0x074fff:S, > 0x075000-0x075fff:S, 0x076000-0x076fff:S, 0x077000-0x077fff:S, > 0x078000-0x078fff:S, 0x079000-0x079fff:S, 0x07a000-0x07afff:S, > 0x07b000-0x07bfff:S, 0x07c000-0x07cfff:S, 0x07d000-0x07dfff:S, > 0x07e000-0x07efff:S, 0x07f000-0x07ffff:S > Erase/write done. > Verifying flash... FAILED at 0x00000000! Expected=0x00, Found=0xff, failed > byte count from 0x00000000-0x0007ffff: 0x3527c > 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! > programmer_unmap_flash_region: unmapped 0x0000000000000000 > >

1 0

Varification trouble - flashrom v0.9.9-r1954, Intel I210 NIC over SPI, Microchip SST25VF040B
by Lamont Dean 12 Dec '17

12 Dec '17

Hello, Flashrom can find the Intel I210 NIC SPI connected to the SST25VF040B flash chip and seems to program but fails to verify and gave me this email to write to about it. The output is included below. Before and after a power cycle the Intel I210 still says its in its unprogrammed state. I'd like to program a Microchip SST26VF016B flash in place of the ...25VF040... but its not on the list so I'm going through the comments I found on the wedsite Design Guide <https://www.flashrom.org/Development_Guidelines>. I'm new to Linux and things so we'll see how it goes. Any help you can offer would be greatly appreciated. Thanks, LaMont Dean Hardware Engineer ImSAR, LLC. ...flashrom> sudo flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin flashrom v0.9.9-r1954 on Linux 4.4.38-tegra (aarch64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.3.1, GCC 5.4.0 20160609, little endian Command line (7 args): flashrom -VVVV -p nicintel_spi:pci=01:00.0 -c SST25VF040B -w Dev_Start_I210_Copper_NOMNG_4Mb_A2_3.25_0.03.bin Calibrating delay loop... OS timer resolution is 1 usecs, 2531M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 1001 us, 10000 myus = 10022 us, 4 myus = 4 us, OK. Initializing nicintel_spi programmer Found "Intel Unprogrammed i210 Gigabit Ethernet Controller" (8086:1531, BDF 01:00.0). === This PCI device is UNTESTED. Please report the 'flashrom -p xxxx' output to flashrom(a)flashrom.org if it works for you. Please add the name of your PCI device to the subject. Thank you for your help! === PCI header type 0x00 Requested BAR is of type MEM, 32bit, not prefetchable PCI header type 0x00 Requested BAR is of type MEM, 32bit, not prefetchable page_size=1000 pre-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 post-rounding: start=0x0000000050800000, len=0x1000, end=0x0000000050801000 The following protocols are supported: SPI. Probing for SST SST25VF040B, 512 kB: programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 RDID returned 0xbf 0x25 0x8d. probe_spi_rdid_generic: id1 0xbf, id2 0x258d Found SST flash chip "SST25VF040B" (512 kB, SPI) on nicintel_spi. Chip status register is 0x1c. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Auto Address Increment Programming (AAI) is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Resulting block protection : all blocks programmer_unmap_flash_region: unmapped 0x0000000000000000 programmer_map_flash_region: mapping SST25VF040B from 0x00000000fff80000 to 0x0000000000000000 Some block protection in effect, disabling... Block protection could not be disabled! Chip status register is 0x1c. Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Auto Address Increment Programming (AAI) is not set Chip status register: Block Protect 3 (BP3) is not set Chip status register: Block Protect 2 (BP2) is set Chip status register: Block Protect 1 (BP1) is set Chip status register: Block Protect 0 (BP0) is set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Resulting block protection : all blocks Reading old flash chip contents... done. Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:S, 0x002000-0x002fff:W, 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:W, 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W, 0x020000-0x020fff:W, 0x021000-0x021fff:W, 0x022000-0x022fff:W, 0x023000-0x023fff:W, 0x024000-0x024fff:W, 0x025000-0x025fff:W, 0x026000-0x026fff:W, 0x027000-0x027fff:W, 0x028000-0x028fff:W, 0x029000-0x029fff:W, 0x02a000-0x02afff:W, 0x02b000-0x02bfff:W, 0x02c000-0x02cfff:W, 0x02d000-0x02dfff:W, 0x02e000-0x02efff:W, 0x02f000-0x02ffff:W, 0x030000-0x030fff:W, 0x031000-0x031fff:W, 0x032000-0x032fff:W, 0x033000-0x033fff:W, 0x034000-0x034fff:W, 0x035000-0x035fff:W, 0x036000-0x036fff:W, 0x037000-0x037fff:W, 0x038000-0x038fff:S, 0x039000-0x039fff:S, 0x03a000-0x03afff:S, 0x03b000-0x03bfff:S, 0x03c000-0x03cfff:W, 0x03d000-0x03dfff:W, 0x03e000-0x03efff:W, 0x03f000-0x03ffff:S, 0x040000-0x040fff:S, 0x041000-0x041fff:S, 0x042000-0x042fff:S, 0x043000-0x043fff:S, 0x044000-0x044fff:S, 0x045000-0x045fff:S, 0x046000-0x046fff:S, 0x047000-0x047fff:S, 0x048000-0x048fff:S, 0x049000-0x049fff:S, 0x04a000-0x04afff:S, 0x04b000-0x04bfff:S, 0x04c000-0x04cfff:S, 0x04d000-0x04dfff:S, 0x04e000-0x04efff:S, 0x04f000-0x04ffff:S, 0x050000-0x050fff:S, 0x051000-0x051fff:S, 0x052000-0x052fff:S, 0x053000-0x053fff:S, 0x054000-0x054fff:S, 0x055000-0x055fff:S, 0x056000-0x056fff:S, 0x057000-0x057fff:S, 0x058000-0x058fff:S, 0x059000-0x059fff:S, 0x05a000-0x05afff:S, 0x05b000-0x05bfff:S, 0x05c000-0x05cfff:S, 0x05d000-0x05dfff:S, 0x05e000-0x05efff:S, 0x05f000-0x05ffff:S, 0x060000-0x060fff:S, 0x061000-0x061fff:S, 0x062000-0x062fff:S, 0x063000-0x063fff:S, 0x064000-0x064fff:S, 0x065000-0x065fff:S, 0x066000-0x066fff:S, 0x067000-0x067fff:S, 0x068000-0x068fff:S, 0x069000-0x069fff:S, 0x06a000-0x06afff:S, 0x06b000-0x06bfff:S, 0x06c000-0x06cfff:S, 0x06d000-0x06dfff:S, 0x06e000-0x06efff:S, 0x06f000-0x06ffff:S, 0x070000-0x070fff:S, 0x071000-0x071fff:S, 0x072000-0x072fff:S, 0x073000-0x073fff:S, 0x074000-0x074fff:S, 0x075000-0x075fff:S, 0x076000-0x076fff:S, 0x077000-0x077fff:S, 0x078000-0x078fff:S, 0x079000-0x079fff:S, 0x07a000-0x07afff:S, 0x07b000-0x07bfff:S, 0x07c000-0x07cfff:S, 0x07d000-0x07dfff:S, 0x07e000-0x07efff:S, 0x07f000-0x07ffff:S Erase/write done. Verifying flash... FAILED at 0x00000000! Expected=0x00, Found=0xff, failed byte count from 0x00000000-0x0007ffff: 0x3527c 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! programmer_unmap_flash_region: unmapped 0x0000000000000000

1 0

Error Message - Your flash chip is in an unknown state.
by Kazer Soze 12 Dec '17

12 Dec '17

Good morning I have a "W25Q128.V" chip on my board and i made a backup off the old boot. I have try to inject the new one but no luck at all. I have this error message appear. "Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on linux_spi. Reading old flash chip contents... done. Erasing and writing flash chip... FAILED at 0x000af000! Expected=0xff, Found=0x00, failed byte count from 0x000af000-0x000affff: 0x500 ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Erase/write done. Verifying flash... FAILED at 0x00036bca! Expected=0x00, Found=0x04, failed byte count from 0x00000000-0x00ffffff: 0x1ea6 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!" Any chance that you could help me please?

1 0

W836xx: QNAP 253a: flashrom -V
by uno 10 Dec '17

10 Dec '17

./flashrom -V -p internal flashrom v0.9.8-unknown on Linux 4.2.8 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.1, GCC 4.8.2, little endian Command line (3 args): ./flashrom -V -p internal Calibrating delay loop... OS timer resolution is 1 usecs, 745M loops per second, 10 myus = 10 us, 100 myus = 109 us, 1000 myus = 1009 us, 10000 myus = 10020 us, 4 myus = 5 us, OK. Initializing internal programmer No coreboot table found. Using Internal DMI decoder. DMI string chassis-type: "Other" DMI chassis-type is not specific enough. DMI string system-manufacturer: "Default string" DMI string system-product-name: "Default string" DMI string system-version: "Default string" DMI string baseboard-manufacturer: "AMI Corporation" DMI string baseboard-product-name: "Aptio CRB" DMI string baseboard-version: "Default string" W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 85. Please send the output of "flashrom -V -p internal" to flashrom(a)flashrom.org with W836xx: your board name: flashrom -V as the subject to help us finish support for your Super I/O. Thanks. Found ITE EC, ID 0x8528, Rev 0x0a on port 0x2e. ======================================================================== WARNING! You may be running flashrom on an unsupported laptop. We could not detect this for sure because your vendor has not setup the SMBIOS tables correctly. You can enforce execution by adding '-p internal:laptop=this_is_not_a_laptop' to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Aborting. Error: Programmer initialization failed. [/share/Public] #

1 0

Re: [flashrom] chipset not found
by David Hendricks 10 Dec '17

10 Dec '17

On Wed, Dec 6, 2017 at 8:29 PM, David Velasco <david(a)bemusic.al> wrote: > Hi carl, > > I have the following error: > > # flashrom --programmer internal > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > WARNING: *No chipset found. Flash detection will most likely fail.* > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > # flashrom --programmer internal > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > WARNING: No chipset found. Flash detection will most likely fail. > No EEPROM/flash device found. > Note: flashrom can never write if the flash chip isn't found automatically. > # flashrom > flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Please select a programmer with the --programmer parameter. > Previously this was not necessary because there was a default set. > To choose the mainboard of this computer use 'internal'. Valid choices are: > internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, > it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, > nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, > ch341a_spi. > > > I can give you the result of > > lspci -nnvvvxxx > > Yes, please copy + paste lspci output to https://paste.flashrom.org/ .

1 0

chipset not found
by David Velasco 07 Dec '17

07 Dec '17

Hi carl, I have the following error: # flashrom --programmer internal flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. WARNING: *No chipset found. Flash detection will most likely fail.* No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. # flashrom --programmer internal flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Calibrating delay loop... OK. WARNING: No chipset found. Flash detection will most likely fail. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. # flashrom flashrom v0.9.9-rc1-r1942 on Linux 4.10.0-40-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org Please select a programmer with the --programmer parameter. Previously this was not necessary because there was a default set. To choose the mainboard of this computer use 'internal'. Valid choices are: internal, dummy, nic3com, nicrealtek, gfxnvidia, drkaiser, satasii, atavia, it8212, serprog, buspirate_spi, dediprog, rayer_spi, pony_spi, nicintel, nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_spi, pickit2_spi, ch341a_spi. I can give you the result of lspci -nnvvvxxx Thanks!

1 0

No EEPROM/flash device found
by JASON.HT.HUANG 黃宏宗 06 Dec '17

06 Dec '17

Hi, I try to write bios. However, I always got “No EEPROM/flash device found”. Could you give me some suggestions. Thanks Jason.Huang 黃宏宗 Delta Networks, INC. TEL：+886-2-8797-3250 ext.3050 E-Mail：Jason.ht.huang(a)delta.com.tw ************************************************************************* This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. [Delta Electronics, INC. Taiwan] *************************************************************************

1 0

Re: [flashrom] particular spi flash controller
by Andriy Gapon 01 Dec '17

01 Dec '17

On 01/12/2017 19:36, David Hendricks wrote: > > > On Fri, Dec 1, 2017 at 12:11 AM, Andriy Gapon <avg(a)freebsd.org > <mailto:avg@freebsd.org>> wrote: > > > Hello. > > I wonder if anyone here encountered an SPI flash controller (master) that has a > three register interface where the first register is used for control and status > bits, the second register is used for setting a flash address (if one is needed) > and the third is used for reading or writing the flash data. A specific > operation is requested by writing an SPI opcode into the control register. > The interface seems to be rather simple, but I couldn't find any driver that > implements access to anything like that or any documentation that would describe > a similar interface. > > Does it sound familiar to anyone? > Could anyone give me some hints / pointers? > > > Is this an interface that you've actually used before? It sounds too simplistic > since at the very least you'd also need to set the number of bytes to transfer, > the direction, and have some control over chip select. Likely, those things are set in the control register, but I don't know the exact meaning of the bits. Also, some status bits are checked in the same register to make sure that the operation is completed. I can make some guesses, but I'd rather find documentation if possible. Meanwhile, I also looked at Linux drivers and this one seems to be somewhat similar but still different: http://elixir.free-electrons.com/linux/latest/source/drivers/spi/spi-falcon… See SFCMD / SFADDR / SFDATA. -- Andriy Gapon

1 0

particular spi flash controller
by Andriy Gapon 01 Dec '17

01 Dec '17

Hello. I wonder if anyone here encountered an SPI flash controller (master) that has a three register interface where the first register is used for control and status bits, the second register is used for setting a flash address (if one is needed) and the third is used for reading or writing the flash data. A specific operation is requested by writing an SPI opcode into the control register. The interface seems to be rather simple, but I couldn't find any driver that implements access to anything like that or any documentation that would describe a similar interface. Does it sound familiar to anyone? Could anyone give me some hints / pointers? Thanks! -- Andriy Gapon

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom December 2017