On Mon, 2 Jan 2012 05:31:48 -0500
CHRIS HONEYCUTT <chrish19902010(a)gmail.com> wrote:
> linux-poa8:/home/chris/Desktop # flashrom -V -w 070830s.ROM
> flashrom v0.9.3-r1246 on Linux 2.6.37.1-1.2-default (i686), built with
> […]
> DMI string system-product-name: "P4M800PRO-M"
Hello CHRIS,
thanks for your report! Version 1.0A was already reported as working. I
have added "2.0" to that line and will commit it later.
> […]
> Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0x9d, id2 0x6e
> Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000.
> […]
> ===
> This flash part has status UNTESTED for operations: WRITE
> The test status of this chip may have been updated in the latest development
> version of flashrom. If you are running the latest development version,
> please email a report to flashrom(a)flashrom.org if any of the above
> operations
> work correctly for you with this flash part. Please include the flashrom
> output with the additional -V option for all operations you tested (-V, -Vr,
> -Vw, -VE), and mention which mainboard or programmer you tested.
> Please mention your board in the subject line. Thanks for your help!
The chip was already reported to be completely working.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
root@wst:~# flashrom -V
flashrom v0.9.4-r1394 on Linux 3.0.0-1-686-pae (i686), built with libpci
3.1.7, GCC 4.6.1, little endian
flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OS timer resolution is 1 usecs, 1011M loops per
second, 10 myus = 11 us, 100 myus = 94 us, 1000 myus = 917 us, 10000 myus =
12822 us, 4 myus = 5 us, OK.
Initializing internal programmer
No coreboot table found.
DMI string system-manufacturer: "ASUSTeK Computer INC."
DMI string system-product-name: "M2N-MX"
DMI string system-version: "System Version"
DMI string baseboard-manufacturer: "ASUSTeK Computer INC."
DMI string baseboard-product-name: "M2N-MX"
DMI string baseboard-version: "Rev 1.xx"
DMI string chassis-type: "Desktop"
Found ITE Super I/O, ID 0x8712 on port 0x2e
Found chipset "NVIDIA MCP61" with PCI ID 10de:03e0.
This chipset is marked as untested. If you are using an up-to-date version
of flashrom please email a report to flashrom(a)flashrom.org including a
verbose (-V) log. Thank you!
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 0xa0000000
Strange. MCP SPI BAR is valid, but chipset apparently doesn't have SPI
enabled.
Please send the output of "flashrom -V" to flashrom(a)flashrom.org with
your board name: flashrom -V as the subject to help us finish support for
your
chipset. Thanks.
OK.
This chipset supports the following protocols: LPC.
Super I/O ID 0x8712 is not on the list of flash capable controllers.
Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Found SST flash chip "SST49LF040B" (512 kB, LPC) at physical address
0xfff80000.
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 0xbf, id2 0x50
Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xbf, id2 0x50
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 0xbf, id2 0x50
===
This flash part has status UNTESTED for operations: WRITE
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to flashrom(a)flashrom.org if any of the above
operations
work correctly for you with this flash part. Please include the flashrom
output with the additional -V option for all operations you tested (-V, -Vr,
-Vw, -VE), and mention which mainboard or programmer you tested.
Please mention your board in the subject line. Thanks for your help!
No operations were specified.
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
On Mon, 2 Jan 2012 10:56:42 +0100
Piotr Król <pietrushnic(a)gmail.com> wrote:
> Yes, you're right it is a motherboard AV18E2 with updated BIOS. I think
> about
> try to write support for coreboot for this board, although I have yet to
> learn a
> lot.
>
OK, thank you for the reply. I have added the board to our list and
marked the north and south bridge tested as well. I will commit all of
this later.
GL with coreboot... afaics that would be quite some work though.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
On Fri, 30 Dec 2011 14:11:39 +0100
Piotr Król <pietrushnic(a)gmail.com> wrote:
> Hi,
> I tested this motherboard for erase and write and everything seems to work
> properly.
> Logs in attachments.
> flashrom -V
> flashrom -VE
> flashrom -Vw bios_bckp.bin
> lspci -nnvvxxx
> superiotool -deV - http://paste.flashrom.org/view.php?id=993
Hello Piotr,
thanks for your report!
Looks like it is working and we can mark some stuff tested, great.
One question though... there is no board named AV18S403 according to the
interwebs, but there is a firmware update named like that for a board
called AV18E2 (v4.0):
http://www.shuttle.eu/_archive/older/de/av18_faq.htm#download
So i guess you really meant AV18E2?
See also http://www.shuttle.eu/_archive/older/de/av18.htm#versionen
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
On Sun, 1 Jan 2012 23:22:18 +0100
Ob Noxious <obnox3(a)gmail.com> wrote:
> 0x5C: 0x017f0003 (FREG2: Management Engine)
> 0x00003000-0x0017ffff is locked
Hello Ob,
thanks for your report!
The problem is the locked ME region as quoted above. We are working on
unlocking it, but intel does not provide us any documentation so please
do not expect a solution soon.
I have added the board to our list of (un)supported boards (with an
appropriate note) and will commit that later together with other small
changes.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Hello Lee,
thanks for your report!
I have added the mainboard to our list of supported boards and will
commit that later together with other small changes.
On Mon, 26 Dec 2011 11:10:27 -0600
Lee Daugherty <leewdaugherty(a)gmail.com> wrote:
> Found chipset "NVIDIA MCP61" with PCI ID 10de:03e1.
> This chipset is marked as untested. If you are using an up-to-date version
> of flashrom please email a report to flashrom(a)flashrom.org including a
> verbose (-V) log. Thank you!
This is already marked as tested in svn or locally in my branch.
> WARNING: unexpected second chipset match: "NVIDIA MCP61"
hm that's interesting... can you please post a log of lspci -nnvvvxxx?
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Hi,
According to flashrom output, please attached the debug output as
suggested by the tool. There are 2 versions for the 2 available
verbosity levels.
Hope it helps :-)
--
ObNox
