• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 41 subscribers
  • Views 1018 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.

[CC3200] Debugger can't find source

Iain McDonald
Intellectual 625 points
Other Parts Discussed in Thread: CC3200SDK, CC3200

We're developing a project on the CC3200 development board, using CCS v6.0.1.00039 and the CC3200SDK v0.5.2. At present we're still setting up our environment, we've got the example projects running and we're figuring out how to fork our own projects from them. We've encountered a problem with (at least) the provisioning_smartconfig project. We can compile, program and run okay, but we hit problems while debugging. While stepping through code, or pausing during run, we get debugger errors like the following:

Can't find a source file at "D:/CC32xx/SDK_0.5.2/simplelink/source/driver.c"

This error happens any time we try to step into OS or driver source, because the SDK isn't there - it's at "C:\ti\CC3200SDK\cc3200-sdk\simplelink\source\driver.c". It should be a fairly simple path variable to solve, but we can't find anywhere in the project debug options that references that path. Is there a way we can fix this without doing something crazy like making a dummy D: drive that points to the SDK folder?

  • 0
    Guru 85655 points

    Hi,

        I encounter this error before, when I am debugging and stepping into a function that is not included in the project view of CCS. So, just add the file at project view and you should be able to step into that function.

    - kel

  • 0 in reply to Markel Robregado
    Intellectual 305 points

    Hi,

    I work alongside the original poster. The file is already added to the project in CCS. The problem is that the debugger is looking for the file on the D drive as opposed to a directory on the C drive. The error is debugger specific. Compiling and linking work OK.

  • 0 in reply to Daniel Kern1
    Guru 85655 points

    Hi Daniel,

         I have a bit of time to help. So, I imported provisioning_smartconfig with "Automatically import referenced projects . . ." and "Copy projects to workspace" unchecked. Build without errors.

         Added driver.c from "C:\ti\CC3200SDK\cc3200-sdk\simplelink\source" and selected link to files to PROJECT_LOC. Build without errors.

        First of all, check if you have the same include options as mine. See, below.

    If you have the same include options as mine. Possible that you have a PROJECT_LOC variable problem. I forgot where it is set at CCS. But follow the instructions in the post below. You, can also try to create a new workspace, then import provisioning_smartconfig and see if you still get the same errors.

    CCS 5: edit or remove pre/automatically-PATH variables?

    - kel

  • 0 in reply to Markel Robregado
    Intellectual 625 points

    Hi Markel,

    Thanks for your help, but that doesn't really address our problem. We have the same project paths as you, and we can build with no errors, using the project as provided with the SDK. The problem only exists during debugging, and occurs for any external files because the debugger is using an absolute reference to D:/CC32xx/SDK_0.5.2, which doesn't exist in our environment and never has

    If you run that project on the hardware and pause it a few times you should see what I mean.

    That file is already on the include path at PROJECT_LOC\..\..\..\simplelink\source. What we need is the equivalent to the Include Options tab for the debugger, to modify the paths the debugger is searching for source code.

  • 0 in reply to Iain McDonald
    Guru 85655 points

    Hi,

       I did not make any changes to provisioning_smartconfig. I run and pause it several times, but did not get the error.

       As this is more of a CCS question, you can alternatively post this at the CCS forum, to get more expert advice.

    - kel