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.

CC1352R: ble5_simple_peripheral_oad_offchip_cc13x2r1lp_app virtual "Application" folder?

Part Number: CC1352R
Other Parts Discussed in Thread: CC1350, CC2640

I noticed that in the simple peripheral OAD example projects for the CC2642 and CC1352 the "Application" folder is a virtual folder and every file within is therefore linked. This is different than the similar projects for the CC1350 and CC2640, where the folder contained live files. I can resolve this manually, but was wondering if there is something I am missing here as to why they would be configured as linked files?

Thanks, Dave

  • Hi Dave,

    I don't think there is any specific reason for this. For CCS projects, the folders are decided in the .projectspec file (ble5_simple_peripheral_oad_offchip_cc13x2r1lp_app.projectspec), and their state is determined by the files within. If you want a "real" folder with the files, set

    action="copy" 

    for all the relevant files.

  • Thanks for the tip, but I couldn't find a .projectSpec file in the folder, and I'm reluctant to create one. I moved on to the associated stack library project that is referenced by the app, with the intent of publishing it on our local git server as well. Unfortunately it has many virtual folders, which of course don't resolve when populating a git commit. So I'm stuck copying the files manually. This brings a couple questions to mind:
    1. Since I'm not modifying the stack library, is there an easy way to simply link the .lib file for the ble stack? I attempted to remove the application's reference of the stack library, thinking that I could just provide the latest stack library .lib file to satisfy the linker. This did not work!
    2. What is the best way to configure our git projects that are created from the CCS example projects to allow the easiest transition to new versions of the SDK?

    Thanks,
    Dave
  • Hi David,

    The projectspec file found in C:\ti\simplelink_cc13x2_sdk_1_60_00_29\examples\rtos\CC1352R1_LAUNCHXL\ble5stack\simple_peripheral\tirtos\ccs . You have to make changes before importing the project into ccs.

    The stack_library is already being linked by the linker. I don't understand what you mean.

    We provide a migration guide for each new version of the SDK. The strategy is normally to start with an example project in the new SDK, and re-do changes to the application.
  • Marie,
    The root of my question comes from the desire to easily port the project into a git repository to facilitate multiple developers at various locations. The stack library would be easier to deal with if it were simply exported as a .lib file with header files to define the API. I don't understand why I have to get the source and build it unless I modify it. I am looking for a source file configuration strategy that allows me to easily move my application code to future releases of the SDK with the minimum amount of manual "re-do changes to the application".
  • I took a look at the .projectspec file, I'm still not clear on how to modify it to simply create physical copies for ALL the files in the project. Is there one command line that I can use to eliminate the linked files and cause them all to be copied? The tedium of modifying the .projectspec file isn't ideal.
  • Hi David,

    I have moved the thread to the CCS forum. If you don't get any response here it's because of the thread status. If this happens, please create a new thread in the CCS forum.
  • Hi,

    >>I took a look at the .projectspec file, I'm still not clear on how to modify it to simply create physical copies for ALL the files in the project. Is there one command line that I can use to eliminate the linked files and cause them all to be copied? The tedium of modifying the .projectspec file isn't ideal.
    There is no command per se to copy all files, but for source files you can do a simple string search-and-replace on your projectspec file: search for action="link" and replace with action="copy".

    Libraries, however, are usually "linked" via the linker options (--search_path for directories and --library for the libraries themselves) - in this case, you would need to modify your project to explicitly add them as files.

    Additional details at:
    processors.wiki.ti.com/.../ProjectSpecs_in_CCS

    Hope this helps,
    Rafael