• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 51 subscribers
  • Views 886 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.

CC2650DK examples with different build settings: having trouble duplicating projects.

Tosa
Expert 1340 points

I'm trying to modify the links in the CC2650DK BLE HeartRate and SimpleBLEPeripheral examples so that it's easy to duplicate the projects without affecting originals. I set the links in CCS as follows:

HeartRate Links:

SimpleBLEPeripheral Links:

However, when I go to build, SimpleBLEPeripheral complains about driverlib.lib, whereas HeartRate links fine:

HeartRate build output

SimpleBLEPeripheral build output:

How can I fix this?

  • 0
    TI__Guru** 105180 points
    Hello Tosa,

    You'll need to make sure the CC26XXWARE path resolves to a valid location where CC26XXWARE is installed from the TI-RTOS bundle. You can use the default SDK installation as a reference. Under ARM Linker settings (File Search Patch), the path to driverlib.lib must resolve as well.

    Best wishes
  • 0 in reply to JXS
    Expert 1340 points
    Hi JXS,

    Both Resources->Linked Resources->Path Variables->CC26XXWARE and Build->Arm Linker->File Search Paths->driverlib.lib path are valid in both projects and I see that driverlib.lib exists already in both projects. However, I don't understand why the linker can't find the file in the SimpleBLEPeripheral project. If I set the linker path to "C:\ti\tirtos_simplelink_2_13_00_06\products\cc26xxware_2_21_01_15600\driverlib\bin\ccs\driverlib.lib" then SimpleBLEPeripheral is able to build, but this is not necessary for the HeartRate project. I don't want to use the c:\ti... location for my projects (except for tools and such); I want everything relative to the new root directory.

    Also I notice something strange about the auto-generated Makefile: after making my new SimpleBLEPeripheral folder, the initial build pointed to driverlib.lib to the original c:\ti\tirtos... location, but subsequent builds failed since they pointed to the new g:\... location. Why did this happen? How does CCS create the makefile?

    Thanks!
  • 0 in reply to Tosa
    TI__Guru** 105180 points
    Hi Tosa,

    Try deleting the auto-generated files in the workspace, such as the FlashROM folder and any auto-generated linker/makefile. If you carry these files over from another install, there may be issues.

    Best wishes
  • 0 in reply to JXS
    Expert 1340 points

    Hi JXS,

    I deleted the FlashROM folder and still get the error that driverlib.lib isn't found. It's important that this is a relative path since the project will be under version control and checked out to developers' local (relative) root directories.

    It seems that the combination of the root folder name and project name lengths seems to affect the finding of the library. For example, default root c:\ti andproject HeartRateStack is able to find driverlib.lib using relative paths, but the combination of c:\simpleBLEperipheral and SimpleBLEPeripheralStack fails to find driverlib.lib relatively. If I shorten the later root and project to c:\test and testStack it buillds fine. Why is this?

    Thanks!