Tracing/Debugging Interface. More...
Topics | |
Tracing/Debugging Types | |
Referred types used by Tracing/Debugging Interface. | |
Macros | |
#define | UCS_TR_INFO |
Trace macro to capture trace info events. | |
#define | UCS_TR_ERROR |
Trace macro to capture trace error events. | |
#define | UCS_TR_SIZE_BUFFER 256 |
Defines the needed buffer size to decode a trace entry. | |
Callback Functions | |
typedef void(* | Ucs_DebugErrorMsgCb_t )(Msg_MostTel_t *msg_ptr, void *user_ptr) |
Optional callback function used to debug received raw messages with OpType UCS_OP_ERROR and UCS_OP_ERRORACK. | |
Tracing/Debugging Interface.
The UCS Trace Interface is intended for debugging and logging purpose. There are 2 different trace options:
info
and error
. Each trace class can be activated by defining the respective macro UCS_TR_INFO UCS_TR_ERROR in the configuration header file ucs_cfg.h
. While the info
class is intended only for debugging purpose during development, the error
class can also be active for logging purpose in a production system.