Well, I was just inspecting this beautiful little M61P-S3 board, and it has an SPI flash chip on it, in particular, the MX25L4005A. I don't seem to see anything that would indicate that anything but the IT8716F would be connecting to it.
I first tried using the version in Debian (testing): It didn't detect any flash chip.
I then tried using the SVN version: It too didn't detect anything.
Then I looked through, and found a reference to the M55. I looked the archives, and found a message from May07: I figured I would see if I could get lucky telling it to look like an M55.
I first got the connection to the IT8716F working, by telling it that the M61 is just like an M55, except with PCI device id 0x03e0. That seemed to work.
However, going from there, it doesn't seem to detect any SPI functionality at all.
It looks to me like support for each flash chip is needed (given that the spec sheet gives commands to output the manufacturer ID & device ID), but maybe that isn't true. In any case, the command set is relatively simple.
Is the SPI stuff properly supported? I feel like I'm a little out of my depth on this code...
Cheers,
Michael
On Sat, Sep 29, 2007 at 01:36:16PM +1000, Michael van der Kolff wrote:
Is the SPI stuff properly supported?
Not yet.
There is work being done, but it's brand new.
Stay around a while and see how the progress goes!
//Peter
Hi,
On 29.09.2007 05:36, Michael van der Kolff wrote:
Well, I was just inspecting this beautiful little M61P-S3 board, and it has an SPI flash chip on it, in particular, the MX25L4005A. I don't seem to see anything that would indicate that anything but the IT8716F would be connecting to it.
I first tried using the version in Debian (testing): It didn't detect any flash chip.
I then tried using the SVN version: It too didn't detect anything.
Please try current svn with my patch (Subject: [PATCH] improved SPI flash support (restructured), date: Sat, 29 Sep 2007 04:08:45) on top of it and use your patched board enable for the GA-M57SLI.
Then I looked through, and found a reference to the M55. I looked the
GA-M57SLI?
archives, and found a message from May07: I figured I would see if I could get lucky telling it to look like an M55.
I first got the connection to the IT8716F working, by telling it that the M61 is just like an M55, except with PCI device id 0x03e0. That seemed to work.
However, going from there, it doesn't seem to detect any SPI functionality at all.
Full log please.
It looks to me like support for each flash chip is needed (given that the spec sheet gives commands to output the manufacturer ID & device ID), but maybe that isn't true. In any case, the command set is relatively simple.
I know. But the command set for each chip differs slightly, so full support is difficult.
Is the SPI stuff properly supported? I feel like I'm a little out of my depth on this code...
I started last week to write support for SPI. It is in a really early stage and can only ID the chip (and with current svn, it will still say that no chip was found even if the ID could be read).
Please run current svn flashrom in verbose mode (-V) and use your patched board enable. If possible, repeat this with my patch applied on top.
Regards, Carl-Daniel
Hi, sorry for the late response, was on holidays.
I just used r2816 with linuxbios_flashrom_ite_spi_restructured3.diff, along with the attached patch (which just adds the different it8716 id used on the GA-M61P-S3 board) and got the following output from flashrom -V -m gigabyte:m61ps3
Calibrating delay loop... 793M loops per second. ok No LinuxBIOS table found. WARNING: No chipset found. Flash detection will most likely fail. Found board "GIGABYTE GA-M61P-S3": Enabling flash write... Serial flash segment 0xfffe0000-0xffffffff enabled Serial flash segment 0x000e0000-0x000fffff enabled Serial flash segment 0xffee0000-0xffefffff disabled Serial flash segment 0xfff80000-0xfffeffff enabled LPC write to serial flash enabled serial flash pin 29 OK. Probing for Am29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Probing for AE49F2008, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for At29C040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for At29C020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Mx29f002, 256 KB probe_29f002: id1 0xc6, id2 0x9b Probing for MX25L4005, 512 KB RDID returned c2 20 13 probe_spi: id1 0xc2, id2 0x2013 MX25L4005 found at physical address: 0xfff80000 Flash part is MX25L4005 (512 KB) OK, only ENABLING flash write, but NOT FLASHING.
and the following output without -m gigabyte:m61ps3 Calibrating delay loop... 794M loops per second. ok No LinuxBIOS table found. WARNING: No chipset found. Flash detection will most likely fail. Probing for Am29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Probing for AE49F2008, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for At29C040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for At29C020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Mx29f002, 256 KB probe_29f002: id1 0xc6, id2 0x9b Probing for MX25L4005, 512 KB Probing for SST29EE020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST28SF040A, 512 KB probe_28sf040: id1 0x49, id2 0x4d Probing for SST39SF010A, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for SST39SF020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST39SF040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST39VF020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for SST49LF002A/B, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF003A/B, 384 KB probe_jedec: id1 0x2e, id2 0x1f Probing for SST49LF004A/B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF008A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for SST49LF004C, 512 KB probe_49lfxxxc: id1 0x49, id2 0x4d Probing for SST49LF008C, 1024 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST49LF016C, 2048 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST49LF160C, 2048 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for Pm49FL002, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Pm49FL004, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W29C011, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for W29C040P, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W29C020C, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W29EE011, 128 KB probe_w29ee011: id1 0xff, id2 0xff Probing for W49F002U, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W49V002A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W49V002FA, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W39V040FA, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M29F002B, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for M50FW040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M29W040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M29F002T/NT, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for M29F400BT, 512 KB probe_m29f400bt: id1 0x49, id2 0x44 Probing for M50FLW040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M50FLW040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M50FLW080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FLW080B, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FW080, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FW016, 2048 KB probe_jedec: id1 0xff, id2 0xff Probing for M50LPW116, 2048 KB probe_jedec: id1 0xff, id2 0xff Probing for M29W010B, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for M29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for 82802ab, 512 KB probe_82802ab: id1 0x49, id2 0x4d Probing for 82802ac, 1024 KB probe_82802ab: id1 0xff, id2 0xff Probing for F49B002UA, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for LHF00L04, 1024 KB probe_lhf00l04: id1 0xff, id2 0xff Probing for S29C51001T, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for S29C51002T, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for S29C51004T, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for S29C31004T, 512 KB probe_jedec: id1 0x49, id2 0x4d No EEPROM/flash device found.
Cheers,
Michael On 9/29/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Hi,
On 29.09.2007 05:36, Michael van der Kolff wrote:
Well, I was just inspecting this beautiful little M61P-S3 board, and it has an SPI flash chip on it, in particular, the MX25L4005A. I don't seem to see anything that would indicate that anything but the IT8716F would be connecting to it.
I first tried using the version in Debian (testing): It didn't detect any flash chip.
I then tried using the SVN version: It too didn't detect anything.
Please try current svn with my patch (Subject: [PATCH] improved SPI flash support (restructured), date: Sat, 29 Sep 2007 04:08:45) on top of it and use your patched board enable for the GA-M57SLI.
Then I looked through, and found a reference to the M55. I looked the
GA-M57SLI?
archives, and found a message from May07: I figured I would see if I could get lucky telling it to look like an M55.
I first got the connection to the IT8716F working, by telling it that the M61 is just like an M55, except with PCI device id 0x03e0. That seemed to work.
However, going from there, it doesn't seem to detect any SPI functionality at all.
Full log please.
It looks to me like support for each flash chip is needed (given that the spec sheet gives commands to output the manufacturer ID & device ID), but maybe that isn't true. In any case, the command set is relatively simple.
I know. But the command set for each chip differs slightly, so full support is difficult.
Is the SPI stuff properly supported? I feel like I'm a little out of my depth on this code...
I started last week to write support for SPI. It is in a really early stage and can only ID the chip (and with current svn, it will still say that no chip was found even if the ID could be read).
Please run current svn flashrom in verbose mode (-V) and use your patched board enable. If possible, repeat this with my patch applied on top.
Regards, Carl-Daniel
Uhm, just forgot to attach the additional patch I applied. Here it comes :)
Cheers,
Michael
On 10/2/07, Michael van der Kolff mvanderkolff@gmail.com wrote:
Hi, sorry for the late response, was on holidays.
I just used r2816 with linuxbios_flashrom_ite_spi_restructured3.diff, along with the attached patch (which just adds the different it8716 id used on the GA-M61P-S3 board) and got the following output from flashrom -V -m gigabyte:m61ps3
Calibrating delay loop... 793M loops per second. ok No LinuxBIOS table found. WARNING: No chipset found. Flash detection will most likely fail. Found board "GIGABYTE GA-M61P-S3": Enabling flash write... Serial flash segment 0xfffe0000-0xffffffff enabled Serial flash segment 0x000e0000-0x000fffff enabled Serial flash segment 0xffee0000-0xffefffff disabled Serial flash segment 0xfff80000-0xfffeffff enabled LPC write to serial flash enabled serial flash pin 29 OK. Probing for Am29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Probing for AE49F2008, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for At29C040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for At29C020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Mx29f002, 256 KB probe_29f002: id1 0xc6, id2 0x9b Probing for MX25L4005, 512 KB RDID returned c2 20 13 probe_spi: id1 0xc2, id2 0x2013 MX25L4005 found at physical address: 0xfff80000 Flash part is MX25L4005 (512 KB) OK, only ENABLING flash write, but NOT FLASHING.
and the following output without -m gigabyte:m61ps3 Calibrating delay loop... 794M loops per second. ok No LinuxBIOS table found. WARNING: No chipset found. Flash detection will most likely fail. Probing for Am29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Probing for AE49F2008, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for At29C040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for At29C020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Mx29f002, 256 KB probe_29f002: id1 0xc6, id2 0x9b Probing for MX25L4005, 512 KB Probing for SST29EE020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST28SF040A, 512 KB probe_28sf040: id1 0x49, id2 0x4d Probing for SST39SF010A, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for SST39SF020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST39SF040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST39VF020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for SST49LF002A/B, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF003A/B, 384 KB probe_jedec: id1 0x2e, id2 0x1f Probing for SST49LF004A/B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF008A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for SST49LF004C, 512 KB probe_49lfxxxc: id1 0x49, id2 0x4d Probing for SST49LF008C, 1024 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST49LF016C, 2048 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST49LF160C, 2048 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for Pm49FL002, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Pm49FL004, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W29C011, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for W29C040P, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W29C020C, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W29EE011, 128 KB probe_w29ee011: id1 0xff, id2 0xff Probing for W49F002U, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W49V002A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W49V002FA, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W39V040FA, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M29F002B, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for M50FW040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M29W040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M29F002T/NT, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for M29F400BT, 512 KB probe_m29f400bt: id1 0x49, id2 0x44 Probing for M50FLW040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M50FLW040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M50FLW080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FLW080B, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FW080, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FW016, 2048 KB probe_jedec: id1 0xff, id2 0xff Probing for M50LPW116, 2048 KB probe_jedec: id1 0xff, id2 0xff Probing for M29W010B, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for M29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for 82802ab, 512 KB probe_82802ab: id1 0x49, id2 0x4d Probing for 82802ac, 1024 KB probe_82802ab: id1 0xff, id2 0xff Probing for F49B002UA, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for LHF00L04, 1024 KB probe_lhf00l04: id1 0xff, id2 0xff Probing for S29C51001T, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for S29C51002T, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for S29C51004T, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for S29C31004T, 512 KB probe_jedec: id1 0x49, id2 0x4d No EEPROM/flash device found.
Cheers,
Michael On 9/29/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Hi,
On 29.09.2007 05:36, Michael van der Kolff wrote:
Well, I was just inspecting this beautiful little M61P-S3 board, and it has an SPI flash chip on it, in particular, the MX25L4005A. I don't seem to see anything that would indicate that anything but the IT8716F would be connecting to it.
I first tried using the version in Debian (testing): It didn't detect any flash chip.
I then tried using the SVN version: It too didn't detect anything.
Please try current svn with my patch (Subject: [PATCH] improved SPI flash support (restructured), date: Sat, 29 Sep 2007 04:08:45) on top of it and use your patched board enable for the GA-M57SLI.
Then I looked through, and found a reference to the M55. I looked the
GA-M57SLI?
archives, and found a message from May07: I figured I would see if I could get lucky telling it to look like an M55.
I first got the connection to the IT8716F working, by telling it that the M61 is just like an M55, except with PCI device id 0x03e0. That seemed to work.
However, going from there, it doesn't seem to detect any SPI functionality at all.
Full log please.
It looks to me like support for each flash chip is needed (given that the spec sheet gives commands to output the manufacturer ID & device ID), but maybe that isn't true. In any case, the command set is relatively simple.
I know. But the command set for each chip differs slightly, so full support is difficult.
Is the SPI stuff properly supported? I feel like I'm a little out of my depth on this code...
I started last week to write support for SPI. It is in a really early stage and can only ID the chip (and with current svn, it will still say that no chip was found even if the ID could be read).
Please run current svn flashrom in verbose mode (-V) and use your patched board enable. If possible, repeat this with my patch applied on top.
Regards, Carl-Daniel
Hi Michael,
On 02.10.2007 02:21, Michael van der Kolff wrote:
Uhm, just forgot to attach the additional patch I applied. Here it comes :)
On 10/2/07, Michael van der Kolff mvanderkolff@gmail.com wrote:
I just used r2816 with linuxbios_flashrom_ite_spi_restructured3.diff, along with the attached patch (which just adds the different it8716 id used on the GA-M61P-S3 board) and got the following output from flashrom -V -m gigabyte:m61ps3
Calibrating delay loop... 793M loops per second. ok No LinuxBIOS table found. WARNING: No chipset found. Flash detection will most likely fail. Found board "GIGABYTE GA-M61P-S3": Enabling flash write... Serial flash segment 0xfffe0000-0xffffffff enabled Serial flash segment 0x000e0000-0x000fffff enabled Serial flash segment 0xffee0000-0xffefffff disabled Serial flash segment 0xfff80000-0xfffeffff enabled LPC write to serial flash enabled serial flash pin 29 OK. [...] Probing for MX25L4005, 512 KB RDID returned c2 20 13 probe_spi: id1 0xc2, id2 0x2013 MX25L4005 found at physical address: 0xfff80000 Flash part is MX25L4005 (512 KB) OK, only ENABLING flash write, but NOT FLASHING.
Can you resend the patch with a signed-off-by statement (http://linuxbios.org/Development_Guidelines#Sign-off_Procedure) and a changelog entry? My code is now in subversion, so you might want to rediff your patch and check whether everything still works.
You can then include the following Acked-by in your mail: Acked-by: Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Regards, Carl-Daniel
Signed-off-by: Michael van der Kolff mvanderkolff@gmail.com
On 10/2/07, Michael van der Kolff mvanderkolff@gmail.com wrote:
Uhm, just forgot to attach the additional patch I applied. Here it comes :)
Cheers,
Michael
On 10/2/07, Michael van der Kolff mvanderkolff@gmail.com wrote:
Hi, sorry for the late response, was on holidays.
I just used r2816 with linuxbios_flashrom_ite_spi_restructured3.diff, along with the attached patch (which just adds the different it8716 id used on the GA-M61P-S3 board) and got the following output from flashrom -V -m gigabyte:m61ps3
Calibrating delay loop... 793M loops per second. ok No LinuxBIOS table found. WARNING: No chipset found. Flash detection will most likely fail. Found board "GIGABYTE GA-M61P-S3": Enabling flash write... Serial flash segment 0xfffe0000-0xffffffff enabled Serial flash segment 0x000e0000-0x000fffff enabled Serial flash segment 0xffee0000-0xffefffff disabled Serial flash segment 0xfff80000-0xfffeffff enabled LPC write to serial flash enabled serial flash pin 29 OK. Probing for Am29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Probing for AE49F2008, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for At29C040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for At29C020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Mx29f002, 256 KB probe_29f002: id1 0xc6, id2 0x9b Probing for MX25L4005, 512 KB RDID returned c2 20 13 probe_spi: id1 0xc2, id2 0x2013 MX25L4005 found at physical address: 0xfff80000 Flash part is MX25L4005 (512 KB) OK, only ENABLING flash write, but NOT FLASHING.
and the following output without -m gigabyte:m61ps3 Calibrating delay loop... 794M loops per second. ok No LinuxBIOS table found. WARNING: No chipset found. Flash detection will most likely fail. Probing for Am29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for Am29F016D, 2048 KB probe_29f040b: id1 0xff, id2 0xff Probing for AE49F2008, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for At29C040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for At29C020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Mx29f002, 256 KB probe_29f002: id1 0xc6, id2 0x9b Probing for MX25L4005, 512 KB Probing for SST29EE020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST28SF040A, 512 KB probe_28sf040: id1 0x49, id2 0x4d Probing for SST39SF010A, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for SST39SF020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST39SF040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST39VF020, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF020A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for SST49LF002A/B, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for SST49LF003A/B, 384 KB probe_jedec: id1 0x2e, id2 0x1f Probing for SST49LF004A/B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for SST49LF008A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for SST49LF004C, 512 KB probe_49lfxxxc: id1 0x49, id2 0x4d Probing for SST49LF008C, 1024 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST49LF016C, 2048 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for SST49LF160C, 2048 KB probe_49lfxxxc: id1 0xff, id2 0xff Probing for Pm49FL002, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for Pm49FL004, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W29C011, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for W29C040P, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W29C020C, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W29EE011, 128 KB probe_w29ee011: id1 0xff, id2 0xff Probing for W49F002U, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W49V002A, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W49V002FA, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for W39V040FA, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for W39V080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M29F002B, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for M50FW040, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M29W040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M29F002T/NT, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for M29F400BT, 512 KB probe_m29f400bt: id1 0x49, id2 0x44 Probing for M50FLW040A, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M50FLW040B, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for M50FLW080A, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FLW080B, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FW080, 1024 KB probe_jedec: id1 0xff, id2 0xff Probing for M50FW016, 2048 KB probe_jedec: id1 0xff, id2 0xff Probing for M50LPW116, 2048 KB probe_jedec: id1 0xff, id2 0xff Probing for M29W010B, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for M29F040B, 512 KB probe_29f040b: id1 0x49, id2 0x4d Probing for 82802ab, 512 KB probe_82802ab: id1 0x49, id2 0x4d Probing for 82802ac, 1024 KB probe_82802ab: id1 0xff, id2 0xff Probing for F49B002UA, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for LHF00L04, 1024 KB probe_lhf00l04: id1 0xff, id2 0xff Probing for S29C51001T, 128 KB probe_jedec: id1 0xff, id2 0xff Probing for S29C51002T, 256 KB probe_jedec: id1 0xc6, id2 0x9b Probing for S29C51004T, 512 KB probe_jedec: id1 0x49, id2 0x4d Probing for S29C31004T, 512 KB probe_jedec: id1 0x49, id2 0x4d No EEPROM/flash device found.
Cheers,
Michael On 9/29/07, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Hi,
On 29.09.2007 05:36, Michael van der Kolff wrote:
Well, I was just inspecting this beautiful little M61P-S3 board, and it has an SPI flash chip on it, in particular, the MX25L4005A. I don't seem to see anything that would indicate that anything but the IT8716F would be connecting to it.
I first tried using the version in Debian (testing): It didn't detect any flash chip.
I then tried using the SVN version: It too didn't detect anything.
Please try current svn with my patch (Subject: [PATCH] improved SPI flash support (restructured), date: Sat, 29 Sep 2007 04:08:45) on top of it and use your patched board enable for the GA-M57SLI.
Then I looked through, and found a reference to the M55. I looked the
GA-M57SLI?
archives, and found a message from May07: I figured I would see if I could get lucky telling it to look like an M55.
I first got the connection to the IT8716F working, by telling it that the M61 is just like an M55, except with PCI device id 0x03e0. That seemed to work.
However, going from there, it doesn't seem to detect any SPI functionality at all.
Full log please.
It looks to me like support for each flash chip is needed (given that the spec sheet gives commands to output the manufacturer ID & device ID), but maybe that isn't true. In any case, the command set is relatively simple.
I know. But the command set for each chip differs slightly, so full support is difficult.
Is the SPI stuff properly supported? I feel like I'm a little out of my depth on this code...
I started last week to write support for SPI. It is in a really early stage and can only ID the chip (and with current svn, it will still say that no chip was found even if the ID could be read).
Please run current svn flashrom in verbose mode (-V) and use your patched board enable. If possible, repeat this with my patch applied on top.
Regards, Carl-Daniel
On Sat, Oct 06, 2007 at 08:21:52AM +1000, Michael van der Kolff wrote:
Signed-off-by: Michael van der Kolff mvanderkolff@gmail.com
Committed in r2864.
Uwe.
-
Carl-Daniel Hailfinger -
Michael van der Kolff -
Peter Stuge -
Uwe Hermann