• State
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 45 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CCSTUDIO-THEIA: Including SDK and Motor SDK folders directly in CCS project causes file loss and build errors

Pleterski Jan
Prodigy 10 points
Part Number: CCSTUDIO-THEIA


We are working on a C++ project in Code Composer Studio based on the empty_driverlib_project_cpp example.

For better organization and traceability, we wanted to include both our SDK and Motor SDK folders directly inside the project directory.

After adding the libraries to the project and updating the Product and Compiler directory paths in CCS project settings, the project starts to lose files from the SDK directories and generates errors such as:

[193] error: unable to open output file 'lib/f29_sdk/source/bitfields/bitfield_structs.o': 'no such file or directory'
[194] 1 error generated.
[195] gmake: *** [device/subdir_rules.mk:11: lib/f29_sdk/source/bitfields/bitfield_structs.o] Error 1
[196] clang -cc1as: error: unable to open output file 'lib/f29_sdk/examples/device_support/source/codestartbranch.o': 'no such file or directory'
[197] gmake: *** [device/subdir_rules.mk:18: lib/f29_sdk/examples/device_support/source/codestartbranch.o] Error 1
[198] Finished building: "../libraries/control/fwc/fwc.c"

Once this occurs, even restoring the original paths and settings does not resolve the issue — the errors persist and the project continues to report missing files.

We also noticed that the folders containing the SDK and Motor SDK libraries must always be marked as “Excluded from Build” in order to avoid other issues. However, this defeats the purpose of having them directly included within the project structure for easier access and traceability.

Has anyone encountered this behavior before?
Is there a supported or recommended way to include the SDK and Motor SDK within the project folder structure, or is this not possible in CCS?

Any suggestions or insights would be greatly appreciated.

  • 0
    TI__Mastermind 26786 points

    Hi Pleterski,

    Motor Control SDK already has a copy of the F29x SDK. It may suffice to just include the Motor Control SDK in your empty project instead of copying both as there will be conflicts between the source files being referenced.

    I have also looped in a motor control SDK expert to chime on this.

    Best regards,

    Ryan Ma

  • 0 in reply to Ryan Ma
    Prodigy 10 points

    Thank you for the fast reply Ryan.

    Unfortunately the issue still persists.

    In Code Composer Studio settings I was able to locate which product is picked up by the compiler and from which path (This also updates then my project paths). If I only add in the Motor Control SDK for some reason the classic SDK is not picked up by the CCS. Maybe there is another way to do this not in CCS settings but in project settings?

    P.S. The project is only able to unsuccessfully compile when both libraries are linked inside the CCS settings and marked as excluded from the build. If they are included in the build the compiler stops at around 20%-40% and even if stopped the CCS has to be restarted in order to retry.

    BR, Jan

  • 0 in reply to Pleterski Jan
    TI__Mastermind 26786 points

    Hi Pleterski, 

    Can you share what your project dependencies look like currently?

    Best regards,

    Ryan Ma

  • 0 in reply to Ryan Ma
    TI__Expert 6475 points

    Hi Pleterski,

    The classic SDK is already packaged inside the Motor Control SDK, so you should be able to pull any files you need from there. Thus, you shouldn't need to include both of them as Products within CCS. 

    Kind regards,

    Skyler