I believe there's commandline option for awdflash to skip checking on bios file. I cannot verify it at this moment, but try awdflash.exe /?
Good Luck!
On Monday 17 March 2008 03:15 am, Jacek Chruscik wrote:
the number 57344 is my vga bios size, you have to replace this number with the size of your vga bios (in boths places of my config: ROM_SIZE and FALLBACK_SIZE)
did that. My vga rom is f1ff.
I suggest to use awardeco or amideco tool to extract the vga bios from original bios. The RAM memory dump didn't work for me on epia.
the perl script worked for me.
After padding vgabios with zeros to 65536 bytes and setting the ROM_SIZE etc to 65536, everything compiles. I have a coreboot.rom with vga of 262144 bytes.
However testing is pending as the award util does not flash the file as it does some check on the bios file and fails with "not a valid bios file". So now I have to sort out why flashrom fails to write correctly. :-(
To recap: flashrom identifies, reads and erases the flash correctly. It also writes but the writes are garbage. I have two boards and the behaviour is the same.
-- Rgds JTD
On Tuesday 18 March 2008 02:37 am, mercury@wirebros.com wrote:
I believe there's commandline option for awdflash to skip checking on bios file. I cannot verify it at this moment, but try awdflash.exe /?
flash867.exe worked. reboot. nothing on ttyS0.
Anyway i was just being optimistic.
swap flash chip. Board still alive.
Now to check the config.lb with lspci -v. Also do i need an irq-tables.c generated for my board?
On Thursday 20 March 2008 04:52 pm, jtd wrote:
Now to check the config.lb with lspci -v. Also do i need an irq-tables.c generated for my board?
Here is the result of getpir
const struct irq_routing_table intel_irq_routing_table = { PIRQ_SIGNATURE, /* u32 signature */ PIRQ_VERSION, /* u16 version */ 32+16*5, /* There can be total 5 devices on the bus */ 0x00, /* Where the interrupt router lies (bus) */ (0x11<<3)|0x0, /* Where the interrupt router lies (dev) */ 0xc20, /* IRQs devoted exclusively to PCI usage */ 0x1106, /* Vendor */ 0x596, /* Device */ 0, /* Crap (miniport) */ { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }, /* u8 rfu[11] */ 0xb3, /* u8 checksum. This has to be set to some value that would give 0 after the sum of all bytes for this structure (including checksum) */ { /* bus, dev|fn, {link, bitmap}, {link, bitmap}, {link, bitmap}, {link, bitmap}, slot, rfu */ {0x00,(0x08<<3)|0x0, {{0x01, 0x0eb8}, {0x02, 0x0eb8}, {0x03, 0x0eb8}, {0x05, 0x00eb8}}, 0x1, 0x0}, {0x00,(0x0d<<3)|0x0, {{0x03, 0x0eb8}, {0x05, 0x0eb8}, {0x01, 0x0eb8}, {0x02, 0x00eb8}}, 0x2, 0x0}, {0x00,(0x11<<3)|0x0, {{0x00, 0x0eb8}, {0x00, 0x0eb8}, {0x03, 0x0eb8}, {0x05, 0x00eb8}}, 0x0, 0x0}, {0x00,(0x01<<3)|0x0, {{0x01, 0x0eb8}, {0x02, 0x0eb8}, {0x03, 0x0eb8}, {0x05, 0x00eb8}}, 0x0, 0x0}, {0x00,(0x10<<3)|0x0, {{0x01, 0x0eb8}, {0x02, 0x0eb8}, {0x03, 0x0eb8}, {0x05, 0x00eb8}}, 0x0, 0x0}, } };
Which is quite different from the epia and the epia-m
Don't worry, my first few builds failed (dead MB), but finally I got it working.
Post your config.lb post lspci output post your exact motherboard model and current configuration (RAM size) You can also try without vgabios, just coreboot and payload.
On Tuesday 18 March 2008 02:37 am, mercury@wirebros.com wrote:
I believe there's commandline option for awdflash to skip checking on bios file. I cannot verify it at this moment, but try awdflash.exe /?
flash867.exe worked. reboot. nothing on ttyS0.
Anyway i was just being optimistic.
swap flash chip. Board still alive.
Now to check the config.lb with lspci -v. Also do i need an irq-tables.c generated for my board?
-- Rgds JTD
-- coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On Friday 21 March 2008 12:11 am, mercury@wirebros.com wrote:
Don't worry, my first few builds failed (dead MB), but finally I got it working.
Everything builds fine. But no ouput. Running the bios with qemu -L ~ -fda fdosorig.img -nographic Serial controller not found
Post your config.lb
attached.
post lspci output
tavera:~# lspci -tvnn -[0000:00]-+-00.0 VIA Technologies, Inc. VT8623 [Apollo CLE266] [1106:3123] +-01.0-[0000:01]----00.0 VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics [1106:3122] +-0d.0 Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] +-10.0 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] +-10.1 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] +-10.2 VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] +-10.3 VIA Technologies, Inc. USB 2.0 [1106:3104] +-11.0 VIA Technologies, Inc. VT8235 ISA Bridge [1106:3177] +-11.1 VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] -11.5 VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] tavera:~#
On Sunday 23 March 2008 03:53 am, Jacek Chruscik wrote:
Hi,
your config.lb points at
chip superio/ite/it8705f
can you verify if this is actually what you have on your board?
yes. It is it8705f. verified by reading the chip marking and superiotool.
My epia has vt1211 for example. There's not much set-up needed to initialise serial port, and it's rather straight forward.
did you try to actually write it to flash and boot up,
yes. wrote the chip and verified correctly. Then booted.
or just under qemu?
Tried qemu after that as there was no serial output. The serial port is working correctly with the null modem.
On Mon, Mar 24, 2008 at 10:54:27AM +0530, jtd wrote:
or just under qemu?
Tried qemu after that as there was no serial output. The serial port is working correctly with the null modem.
Which image did you use for QEMU? coreboot v2 or v3? And which board code? The QEMU "board" or the VIA EPIA? The latter cannot work obviously, as QEMU doesn't emulate a VIA chipset, but rather Intel 440BX-like hardware.
Uwe.
-
Jacek Chruscik -
jtd -
mercury＠wirebros.com
-
Uwe Hermann