• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 2947 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.

Common Source Path Lookup - CCS 4.2.3

_Ralph_
Guru 10685 points
Other Parts Discussed in Thread: SYSBIOS

Basically I am debugging an Integra EZSDK Syslink application in CCS; I am trying to debug the DSP side of things. I do not have a project loaded in CCS but I do have the symbols loaded into it (the .xe674 file that contains the symbols was built as "debug" format) and all the directories and subdirectories in the EZSDK added to my "Common Source Path Lookup".

Despite including all these subdirectories which contain the source code relevant to the loaded symbols, CCS does not find the source code itself. All that happens is that after quite a big delay it says "Source not found". How can this be given that I have definitely included the source code directories in the common source lookup path? Is this something to do with the message in CCS 5 that I get saying "Can't find a source file at "/db/vtree/library/trees/avala/avala-o06x/src/ti/sysbios/hal/Hwi_stack.c" "? I have no idea what this /db refers to as it certainly isn't on my computer.

My post where I discuss this in slightly more detail is here:

http://e2e.ti.com/support/dsp/integra_dsparm/f/625/p/109185/400013.aspx#400013

Thanks,
Ralph

  • 0
    TI__Genius 15710 points

    Ralph, 

    I would double check that source lookup is configured for your specific debug session. see slide set below for some background information. I would go through slides starting at #27

    slide #34: covers where debugger settings can be configured. 

    slide #37: I would use method described here to double check that your global source lookup setting made into debug session specific settings. 

    http://processors.wiki.ti.com/images/0/09/CCSv4_Tips_%26_Tricks.pdf

     

    Martin

     

     

  • 0 in reply to MartinS
    Guru 10685 points

    Hi,

    thanks for your reply. I would say slide 35 is most applicable as I am debugging without a project.

    It says:

    "Set “Source Lookup Paths” for CCS to scan when looking for source files:
    • Set for current debug session
    • Set for launch configuration - apply for every debug session started for that target only
    • Set at global (workspace) level – apply for any debug session started with this workspace"

    I have highlighted in bold what I am doing but this has no effect. Do I need to delete all projects from the workspace to get the bold method to work? Is the active project in my workspace (which I am not using) having some effect on the paths that are being looked at to find source code?

    Anyway, at least slide 37 works fine even if I have to repeatedly do it for each debug session.

    Ralph

     

  • 0 in reply to _Ralph_
    TI__Genius 15710 points

    no, you don't need to delete your projects. I would first try going to "Target-> Debug...", menu and delete entries under "Non-Project Debug Session" node in left side tree. This will force them to be re-created next time you start a debug session and should pick up settings from global preferences. 

    The method on slide #37 should persist between debugger starts, thus you should only enter it once per CPU. You may need to redo it for other CPUs on your device(if you have a multi-CPU device) or if you switch to a different target configuration. You can check how this is stored by looking at dialog that pops up from Target->Debug... and selecting your emulator/CPU combination as defined in your .ccxml file and going to source tab. 

    Martin

     

     

  • 0 in reply to MartinS
    Guru 10685 points

    MartinS said:

    no, you don't need to delete your projects. I would first try going to "Target-> Debug...", menu and delete entries under "Non-Project Debug Session" node in left side tree. This will force them to be re-created next time you start a debug session and should pick up settings from global preferences. 

    Hi, unfortunately that didn't work for me. I see that once global source paths have been set that now when I "right click->edit source path" on a target the directories I added under Window->Preferences appear under "default" (whereas the slide 37 method puts the directories outside the default section). Loading symbols and connecting to the target does not give me any joy though.

    I'll stick with the slide 37 method as at least that works.

    Thanks,
    Ralph