RE: Difference in assemble language

[Daniel dot Andersson at combitechsystems dot com]

Hi,

I am slightly coming around the assembler problem now by manually editing
the files. However, when i compile my files a get some strange problem (se
below)

bash.exe-2.04$ make
arm-elf-gcc -mcpu=arm7tdmi                       -lgcc -nostdlib -o
LED_BLINK led_blink.o ../../periph/pio/lib_pio.o ../../periph/power_savi
ng/lib_ps40800.o ../../periph/aic/lib_aic.o ../../periph/ebi/lib_ebi.o
../../periph/mem/ram_test.o ../../periph/mem/relocate.o ../../periph/
special_function/lib_sf.o ../../periph/spi/lib_spi.o
../../periph/stdc/lib_err.o ../../periph/timer_counter/lib_tc.o
../../periph/usart/lib_
usart.o ../../periph/watchdog/lib_wd.o ../../periph/watchdog/irq_wd.o
-Tlinkerscript.ld -lgcc
crt0.o: In function `have_jeeni0':
crt0.o(.text+0xc0): undefined reference to `memcpy'
crt0.o(.text+0xc0): relocation truncated to fit: R_ARM_PC24 memcpy
crt0.o: In function `have_jeeni1':
crt0.o(.text+0xdc): undefined reference to `memset'
crt0.o(.text+0xdc): relocation truncated to fit: R_ARM_PC24 memset
crt0.o(.text+0xf0): undefined reference to `exit'
crt0.o(.text+0xf0): relocation truncated to fit: R_ARM_PC24 exit
led_blink.o: In function `delay':
/arm/software/projects/led_blink_eb40/led_blink.c:47: undefined reference to
`PIO_DESC'
led_blink.o: In function `main':
/arm/software/projects/led_blink_eb40/led_blink.c:100: undefined reference
to `PIO_DESC'
../../periph/watchdog/irq_wd.o: In function `PtWDBase':
../../periph/watchdog/irq_wd.o(.text+0x0): undefined reference to `WD_BASE'
/tools/H-i686-pc-cygwin/lib/gcc-lib/arm-elf/2.95.2/libgcc.a(__main.o): In
function `__do_global_ctors':
__main.o(.text+0xbc): undefined reference to `atexit'
__main.o(.text+0xbc): relocation truncated to fit: R_ARM_PC24 atexit
collect2: ld returned 1 exit status
make: *** [LED_BLINK] Error 1 


....i think it maight be some linking problem caused by my makefile. Since i
am quite now to this i have encountered some difficulty when i am setting
the options in the makefile. What is for example the relationship between
the crt0.s file and the cstartup_angel.s and the stdlibs....? Can anybody
help me to setup the makefile so that it performs the way i want?

I have includeed the files that causes the errors in the output from gcc.

Thanks!

/Daniel




-----Original Message-----
From: Richard Earnshaw [mailto:rearnsha@arm.com]
Sent: den 28 mars 2001 11:54
To: Andersson Daniel
Cc: Richard.Earnshaw@arm.com; crossgcc@sourceware.cygnus.com
Subject: Re: Difference in assemble language 


> Hi Richard,
> 
> I have just come to the knowledge that i cannot use files from ARM STD
when
> i am building an application with GNU-tools. After i corrected the below
> problem a lot of other problem appeared. It seams that i have two option.
> One is to re-write the cstartup_angel.s that i am trying to assemble so it
> complies with GNU tools. The other is to find a project that is up and
> running and take the startup-file from there. Do you know of any such
> project? 

You could look at the startup files that come with Newlib, or those that 
come with ecos.  Both of those should work with GAS.

> 
> Currently i am setting up an AT91 EB40 board with all its registers
> 
> As to the below mail I tried with the following:
> 
> arm-elf-as -o cstartup_angel.o cstartup_angel.S
> 
> .....but unfortunately i got the same errors i.e 

Some of the errors are the same (those referring to unrecognized 
directives).  But the real instructions are recognized now :-)

> Isn't there a GNU assembler that can take an ARMASM-file as an input? 

No.  Unfortunately the syntax is so radically different that it would be 
completely non-trivial to write a parser for GAS that could handle it.  
(so there's a challenge for someone ;-).

crt0.S

makefile

irq_wd.s

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com