Hi,
Here is some more info regarding my last email. Writing the new flash image failed. Before that I read the old and verified it with flashrom.
//Jonte
--8<--- $ sudo flashrom -v bios_old_2013-05-26.bin flashrom v0.9.5.2-r1517 on Linux 3.2.0-44-generic (x86_64), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found chipset "NVIDIA MCP67". Enabling flash write... This chipset is not really supported yet. Guesswork... Please send the output of "flashrom -V" to flashrom@flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH) at physical address 0xfff80000. Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Verifying flash... VERIFIED. jonte@wintermute:/home/jonte$ sudo flashrom -w /mnt/floppy/abit/ ABITFAE.BAT AWDFLASH.EXE M628A_20.BIN M628A_20.TXT RUNME.BAT jonte@wintermute:/home/jonte$ sudo flashrom -w /mnt/floppy/abit/M628A_20.BIN flashrom v0.9.5.2-r1517 on Linux 3.2.0-44-generic (x86_64), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found chipset "NVIDIA MCP67". Enabling flash write... This chipset is not really supported yet. Guesswork... Please send the output of "flashrom -V" to flashrom@flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH) at physical address 0xfff80000. Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x00000fff: 0x6ee ERASE FAILED! Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0000ffff: 0x6ee ERASE FAILED! Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x5f21f ERASE FAILED! FAILED! Uh oh. Erase/write failed. Checking if anything changed. Good. It seems nothing was changed. Writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at irc.freenode.net (channel #flashrom) or mail flashrom@flashrom.org! ------------------------------------------------------------------------------- You may now reboot or simply leave the machine running.
On Sun, 26 May 2013 11:28:43 +0300 Jon Wickström jonte@xn--wickstrm-t4a.fi wrote:
Hi,
Here is some more info regarding my last email. Writing the new flash image failed. Before that I read the old and verified it with flashrom.
//Jonte
--8<--- $ sudo flashrom -v bios_old_2013-05-26.bin flashrom v0.9.5.2-r1517 on Linux 3.2.0-44-generic (x86_64), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found chipset "NVIDIA MCP67". Enabling flash write... This chipset is not really supported yet. Guesswork... Please send the output of "flashrom -V" to flashrom@flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH) at physical address 0xfff80000. Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Verifying flash... VERIFIED. jonte@wintermute:/home/jonte$ sudo flashrom -w /mnt/floppy/abit/ ABITFAE.BAT AWDFLASH.EXE M628A_20.BIN M628A_20.TXT RUNME.BAT jonte@wintermute:/home/jonte$ sudo flashrom -w /mnt/floppy/abit/M628A_20.BIN flashrom v0.9.5.2-r1517 on Linux 3.2.0-44-generic (x86_64), built with libpci 3.1.8, GCC 4.6.3, little endian flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found chipset "NVIDIA MCP67". Enabling flash write... This chipset is not really supported yet. Guesswork... Please send the output of "flashrom -V" to flashrom@flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. Found PMC flash chip "Pm49FL004" (512 kB, LPC, FWH) at physical address 0xfff80000. Flash image seems to be a legacy BIOS. Disabling coreboot-related checks. Reading old flash chip contents... done. Erasing and writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x00000fff: 0x6ee ERASE FAILED! Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0000ffff: 0x6ee ERASE FAILED! Reading current flash chip contents... done. ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x5f21f ERASE FAILED! FAILED! Uh oh. Erase/write failed. Checking if anything changed. Good. It seems nothing was changed. Writing to the flash chip apparently didn't do anything. This means we have to add special support for your board, programmer or flash chip. Please report this on IRC at irc.freenode.net (channel #flashrom) or mail flashrom@flashrom.org!
You may now reboot or simply leave the machine running.
Hi Jonte,
this is pretty much a shot into the dark but you could try the code that is believed to work for the AN-M2. Please get the source code, add the following line to the big table in board_enable.c around line 2300, recompile, and retry to write a different image. " {0x10DE, 0x0547, 0x147B, 0x1C2E, 0x10DE, 0x0548, 0x147B, 0x1C2E, NULL, NULL, NULL, P3, "abit", "AN-M2HD", 0, OK, nvidia_mcp_gpio2_raise},"
Don't forget to use the compiled binary (./flashrom) and not the one previously installed. Please use the verbose switch (-V) when testing and send us the output. Please note that this potentially could harm your hardware, if that GPIO pin is connected to something that does not like it to be changed.
-
Jon Wickström -
Stefan Tauner