On Thu, 20 Feb 2014 22:58:10 +0100 Alex Moracchini president@reseau-js.com wrote:
Hello Flahsrom staff !
I have a problem with my stuff and flashrom. I want upgrade my Bios version but the erase/write function of flashrom has failed. I use “ASUS P5N32-SLI SE Deluxe” motherboard ( Bios version 0801 ) and i would install this new Bios version : http://fr.driverscollection.com/_440158660264bb85a1400351c90/T%C3%A9l%C3%A9c...
First operation :
# flashrom -p internal
flashrom v0.9.7-r1711 on FreeBSD 10.0-RELEASE (i386) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found chipset "NVIDIA CK804". Enabling flash write... OK. Found SST flash chip "SST49LF080A" (1024 kB, LPC) at physical address 0xfff00000 . No operations were specified.
Second operation :
# flashrom -p internal -w P5N32-SLI-SE-ASUS-Deluxe-0901.ROM
flashrom v0.9.7-r1711 on FreeBSD 10.0-RELEASE (i386) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found chipset "NVIDIA CK804". Enabling flash write... OK. Found SST flash chip "SST49LF080A" (1024 kB, LPC) at physical address 0xfff00000. Reading old flash chip contents... done. Erasing and writing flash chip... writing sector at 0x28c35200 failed! Reading current flash chip contents... done. FAILED at 0x0003c308! Expected=0xff, Found=0x48, failed byte count from 0x00030000-0x0003ffff: 0x3ca7 ERASE FAILED! FAILED!
Flashrom should also have told you if you are safe or not (to reboot). So I presume you did not include everything flashrom printed. Nevertheless it looks like flashrom modified the content of the flash memory and that makes it potentially unsafe to reboot. To recover I would first try to write the backup you read before with flashrom -r ... you did make a backup, didnt you? Please send us the complete log file created, e.g. "recovery.log" when running flashrom -p internal -o recovery.log -w "backup.img"