Hi everyone, I have got a Olimex SAM7s256 ARM board. I am new to the field of embedded programming. I am using Ubuntu 10.04. I installed GCC 4.2.2 and GNU assembler, linker and obj copy all 2.18 versions. For writing in the board's RAM (ARM's ram) I used a custom made SAM- Boot utility called Sam_I_Am from the following website http://claymore.engineer.gvsu.edu/~steriana/Software/ It is a command line program and I was able to connect to the board. Now I downloaded a LED blinking program and tried to compile and run to get the HEX file to dump in the board. When I run the 'make' I get the following error, error: no memory region specified for loadable section `.text.1' make: *** [blink.elf] Error 1 Can anyone help me in that? I am not able to understand this. In some other forums it is given that it is a bug w.r.t GCC 4.2.2. When tried to search for 'text.1' it is shown in many discussions that the linker will break the .text into .text.1 and .text.2 if it is more than 50K in size. Is it the case here? I am really new to this and it is one of knowing whether my board in conjunction with the boot loader and linux works after I purchased it. Any suggestion here will be very much appreciated. I am attaching both the make file and the linker file for clarification.
The linker-script looks too simple. There are no input-sections (.text) given in in the defintion for the .text output-section. Get Atmel's software-package for the AT91SAM7S-EK, as far as I remember the packages includes linker-scrips, makefiles, startup-code for both "targets" FLASH and RAM.
Hi, The same error got solved when I downgraded GCC to 4.1.1 and bin-utils to 2.17. I was told by come other person that it is due to the problem with GCC 4.2.2. Is it so? If so then is there a fix to this problem? Thank you.
Muthukrishnan Neelakandan wrote: > Hi, > The same error got solved when I downgraded GCC to 4.1.1 and bin-utils > to 2.17. > I was told by come other person that it is due to the problem with GCC > 4.2.2. Is it so? Maybe the older versions of the toolchains just had some build-in defaults to handle the .text/.data/.bss input-sections during linkage. I have never seen a linker-script that has been reduced like the one given in the attachment. >If so then is there a fix to this problem? Try to place the input-section names for .text/.data/.bss in the defintions for the output-sections in the linker-script. You may use the linker-scripts from Atmel's software-package or the default linker-script (arm-*-ld --verbose) as template.