[flashrom] MSI K9N6SGM-V: flashrom -V

Benoit Sarels benoit.sarels at gmail.com
Tue Sep 18 22:24:09 CEST 2012


Thanks for the explanation !


bibi at k9n6sgm-v:~/flashrom$ sudo flashrom -V -p internal
flashrom v0.9.6.1-r1599 on Linux 3.2.0-30-generic (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org

flashrom was built with libpci 3.1.8, GCC 4.6.3, little endian
Command line (3 args): flashrom -V -p internal
Calibrating delay loop... OS timer resolution is 2 usecs, 1201M loops
per second, 10 myus = 11 us, 100 myus = 100 us, 1000 myus = 1010 us,
10000 myus = 9978 us, 8 myus = 9 us, OK.
Initializing internal programmer
No coreboot table found.
DMI string system-manufacturer: "MSI"
DMI string system-product-name: "MS-7309"
DMI string system-version: "1.0"
DMI string baseboard-manufacturer: "MSI"
DMI string baseboard-product-name: "MS-7309"
DMI string baseboard-version: "1.0"
DMI string chassis-type: "Desktop"
Found Fintek Super I/O, ID 0x0541.
Found chipset "NVIDIA MCP61" with PCI ID 10de:03e0. Enabling flash
write... This chipset is not really supported yet. Guesswork...
ISA/LPC bridge reg 0x8a contents: 0x00, bit 6 is 0, bit 5 is 0
Flash bus type is LPC
Found SMBus device 10de:03eb at 00:01:1
MCP SPI BAR is at 0xfec80000
Strange. MCP SPI BAR is valid, but chipset apparently doesn't have SPI enabled.
Please send the output of "flashrom -V" to flashrom at flashrom.org with
your board name: flashrom -V as the subject to help us finish support for your
chipset. Thanks.
OK.
Super I/O ID 0x0541 is SPI capable. TODO: Check if SPI is active.
The following protocols are supported: LPC.
Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2
0x06, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2
0x06, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xff, id2
0x06, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xff, id2
0x06, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing
information, using default 10mS/40uS. probe_jedec_common: id1 0xff,
id2 0xff, id1 parity violation, id1 is normal flash content, id2 is
normal flash content
Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2
0xff, id1 parity violation, id1 is normal flash content, id2 is normal
flash content
Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff,
id1 parity violation, id1 is normal flash content, id2 is normal flash
content
Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xff,
id2 0xff, id1 parity violation, id1 is normal flash content, id2 is
normal flash content
Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xff,
id2 0xff, id1 parity violation, id1 is normal flash content, id2 is
normal flash content
Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xff,
id2 0xff, id1 parity violation, id1 is normal flash content, id2 is
normal flash content
Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff,
id2 0xff, id1 parity violation, id1 is normal flash content, id2 is
normal flash content
Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xff,
id2 0x06, id1 parity violation, id1 is normal flash content, id2 is
normal flash content
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
Restoring PCI config space for 00:01:0 reg 0x6d
Restoring PCI config space for 00:01:0 reg 0x90
Restoring PCI config space for 00:01:0 reg 0x8c
Restoring PCI config space for 00:01:0 reg 0x88




2012/9/18 Stefan Tauner <stefan.tauner at student.tuwien.ac.at>:
> On Tue, 18 Sep 2012 16:01:20 +0200
> Benoit Sarels <benoit.sarels at gmail.com> wrote:
>
> hi
>
>> It seems like I am missing something :
> yes indeed, namely the --programmer parameter ;)
> you need to add -p internal to the command line.
>
> since r1552 flashrom requires that you select the programmer. the
> previous behavior of having a default programmer has been disabled,
> because it could lead to unexpected bricking of devices if one gets too
> much used to a specific default programmer and then using another
> version of flashrom which uses another one...
>
> --
> Kind regards/Mit freundlichen Grüßen, Stefan Tauner




More information about the flashrom mailing list