SPRADN5 December   2024 F29H850TU , F29H859TU-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2C28x vs C29x vs ARM Logging
  6. 3SysConfig
    1. 3.1 Start or Stop Logging
    2. 3.2 Capture Modes
    3. 3.3 Trigger for transferring Logs
  7. 4Interpreting DLT Logs
  8. 5Compiler Intrinsic
  9. 6DLT Tool
    1. 6.1 Visualization
    2. 6.2 Walkthrough on Tool
    3. 6.3 Add Logs to Application
    4. 6.4 Export DLT Log
    5. 6.5 CCS Theia
  10. 7Summary
  11. 8References

5 Compiler Intrinsic

The dedicated instructions from the C29x user guide can be abstracted by using the built-in compiler intrinsic provided in the ti-cgt-c29 compiler. Under the hood of using the built-in compiler intrinsic uses dedicated DLT instructions.

For code markers use: __builtin_c29_datalog_tag(TAG);

  • This intrinsic expects any 16-bit tag value

For data logging variables use: __builtin_c29_datalog_write(VAR);

  • This intrinsic expects any 32-bit variable
Note: Every new function scope must have at least one code marker to denote the new function scope then followed by the variables to be data logged. Only having code markers is acceptable. TI does not recommended to have no code markers in a function scope followed by variables to be data logged.