Stuck. Compile error with a clean tree.

[Adam Talbot]

Any one have an idea on this error?
I grab a new copy of the freebios2 tree.

cvs -d:pserver:[e-mail]:/cvsroot/freebios login
cvs -z3 -d:pserver:[e-mail]:/cvsroot/freebios co
freebios2

cd ~/freebios2/targets/
./buildtarget digitallogic/adl855pc
cd digitallogic/adl855pc/adl855pc
make

gcc -m32 -nostdlib -nostartfiles -static -o linuxbios -T ldscript.ld crt0.o
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/../../../../i686-pc-linux-gnu/bin/l
d: section .reset [00000000fffdfff0 -> 00000000fffdffff] overlaps section
.rom [00000000fffd54f8 -> 00000000fffe686f]
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/../../../../i686-pc-linux-gnu/bin/l
d: section .id [00000000fffdffce -> 00000000fffdffef] overlaps section .rom
[00000000fffd54f8 -> 00000000fffe686f]
collect2: ld returned 1 exit status
make[1]: *** [linuxbios] Error 1
make[1]: Leaving directory
`/root/freebios2/targets/digitallogic/adl855pc/adl855pc/normal'
make: *** [normal/linuxbios.rom] Error 1

Here I stand stuck. fixing memory problems is beyond my C skill's
-Adam Talbot

[Ronald G. Minnich]

Adam, I just committed my changes and the adl855pc builds with same error.

The problem is simple: the debug levels are so high that our code is
getting too big.

I will try to fix this monday. Looks like recent changes made linuxbios 
grow a bit.

ron

"Ronald G. Minnich"  writes:
> Adam, I just committed my changes and the adl855pc builds with same error.
>
> The problem is simple: the debug levels are so high that our code is
> getting too big.
>
> I will try to fix this monday. Looks like recent changes made linuxbios 
> grow a bit.

Can you bump up ROM_IMAGE_SIZE by a small amount to avoid this?

I wish I knew a way to implement a grow down segment in LD.

Eric

[Ronald G. Minnich]

On Mon, 29 Nov 2004, Eric W. Biederman wrote:
> I wish I knew a way to implement a grow down segment in LD.

I worry that we're asking LD to do more than it should be asked to do.

ron

[Adam Talbot]

Well if I up my ROM_IMAGE_SIZE, it does go through and compile the
digitallogic/adl855pc with out any errors... Rebuilding my configs for my
board, I will get back to you in a few hours.
-Adam Talbot

----- Original Message ----- 
From: "Ronald G. Minnich" 
To: "Eric W. Biederman" 
Cc: "Adam Talbot" ; 
Sent: Monday, November 29, 2004 12:14 PM
Subject: Re: Stuck. Compile error with a clean tree.
> On Mon, 29 Nov 2004, Eric W. Biederman wrote:
> > I wish I knew a way to implement a grow down segment in LD.
>
> I worry that we're asking LD to do more than it should be asked to do.
>
> ron

[Adam Talbot]

Woot!!!
It compiles and boot, kinda.  The compile finishes with out any errors, but
when I go to boot the system all I get is garbage on the minicom screen.
Same with hyperterm. I have seen this out put in minicom before, simple fix,
set minicom to the right speed ( 115200 8N1, no hard/software flow control).
I when through all speed, it still does not like me. Any ideas?

my current config:

target lv671
mainboard commell/lv671

option ROM_SIZE=524288

romimage "normal"
        option USE_FALLBACK_IMAGE=0
        option ROM_IMAGE_SIZE=0x15000
        option LINUXBIOS_EXTRA_VERSION=".0Normal"
        payload /etc/hosts
end

romimage "fallback"
        option USE_FALLBACK_IMAGE=1
        option ROM_IMAGE_SIZE=0x15000
        option LINUXBIOS_EXTRA_VERSION=".0Fallback"
        payload /etc/hosts
end

buildrom ./linuxbios.rom ROM_SIZE "normal" "fallback"

[Ronald G. Minnich]

that's odd, in the adl855pc I got output just fine.

For the heck of it, build an adl855pc target and see if you get the same 
problem.

ron

[Adam Talbot]

Clean compile of the adl855pc.  I changed 2 lines in the config and added
one.

added:        option ROM_SIZE=524288
normal,
changed:     option ROM_IMAGE_SIZE=0x10000    to    option
ROM_IMAGE_SIZE=0x15000
fallback,
changed:     option ROM_IMAGE_SIZE=0x10000    to    option
ROM_IMAGE_SIZE=0x15000

Still get garbage to the screen... Bad cable?  Switched cables, same.  Idea,
added console redirect to my grub.conf set the speed to 115200 8n1, works
fine.  Hummm
What does it take to get the onboard VGA running? Can you give me a quick
"how to"?
-Adam Talbot

----- Original Message ----- 
From: "Ronald G. Minnich" 
To: "Adam Talbot" 
Cc: 
Sent: Monday, November 29, 2004 1:47 PM
Subject: Re: Stuck. Compile error with a clean tree.
> that's odd, in the adl855pc I got output just fine.
>
> For the heck of it, build an adl855pc target and see if you get the same
> problem.
>
> ron

[Ronald G. Minnich]

On Mon, 29 Nov 2004, Adam Talbot wrote:
> What does it take to get the onboard VGA running? Can you give me a quick
> "how to"?

there's nothing quick about vga. stick to serial. YOur problems are in the 
dram, so stay with that for now.

ron

[Adam Talbot]

dram issue's, where should I start hunting?
-Adam Talbot
----- Original Message ----- 
From: "Ronald G. Minnich" 
To: "Adam Talbot" 
Cc: 
Sent: Monday, November 29, 2004 2:21 PM
Subject: Re: Stuck. Compile error with a clean tree.
> On Mon, 29 Nov 2004, Adam Talbot wrote:
> > What does it take to get the onboard VGA running? Can you give me a

quick
> > "how to"?
>
> there's nothing quick about vga. stick to serial. YOur problems are in the
> dram, so stay with that for now.
>
> ron

[Ronald G. Minnich]

On Mon, 29 Nov 2004, Adam Talbot wrote:
> dram issue's, where should I start hunting?

start with the l440gx data book from developer.intel.com, it has a nice 
overview of how to turn on SDRAM. Then read about DDR which is on that 
board. Then read the e7501 code which turns on that part. Then read teh 
855GME manual.

ron