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

6.1.1 Debug Error using MSP432P401R Launchpad

JimS
Prodigy 140 points
Other Parts Discussed in Thread: MSPWARE, CC3200

I got a debug error on my "main machine" running a licensed copy of CCSv6.1.0, so
I did a clean install of CCSv6.1.1 on another machine, choosing install options for
MSP430, MSP432, and TivaC. I accepting all the defaults and created a workspace in
D:\TI\MSP432_WS\. I ran CCSv6.1.1 and used App Center to install/update the
following CCS Add-ons:
MSP430 GCC            MSPWare               GUI Composer           CC3200 Add-On 
TI-RTOS for MSP43x    TI-RTOS for TivaC     TI-RTOS for Simplet..  TI ARM Compiler
MSP430 Compiler       Javascript Develop..  CDT GNU                ARM GCC
Grace Peripheral Co.. 

I used TI Resource Explorer to import the project:
C:\ti\msp430\MSPWare_2_30_00_49\driverlib\examples\MSP432P4xx\uart\uart_loopback_48mhz_brclk

I connected a MSP432P401R LaunchPad, compiled, and ran the program, which echoed
characters to Tera Term at 115,200 baud (as expected). When I paused operation to
look at variables with the Debugger, I got the following error:

Can't find a source file at "C:\space\msp432-driverlib\build\MSP432P4xx/cpu.c"
Locate the file or edit the source lookup path to include its location.

This is the exact same error that I had gotten on the other PC running CCSv6.1.0.

I could resume the program operation and it appeared to operate properly, but I
could not pause and look at variables with the debugger.

Can anyone give me a hand? Where do I find "source lookup path"?

Thanks,
Jim Smith

  • 0
    Guru 85685 points
    Hi James,

    This, "Can't find a source file at "C:\space\msp432-driverlib\build\MSP432P4xx/cpu.c", happens when you debug step into a function within a c file example cpu.c, that is not in your CCS project. You would be able to debug step into that function in cpu.c if you add cpu.c in your CCS project.

    - kel
  • 0 in reply to Markel Robregado
    Prodigy 140 points
    Hi kel,

    Thanks for your prompt reply. I was tied up for a few days, but am back on my "learning stint" with CCS and MSP432.

    I realize that I could include the driverlib's cpu.c file in my project, but isn't there a way to point CCS to the driverlib source, so that it isn't necessary to just include specific *.c files in my project? I suspect, that before I'm finished, I may need more of the driverlib source files for the debugger to work.

    -Jim
  • 0 in reply to JimS
    Guru 85685 points
    Hi James,

    For C functions that are called in C files that are not in your CCS project, you can debug "step over" it.

    - kel
  • 0
    Guru 92251 points

    James H. Smith77346 said:
    Where do I find "source lookup path"?

    There should be a "Locate File..." button on the window which is displaying the "can't find a source file at ..." message. Using "Locate File..." you can select the directory which contains the driverlib source file, and the debugger should then be able to single step the driverlib source file without having to add it to your CCS project.