On Wed, 4 Oct 2017 07:21:45 +0200
ondrej ondrej <pondrej3(a)gmail.com> wrote:
> Hi,
> I try to send mail to this address two days before, but I don't receive any
> reply. Maybe my mail was blocked, because I added attachment to it.
> I try to resend it (please see next mail) without attachment.
>
> Is there any change to use flashrom with my board to flash BIOS? Before
> flashroom a try to use "awdflash", but it must be used from FreeDos. I used
> various
> versions, but every hang and don't flash nothing to my BIOS Flash.
Hi!
We received both mails without problems. There is no need to impatiently
send more mails to the mailing list further.
--
Kind regards/Mit freundlichen Grüßen, Stefan Tauner
Hi,
I try to send mail to this address two days before, but I don't receive any
reply. Maybe my mail was blocked, because I added attachment to it.
I try to resend it (please see next mail) without attachment.
Is there any change to use flashrom with my board to flash BIOS? Before
flashroom a try to use "awdflash", but it must be used from FreeDos. I used
various
versions, but every hang and don't flash nothing to my BIOS Flash.
---------- Forwarded message ----------
From: ondrej ondrej <pondrej3(a)gmail.com>
Date: Mon, Oct 2, 2017 at 4:02 PM
Subject: GA-C7V7VX-RH
To: flashrom(a)flashrom.org
Hi,
I try to use flashrom with the board "GA-C7V7VX-RH" and I get error "Super
I/O ID 0x8712 is not on the list of flash-capable controllers."
This board have chipset "VIA VT8237(R)", bios flash chip "mx25l4005" and
Super I/O chip "IT8712F-S".
I attached to my mail debug of the command: flashrom -p internal -VVV -o
./flashrom.txt.
Thank you for your support.
Hi,
I try to use flashrom with the board "GA-C7V7VX-RH" and I get error "Super
I/O ID 0x8712 is not on the list of flash-capable controllers."
This board have chipset "VIA VT8237(R)", bios flash chip "mx25l4005" and
Super I/O chip "IT8712F-S".
I attached to my mail debug of the command: flashrom -p internal -VVV -o
./flashrom.txt.
Thank you for your support.
Hello,
I would like to make a request for an EEPROM to be added to what
flashrom can program to.
VENDOR : ATMEL
MODEL : AT28C64B
SIZE : 64k (8k x 8)
MEM TYPE : Parallel EEPROM
DATASHEET : http://ww1.microchip.com/downloads/en/DeviceDoc/doc0270.pdf
Sincerely,
Zachary T Stuart
ZTEX
ZTEX MUSEUM
zach.stuart(a)ztex.us
Hi,
I try to use flashrom with the board "GA-C7V7VX-RH" and I get error "Super
I/O ID 0x8712 is not on the list of flash-capable controllers."
This board have chipset "VIA VT8237(R)", bios flash chip "mx25l4005" and
Super I/O chip "IT8712F-S".
I attached to my mail debug of the command: flashrom -p internal -VVV -o
./flashrom.txt.
Thank you for your support.
Hi,
I recently bought two VMAC V1 Mini PC's with Winbond W25Q64FWSIG EFI chips. Updating the EFI information on teh devices using the normal software route is extremely flakey and I managed to corrupt the EFI on both boards, making them unbootable.
I now have a Chinese CH341a ("Black Edition") usb programmer and a "piggy-back" 1.8v adapter and can connect to the Winbond chip using a test clip.
I installed flashrom from the debian package V0.99 and can do a:
Initially, I thought I had problems getting the clip properly seated, but no matter how much I clean the contacts and re-seat the clip, if I do a:
#flashrom -p ch341a_spi -V
I get (randomly):
Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) on ch341a_spi.
Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on ch341a_spi.
Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on ch341a_spi.
Finding the correct chip or not seems to have little or nothing to do with the physical contact to the chip.
If I then try to erase the chip. I get:
# flashrom -p ch341a_spi -c W25Q64.W -E
flashrom v0.9.9-r1954 on Linux 4.10.1-towo.1-siduction-amd64 (x86_64)
flashrom is free software, get the source code at https://flashrom.org
Calibrating delay loop... OK.
Found Winbond flash chip "W25Q64.W" (8192 kB, SPI) on ch341a_spi.
Erasing and writing flash chip... FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00000fff: 0x1000
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x00007fff: 0x53cb
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x00000000! Expected=0xff, Found=0xd6, failed byte count from 0x00000000-0x0000ffff: 0x9264
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x5e1391
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x00000000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x007fffff: 0x5ce187
ERASE FAILED!
Looking for another erase function.
No usable erase functions left.
FAILED!
Your flash chip is in an unknown state.
Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom(a)flashrom.org, thanks!
Again, the hex codes for the failures seem pretty random and are different each time I try the command.
I attach the log.
Can anyone say what's going on?
Best Regards
Marius