|
From: | Noam Weissman |
Subject: | Re: [lwip-users] LwIP configuration for directing LWIP_DEBUGF to user function |
Date: | Sun, 25 Feb 2018 18:38:14 +0000 |
Hi Yacob,
Redirecting may be different from IDE to IDE. Redirecting is not only for printf.
In general you should define the macro PUTCHAR or similar to some low level handling depended on your own hardware.
Here are some examples I found, for KAIL: http://www.keil.com/forum/60531/ For IAR:
https://stackoverflow.com/questions/23388659/redirect-printf-to-console-i-o-on-iar-embedded-workbench BR,
From: lwip-users <lwip-users-bounces+address@hidden> on behalf of Yacob Hassidim <address@hidden>
Sent: Sunday, February 25, 2018 5:28 PM To: 'Mailing list for lwIP users' Subject: Re: [lwip-users] LwIP configuration for directing LWIP_DEBUGF to user function Helo Simon,
Thank you for referring me to lwip-contrib.
I downloaded the version contrib-2.0.1.
I found that LWIP_DEBUG is defined as compilation parameters of project layer.
I didn’t find mention of LWIP_PLATFORM_DIAG.
I use LwIP as part of ST CubeMx environment that defines LWIP_PLATFORM_DIAG in cc.h as the following: #define LWIP_PLATFORM_DIAG(message) printf message
Can you please advise me how should I direct the “printf message” to serial_write(char *message_string)?
Yacob Hassidim.
From: lwip-users [mailto:lwip-users-bounces+address@hidden
On Behalf Of address@hidden
On 25.02.2018 13:18, Yacob Hassidim wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |