Myles,
Thanks for the link, that's exactly what I've been looking for! I seem to have been looking round the coreboot pages for days on end and managed to miss this.
I've not had a play with qemu, but have seen it mentioned on the list.
I think that's my next port of call. I'll have more of a tinker first.
Regards, Jon
-----Original Message----- From: coreboot-bounces@coreboot.org [mailto:coreboot-bounces@coreboot.org] On Behalf Of coreboot-request@coreboot.org Sent: 09 June 2009 07:29 To: coreboot@coreboot.org Subject: coreboot Digest, Vol 52, Issue 65
*** WARNING ***
This message has originated outside your organisation, either from an external partner or the Global Internet. Keep this in mind if you answer this message.
Send coreboot mailing list submissions to coreboot@coreboot.org
To subscribe or unsubscribe via the World Wide Web, visit http://www.coreboot.org/mailman/listinfo/coreboot or, via email, send a message with subject or body 'help' to coreboot-request@coreboot.org
You can reach the person managing the list at coreboot-owner@coreboot.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of coreboot digest..."
Today's Topics:
1. Re: Via EPIA-N(L) C3/CN400 Support - Help Wanted (Myles Watson) 2. Re: Is this boar/chipset combination supported? (saueimer) 3. Re: Is this boar/chipset combination supported? (Stefan Reinauer) 4. Re: [v3] r1170 - coreboot-v3/util/x86emu (ron minnich) 5. Re: Is this boar/chipset combination supported? (ron minnich) 6. Re: Via EPIA-N(L) C3/CN400 Support - Help Wanted (bari) 7. VIA VT8235 + SST39SF020A problem (Murawski Mateusz) 8. Re: [v3] r1170 - coreboot-v3/util/x86emu (Stefan Reinauer)
----------------------------------------------------------------------
Message: 1 Date: Mon, 8 Jun 2009 15:09:15 -0600 From: Myles Watson mylesgw@gmail.com To: Jon Harrison bothlyn@blueyonder.co.uk Cc: coreboot@coreboot.org Subject: Re: [coreboot] Via EPIA-N(L) C3/CN400 Support - Help Wanted Message-ID: 2831fecf0906081409i3c9ce565t5166997f40949d74@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1
I'm currently working on porting coreboot to the Via EPIA-N(L) i.e. C3/CN400/VT8237R/Winbond SuperIO.
Welcome!
I'm a fairly competent embedded systems designer/coder, and I'm aiming
to
get to the point where I can use the EPIA to run a small linux kernel
and
custom service from flash to act as a data logger from a custom
perpheral to
a SATA disk.
I'm not NDAd with Via (spent months trying to do this and gave up
?after
getting the run around for so long) ?but have aquired some data on the
CN400
that has allowed me to get this far. I don't have the BIOS Porting
Guide,
which suspect would be quite illuminating, if there is anyone out
there who
does have this and could review/correct my code for errors I'd
appreciate
it.
I'm not the right person for that, but hopefully this will help a little anyway.
I've got to the point where I have flashrom programming the board, I
have a
working build environment for V2 which is running the early romcc
compiled
code and seems to have done the CN400 meminit stuff OK, near as I can
tell I
am able to access SDRAM OK from romcc code (the early serial stuff is
up and
running OK, and i can get debug out that way), but I'm getting strange things happening when jumping to copy_and_run_core.
A log file would probably be helpful.
I think that the basic problem is a linking/location problem.
Options.lb doesn't seem to let me turn on print_spew in the gcc code
but
works OK in the romcc code, and
the .map file looks suspicious to me with loads of constants all defined at the same location.
It's probably fine, but you can compare with the map file of a working board to see what it looks like. There are several constants defined at the same location, and the build process will usually fail if they're wrong.
I'm happy to do the leg work if someone can give me a steer into how
all of
the different ROM_SIZE, ROM_SECTION_SIZE PAYLOAD_SIZE, FALLBACK_SIZE
etc.
etc. relate to the linking and location of code. I'm finding this a
bit
impenetrable at the moment.
Have you seen this page? http://www.coreboot.org/Anatomy_of_a_Failover_coreboot_v2_Image
You probably want an image that only contains fallback, which makes life simpler anyway.
Have you played around with qemu? It has a single image solution implemented with CBFS (which is new) or you can go back a few revisions to before CBFS.
Thanks, Myles
------------------------------
Message: 2 Date: Mon, 8 Jun 2009 23:01:19 +0200 From: saueimer saueimer@googlemail.com To: coreboot@coreboot.org Subject: Re: [coreboot] Is this boar/chipset combination supported? Message-ID: 51ec7b340906081401r592aa780h41beddd0a9510763@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"
Hi again,
how about the VIA EPIA EX15000G, CX700M2 (PC2-4200U DDR2) mainboard? Is or will this be supported? I am trying to build up a PC for my car so I need a ITX-motherboard and a DVI-Port. Coreboot in cobination with a SSD as harddisk would ensure a very quick boot ;) So if anyone could advise some board to me, if the upper one is not supported, I would really apprechiate it!
Thanks in advance!
2009/6/5 Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Hi,
On 05.06.2009 12:59, saueimer wrote:
Jetway JNC62K SocketAM2/AM2+ Mini-ITX
Unfortunately the NVidia MCP78S chipset is not supported yet and it is unlikely we'll support it in the future because we don't have the
needed
data sheets and programming information.
Regards, Carl-Daniel