Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
Discussion Groups | LPC2000 | Question about Crossstudio stdio and __putchar
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
Question about Crossstudio stdio and __putchar - ds19968902 - Feb 15 1:48:47 2007
In Crossstudio I am including stdio.h and trying to use printf with my
own __putchar (over the uart). I successfully did this when my project
was being compiled by the c compiler. But then I switched all my files
to cpp. Now the linker error keeps stating that I must provide
__putchar even though I have one. It sounds to me as though the C++
compiler is having difficulty associating my __putchar to stdio.h
Would anyone know a way around this?
Thanks Alot!!!
Eric
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
own __putchar (over the uart). I successfully did this when my project
was being compiled by the c compiler. But then I switched all my files
to cpp. Now the linker error keeps stating that I must provide
__putchar even though I have one. It sounds to me as though the C++
compiler is having difficulty associating my __putchar to stdio.h
Would anyone know a way around this?
Thanks Alot!!!
Eric
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Question about Crossstudio stdio and __putchar - haare_in_der_dusche - Feb 15 3:15:46 2007
ds19968902 schrieb:
> In Crossstudio I am including stdio.h and trying to use printf with my
> own __putchar (over the uart). I successfully did this when my project
> was being compiled by the c compiler. But then I switched all my files
> to cpp. Now the linker error keeps stating that I must provide
> __putchar even though I have one. It sounds to me as though the C++
> compiler is having difficulty associating my __putchar to stdio.h
>
> Would anyone know a way around this?
Have you declared your "__putchar" with C linkage? Else it'll be
declared with C++ linkage, thus getting a decorated symbolic name ...
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> In Crossstudio I am including stdio.h and trying to use printf with my
> own __putchar (over the uart). I successfully did this when my project
> was being compiled by the c compiler. But then I switched all my files
> to cpp. Now the linker error keeps stating that I must provide
> __putchar even though I have one. It sounds to me as though the C++
> compiler is having difficulty associating my __putchar to stdio.h
>
> Would anyone know a way around this?
Have you declared your "__putchar" with C linkage? Else it'll be
declared with C++ linkage, thus getting a decorated symbolic name ...
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )