• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 265 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

SysLink debug

Risto Hedman
Expert 1760 points

Hi,

I've been trying to find instructions how  to debug SysLink applications in CCS - mainly DSP- code. If I build in Linux e.g. an ex01_helloworld, what should I transfer to Win7 to feed CCS and how to import that to CCS? CCS is 5.5.0, SysLink is 2_21_01_05 and sys/BIOS is 6.35.4.50.

BR,

Risto

  • 0
    TI__Mastermind 18260 points

    Risto,

    For simple debugging with just symbols available for memory & disassembly windows, you can just "Load Symbols...", found under the Run -> Load dropdown menu.  This will require having access to your DSP executable program from your Win7 machine.

    For C-level debugging you will need to "translate" your Linux path of the C code to a Win7 path.  First, in Windows Explorer, right-click Computer and select "Map network drive..." to map a drive letter to your Linux file share.  Then, in CCS...

    1. select the Window -> Preferences dropdown menu
    2. expand C/C++ on the left
    3. expand Debug
    4. select "Source Lookup Path"
    5. add a "Path Mapping" to map your chosen driver letter to your file share

    I have Y: -> /db/atree, so a program built in /db/atree/foo would be seen as Y:\foo in CCS on Windows

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Expert 1760 points

    Perfect,

    Thank you Rob.

    Risto