Hi.
I tested flashrom on my Jetway J7F5M motherboard.
# flashrom Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA CX700", enabling flash write... OK. Found chip "Winbond W39V040B" (512 KB) at physical address 0xfff80000. No operations were specified.
So probing seems to work ok, as do reading. Writing, however, does not work - the image on the flash chip remains unchanged (had a sweaty moment after the FAILED message before I had read the chip again and diffed it against the backed-up original image!).
The "Protect flash part" option in BIOS is set to Disabled (I also tried Enabled, just to be sure).
Is there any hope on getting flashrom support for this card? The AWDFLASH.EXE utility recommended for flashing by Jetway is "only" some sixty thousand bytes - any hints on reverse engineering this?
The computer is head-, FD- and CDR-less and runs linux, so it's a chore to flash it with the d**n DOS utility...
On Sat, Jul 04, 2009 at 04:12:06PM +0200, Arvid Brodin wrote:
Hi.
I tested flashrom on my Jetway J7F5M motherboard.
# flashrom Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA CX700", enabling flash write... OK. Found chip "Winbond W39V040B" (512 KB) at physical address 0xfff80000. No operations were specified.
So probing seems to work ok, as do reading. Writing, however, does not work - the image on the flash chip remains unchanged (had a sweaty moment after the FAILED message before I had read the chip again and diffed it against the backed-up original image!).
The "Protect flash part" option in BIOS is set to Disabled (I also tried Enabled, just to be sure).
Is there any hope on getting flashrom support for this card? The AWDFLASH.EXE utility recommended for flashing by Jetway is "only" some sixty thousand bytes - any hints on reverse engineering this?
The computer is head-, FD- and CDR-less and runs linux, so it's a chore to flash it with the d**n DOS utility...
-- Arvid
Please provide the output of lspci -vnn.
Luc Verhaegen.
Luc Verhaegen wrote:
On Sat, Jul 04, 2009 at 04:12:06PM +0200, Arvid Brodin wrote:
Hi.
I tested flashrom on my Jetway J7F5M motherboard.
# flashrom Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA CX700", enabling flash write... OK. Found chip "Winbond W39V040B" (512 KB) at physical address 0xfff80000. No operations were specified.
So probing seems to work ok, as do reading. Writing, however, does not work - the image on the flash chip remains unchanged (had a sweaty moment after the FAILED message before I had read the chip again and diffed it against the backed-up original image!).
The "Protect flash part" option in BIOS is set to Disabled (I also tried Enabled, just to be sure).
Is there any hope on getting flashrom support for this card? The AWDFLASH.EXE utility recommended for flashing by Jetway is "only" some sixty thousand bytes - any hints on reverse engineering this?
The computer is head-, FD- and CDR-less and runs linux, so it's a chore to flash it with the d**n DOS utility...
-- Arvid
Please provide the output of lspci -vnn.
Luc Verhaegen.
Output at pastebin, good for a month:
On Mon, Jul 06, 2009 at 12:13:12AM +0200, Arvid Brodin wrote:
Luc Verhaegen wrote:
On Sat, Jul 04, 2009 at 04:12:06PM +0200, Arvid Brodin wrote:
Hi.
I tested flashrom on my Jetway J7F5M motherboard.
# flashrom Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA CX700", enabling flash write... OK. Found chip "Winbond W39V040B" (512 KB) at physical address 0xfff80000. No operations were specified.
So probing seems to work ok, as do reading. Writing, however, does not work - the image on the flash chip remains unchanged (had a sweaty moment after the FAILED message before I had read the chip again and diffed it against the backed-up original image!).
The "Protect flash part" option in BIOS is set to Disabled (I also tried Enabled, just to be sure).
Is there any hope on getting flashrom support for this card? The AWDFLASH.EXE utility recommended for flashing by Jetway is "only" some sixty thousand bytes - any hints on reverse engineering this?
The computer is head-, FD- and CDR-less and runs linux, so it's a chore to flash it with the d**n DOS utility...
-- Arvid
Please provide the output of lspci -vnn.
Luc Verhaegen.
Output at pastebin, good for a month:
One month is not good enough for us. Please next time add this as an attachment so we have a reference for the future.
Attached from pastebin now.
Luc Verhaegen.
After looking at the picture of the jetway website, and i noticed the layout of the board with the philips tv decoder on it, my coin dropped that i actually own this board.
Still stumped as to how to write to it, the board enable in the latest jetway bios fails.
Does the dos utility work for you?
Output of flashrom failing:
./flashrom -E flashrom v0.9.0-runknown No coreboot table found. Found chipset "VIA CX700", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "Winbond W39V040B" (512 KB, LPC) at physical address 0xfff80000. Erasing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49 ERASE FAILED! FAILED! ERROR at 0x00000000: Expected=0xff, Read=0x49
No change no matter what i do.
Luc Verhaegen.
On Mon, Jul 06, 2009 at 04:43:02AM +0200, Luc Verhaegen wrote:
After looking at the picture of the jetway website, and i noticed the layout of the board with the philips tv decoder on it, my coin dropped that i actually own this board.
Still stumped as to how to write to it, the board enable in the latest jetway bios fails.
Does the dos utility work for you?
Output of flashrom failing:
./flashrom -E flashrom v0.9.0-runknown No coreboot table found. Found chipset "VIA CX700", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "Winbond W39V040B" (512 KB, LPC) at physical address 0xfff80000. Erasing flash chip... ERASE FAILED at 0x00000000! Expected=0xff, Read=0x49 ERASE FAILED! FAILED! ERROR at 0x00000000: Expected=0xff, Read=0x49
No change no matter what i do.
Luc Verhaegen.
After carldani gave me some hints on irc, i'm currently blaming the flashchip itself. I think the support for the w39v040b has regressed in the last 13 months, after it was set to TEST_OK_PREW in commit 252.
Dan, apparently you then said it tested ok (and i hope this is your correct email address). What board were you using this rom on and can you test a recent svn version of flashrom?
Thanks,
Luc Verhaegen.
On Mon, Jul 06, 2009 at 02:38:45PM +0200, Luc Verhaegen wrote:
After carldani gave me some hints on irc, i'm currently blaming the flashchip itself. I think the support for the w39v040b has regressed in the last 13 months, after it was set to TEST_OK_PREW in commit 252.
Dan, apparently you then said it tested ok (and i hope this is your correct email address). What board were you using this rom on and can you test a recent svn version of flashrom?
Thanks,
Luc Verhaegen.
Yes, definitely not a motherboard issue, as it fails in an epia-sp as well. W39V040B erase/write is just not working at all. Will send a patch to mark it as bad, until someone (carldani? uwe?) has time to fix it.
Luc Verhaegen.
Luc Verhaegen wrote:
On Mon, Jul 06, 2009 at 02:38:45PM +0200, Luc Verhaegen wrote:
After carldani gave me some hints on irc, i'm currently blaming the flashchip itself. I think the support for the w39v040b has regressed in the last 13 months, after it was set to TEST_OK_PREW in commit 252.
Dan, apparently you then said it tested ok (and i hope this is your correct email address). What board were you using this rom on and can you test a recent svn version of flashrom?
Thanks,
Luc Verhaegen.
Yes, definitely not a motherboard issue, as it fails in an epia-sp as well. W39V040B erase/write is just not working at all. Will send a patch to mark it as bad, until someone (carldani? uwe?) has time to fix it.
Luc Verhaegen.
Ok. Thanks for testing it out!
-
Arvid Brodin -
Luc Verhaegen