Dear coreboot folks,
I tried flashrom on a Syntax SV266A board and it displays the following message.
No EEPROM/flash device found.
I am putting the flashrom -V output inline and am attaching the archive from the output of the system analyzer Carl-Daniel once posted.
If you need more information, please tell me.
Thanks,
Paul
Calibrating delay loop... 488M loops per second, 100 myus = 141 us. OK. No coreboot table found. Found chipset "VIA VT8235", enabling flash write... OK. Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0x25, id2 0xe4 Probing for AMD Am29F080B, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0x25, id2 0xe4 Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xff, id2 0xff Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Atmel AT25DF021, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF041A, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF081, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF161, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF321, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF321A, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF641, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25F512B, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25FS010, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25FS040, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF041, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF081A, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF161, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF161A, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26F004, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Atmel AT45CS1282, 16896 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB011D, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB021D, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB041D, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB081D, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB161D, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB321C, 4224 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB321D, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB642D, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for AMIC A25L40P, 512 KB: 4b ID not supported on this SPI controller Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0x25, id2 0xe4 Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x25, id2 0xe4 Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Macronix MX25L512, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L1005, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L2005, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L4005, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L8005, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L1605, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L3205, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L6405, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for Numonyx M25PE10, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE40, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE16, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV010, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV016B, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV020, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV040, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV080B, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV512, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff Probing for Spansion S25FL016A, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF016B, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF032B, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF040B, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF040.REMS, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF040B.REMS, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF080B, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x25, id2 0xe4 Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x25, id2 0xe4 Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF020, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P10-A, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P40, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P40-old, 512 KB: spi_command called, but no SPI chipset/strapping detected spi_command called, but no SPI chipset/strapping detected Probing for ST M25P80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P16, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P32, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P64, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P128, 16384 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0x25, id2 0xe4 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for ST M29W010B, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0x25, id2 0xe4 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0x25, id2 0xe4 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x25, id2 0xe4 Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x25, id2 0xe4 Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W25x10, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x40, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W29EE011, 128 KB: === Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. === Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0x25, id2 0xe4 Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0xff, did 0xff Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: vid 0x25, did 0xe4 Probing for Atmel unknown Atmel SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for EON unknown EON SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix unknown Macronix SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC unknown PMC SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST unknown SST SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST unknown ST SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected No EEPROM/flash device found. If you know which flash chip you have, and if this version of flashrom supports a similar flash chip, you can try to force read your chip. Run: flashrom -f -r -c similar_supported_flash_chip filename
Note: flashrom can never write when the flash chip isn't found automatically.
2009/3/18 Paul Menzel paulepanter@users.sourceforge.net:
probe_jedec: id1 0x25, id2 0xe4
flash.h suggests that the manufacturer might be ASD:
#define ASD_ID 0x25
I did a search and found that the flash chip should be 2Mb. Therefore I guess the flash chip is AE29F2008. Could you verify that?
From this[0] page, it seems that AE29F2008 and AT29C020 behave in
similar way. If you are trying to read the content, maybe you can try a force read.
Hope I am giving some useful information.
[0]http://www.geocities.com/mpu51/eprom/eprom.html
yu ning
Am Donnerstag, den 19.03.2009, 00:13 +0800 schrieb FENG Yu Ning:
2009/3/18 Paul Menzel paulepanter@users.sourceforge.net:
probe_jedec: id1 0x25, id2 0xe4
flash.h suggests that the manufacturer might be ASD:
#define ASD_ID 0x25
I did a search and found that the flash chip should be 2Mb. Therefore I guess the flash chip is AE29F2008. Could you verify that?
Right. Removing the sticker sure helps. Atmel AT49F002NT is written on the chip, which is supposed to be supported by Flashrom.
From this[0] page, it seems that AE29F2008 and AT29C020 behave in
similar way. If you are trying to read the content, maybe you can try a force read.
$ sudo flashrom -f -r -c "AT49F002(N)T" test.rom Calibrating delay loop... 490M loops per second, 100 myus = 174 us. OK. No coreboot table found. Found chipset "VIA VT8235", enabling flash write... OK. Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0x25, id2 0xe4 No EEPROM/flash device found. Force read (-f -r -c) requested, forcing chip probe success: Probing for Atmel AT49F002(N)T, 256 KB: Found chip "Atmel AT49F002(N)T" (256 KB) at physical address 0xfffc0000. Force reading flash... done.
test.rom also has not only null written to it, so it seems to be working.
What could be done, that the chip is auto-detected?
Hope I am giving some useful information.
Yes. Thanks a lot. I should have figured this out by myself.
Anything else I can do?
Thanks,
Paul
Paul Menzel wrote:
Right. Removing the sticker sure helps. Atmel AT49F002NT is written on the chip, which is supposed to be supported by Flashrom.
test.rom also has not only null written to it, so it seems to be working.
What could be done, that the chip is auto-detected?
Anything else I can do?
Since the reported IDs differ from those(id1 = 1Fh, id2 = 08h) in datasheet of AT49F002NT, I am not sure whether access to the flash is properly done. Let's do some investigation before going further.
You may want to take a closer look at test.rom. * How do the first few bytes look like? Do they look like magic numbers(0xff00, 0x55aa, ..)? * What are the instructions located at (top - 0x10)? Is it a cache disable instruction followed by a jump? * Try `strings' of binutils. See if you can find board information and strings appearing in the BIOS setup screen, etc..
If yes, then we have a special AT49F002NT. Adding auto-detecting for the chip should be trival. Otherwise, we will have to head towards the other direction, to see what we can do with the super IO chip.
Maybe there are other things to be taken into account, but I can only think of the aboves with my limited knowledge.
yu ning
Am Sonntag, den 22.03.2009, 01:28 +0800 schrieb FENG Yu Ning:
Paul Menzel wrote:
Right. Removing the sticker sure helps. Atmel AT49F002NT is written on the chip, which is supposed to be supported by Flashrom.
test.rom also has not only null written to it, so it seems to be working.
What could be done, that the chip is auto-detected?
Anything else I can do?
Since the reported IDs differ from those(id1 = 1Fh, id2 = 08h) in datasheet of AT49F002NT, I am not sure whether access to the flash is properly done. Let's do some investigation before going further.
You may want to take a closer look at test.rom.
- How do the first few bytes look like? Do they look like magic
numbers(0xff00, 0x55aa, ..)?
What is the correct command for doing this. hexdump first lines look like
0000000 e425 6c2d 3568 6f2d 0129 0000 0200 0000 0000010 0000 2050 0c01 3632 6136 3333 3632 422e
- What are the instructions located at (top - 0x10)? Is it a cache
disable instruction followed by a jump?
Sorry, could you give me a link (article, lecture notes?) for this, so I can read this up.
- Try `strings' of binutils. See if you can find board information and
strings appearing in the BIOS setup screen, etc..
Strings shows something useful.
-lh5-o) 266a3326.BIN […] 7Phoenix Technologies, LTD 6.00 PG 03/26/2003 VIA Technologies, Inc. VT8367-8235 VT8367-8235 Socket A AMD Athlon(tm) XP Internal Cache External Cache PRIMARY IDE SECONDARY IDE COM1 COM2 LPT1 Keyboard PS/2 Mouse USB0 […]
If yes, then we have a special AT49F002NT. Adding auto-detecting for the chip should be trival. Otherwise, we will have to head towards the other direction, to see what we can do with the super IO chip.
Well it looks like we are lucky and it is the first alternative.
Maybe there are other things to be taken into account, but I can only think of the aboves with my limited knowledge.
Thank you for your answer and great instructions!!!
Please tell what else I can do.
Thanks,
Paul
On 21.03.2009 18:57, Paul Menzel wrote:
Am Sonntag, den 22.03.2009, 01:28 +0800 schrieb FENG Yu Ning:
Paul Menzel wrote:
Right. Removing the sticker sure helps. Atmel AT49F002NT is written on the chip, which is supposed to be supported by Flashrom.
test.rom also has not only null written to it, so it seems to be working.
What could be done, that the chip is auto-detected?
Anything else I can do?
Since the reported IDs differ from those(id1 = 1Fh, id2 = 08h) in datasheet of AT49F002NT, I am not sure whether access to the flash is properly done. Let's do some investigation before going further.
You may want to take a closer look at test.rom.
- How do the first few bytes look like? Do they look like magic
numbers(0xff00, 0x55aa, ..)?
What is the correct command for doing this. hexdump first lines look like
0000000 e425 6c2d 3568 6f2d 0129 0000 0200 0000
OK, the ID cycle is not working. Basically, if the first two bytes of a dump are identical to id1,id2 then id1,id2 are not responses to the ID command. Try shorter (down to 10 us) or longer (up to 40 ms) delays in probe_jedec.
By the way, using "xxd" or "hexdump -C" makes sure the bytes in the output are not switched around pairwise.
Regards, Carl-Daniel
Am Samstag, den 21.03.2009, 19:23 +0100 schrieb Carl-Daniel Hailfinger:
On 21.03.2009 18:57, Paul Menzel wrote:
Am Sonntag, den 22.03.2009, 01:28 +0800 schrieb FENG Yu Ning:
Paul Menzel wrote:
Right. Removing the sticker sure helps. Atmel AT49F002NT is written on the chip, which is supposed to be supported by Flashrom.
test.rom also has not only null written to it, so it seems to be working.
What could be done, that the chip is auto-detected?
Anything else I can do?
Since the reported IDs differ from those(id1 = 1Fh, id2 = 08h) in datasheet of AT49F002NT, I am not sure whether access to the flash is properly done. Let's do some investigation before going further.
You may want to take a closer look at test.rom.
- How do the first few bytes look like? Do they look like magic
numbers(0xff00, 0x55aa, ..)?
What is the correct command for doing this. hexdump first lines look like
0000000 e425 6c2d 3568 6f2d 0129 0000 0200 0000
OK, the ID cycle is not working. Basically, if the first two bytes of a dump are identical to id1,id2 then id1,id2 are not responses to the ID command. Try shorter (down to 10 us) or longer (up to 40 ms) delays in probe_jedec.
I did change the following myusec_delay() in probe_jedec() in jedec.c
/* Older chips may need up to 100 us to respond. The ATMEL 29C020 * needs 10 ms according to the data sheet. */ myusec_delay(10000);
I tried 10, 100, 1000, 10000 and 40000 (all us) and all produced identical images (checked with diff).
Can this happen? Or did I do something incorrectly?
By the way, using "xxd" or "hexdump -C" makes sure the bytes in the output are not switched around pairwise.
Thanks for the tip.
Bests,
Paul
On 21.03.2009 22:59, Paul Menzel wrote:
Am Samstag, den 21.03.2009, 19:23 +0100 schrieb Carl-Daniel Hailfinger:
OK, the ID cycle is not working. Basically, if the first two bytes of a dump are identical to id1,id2 then id1,id2 are not responses to the ID command. Try shorter (down to 10 us) or longer (up to 40 ms) delays in probe_jedec.
I did change the following myusec_delay() in probe_jedec() in jedec.c
/* Older chips may need up to 100 us to respond. The ATMEL 29C020 * needs 10 ms according to the data sheet. */ myusec_delay(10000);
I tried 10, 100, 1000, 10000 and 40000 (all us) and all produced identical images (checked with diff).
Can this happen? Or did I do something incorrectly?
The delay should not influence the dump, but the id1, id2 responses. If id1,id2 were the same for all delays, that means the delay is irrelevant to the problem. Either the writes are not passed through or they are mangled by cache effects. It would be interesting to know the MTRR settings (/proc/mtrr) of that machine. An area can be covered by multiple MTRRs. As long as at least one MTRR covering the area is "uncachable", everything is OK. If no MTRR is covering the area, you have to find out MTRRdefType (no idea how to do this without a special program).
If you have time for it, extending flashrom to read MTRRs and calculate ROM cache settings would be great!
Regards, Carl-Daniel
Am Sonntag, den 22.03.2009, 01:43 +0100 schrieb Carl-Daniel Hailfinger:
On 21.03.2009 22:59, Paul Menzel wrote:
Am Samstag, den 21.03.2009, 19:23 +0100 schrieb Carl-Daniel Hailfinger:
OK, the ID cycle is not working. Basically, if the first two bytes of a dump are identical to id1,id2 then id1,id2 are not responses to the ID command. Try shorter (down to 10 us) or longer (up to 40 ms) delays in probe_jedec.
I did change the following myusec_delay() in probe_jedec() in jedec.c
/* Older chips may need up to 100 us to respond. The ATMEL 29C020 * needs 10 ms according to the data sheet. */ myusec_delay(10000);
I tried 10, 100, 1000, 10000 and 40000 (all us) and all produced identical images (checked with diff).
Can this happen? Or did I do something incorrectly?
The delay should not influence the dump, but the id1, id2 responses. If id1,id2 were the same for all delays, that means the delay is irrelevant to the problem. Either the writes are not passed through or they are mangled by cache effects. It would be interesting to know the MTRR settings (/proc/mtrr) of that machine.
$ cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1 reg02: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1 reg03: base=0xd8000000 (3456MB), size= 64MB: write-combining, count=1
An area can be covered by multiple MTRRs. As long as at least one MTRR covering the area is "uncachable", everything is OK. If no MTRR is covering the area, you have to find out MTRRdefType (no idea how to do this without a special program).
If you have time for it, extending flashrom to read MTRRs and calculate ROM cache settings would be great!
In addition to not much time, I also do not have any knowledge about this stuff. So this is not something to expected from me in the near future. Sorry.
Thanks for your help so far.
Paul
Paul Menzel wrote:
$ cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1 reg02: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1 reg03: base=0xd8000000 (3456MB), size= 64MB: write-combining, count=1
Carl-Daniel Hailfinger wrote:
An area can be covered by multiple MTRRs. As long as at least one MTRR covering the area is "uncachable", everything is OK.
If I understood correctly, Paul could do
echo "base=0x1ffc0000 size=0x40000 type=uncachable" >| /proc/mtrr
and then try flashrom again.
Am I right?
yu ning
FENG Yu Ning wrote:
An area can be covered by multiple MTRRs. As long as at least one MTRR covering the area is "uncachable", everything is OK.
If I understood correctly, Paul could do
echo "base=0x1ffc0000 size=0x40000 type=uncachable" >| /proc/mtrrand then try flashrom again.
Am I right?
Flash is at top of 4GB so I think it should be
echo "base=0xfffc0000 size=0x40000 type=uncachable" >| /proc/mtrr
//Peter
Peter Stuge wrote:
Flash is at top of 4GB so I think it should be
echo "base=0xfffc0000 size=0x40000 type=uncachable" >| /proc/mtrr
I made a stupid mistake.
Thanks, Peter.
yu ning
Dear Yu Ning, Carl-Daniel and Peter,
thanks for your ongoing help.
Am Sonntag, den 22.03.2009, 18:27 +0100 schrieb Peter Stuge:
FENG Yu Ning wrote:
An area can be covered by multiple MTRRs. As long as at least one MTRR covering the area is "uncachable", everything is OK.
If I understood correctly, Paul could do
echo "base=0x1ffc0000 size=0x40000 type=uncachable" >| /proc/mtrrand then try flashrom again.
Am I right?
Flash is at top of 4GB so I think it should be
echo "base=0xfffc0000 size=0x40000 type=uncachable" >| /proc/mtrr
# echo "base=0xfffc0000 size=0x40000 type=uncachable" >| /proc/mtrr $ cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1 reg02: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1 reg03: base=0xd8000000 (3456MB), size= 64MB: write-combining, count=1 reg04: base=0xfffc0000 (4095MB), size= 256KB: uncachable, count=1
I tried flashrom with the different delays (10, 100, 1000, 10000, 40000 all in us) afterwards, but the image did not differ.
Thanks,
Paul
2009/3/23 Paul Menzel paulepanter@users.sourceforge.net:
thanks for your ongoing help.
Glad that I did help you a bit.
I tried flashrom with the different delays (10, 100, 1000, 10000, 40000 all in us) afterwards, but the image did not differ.
How about probing? does auto-detect work now?
yu ning
Am Montag, den 23.03.2009, 02:29 +0800 schrieb FENG Yu Ning:
2009/3/23 Paul Menzel paulepanter@users.sourceforge.net:
[…]
I tried flashrom with the different delays (10, 100, 1000, 10000, 40000 all in us) afterwards, but the image did not differ.
How about probing? does auto-detect work now?
I am afraid it does not.
$ cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1 reg02: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1 reg03: base=0xd8000000 (3456MB), size= 64MB: write-combining, count=1 reg04: base=0xfffc0000 (4095MB), size= 256KB: uncachable, count=1 $ $ sudo ./flashrom -V Calibrating delay loop... 490M loops per second, 100 myus = 141 us. OK. No coreboot table found. Found chipset "VIA VT8235", enabling flash write... OK. Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0xff, id2 0xff Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0x25, id2 0xe4 Probing for AMD Am29F080B, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0x25, id2 0xe4 Probing for AMD Am29LV081B, 1024 KB: probe_29f040b: id1 0xff, id2 0xff Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Atmel AT25DF021, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF041A, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF081, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF161, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF321, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF321A, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25DF641, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25F512B, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25FS010, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT25FS040, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF041, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF081A, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF161, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26DF161A, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT26F004, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Atmel AT45CS1282, 16896 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB011D, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB021D, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB041D, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB081D, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB161D, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB321C, 4224 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB321D, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT45DB642D, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for AMIC A25L40P, 512 KB: 4b ID not supported on this SPI controller Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0x25, id2 0xe4 Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x25, id2 0xe4 Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for Macronix MX25L512, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L1005, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L2005, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L4005, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L8005, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L1605, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L3205, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX25L6405, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0x25, id2 0xe4 Probing for Numonyx M25PE10, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE40, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Numonyx M25PE16, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV010, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV016B, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV020, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV040, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV080B, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm25LV512, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0xff, id2 0xff Probing for Spansion S25FL016A, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF016B, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF032B, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF040B, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF040.REMS, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF040B.REMS, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST25VF080B, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x25, id2 0xe4 Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST39VF080, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x25, id2 0xe4 Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST SST49LF020, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M25P05-A, 64 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P10-A, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P40, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P40-old, 512 KB: spi_command called, but no SPI chipset/strapping detected spi_command called, but no SPI chipset/strapping detected Probing for ST M25P80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P16, 2048 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P32, 4096 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P64, 8192 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M25P128, 16384 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST M29F002B, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0x25, id2 0xe4 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x25, id2 0x2d Probing for ST M29W010B, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0x25, id2 0xe4 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0x25, id2 0xe4 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0xff, id2 0xff Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0x25, id2 0xe4 Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x25, id2 0xe4 Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0xff, id2 0xff Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W25x10, 128 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x20, 256 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x40, 512 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W25x80, 1024 KB: spi_command called, but no SPI chipset/strapping detected Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0xb7, id2 0x44, id1 parity violation Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W29EE011, 128 KB: === Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. === Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0x25, id2 0xe4 Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x25, id2 0xe4 Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0xff, did 0xff Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: vid 0x25, did 0xe4 Probing for Atmel unknown Atmel SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for EON unknown EON SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for Macronix unknown Macronix SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for PMC unknown PMC SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for SST unknown SST SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected Probing for ST unknown ST SPI chip, 0 KB: spi_command called, but no SPI chipset/strapping detected No EEPROM/flash device found. If you know which flash chip you have, and if this version of flashrom supports a similar flash chip, you can try to force read your chip. Run: flashrom -f -r -c similar_supported_flash_chip filename
Note: flashrom can never write when the flash chip isn't found automatically.
Thanks,
Paul
-
Carl-Daniel Hailfinger -
FENG Yu Ning -
Paul Menzel -
Peter Stuge