[En-Nut-Discussion] NutHeapAvailable() question

Harald Kipp harald.kipp at egnite.de
Fri Sep 29 18:00:06 CEST 2006


Alexander,

...or a problem of the uart driver...

Another thing you could do is to check the .map file.

Here's the API tree for fprintf:
http://www.ethernut.de/api/group__xgCrtStdio.html

Down to _write, all routines should be supplied by libnutcrt.a and
must not be provided by any WinAVR library. The final dev_write
is the link to the UART driver, typically contained in libnutarch.a.

Btw. how does your fopen() look like?

Harald


At 11:28 29.09.2006 -0400, you wrote:

>Then I tried
>int amama = 12;
>fprintf(uart, "\n\r%d, %d, %d\n\r", amama, amama, amama );
>and also got
>-1, 12, 12
>So the reason is not in NutHeapAvailable() but in some fprintf issues.
>Regards
>Alex.




More information about the En-Nut-Discussion mailing list