Resending this patch to the newly formed flashrom ml. Ron already
kindly acked this patch.
Mateusz, the owner of this board gave me a brief comment on irc stating
that it didn't work. Which is also the last i heard from him.
Mateusz, get back to us and get us at least the flashrom output.
Luc Verhaegen.
After last night, i was disgusted to such an extent that i went and did
this code that should meet all the (at least) logical demands made
earlier. And to think that this started with adding 1 more simple board
enable
(http://www.flashrom.org/pipermail/flashrom/2009-October/000750.html).
Some remarks here:
* we do not care about the name of the intel ICH. ICH name was detected
and mentioned before anyway.
* we do not try to match a specific intel ICH in the board enable.
That's what the big table was for to begin with.
* This tiny 190 line function is entirely redone if we have a second
io line that needs to be toggled.
* dell poweredge: comment is useless, use the commit message. There
might be a time when 50 boards might need exactly this gpio pin raised.
* i might have messed up a bit or so in the gpio line checking masks,
but cannot be bothered to go and trawl through everything yet again to
verify this.
Feel free to go and correct capitalisation. I'm off to do some real code
on unichrome.
Luc Verhaegen.
Hi
I saw that someone was asking for support for the k7VT4A+
Since I desperately need support for this board to get my epia board
working again
here is the F segment from my board
Tor
Hi, Ran flashrom and it reports "No EEPROM/flash device found", same
with -m ecs:k7s5a. Any suggestions how I can test further. I am
running Lenny and my cpu [an AMD 2600] is being mis-reported as 1406?
regards, Dave (dja.)
Hi,
carldani asked me to send this Mail - so i did.
Both files attached to this mail explain themselfs i think and here is
link to the motherboard:
http://eu.shuttle.com/archive/en/fs51.htm#mainboardfs5
Thanks and good luck,
Emil
Here it is what happened
andrea@andrea-desktop:~/Scrivania$ sudo flashrom -w W7046IM7.21C
flashrom v0.9.1-r706
No coreboot table found.
Found chipset "Intel ICH6/ICH6R", enabling flash write... OK.
This chipset supports the following protocols: Non-SPI.
Disabling flash write protection for board "MSI MS-7046"... OK.
Calibrating delay loop... OK.
Found chip "Winbond W39V040FA" (512 KB, FWH) at physical address 0xfff80000.
Flash image seems to be a legacy BIOS. Disabling checks.
Writing flash chip... ERASE FAILED at 0x00000000! Expected=0xff,
Read=0x49, failed byte count from 0x00000000-0x0007ffff: 0x53e8d
ERASE FAILED!
ERASE FAILED!
FAILED!
Your flash chip is in an unknown state.
Get help on IRC at irc.freenode.net channel #flashrom or
mail flashrom(a)flashrom.org
------------------------------------------------------------
DO NOT REBOOT OR POWEROFF!
I can see only now that I did not write the "v" on the command line,
dammit, please help needed.
Thank you very much for your atenction in advance.
Hi,
Just want to report a non-working board - the Asrock K7S41GX, tested with
flashrom r711 and superiotool r4623.
first some brief details ...
Board: Asrock K7S1GX
Bios Vendor: AMI
Bios Version: P1.90
root@ubuntu:~# lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host
(rev 03)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual
PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media
IO] (rev 25)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97
Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
(rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller
(rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI
Fast Ethernet (rev 90)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
flashrom v0.9.1-r711
No coreboot table found.
This chipset supports the following protocols: Non-SPI.
WARNING: No chipset found. Flash detection will most likely fail.
Calibrating delay loop... OK.
No EEPROM/flash device found.
If you know which flash chip you have, and if this version of flashrom
supports a similar flash chip, you can try to force read your chip. Run:
flashrom -f -r -c similar_supported_flash_chip filename
Note: flashrom can never write when the flash chip isn't found
automatically.
root@ubuntu:~# ./superiotool/superiotool
superiotool r4623
Found Winbond W83697HF/F/HG (id=0x60, rev=0x12) at 0x2e
Cheers,
--
Udu Ogah
.~~~~~~~~~~.
On Sun, Oct 18, 2009 at 06:33:11PM -0700, Sean Nelson wrote:
> the "anomaly" is the code for my board to enable flash writing. That's
> the reason why it's has it's own board enable arguments in flashrom.
>
> Sadly I don't remember what I did with the board since I upgraded the
> machine to a NForce4 set. If I find it, i'll try to send you the dumps
> you need.
>
> On Sat, Oct 17, 2009 at 2:58 PM, Luc Verhaegen <libv(a)skynet.be> wrote:
> > Hi Sean,
> >
> > I have some questions about your kt4v/kt4ultra board enable:
> >
> > 1) I am about to move some code from many vt823x based board
> > enables to the chipset enable. Your board enable has some "similar"
> > code, but not quite, and it now forms the only anomaly.
> >
> > Can you send me the output of:
> > dd if=/dev/mem of=/tmp/kt4v_system.rom bs=64k count=1 skip=15
> > so i can have a dig through the top segment of your AMI BIOS to verify
> > this code?
> >
> > 2) I am about to tighten up the board enable matching table.
> > * both the coreboot ids will disappear.
> > * we need a second set for the kt4v.
> > Can you send in lspci -vvnnxxx on both boards?
> >
> > Thanks,
> >
> > Luc Verhaegen.
> >
The anomalies are the following:
* it touches the register that vt823x based board enables often touch.
but instead of clearing the 1 bit, it clears all except two.
* it provides coreboot ids while it can match the one board just fine.
* it provides no full set of pciids for the second board.
Luc Verhaegen.