RE: Printf doesn't result in a call to write

["Matt Gessner" <mgessner at Avidyne dot com>]

OK, as far as initialization goes, I'm clearing the bss section, so that
shouldn't be an issue.  But what crt initialization do I need to invoke?

I've got a VERY simple setup: from powerup, a bootloader starts up my
application, which is a bunch of stuff to init the processor's memory
configuration registers, relocate the code out of ROM, clear bss, and
then invoke main() which invokes __eabi and then sets up some interrupt
stuff and then runs the application.  So what crt initialization must I
also do?

> -----Original Message-----
> From: Dave Korn [mailto:dave.korn@artimi.com]
> Sent: Monday, September 11, 2006 12:42 PM
> To: Matt Gessner
> Cc: newlib@sourceware.org
> Subject: RE: Printf doesn't result in a call to write
> 
> On 11 September 2006 17:39, Matt Gessner wrote:
> 
> > I was under the impression that the \n character at the end would
bypass
> > that.
> 
>   Yeh, it should have done.
> 
> > I'll add an fflush to stdout to see if that helps.
> 
>   Particularly also check the crt initialisation is taking place
> correctly.
> 
>     cheers,
>       DaveK
> --
> Can't think of a witty .sigline today....