Not a dumb question, and yes I've done a lot of work with the examples,
although none of them use 'printf'. I wrote a set for the STM32F429 and the
-Disco board [its a branch in my copy of the examples repo] and in those
and others I was using my own handrolled gets() and puts(), getc(), and
putc() equivalents. The bug was, as you spotted, the lack of a \n and the
fact that by default stdio was buffering to stdout.
I'm looking at what it will take to get rid of the custom startup code in
libopencm3 and just use the ARM supplied startup code in the GCC toolkit.
--Chuck
On Fri, May 30, 2014 at 12:25 AM, <[email protected]> wrote:
>
>
> On 30 May 2014 08:07:41 BST, Chuck McManis <[email protected]>
> wrote:
> >So I was looking at the newlib nano code and thinking "Oh cool, I can
> >use
> >printf" and have had some issues getting it to work. An example repo is
> >here: https://github.com/ChuckM/retarget-hang which demonstrates the
> >problem on the STM32F4-Butterfly with the Embest BaseBoard
>
> Dumb question but did you look at the libopencm3-examples? They have code
> that does more or less what your example does. The code for
> STM32F4Discovery should run on most F4 series boards.
>
> PS Your printf has no \n so you might find studio buffering stops the
> characters from being issued to _write (normal newlib has this, not sure
> about nano)
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
libopencm3-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
