• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 331 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.

Query regarding debugging setup for DM816x on the iCont side

Preeti Joshi
Prodigy 120 points

Hi,

I want to enable debugging setup for DM816x EVM on the iCont side.

As of now, on the iCont side, the source code is in release mode with -o3 optimization level and occupying almost full ITCM available size. It is building fine.

But, I want to debug some files for which I have enabled -g option, but I am getting undefined symbols error.

Kindly let me know the procedure to enable debugging on the iCont side. Do I need to do some additional settings or changes for enabling -g option for specific files on the iCont side.

Thanks..

  • 0
    TI__Expert 5000 points

    Please share the exact error what you are getting.

    Also the way to debug is make few file built with -g but the problem becomes overall exectables/binary size of iCOnts increases which would be tough to fit in ITCM.

    So for that one might need to build some more files in thumb mode so that overall size fits in ITCM.

    Or other way would be disable few flows in encoder/decoder which are not used/relevent for the current issue. For doing this one should have good knowledge of standard and code base too.

    Regards,

    Venugopala Krishna 

  • 0 in reply to Venugopala
    Prodigy 120 points

    Thanks, your suggestion helped. Now, I am able to build the code on the iCont side by enabling -g option for few files & enabled thumb mode for most of the files.

    But, by enabling thumb mode, apart from code size reduction, will it impact the output or any other implications??

     

  • 0 in reply to Preeti Joshi
    TI__Expert 5000 points

    Glad to know that you are able to overcome the roadblocks.

    Again for you question:

    Preeti Joshi said:
    by enabling thumb mode, apart from code size reduction, will it impact the output or any other implications??

    It should not impact the output unless the issue you are debugging is timing related. As the thumb mode takes more time compared to Normal mode some of the timing sensitive scenarios might be debugged with this technique.

    For timing sensitive issue, one need to have a different instrumentation in the code to dump the critical variables to SL2 and then analyze and trace.

  • 0 in reply to Venugopala
    Prodigy 120 points

    Thanks for the information.

  • 0 in reply to Preeti Joshi
    Prodigy 120 points

    Kindly let me the procedure for setting breakpoints on the iCont side for the files that are built with -g option to enable stepping inside the iCont code.

    Also, M3 host is built in "Debug" mode.

    As of now, I am able to set breakpoints & debug only on the M3 side.

    Appreciate if the procedure is provided at the earliest as I am stuck at this point and not able to proceed futher.

    Thanks..

     

     

  • 0 in reply to Preeti Joshi
    TI__Expert 5000 points

    In the disassembly window put the breakpoint at the start of the function to be debugged.

    Once the PC encounters it one should be able to stepthrough the C code. If this is happening you  might need to review your compile options.