Hello Simon,
Thank you. The example helped me. I am glad that I caused to a little improvement to LwIP. Yacob Hassidim. From: lwip-users [mailto:[email protected]] On Behalf Of [email protected] Sent: Sunday, February 25, 2018 8:57 PM To: Mailing list for lwIP users <[email protected]> Subject: Re: [lwip-users] LwIP configuration for directing LWIP_DEBUGF to user function On 25.02.2018 16:28, Yacob Hassidim wrote: 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. Exactly. 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)? Right, I wasn't aware of the win32 port not doing this. I've added an example now, have a look at the latest contrib code in git (e.g. via gitweb). Simon
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
