Hm...
thats strange... yabel should print some output before it even touches the copied ROM...
did you try a clean rebuild after changing the CONFIG values ?
Pattrick
On Wed, Jun 24, 2009 at 2:40 PM, Thomas JOURDANthomas.jourdan@gmail.com wrote:
Hi Pattrick
With Yabel I have the following error : CBFS: Could not find file pci102b,2527.rom In cbfs, rom address for PCI: 03:00.0 = 00000000 On card, rom address for PCI: 03:00.0 = fe800000 copying VGA ROM Image from fe800000 to 0xc0000, 0x9000 bytes Unexpected Exception: 0 @ 10:0011bfa1 - Halting Code: 0 eflags: 00010046 eax: 00000001 ebx: 00000061 ecx: 00000000 edx: 00000000 edi: 00000003 esi: 00000000 ebp: 00155abc esp: 00155a98
Setting CONFIG_YABEL_DEBUG_FLAGS to 0x9 (or 0x31FF) won't print more traces.
Regards, Thomas
2009/6/24 Pattrick Hueper phueper@hueper.net:
Hi,
On Tue, Jun 23, 2009 at 8:42 PM, Thomas JOURDANthomas.jourdan@gmail.com wrote:
- vga rom -> The evaluation board comes with a PCIe 1x Matrox G550
graphics card. Coreboot fails to execute the vga rom (either x86emu, yabel or real mode). There is an exception 0x06 and everything will freeze. It could be the loadall instruction
i would be interested in a log with CONFIG_YABEL_DEBUG_FLAGS=0x9 to see whats happening in yabel...
Regards, Patty