Lpc2000

miruffer wrote:

>Hi,
>
>I have big problems with the gcc-linker. Last week I compiled the
>newest version of gcc(4.0.2), binutils(2.16.1) and newlib(1.13) under
>linux debian. Before I worked with WinARM(gcc 4.0.0).
>
>I tried to compile my project with the new toolchain. No warnings no
>errors. But the printf didn't work. To let the printf work via uart1 I
>have initialized it and have rewritten some function of the libc:
>_write_r and _read_r. Everything works well with WinARM. Now I looked
>in the assembler code compiled with the new toolchain and the linker
>has used the _write_r from libc and not my new one.
>
>Can I force the linker to use my new one?
>
>  
>
Sure, get a large hammer...  I would look to your library itself, you 
have to turn on some options within newlib to compile it out into stubs 
for some of the I/O code.  Take a look at the scripts I use to build my 
development environment with, I use the newlib stubs to do char I/O from 
the library: 


http://www.openhardware.net/?title=ARM%20Thumb%20tools%20for%20LPC2000&dir=ArmTools&file=ThumbToolchain.html

Regards,

TomW

-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------