Instrumented Trace Tips

When using _TRACE and _LOG macros in your code, consider the following:

  • Focus on one area of an application and place _TRACE and _LOG macros so that they form a flow in the Trace window. That way, you can follow the execution flow and debug the application based on missing or incorrect trace points or an abrupt end to the trace flow.
  • Use _TRACE and _LOG macros with conditional statements in your code to aid in debugging.
    Example: When a variable reaches a certain value, start logging it.

  • Leave _TRACE and _LOG macros in your code for future debugging, if this is allowable. (For Project Properties dialog, REAL ICE Category, and Trace Options Category pages, select Disable Trace Macros.)
© 2024 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.