• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 2292 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/LAUNCHXL-F28379D: Difficulty building demo project (ADC Sample Mode)

William Campbell5
Prodigy 160 points
Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE, CONTROLSUITE

Tool/software: Code Composer Studio

Hey all,


I just got this board to use for my design team, and I'm trying to build the demo project just to get a feel for it. I installed controlsuite and reinstalled CCS with the C2000 box checked. I also installed the latest version of C2000Ware. I've gotten the error message below when building. When I click F2837xD_Adc.c in the file list, I get the message "File not found: /Example_28379D_LaunchPad/F2837xD_Adc.c." The file exists in the controlsuite and C2000Ware paths, but not the actual project folder.  I think this might be an issue with the build variables, but I don't know why they wouldn't point where they're supposed to. The "../../../" in the middle of the path moves it back to the "Users" level, and I think that might be part of the issue.


Thanks for your help.



 

**** Build of configuration CPU1_Flash for project Example_28379D_LaunchPad ****

"C:\\ti\\ccsv8\\utils\\bin\\gmake" -k all 
 
Building file: "../Example_F28379D_LaunchPadDemo.c"
Invoking: C2000 Compiler
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/bin/cl2000" -v28 -ml -mt --vcu_support=vcu2 --tmu_support=tmu0 --cla_support=cla1 --float_support=fpu32 --include_path="C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/include" --include_path="C:/Users/device_support/F2837xD/v200/F2837xD_headers/include" --include_path="C:/Users/device_support/F2837xD/v200/F2837xD_common/include" --advice:performance=all -g --define=CPU1 --define=_LAUNCHXL_F28379D --define=_FLASH --display_error_number --diag_suppress=1311 --diag_warning=225 --preproc_with_compile --preproc_dependency="Example_F28379D_LaunchPadDemo.d_raw"  "../Example_F28379D_LaunchPadDemo.c"
 
>> Compilation failure
subdir_rules.mk:9: recipe for target 'Example_F28379D_LaunchPadDemo.obj' failed
"../Example_F28379D_LaunchPadDemo.c", line 32: fatal error #1965: cannot open source file "F28x_Project.h"
1 catastrophic error detected in the compilation of "../Example_F28379D_LaunchPadDemo.c".
Compilation terminated.
gmake: *** [Example_F28379D_LaunchPadDemo.obj] Error 1
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_Adc.c', needed by 'F2837xD_Adc.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_CodeStartBranch.asm', needed by 'F2837xD_CodeStartBranch.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_CpuTimers.c', needed by 'F2837xD_CpuTimers.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_DefaultISR.c', needed by 'F2837xD_DefaultISR.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_headers/source/F2837xD_GlobalVariableDefs.c', needed by 'F2837xD_GlobalVariableDefs.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_Gpio.c', needed by 'F2837xD_Gpio.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_PieCtrl.c', needed by 'F2837xD_PieCtrl.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_PieVect.c', needed by 'F2837xD_PieVect.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_Sci.c', needed by 'F2837xD_Sci.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_SysCtrl.c', needed by 'F2837xD_SysCtrl.obj'.
gmake: *** No rule to make target 'C:/Users/device_support/F2837xD/v200/F2837xD_common/source/F2837xD_usDelay.asm', needed by 'F2837xD_usDelay.obj'.
Building file: "../sci_io.c"
Invoking: C2000 Compiler
"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/bin/cl2000" -v28 -ml -mt --vcu_support=vcu2 --tmu_support=tmu0 --cla_support=cla1 --float_support=fpu32 --include_path="C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/include" --include_path="C:/Users/device_support/F2837xD/v200/F2837xD_headers/include" --include_path="C:/Users/device_support/F2837xD/v200/F2837xD_common/include" --advice:performance=all -g --define=CPU1 --define=_LAUNCHXL_F28379D --define=_FLASH --display_error_number --diag_suppress=1311 --diag_warning=225 --preproc_with_compile --preproc_dependency="sci_io.d_raw"  "../sci_io.c"
 
>> Compilation failure
subdir_rules.mk:93: recipe for target 'sci_io.obj' failed
"../sci_io.c", line 24: fatal error #1965: cannot open source file "F28x_Project.h"
1 catastrophic error detected in the compilation of "../sci_io.c".
Compilation terminated.
gmake: *** [sci_io.obj] Error 1
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

  • 0
    Guru 26200 points

    Hello William,

    how did you imported that project example?

    Path like this: C:/Users/device_support/F2837xD/
    look strange, not defaults for TI setup.

  • 0 in reply to Tomasz Kocon
    Guru 26200 points
    should be here: C:\ti\C2000Ware_1_00_05_00_Software\device_support\f2837xd\examples\dual\F2837xD_sci_flash_kernels\cpu02
    or like this.
  • 0 in reply to Tomasz Kocon
    TI__Guru**** 173310 points
    William,

    Tom is right. The paths to the file look incorrect which means that the path and build variables are not set correctly.

    How did you import the project? There are couple of ways to import it:
    1) Directly from Resource Explorer inside CCS (menu View->Resource Explorer). Navigate down to the example inside C2000Ware, then click on the icon in the center pane to "Import to IDE", or
    2) Import using CCS menu Project->Import CCS Projects, navigate to the directory that contains the project (C:\ti\C2000Ware_1_00_05_00_Software\device_support\f2837xd\examples\cpu1\launchxl_f28379d\cpu01\ccs), select the project and Finish.

    Try opening a new workspace and import using one of the above methods. Let us know if the build errors persist.
  • 0 in reply to AartiG
    Guru 26200 points
    Hello AartiG,

    my question is not directly related to this topic.
    Today I did a clear answer to someone of community members with the Suggest an Answer marked ON.
    After hours I have seen that the post status had been changed to the TI Thinks Resolved.
    No one other than me have responded to that thread.
    What happened, what does it mean?
  • 0 in reply to Tomasz Kocon
    TI__Guru**** 173310 points

    It means that someone from TI marked your post as "TI Thinks Resolved" because they agree with your response. Please see this post that explains the different validation types on E2E.

  • 0 in reply to AartiG
    Prodigy 160 points
    That fixed it, thanks! The issue was that in controlSUITE, the Demo page says to "click on the link above to copy the files to the desired destination directory", and I just copied them to an arbitrary directory, not realizing the specific path they were in is important.
  • 0 in reply to AartiG
    Guru 26200 points
    That is according to my expectations.
    Being community member, is there any possibility to see who marked my response as TI Thinks Resolved?
    If it takes you 2-3 minutes, do not waste your time.
  • 0 in reply to Tomasz Kocon
    TI__Guru**** 173310 points

    Tomasz Kocon said:
    Being community member, is there any possibility to see who marked my response as TI Thinks Resolved?

    No there isn't.