Your reply is very helpfull to me (especailly the part about using v2 - I was unsure which of v2 or v3 was appropriate) and very clear. I will follow the "destructions" (probably not till August becasue busy in June and holiday most of July) and once I have blown up the board will post the results to this list.
--- On Wed, 17/6/09, Myles Watson <mylesgw(a)gmail.com> wrote:
> From: Myles Watson <mylesgw(a)gmail.com>
> Subject: Re: [coreboot] ASUS KFN4D16 - K8 FAM10
> To: "Thomas Ward" <tomwardathome(a)yahoo.co.uk>
> Cc: "coreboot(a)coreboot.org" <coreboot(a)coreboot.org>
> Date: Wednesday, 17 June, 2009, 5:13 PM
> On Tue, Jun 16, 2009 at 3:36 AM,
> Thomas Ward <tomwardathome(a)yahoo.co.uk>
> I realise your list is very technical and this is probably
> a daft set of question so please forgive me if it is
> cluttering up your list but I couldn't find a more
> appropriate place to ask,..
> ... so here goes.
> My questions are about running coreboot on an ASUS KFN4-D16
> with an NVIDIA CK804 chipset and a SST SST49LF080A (BIOS?)
> chip 33-4C-NHE 0631138-B
> I have 2 cpus one is a 65nm dual core opteron 2210, the
> second CPU is a quad core 45nm "Shanghai" opteron
> 2376 - this CPU isn't supported by the ASUS BIOS.
> My aim is to get the board to boot with the quad core CPU,
> I would be happy if it boots with support for all the RAM
> and at least one of the ethernet ports, I can live without
> PCI, SATA, USB etc.They should all work.
> My plan is to use a BIOS saviour and buy a second
> SST49LF080A chip and then
> 1. flash coreboot for K8 (?) with flashrom to verify that
> coreboot works on this board
> 2. flash coreboot for fam10 (?) with flashrom
> does this sound like a good plan?Yes.
> I have a couple of other questions
> E. what sort of BIOS chip / bios saviour kit should I use
> with this board?RD1
> output from flashrom, superiotool and lspci appended
> many thanks for any help and good luck with your project,
> Tom Ward
> root@shed:/home/tom/coreboot/flashrom# ./flashrom
> flashrom v0.9.0-r555
> No coreboot table found.
> Found chipset "NVIDIA CK804", enabling flash
> write... OK.
> Calibrating delay loop... OK.
> Found chip "SST SST49LF080A" (1024 KB) at
> physical address 0xfff00000.Hopefully this
> chip is socketed.
> superiotool r3695
> Found Winbond W83627THF/THG (id=0x82, rev=0x84) at
> 0x2eThis SuperIO is supported.
> 00:00.0 Memory controller: nVidia Corporation CK804 Memory
> Controller (rev a4)
> This board is very similar to the
> If I were you, my first step would be to get the BIOS
> savior (or just use the pushpin method)
> Once you can recover from a bad flash,
> check out the latest coreboot-v2
> mkdir src/mainboard/asus/kfn4-d16
> svn cp src/mainboard/tyan/s2892/*
> mkdir targets/asus/kfn4-d16
> svn cp targets/tyan/s2892/Config.lb targets/asus/kfn4-d16/
> edit src/mainboard/asus/kfn4-d16/Config.lb
> Enable devices that are in your lspci, disable any that
> don't show up. Don't worry about cards that you
> plug in, they'll be found automatically.
> Change the SuperIO from chip superio/winbond/w83627hf to
> superio/winbond/w83627thf and change any settings there that
> you need to.
> Change socket_940 to socket_F
> (When you're ready to switch to fam10)
> Change amdk8 to amdfam10 everywhere (may need some other
> small fixups)
> edit targets/asus/kfn4-d16/Config.lb
> Change s2892 to kfn4-d16
> make sure ROM_SIZE matches the chip you're using.
> cd targets
> ./buildtarget asus/kfn4-d16
> make a payload (Maybe seabios)
> cp your_payload targets/asus/kfn4-d16/kfn4-d16/payload.elf
> make -C asus/kfn4-d16/kfn4-d16
> Last step is to send your patches to the list with a
> Signed-off-by: <your-email> line.
> -----Inline Attachment Follows-----
> coreboot mailing list: coreboot(a)coreboot.org
I'd like to re-open a tread from Michal Janke about supporting Dell latitude
C610 and its SMSC LPC47N252 SuperIO.
- I've found the closest chip from SMSC was FDC37N972, supported by
superiotool so I added corresponding entries in smsc.c.
- for FDC, UARTS, KBD, RTC, everything seems quite common so I added it in
(the big difference betweenn supported smsc chips an LPC47N252 is the
EC-8051 core... )
What could be the next step ?
Thanks for advices
Support for an external serial flasher protocol.
Supports RS-232, USB serial converters (untested) and TCP streams.
Signed-off-by: Urja Rannikko <urjaman(a)gmail.com>
Please commit my jedec.c readb to readn patch (or carldani's version
that i've only heard of in IRC) before this
- they're not dependent but without that patch this protocol is awfully slow.
Also attached is a simple specification of the protocol this code
implements, it hasnt changed much from my last mail,
but i attach it here so it's readily available in the same mail with
I also have the implementation of this protocol on the device side for
an Atmel AVR ATmega168 microcontroller, it is
also included just for an idea of how i implemented the device side
parser - it has GPL headers added to all files and COPYING
included to make it GPLv2+ for real, but has not otherwise been looked
at for release - the device it runs on is in a way very special,
so i think compiling that directly would be of little use to anyone atm.
as I posted on the blog of Uwe, I have a sony vaio pcg sr1k laptop, and
wonder if I could flash it with coreboot. The box has
Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge chipset.
hovewer the results of the following commands are not encouriging, please
tell me if there is any chance to get coreboot working. Please find attached
the outpoot of the commands.
sudo superiotool -dV > siot.out
lspci -tvnn > lspci.out
sudo flashrom -V
#137: S2895 no function after coreboot 2 flash
Reporter: anonymous | Type: defect
Status: new | Priority: major
Milestone: | Component: buildrom
Version: v2 | Keywords:
Dependencies: | Patchstatus: there is no patch
I am not sure whether i am correct here with you guys. But i have some
troubles after flashing the tyan-s2895.rom that has been generated with
seabios as payload by the buildrom tool.
There are no logs in the log folders and everything worked fine.
But after flashing the coreboot bios to the board using "flashrom -v -w
tyan-s2895.rom" and i "halt" the system, it will come up for a second and
switches off immediately. I tried clearing the CMOS, but this did not
solve the problem.
Any idea what i am doing wrong?
Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/137>
This patch series makes v2 more similar to v3. It splits resource
allocation into read, compute, allocate. There is no more mutual recursion.
They go in this order:
It is boot tested on SimNOW and qemu.
domain_resources needs to be expanded to include other southbridges and
domains. I just wanted early feedback rather than late.
Signed-off-by: Myles Watson <mylesgw(a)gmail.com>