FAILED: Abit nf-m2-nView

[Guntram Schmidt]

Hi folks,

I wanted to reflash the just-before-backupped BIOS with self-compiled
Flashform 0.9.3 on Ubuntu Karmic Koala (9.10) 32-Bit, PAE-Kernel
2.6.31-22.

This is the message I got:

$ sudo flashrom -w abit_093.bin

flashrom v0.9.3-r1205 on Linux 2.6.31-22-generic-pae (i686), built
with libpci 3.0.0, GCC 4.4.1, little endian
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
No coreboot table found.
Found chipset "NVIDIA MCP51", enabling flash write... OK.
This chipset supports the following protocols: Non-SPI.
WARNING: Your mainboard is abit NF-M2 nView, but the mainboard-specific
code has not been tested, and thus will not not be executed by default.
Depending on your hardware environment, erasing, writing or even probing
can fail without running the board specific code.

Please see the man page (section PROGRAMMER SPECIFIC INFO, subsection
"internal programmer") for details.
Found chip "PMC Pm49FL004" (512 KB, LPC,FWH) at physical address 0xfff80000.
Flash image seems to be a legacy BIOS. Disabling checks.
Writing flash chip... Erasing flash chip... ERASE FAILED at
0x00000000! Expected=0xff, Read=0x49, failed byte count from
0x00000000-0x00000fff: 0x70f
ERASE FAILED!
ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte
count from 0x00000000-0x0000ffff: 0x70f
ERASE FAILED!
ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte
count from 0x00000000-0x0007ffff: 0x5973f
ERASE FAILED!
FAILED!
ERASE FAILED!
FAILED!
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net (channel #flashrom) or
mail [e-mail] with FAILED: your board name in the subject line!
-------------------------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!

I first wanted simply to write the saved BIOS again, to be sure,
everything works fine before flashing the new version of the bios.
To be honest: I could'nt figure out the meaning concerning the
"mainboard-specific code", that's why I tried nevertheless.

Thanks for any hints on how to continue,
Guntram

[Stefan Tauner]

On Tue, 12 Apr 2011 22:14:16 +0200
Guntram Schmidt  wrote:
> I first wanted simply to write the saved BIOS again, to be sure,
> everything works fine before flashing the new version of the bios.
> To be honest: I could'nt figure out the meaning concerning the
> "mainboard-specific code", that's why I tried nevertheless.

hello

please retry with "-p internal:boardenable=force" added to your command
and report back, thanks.

disclamer: i read that manpage section the first time 2 minutes ago. :)

[PATCH] fix typo "not not" in board_enable.c

[Stefan Tauner]

Signed-off-by: Stefan Tauner 
---
 board_enable.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/board_enable.c b/board_enable.c
index d459b98..e8b3ad3 100644
--- a/board_enable.c
+++ b/board_enable.c
@@ -2123,7 +2123,7 @@ int board_flash_enable(const char *vendor, const char *part)
    if (board && board->status == NT) {
    	if (!force_boardenable) {
    		msg_pinfo("WARNING: Your mainboard is %s %s, but the mainboard-specific\n"
-			       "code has not been tested, and thus will not not be executed by default.\n"
+			       "code has not been tested, and thus will not be executed by default.\n"
    		       "Depending on your hardware environment, erasing, writing or even probing\n"
    		       "can fail without running the board specific code.\n\n"
    		       "Please see the man page (section PROGRAMMER SPECIFIC INFO, subsection\n"