[coreboot] Problems compiling H8DMR_FAM10 because of section overlaps.

Knut Kujat knuku at gap.upv.es
Wed Dec 16 15:30:34 CET 2009


Hello,

I'm now trying to get coreboot working on a Supermicro H8QME-2+ board.
This board is really similar to the H8DMR/H8DMR_FAM10 boards already
supported by coreboot. Since my board is populated with 4 Opteron family
10 processors I thought of trying to compile  the H8DMR_FAM10 to get a
rom and flash it to board to see what happens. But compiling I got the
section overlaps error since its recommended to increase the
ROM_IMAGE_SIZE I added the following lines to Kconfig:

config ROM_IMAGE_SIZE
        hex
        default 0x15800
        depends on BOARD_SUPERMICRO_H8DMR_FAM10
than a made a make distclean, make config, make and got following message:

/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
section .reset [00000000fffffff0 -> 00000000ffffffff] overlaps section
                                             .rom [00000000ffff5800 ->
000000010000929f]
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
/home/knut/Documents/Supertrunk4978/build/coreboot: section .reset vma
0xfffffff0 overlaps previous sections

Taking a good look at the ranges I increased ROM_SIZE to 0x100000000 and
it worked but not at all because:

/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
section .id [00000001fffeff58 -> 00000001fffeff7f] overlaps section
                                          .rom [00000001fffe0000 ->
00000001ffff3a9f]
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
/home/knut/Documents/Supertrunk4978/build/coreboot: section .id vma
0x1fffeff58 overlaps previous sections
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
/home/knut/Documents/Supertrunk4978/build/coreboot: section .romstrap
vma 0x1fffeffa0 overlaps previous sections

now it's .id that overlaps section .rom and not .reset :(

Now I followed the instructions on the coreboot side about section
overlaps and I did this:

00000001ffff3a9f-00000001fffeff58= 3b47 => 3b48

config ROM_IMAGE_SIZE
        hex      
        default 0x100003b48
        depends on BOARD_SUPERMICRO_H8DMR_FAM10
make distclean, make config, make and got


/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
section .id [00000001ffff3aa0 -> 00000001ffff3ac7] overlaps section
                                          .rom [00000001fffe3b48 ->
00000001ffff75ef]
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
/home/knut/Documents/Supertrunk4978/build/coreboot: section .id vma
0x1ffff3aa0 overlaps previous sections
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld:
/home/knut/Documents/Supertrunk4978/build/coreboot: section .romstrap
vma 0x1ffff3ae8 overlaps previous sections
 I can see that no only the .rom range changed but also the .id range
should it do that?? So what can I do to make it work?

A little frustrated I successfully compiled the H8DMR rom and flashed it
into the bios chip thinking that at least some debug messages should
appear since on both boards the way to the winbond chip is the same but
I only got some ????·$·)"?· rubbish. I of course tested the serial
before and it worked fine.

thanks,
Knut Kujat.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20091216/3a5c0296/attachment.html>


More information about the coreboot mailing list