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

Problem in driverlib in tiva c series launchpad

Braian Demian
Prodigy 140 points

Hi everyone. I have a problem and i don't know how to fix it. The problem is when i debug the program to the launchpad the CCS tells me

"Can't find a source file at "C:/DriverLib/build/DriverLib.test/driverlib/sysctl.c"

Locate the file or edit the source lookup path to include its location."

When i look if there is any kind of file like that, the file doesn't appear. This file should be in the TIVAWARE Launchpad Workshop but there isn't.

It would be nice for me if anyone could tell how to fix that.

Thanks

  • 0
    TI__Guru**** 244400 points

    Hello Braian,

    The sysctl.c file is in the TIVAWare driverlib directory after installation. Normally during link phase it the compiled drivelib.lib is used and it should be referred to for debug which has the relative path for the sysctl.c and other API files.

    I haven't seen this issue so far, so I could suggest the following

    1. Import the driverlib project from TIVAWare Installation path. When importing the project is called "driverlib"

    2. Build the same in CCS.

    3. Use the output lib file generated (in the workspace) during linker phase of your other projects

    Regards

    Amit

  • 0
    Guru 86745 points

    Braian Demian said:
    "Can't find a source file at "C:/DriverLib/build/DriverLib.test/driverlib/sysctl.c"

    This could mean that you are stepping into a sysctl C API, but "sysctl.c" is not in your project. Is that what you are doing?

    If so, then just add the file "sysctl.c" to your project and you would be able to step into sysctl C API's

    -kel

  • 0 in reply to Markel Robregado
    Guru 117855 points

    Markel Robregado said:
    This could mean that you are stepping into a sysctl C API, but "sysctl.c" is not in your project ... just add the file "sysctl.c" to your project! 

    But - is not sysctl.c integrated w/in driverlib (as Amit indicates) and thus never required to be added, manually!  In fact I recall Sue C. admonishing users (in the past) not to add such (existing) library .c files!  Sysctl.c will be pulled in nicely provided sysctl.h (alone) is included w/in the appropriate, calling user files...

    How that c file (alone) has, "gone missing" is the real mystery. (unless sysctl.h is awol)  One expects user's penchant for, "creating their own project" has (yet again) tossed their small ship onto the rocks! 

  • 0 in reply to cb1_mobile
    Guru 86745 points

    @cb1.

            I mean if sysctl.c is not at your IDE project window under "Source". I remember getting the same error before below in debug mode and stepping into API's like SysCtlClockSet. The solution was to add sysctl.c at project window under "Source". After adding sysctl.c, I was able to step into SysCtlClockSet API.

            Can't find a source file at " xxxxxx"

           I also have read some post with the same error at Code Composer Studio forum. I just can't find now a post that is related to Tiva or Stellaris to show here. 

    -kel

  • 0 in reply to Markel Robregado
    Guru 117855 points

    @Kel,

    Recall our small shop is, "IAR only" as clients demand we source best MCU solution, always.  Thus any "one vendor confinement" is disallowed. (i.e. can any single vendor - at all times - have best price/performance/available MCU solution?)  And - what if the best MCU is among Cortex M3 (banished) or Cortex M0 (too competitive?)

    The driverlib really should encapsulate all, "normal/customary" C files.   Having to add each/every one of these C files (or far worse - having to "inspect" for their full/proper inclusion - each/every time you start a project using your IDE) is, "Nightmare in the making" is it not?  Oh well - that oft offending - unary vendor IDE - is free...   (and most often - you get what you pay for...)

    Resolution of this awol sysctl.c file far beyond my pay-grade.   In near 15 years use of paid IAR - never/ever encountered!