Enabling debug messages

[SytechDesigns]

In the normal build debug_printf messages are using the ITM0 channel and show up in the uVision debugger. But there is a lot of debug data going out as hal_printf messages.
How do we monitor hal_printf messages and is it possible to send these to ITM0.
In lwip there are also levels of lwip debug messages - how do we enable these and can they be set up to come out of itm0 ( I am assuming we change a define in lwipopts.h)
If we have to use mfdeploy and 'connect to device' - only a few messages come thru - how do we enable more debug messages here - just doing a flavour-debug build does not seem to change much.

[smaillet-ms]

There are several layers of messages in NETMF not only from the framework itself but the additional libraries such as the LWIP stack. The distinction between debug_printf and hal_printf is subtle but important. To understand that consider the case where the transport used for MFDeploy is TCP/IP. When debugging the Ethernet driver or the LWIP stack itself, you can't use TCP/IP to send debug messages about the TCP/IP stack. This is why there are multiple "channels" of debug information. One is used for early boot/startup and communications transport debugging (by default on the MCBSTM32F400 that is ITM0). All others go through the MFDeploy transport.