• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 549 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MCU-PLUS-SDK-AM263X: SysConfig DPL (Driver Porting Layer) Debug Log

TollMan
Intellectual 485 points
Part Number: MCU-PLUS-SDK-AM263X
Other Parts Discussed in Thread: SYSCONFIG

I am fairly new to the TI parts, and am trying to educate myself by running and analyzing mcu_plus_sdk_am263x example projects. 

When I look into the SysConfig Driver Porting Layer section I see checkboxes for:

  • Enable Error Log Zone
  • Enable Warning Log Zone
  • Enable Info Log Zone
  • Enable CCS Log
  • Enable Memory Log

I tried searching for where configurations these are documented but could not find it.

Can somebody point me to where to find the documentation?

  • 0
    TI__Guru 55045 points

    Hi Tollman,

    You can find the Debug_log related document at: AM263x MCU+ SDK: Debug (ti.com)

    Best regards,

    Ming

  • 0 in reply to Ming Wei
    Intellectual 485 points

    Thanks Ming Wei,

    I think I can answer my questions by using:

      AM263x MCU+ SDK: Debug (ti.com)

    and the DebugP_8h module API reference here:

      mcu_plus_sdk_am263x_09_01_00_41/docs/api_guide_am263x/DebugP_8h.html

    Since I'm new to the TI ecosystem I want to make sure there isn't additional resources.

    It seems that calling these functions:

      DebugP_log(format, ...)
      DebugP_logError(format, ...)
      DebugP_logWarn(format, ...)
      DebugP_logInfo(format, ...)

    ... will conditionally print based on the SyConfig configuration.

    Is this accurate?

    Also, If you need to log from multiple cores, you should use shared memory writers and a reader that calls the appropriate log function.

    Is this accurate?

    Is Control Logging documented here:

    AM263x MCU+ SDK: Control logging

    ... a different, and more complex implementation of DebugP?

    Can DebugP, and Control Logging coexist without a large effort?