Hello the Design Team,
I am not sure to understand your question, could you please detail a bit more your need ?
Let me anyway do some few comments.
First, the FW is totally independent from MW and Host parts, it is self sufficient and can work by itself.
Second, AFAIU you are working in FW part only, the Host part is consequently not needed, so for better performance you can remove STUHFL_HOST_COMMUNICATION from project defines.
Third, the main advantage of STUHFL Api is that it has exactly the same behavior between Host and FW parts. So you can develop and fine tune your intended FW application on Host side (remind to re-enable STUHFL_HOST_COMMUNICATION at this stage 😉 ) with all high level host debug tools that are available on the market and then port directly the code as is to the FW part.
Fourth, a TrueStudio project is provided with the SDK.
TrueStudio provides all means for FW debugging including the SWD interface (cf Atollic, https://info.atollic.com/hs-fs/hub/460400/file-2413851466-pdf/Whitepapers/Atollic_Serial_wire_viewer_realtime_tracing_whitepaper.pdf:(
SERIAL WIRE DEBUG (SWD) Serial Wire Debug (SWD) is a debug port similar to JTAG, and provides the same debug capabilities (run, stop on breakpoints, single-step) but with fewer pins. It replaces the JTAG connector with a 2-pin interface (one clock pin and one bi-directional data pin). The SWD port itself does not provide for real-time tracing.
Moreover, please refer to the Atollic discussion around SWD for more details: https://forum.atollic.com/viewtopic.php?t=1612
best regards,
Cedric.
