I'm trying to build a rom with filo for my tyan s2885. I'd like to write a generic build tutorial for the lay person, or at least for non-programmers (me). I have identified some general steps, and have some questions.
Some steps: ===================== Procedure 1: get a payload source, e.g. filo-trunk configure and make the payload make the payload available for Procedures 2 or 3
Procedure 2: check out coreboot-v2 source cd into coreboot-v2 directory make menuconfig make
Procedure 3: cd into targets/vendor/model edit Config.lb make
Procedure 4: Test the rom (qemu, etc) Put it in the machine and go! (flashrom)
Questions: =================== Do I have to do both Procedures 2 and 3 if kconfig works for me? And in what order?
Where is kconfig looking for payload.elf? It didn't seem to like the absolute path that I put into menuconfig. IIRC someone mentioned that it doesn't like non-'sane' paths.
Thanks for any help & suggestions.
FYI flashrom works on my board, I upgraded and verified my vendor bios with it. I'm using the push-pin method of chip-wrangling and have bought some 16Mbit flash to burn.
Mick Reed wrote:
Procedure 2: check out coreboot-v2 source cd into coreboot-v2 directory make menuconfig make
Note that this is still in alpha stage for most if not all listed boards.
Procedure 3: cd into targets/vendor/model edit Config.lb
cd ../.. into targets ./buildtarget vendor/model cd target/vendor/model
make
Do I have to do both Procedures 2 and 3 if kconfig works for me? And in what order?
No, Kconfig will replace buildtarget and Config.lb will be removed. It is a big improvement, but getting it done also requires some effort.
Where is kconfig looking for payload.elf?
Either in coreboot-v2 or in the build/ directory.
It didn't seem to like the absolute path that I put into menuconfig.
I consider that a bug then. Again, note that Kconfig does not really work completely yet. An absolute path should work there. I would like a relative path be relative to the coreboot-v2 directory rather than the build subdirectory.
In any case, to find you more about what is going wrong, you can run make V=1 to get more information. Send the output to the list and we'll try to spot the issue with the absolute path.
//Peter
On Thu, Oct 22, 2009 at 07:29:14AM +0200, Peter Stuge wrote:
Mick Reed wrote:
Procedure 2: check out coreboot-v2 source cd into coreboot-v2 directory make menuconfig make
Note that this is still in alpha stage for most if not all listed boards.
Yep.
Where is kconfig looking for payload.elf?
Either in coreboot-v2 or in the build/ directory.
Top-level coreboot-v2 directory works (don't know about build/).
It didn't seem to like the absolute path that I put into menuconfig.
I consider that a bug then. Again, note that Kconfig does not really work completely yet. An absolute path should work there.
It does, I just tested on trunk.
I would like a relative path be relative to the coreboot-v2 directory rather than the build subdirectory.
That's the case in trunk, works fine.
I'm trying to build a rom with filo for my tyan s2885. I'd like to write a generic build tutorial for the lay person, or at least for non-programmers (me). I have identified some general steps, and have some questions.
We'll have such a generic HOWTO in the wiki as soon as kconfig becomes the default (no need to write something for the old system, it'll be gone soon).
Here's the current (work in progress) page:
http://www.coreboot.org/Build_HOWTO
Please let us know if there is missing information or if you have suggestions for improvements (but note that kconfig is a moving target right now, one or two things may change until we make it the default).
Procedure 4: Test the rom (qemu, etc) Put it in the machine and go! (flashrom)
You cannot test an image meant for real hardware in QEMU. Only the "Emulation / QEMU" mainboard works in QEMU. And the QEMU "mainboard" won't work on any actual hardware either, of course.
FYI flashrom works on my board, I upgraded and verified my vendor bios with it.
Tyan S2885? We don't seem to list that on the flashrom page, yet. Can you post "flashrom -V" output to the flashrom mailing list for reference? Did flashrom say "VERIFIED" after the write? Thanks!
Uwe.
-
Mick Reed -
Peter Stuge -
Uwe Hermann