Problems with sprintf and libgcc.a

Mayank Kaushik · 2005-04-10T14:53:44+00:00

Hi everyone,im using "toolchain" to compile asimple program for an ARM920T based microcontroller (AT91RM9200). Thedevelopment system is running Fedora Core 3.i have not been able to use the "sprintf" function..the program doesnot compile if i do so. here are the details of my problem:************************************************************code snippet of my main.c program (where im calling sprintf):==============================#include.sprintf( buf, "This is a test %d one and %d two", 420, 840 );.==============================This is the error i get:==============================.arm-elf-gcc -c -Os -DAT91RM9200 -mlittle-endian -mapcs-32 -mcpu=arm920t-fno-inline -o "init.o" "init.c"arm-elf-gcc -c -Os -DAT91RM9200 -mlittle-endian -mapcs-32 -mcpu=arm920t-fno-inline -o "main.o" "main.c"arm-elf-ld -L --cref -Map -EL -T./ -o"./Mayank/Output/BasicBootDebug.elf" cstartup.o init.o main.oinit.o(.text+0x100): In function `AT91F_US_Baudrate':: undefined reference to `__udivsi3'init.o(.text+0x10c): In function `AT91F_US_Baudrate':: undefined reference to `__umodsi3'init.o(.text+0x120): In function `AT91F_US_Baudrate':: undefined reference to `__udivsi3'init.o(.text+0x134): In function `AT91F_US_Baudrate':: undefined reference to `__udivsi3'init.o(.text+0x26c): In function `AT91F_CheckPLL_FrequencyRange':: undefined reference to `__divsi3'main.o(.text+0x60): In function `main':: undefined reference to `sprintf'make: *** [Mayank/Output/BasicBootDebug.elf] Error 1==============================I had searched the net and found that undefined references to`__divsi3` and `__umodsi3' are caused because of problems or versionmismatches related to libgcc.a . Heres my linker script:==============================GROUP("/home/guest/mayank_arm/gnuarm-3.4.3/arm-elf/lib/libc.a""/home/guest/mayank_arm/gnuarm-3.4.3/lib/gcc/arm-elf/3.4.3/libgcc.a")MEMORY{ ram : ORIGIN = 0x200000, LENGTH = 0x3000 /*12kb*/}SECTIONS{ .text : { __stext_start = . ; /*Start of the text section*/ *(.text) ...

Apr 10, 2005 21 Replies

Rate this thread:

Mayank Kaushik 21 years ago

Im the OP, i would like to reiterate the following comment:

produce.

Im a senior undergrad who has just started working with the GNU-ARM toolchain. Ive found it difficult to understand what sections the compiler would produce, and how to map them in the appropriate output section (.text or .data, since these are the only two i would extract from the *.elf file to make a final *.bin file that would be loaded onto the chip). Would someone please help me with that.

Regards, Mayank

Vote

Tauno Voipio 21 years ago

Mayank,

mail me with a good return address.

Correct the address in my sig in the obvious way.

Tauno Voipio tauno voipio (at) iki fi

Vote

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required