Trying to work through the helloworld tutorial and hit a snag while trying to "Build All User Applications" in EDK:
mb-gcc -O2 code/HelloWorld_sw.c code/HelloWorld.c code/co_init.c -o TestApp_Peripheral/executable.elf \
-mno-xl-soft-mul -Wl,-T -Wl,TestApp_Peripheral/src/TestApp_Peripheral_LinkScr -g -I./microblaze_0/include/ -L./microblaze_0/lib/ \
-xl-mode-executable \
/cygdrive/c/EDK/gnu/microblaze/nt/bin/../lib/gcc/microblaze/3.4.1/../../../../microblaze/bin/ld.real: region ilmb_cntlr is full (TestApp_Peripheral/executable.elf section .text)
/cygdrive/c/EDK/gnu/microblaze/nt/bin/../lib/gcc/microblaze/3.4.1/../../../../microblaze/bin/ld.real: region ilmb_cntlr is full (TestApp_Peripheral/executable.elf section .text)
/cygdrive/c/EDK/gnu/microblaze/nt/bin/../lib/gcc/microblaze/3.4.1/
../../../../microblaze/bin/ld.real: section .rodata [00000000 -> 000001ad] overlaps section .text [00000000 -> 000022c7]
/cygdrive/c/EDK/gnu/microblaze/nt/bin/../lib/gcc/microblaze/3.4.1/../../../../microblaze/bin/ld.real: section .sdata2 [000001b0 -> 00000347] overlaps section .text [00000000 -> 000022c7]
/cygdrive/c/EDK/gnu/microblaze/nt/bin/../lib/gcc/microblaze/3.4.1/../..
/../../microblaze/bin/ld.real: section .data [00000348 -> 00000a53] overlaps section .text [00000000 -> 000022c7]
/cygdrive/c/EDK/gnu/microblaze/nt/bin/../lib/gcc/microblaze/3.4.1/../../../../microblaze/bin/ld.real: section .sdata [00000a54 -> 00000a5b] overlaps section .text [00000000 -> 000022c7]
collect2: ld returned 1 exit status
make: *** [TestApp_Peripheral/executable.elf] Error 1
Running:
Impulse 2.20.d.3
EDK 7.1.02
ISE 7.1.04
Brett Boren
University of Alabama, Huntsville
newbie: error in helloworld for ublaze demo
Started by Brett, Jan 16 2007 02:40 PM
2 replies to this topic
#1
Posted 16 January 2007 - 02:40 PM
Brett Boren
Computer Engineering Graduate Student
University of Alabama, Huntsville
Computer Engineering Graduate Student
University of Alabama, Huntsville
#2
Posted 17 January 2007 - 06:15 PM
Hi Brett,
It looks like you'll have to tell the linker to put the executable in a larger memory. Right-click the application in XPS and select "Generate linker script". Choose a different memory to store the .text and other sections in.
If that doesn't work, you may have to recreate the XPS project from the beginning and specify larger sizes for the ilmb_cntlr memory.
Regards,
Ralph
It looks like you'll have to tell the linker to put the executable in a larger memory. Right-click the application in XPS and select "Generate linker script". Choose a different memory to store the .text and other sections in.
If that doesn't work, you may have to recreate the XPS project from the beginning and specify larger sizes for the ilmb_cntlr memory.
Regards,
Ralph
Ralph Bodenner
Impulse Accelerated Technologies, Inc.
Impulse Accelerated Technologies, Inc.
#3
Posted 02 February 2007 - 07:12 AM
QUOTE (RalphBodenner @ Jan 17 2007, 08:15 PM) <{POST_SNAPBACK}>
Hi Brett,
It looks like you'll have to tell the linker to put the executable in a larger memory. Right-click the application in XPS and select "Generate linker script". Choose a different memory to store the .text and other sections in.
If that doesn't work, you may have to recreate the XPS project from the beginning and specify larger sizes for the ilmb_cntlr memory.
Regards,
Ralph
It looks like you'll have to tell the linker to put the executable in a larger memory. Right-click the application in XPS and select "Generate linker script". Choose a different memory to store the .text and other sections in.
If that doesn't work, you may have to recreate the XPS project from the beginning and specify larger sizes for the ilmb_cntlr memory.
Regards,
Ralph
Exactly. Memory was too small. My subject line says it all...
Brett Boren
Computer Engineering Graduate Student
University of Alabama, Huntsville
Computer Engineering Graduate Student
University of Alabama, Huntsville
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












