• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1265 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: CC3200

I posted this over in the CC3200 forum here, but they directed us here. Hope you guys can help.

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
    TI__Guru**** 159725 points

    Iain,

    There are a couple ways to resolve this.  There should be a button in the blank window that opens with the can't find source message.  If you use that button to browse to the location CCS should store that location for future use.

    The other way to do it is in the Debug view right click on the top level node that represents your debug session.  Select "Edit source lookup..."  Then click on the Add button and you can add the path.  It gives you all kinds of options for how to add the path, relative to project, relative to the program file.  The easiest is to just use the absolute path option.

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 625 points

    Excellent, thanks John, exactly what we needed. I didn't want to manually add each file in the OS, but the edit source lookup did the trick.

    One more related, but less worrisome, question.

    "No source available for "UtilsDelay() at <project.out>"

    happens when we pause during, apparently, an OS wait. I'm betting this is because that function is heavily optimized at compile time and the debugger can't link it to source, but that source is at least available. This project doesn't have Release and Debug configurations, only release. Is there a quide somewhere for creating these configs, or specific optimizations I should turn off to allow full debugging without overflowing the flash space? I don't care so much about the delay function, just wondering what happens if we encounter this with another function we actually need to see into.

  • 0 in reply to Iain McDonald
    TI__Guru**** 159725 points

    With our current ARM compiler if you turn on symbolic debug it will put in as much debug info as it can without impacting optimization.  The behavior is different in our older compilers where the debug info generation would take precedence and impact optimization.  

    This would mean that if you need more debug info you could reduce the optimization level for the file containing that function.  By doing it at the file level you will have less impact on the rest of the application.  If you do hit this problem later the team in the compiler forum can help you through it.

    Regards,

    John