• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 418 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.

CCS/CODECOMPOSER: Auto target-configs incorrect

Michael Fralick
Prodigy 30 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: BOOST-CC2564MODA, CC3200AUDBOOST

Tool/software: Code Composer Studio

Hey all, 

I am extremely new to this world. I am starting to experiment and play around with the MSP432P401R, with the BOOST-CC2564MODA. At the moment I have a simple goal of uploading an example to this and being able to connect to it. I understand I'll need other BoosterPacks to do audio functions and such, that will come at a later time. 

My current issue is in Code Composer Studio. I have imported SPPDemo into IDE following the SWRU453B user guide. I opened the properties and made sure the correct LaunchPad was selected, I tested the connection, and made sure the checkbox to automatically configure the target-configs was selected. When I build the file I get the following errors:

gmake: *** No rule to make target 'C:/Users/frali/workspace_v9/Main.c', needed by 'Application/Main.obj'.
gmake: *** No rule to make target 'C:/Users/frali/workspace_v9/SPPDemo.c', needed by 'Application/SPPDemo.obj'.
gmake: *** No rule to make target 'C:/Users/Bluetopia/btpskrnl/BTPSKRNL.c', needed by 'Bluetopia/btpskrnl/BTPSKRNL.obj'.
gmake: *** No rule to make target 'C:/Users/Bluetopia/btpsvend/BTPSVEND.c', needed by 'Bluetopia/btpsvend/BTPSVEND.obj'.
gmake: *** No rule to make target 'C:/Users/Bluetopia/btvs/BTVS.c', needed by 'Bluetopia/btvs/BTVS.obj'.
gmake: *** No rule to make target 'C:/Users/Bluetopia/hcitrans/HCITRANS.c', needed by 'Bluetopia/hcitrans/HCITRANS.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/MSP-EXP432P401R/CC3200AUDBOOST.c', needed by 'Platforms/MSP-EXP432P401R/CC3200AUDBOOST.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/MSP-EXP432P401R/HAL.c', needed by 'Platforms/MSP-EXP432P401R/HAL.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/MSP-EXP432P401R/ccs/msp432_startup_ccs.c', needed by 'Platforms/MSP-EXP432P401R/ccs/msp432_startup_ccs.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/cpu.c', needed by 'Platforms/driverlib/cpu.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/cs.c', needed by 'Platforms/driverlib/cs.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/flash.c', needed by 'Platforms/driverlib/flash.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/gpio.c', needed by 'Platforms/driverlib/gpio.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/i2c.c', needed by 'Platforms/driverlib/i2c.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/interrupt.c', needed by 'Platforms/driverlib/interrupt.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/pcm.c', needed by 'Platforms/driverlib/pcm.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/rtc_c.c', needed by 'Platforms/driverlib/rtc_c.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/sysctl.c', needed by 'Platforms/driverlib/sysctl.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/systick.c', needed by 'Platforms/driverlib/systick.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/uart.c', needed by 'Platforms/driverlib/uart.obj'.
gmake: *** No rule to make target 'C:/Users/Platforms/driverlib/wdt_a.c', needed by 'Platforms/driverlib/wdt_a.obj'.
gmake: Target 'all' not remade because of errors.

The directory it created for the target-configs is incorrect. I was under the impression it decides the locations based on the LaunchPad selection, which is why I made it a point to test my connection to ensure I had the right thing selected, but the directories on my computer are incorrect. Has anyone encountered this before? I wasn't able to find much searching for this issue. Hopefully it is a simple mistake!

Thanks

  • 0
    TI__Guru**** 173310 points

    Michael,

    The project build errors shown here are not related to the target configuration. These errors are coming even prior to CCS launching a debug session and trying to connect to target. 

    Which version of CCS are you using? When you imported the project did you check the box for "Copy projects into workspace"? If you did, that might the reason for these errorprs. I don't believe this project is designed to be copied to workspace, but rather should be left in its original directory. 

    Try the following: open a new CCS workspace, then import the project with the "Copy projects into workspace" box unchecked (shown below). Build the project (right-click on the project in Project Explorer view and select Build Project) and let us know if that fixes the errors.

  • 0
    Guru 26200 points

    To avoid very rare issues, do not install shared packages within c:\users folder.
    Try to do reinstalls with default folders.

  • 0 in reply to Tomasz Kocon
    Prodigy 30 points

    That's the crazy part...... I left all options set to default. CCS is installed in C:\ti, and I just hit the download/install button within the resource explorer. I'll uninstall the packages and watch more carefully to see if I was given the option to put the packages somewhere else. I don't recall having the ability to define the install location for those.

    Thanks

  • 0 in reply to Michael Fralick
    TI__Guru**** 173310 points

    Michael Fralick said:
    CCS is installed in C:\ti, and I just hit the download/install button within the resource explorer.

    Which package are you referring to that you downloaded and installed using Resource Explorer?

  • 0 in reply to AartiG
    Prodigy 30 points

    It appears that using the default location for my workspace is what was causing the issues. I created the folder C:\ti\workspace and pointed my workspace to that path. From there everything worked great.