• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 83 subscribers
  • Views 538 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.

LAUNCHXL-F28069M: CCS compiling errors

Weiliang Xu
Prodigy 90 points

Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: CONTROLSUITE, SYSCONFIG, C2000WARE

This is the first time I use CCS for TI's MCU/DSP. I tried to use the Launchxl-f28069M to get familiar with the programming of TI's product. I ran the demo program built-in with the package. No problem. Then I tried to build the demo project stored in C:\ti\controlSUITE\development_kits\LAUNCHXL-F28069M\LaunchPadDemo. I imported the project with copy to workspace checked. When I built the project, errors appeared indicated it could not find ALL the compiled .obj files like this:

>> Compilation failure
makefile:149: recipe for target 'Example_2806xLaunchPad.out' failed
"C:\\Users\\weiliang.xu\\AppData\\Local\\Temp\\380923", line 27: error: cannot
find file "./Example_F2806xLaunchPadDemo.obj"

It seemed like in CCS settings, the .obj file path was set to C:\\Users\\weiliang.xu\\AppData\\Local\\Temp\\380923. I searched all CCS settings to correct this, and I could not find where is it. In addition, I searched the folders C:\ti and C:\\Users\\weiliang.xu. I could not find the corresponding .obj files. So I do not even know where CCS put them. I know CCS had built them successfully as the message showed:

Building file: "../Example_F2806xLaunchPadDemo.c"
Invoking: C2000 Compiler
"C:/ti/ccs1230/ccs/tools/compiler/c2000_15.12.3.LTS/bin/cl2000" -v28 -ml -mt --float_support=fpu32 --cla_support=cla0 --vcu_support=vcu0 --include_path="C:/ti/ccs1230/ccs/tools/compiler/c2000_15.12.3.LTS/include" --include_path="/packages/ti/xdais" --include_path="C:/ti/controlSUITE/device_support/f2806x/v140/F2806x_headers/include" --include_path="C:/ti/controlSUITE/device_support/f2806x/v140/F2806x_common/include" --include_path="C:/ti/controlSUITE/libs/math/IQmath/v160/include" --include_path="C:/ti/controlSUITE/libs/math/FPUfastRTS/V100/include" -g --define=_DEBUG --define=_FLASH --define=LARGE_MODEL --quiet --verbose_diagnostics --issue_remarks --diag_warning=225 -k --asm_listing --output_all_syms --asm_includes --cdebug_asm_data --preproc_with_compile --preproc_dependency="Example_F2806xLaunchPadDemo.d_raw" "../Example_F2806xLaunchPadDemo.c"
"../Example_F2806xLaunchPadDemo.c", line 216: note: comparison between
signed and unsigned operands
if(tempDelta > cycleCount){
^

"../Example_F2806xLaunchPadDemo.c", line 224: note: comparison between
signed and unsigned operands
if(abs(tempDelta) > cycleCount){
^

"../Example_F2806xLaunchPadDemo.c", line 248: warning: variable "fid" was set
but never used
volatile FILE *fid;
^

Finished building: "../Example_F2806xLaunchPadDemo.c"

By the way, if I used the linking option without copying to the workspace, the .obj files can be found in the linked Debug folder. However, if using copy project to workspace, the .obj files do not appear in the Debug folder inside the project folder.

Can anyone help to find out what was wrong? Thanks in advance for any help!
 

  • 0
    TI__Mastermind 30185 points

    Hello,

    Before debugging this example, is there a particular reason that you're choosing to use an old device/software development kit? This device is about 14 years old, and the ControlSUITE SDK is no longer being updated. If you're not using a legacy system/design I highly recommend using a newer device, you can see some available devices based on performance and Flash size on this page. These newer devices also have easier migration amongst each other because of features created using SysConfig (this tool is not available for the F2806x and similarly aged devices).

    If you want to continue using this device, I highly recommend using C2000Ware as there are still examples provided for the F2806x device there which have been tested actively and which can be fixed if they have any errors.

  • 0 in reply to Omer Amir
    Prodigy 90 points

    @Omer,

    Thanks for your reply. First of all, I used that because I designed an embedded system using F28069M MCU and we purchased a Launchxl_f28069M as development kit. To verify it working okay, I tried this example demo project. But this problem is not the device issue, rather I think it is how the CCS is configured. In this case I did not change any settings imported from the example project. I am wandering if there is somewhere it specifies an environment path, since the error message pointing the path to a user related location. 

  • 0 in reply to Weiliang Xu
    TI__Mastermind 30185 points

    Hello Weiliang,

    Weiliang Xu said:
    But this problem is not the device issue, rather I think it is how the CCS is configured. In this case I did not change any settings imported from the example project.

    I agree, this looks to be an issue with the example itself. Have you verified whether you get this same problem with a C2000Ware example? You should be able to install ControlSUITE and C2000Ware and have them be independent, but if you can replicate this on C2000Ware then I may be able to locate the issue more easily on my side.

    Weiliang Xu said:
    I am wandering if there is somewhere it specifies an environment path, since the error message pointing the path to a user related location. 

    I'm not too familiar with how ControlSUITE examples work, but if it's similar to C2000Ware examples then you should be able to see the dynamically created paths in the Linked Resources options of the Project Properties. There are projectspec files that are used to generate the example which include generic paths to try and locate certain resources for the device's software.

  • 0 in reply to Omer Amir
    Prodigy 90 points

    I tried one example project Example_2806xAdcTempSensor in C2000ware. It can compile properly. The problem is that I am not sure if this project is compatible with the hardware configuration of the Launchxl-f28069M kit. I cannot simply program it to the kit and run it. That is why I still want to figure out what is wrong with the demo project compilation.

  • 0 in reply to Weiliang Xu
    TI__Mastermind 30185 points
    Weiliang Xu said:
    The problem is that I am not sure if this project is compatible with the hardware configuration of the Launchxl-f28069M kit.

    I'm not sure what your concern is, the LaunchPAD still uses a F2806x device, and the example isn't relying on something externally connected:

    "In this example the ePWM1 is set up to generate a periodic ADC SOC interrupt - ADCINT1. One channel is converted - ADCINA5, which is internally connected to the temperature sensor."

    Weiliang Xu said:
    That is why I still want to figure out what is wrong with the demo project compilation.

    Since the C2000Ware example built properly but the ControlSUITE example didn't, I will forward this to the current ControlSUITE owner.

  • 0 in reply to Omer Amir
    Prodigy 90 points

    This is the problem with the compiler rather than with the ControlSUITE package. This example project was compiled using V6.1.0 compiler while my CCS used V15.12.3 when it gave out all error messages. I tried installing the old compiler V6.1.0 and recompiled the project. All errors were gone and only a few warnings.

  • 0 in reply to Omer Amir
    TI__Mastermind 21406 points

    Weiliang,

    Please continue using the C2000Ware equivalent example. If you're debugging this on the LaunchPad, ensure that you're using appropriate linker command files (.cmd) and target configuration files (.ccxml). You can find the launch pad equivalent for the F2806x in C2000Ware under device support.

    As mentioned previously, we've migrated device support for that device to C2000Ware and all examples should be present. Let us know if you're still having any issues.

    Regards,

    Ozino

  • 0 in reply to Ozino Odharo
    Prodigy 90 points

    Ozino,

    Thank you for your advice. I am able to run the demo project in ControlSUITE. I am aware that migrating to C2000WARE can get more support. So I will try to use the example projects there to start my firmware development.