• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 412 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.

How to debug DSP (for RTOS) application loaded by ARM (from HLOS-Linux) on TI816x EVM

Hitesh Viradiya
Expert 1505 points

Hello,

I am using syslink_02_00_00_68_beta1 which is having simple IPC demo "Notify" which demonstrate the 32-bit payload transfer (IPC) from ARM to DSP.

To explain in detail,

I have gone through "SysLink_02.00.00.68_beta1_InstallGuide.pdf" file, i compiled the syslink samples. As far as i understand i tried to playing with those demos. I choose Notify application from those, as it looks simplest one.

I boot the board (ti816x evm). i ran application as below:

./notifyapp_release 1 0 ./notify_ti81xx_dsp.xe674

It successfully executed. I understand the application very well. I want to debug the DSP side application, i want to see the prints which are there in DSP application. So how could i do this ??

I made an attempt, i tried to connect DSP using CCSv5, once i boot ARM from Linux, but as per my understanding it is the "ARM boots DSP" case. So i was unable to connect.

I might be wrong. So is there any way to do so ?? Or There might be anything missing in my understandings.

Regards,

HiteshV

  • 0
    Genius 4615 points

    You need to do a "Non-project Debug" session with CCS.  First of all, I do this with CCS4.2.3 as I have not been able to get CCS5 to do a source lookup.  The steps are the following:

    1.  Rebuild the hlos-side (ARM) code with a getchar() located after procMgr().  The idea is to let the ARM load and start up the DSP.  You also will want to build your DSP code with debug symbols.  To do that use:

    xdc XDCARGS="profile=debug"

    2.  Launch the target configuration  (I'm asuming that you have already set this up) and right click on the C674x device and click on edit source lookup.  Navigate to your DSP source files.

    3.  With the getchar() reached, connect to the DSP from CCS.  Do not use a GEL file.

    4.  click on target-->load symbols and navigate to your DSP executable.

    5.  Load your source files, set break points, and run (click on the green arrow)

    6.  In the EVM console, press return for the getchar() and you're off to the races.

    7.  [Optionally] you can copy the packages/cfg/plaform/debug/*.rov.xs file to the directory where your DSP executable is to get rov to work.  This will tell you about such things as the state of tasks once you halt the DSP.  I have also discovered that inorder to see all of the task output you need to build using sysmin.  procMgr will startup all of your DSP tasks prior to the getchar() and not everything will be communicated to CCS's console.  There are changes made to the .cfg configuration file to set this up.

    Lee Holeva

     

  • 0 in reply to Lee Holeva
    Expert 1505 points

    Thanks Lee,

    It helps me a lot, Now i am able to get the debug prints (of DSP) on the console window of CCS.

    Regards,

    HiteshV