• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 1270 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.

CCS/LAUNCHXL-F28069M: Example_F2806xLaunchPadDemo Compilation failure

Manu Abraham
Genius 3510 points
Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: CONTROLSUITE, C2000WARE,

Tool/software: Code Composer Studio

Hi,

After getting my hands on a F28069M Launchpad, have been trying for a few days to get some activity on the board other than for the stock demo from the Flash.

CCS (Eclipse seems to be a huge pain, even for setting up even the simplest stuff. Don't understand why though ..) Though worked with a plethora of MCU's and DSC's, but being an Eclipse first time user has sent shivers down my spine. The simplest of tasks looks like rocket science ! I can't believe that people are able to adapt to this environment ! Sorry, that was the amount of built up frustration over days.

I am trying to build the Launchpad demo with the following configuration:

Code Composer Studio  Version: 8.0.0.00016 OS: Windows 7, v.6.1, x86 / win32

Initially it resulted in an error with "make not found". After a bit of googling, came up on this thread:

That fixed the make issue, but results in stdint.h not found.

It results in a build failure, as shown.

>> Compilation failure
subdir_rules.mk:9: recipe for target 'Example_F2806xLaunchPadDemo.obj' failed
"../Example_F2806xLaunchPadDemo.c", line 25: fatal error: could not open source file "stdint.h" (no directories in search list)
1 catastrophic error detected in the compilation of "../Example_F2806xLaunchPadDemo.c".
Compilation terminated.
gmake: *** [Example_F2806xLaunchPadDemo.obj] Error 1

**** Build Finished ****

Any idea, what package/setting, I might be missing here ?

Is it possible for someone to help ?

Thanks,

Manu

  • 0
    TI__Guru**** 173310 points

    Manu,

    Are you importing the Launchpad demo project from ControlSuite or C2000Ware? C2000Ware is the newer and recommended software package. 

    In CCSv8, you can download and install C2000Ware, and also import projects all through the Resource Explorer view. 

    Below is a screenshot of my CCSv8 Resource Explorer view where I navigate down to the LaunchPad Demo project (C2000Ware->English->Devices->F2806X->F28069M->Examples->Bitfield->c28->launchxl-f28069m). I click the "Import to IDE" icon to import the project into CCS and then build the project, which builds successfully.

    Please let us know how and where you imported the project from, if different from the above.

  • 0 in reply to AartiG
    Genius 3510 points

    Hi AartiG,

    Thanks for the quick response!

    Imported the demo project from ti\controlSUITE\development_kits\LAUNCHXL-F28069M\LaunchPadDemo

    I have installed C2000Ware (C2000Ware_1_00_02_00) in D:\ti\, but could not get Resource Explorer to point in there.

    (It was one of those frustrating moments)

    Have been trying to get Resource Explorer, but I get this error.

    "An internal error has occurred.

    java.lang.NullPointerException"

    No wonder, I never liked Java and it never liked me .. ;-)

    Closed it tried to run it again, no difference.

    It goes on for a while Loading TIREX ..

    Finally, after 2 - 3 close and open CCS8 sessions, Resource explorer worked.. Finally.

    Finally, I got Resource Explorer as in the snapshot. Clicking on the import to IDE, it said it is in the cloud, therefore must be downloaded to the desktop first. By default it installs into C:\ti, but wanted to install it in D:\ti, the message stated the install path can be changed in preference. Couldn't find anything specific in Preferences, except for Product Discovery path, it had C:ti, D:\ti, C:\Progra ... unchecked both except D:\ti, tried again. Whatever I tried, it wants C:\ti. Oh well, stubborn it is.  c:\ti then.

    Well, the downloaded one is slightly newer, (C2000Ware_1_00_04_00)

    Downloaded, imported to IDE, built ..

    Some warnings, not a big issue, but for the sake of completeness here it is:

    Building file: "../sci_io.c"

    Invoking: C2000 Compiler

    "D:/ti/ccsv8/tools/compiler/ti-cgt-c2000_16.9.7.LTS/bin/cl2000" -v28 -ml -mt --cla_support=cla0 --float_support=fpu32 --vcu_support=vcu0 -g --include_path="D:/ti/ccsv8/tools/compiler/ti-cgt-c2000_16.9.7.LTS/include" --include_path="C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2806x/headers/include" --include_path="C:/ti/C2000Ware_1_00_04_00_Software/device_support/f2806x/common/include" --include_path="C:/ti/C2000Ware_1_00_04_00_Software/libraries/math/IQmath/c28/include" --include_path="C:/ti/C2000Ware_1_00_04_00_Software/libraries/math/FPUfastRTS/c28/include" --define="_DEBUG" --define=_FLASH --define="LARGE_MODEL" --quiet --verbose_diagnostics --diag_warning=225 --diag_suppress=552 --issue_remarks --preproc_with_compile --preproc_dependency="sci_io.d_raw"  "../sci_io.c"

    "../sci_io.c", line 74: remark: parameter "path" was never referenced

     int SCI_open(const char * path, unsigned flags, int llv_fd)

                               ^

    "../sci_io.c", line 74: remark: parameter "flags" was never referenced

     int SCI_open(const char * path, unsigned flags, int llv_fd)

                                              ^

    "../sci_io.c", line 74: remark: parameter "llv_fd" was never referenced

     int SCI_open(const char * path, unsigned flags, int llv_fd)

                                                         ^

    "../sci_io.c", line 106: remark: parameter "dev_fd" was never referenced

     int SCI_read(int dev_fd, char * buf, unsigned count)

                      ^

    "../sci_io.c", line 129: remark: parameter "dev_fd" was never referenced

     int SCI_write(int dev_fd, const char * buf, unsigned count)

                       ^

    "../sci_io.c", line 153: remark: parameter "dev_fd" was never referenced

     off_t SCI_lseek(int dev_fd, off_t offset, int origin)

                         ^

    "../sci_io.c", line 153: remark: parameter "offset" was never referenced

     off_t SCI_lseek(int dev_fd, off_t offset, int origin)

                                       ^

    "../sci_io.c", line 153: remark: parameter "origin" was never referenced

     off_t SCI_lseek(int dev_fd, off_t offset, int origin)

                                                   ^

    "../sci_io.c", line 161: remark: parameter "path" was never referenced

     int SCI_unlink(const char * path)

                                 ^

    "../sci_io.c", line 169: remark: parameter "old_name" was never referenced

     int SCI_rename(const char * old_name, const char * new_name)

                                 ^

    "../sci_io.c", line 169: remark: parameter "new_name" was never referenced

     int SCI_rename(const char * old_name, const char * new_name)

                                                        ^

    Finished building: "../sci_io.c"

    Tried loading it:

    and

    Run->Load->Select Program to Load, gives this error..

    Wonder, what it might be though .. ?

    Thanks a lot for the help,

    Manu

  • 0 in reply to Manu Abraham
    TI__Guru**** 173310 points

    Manu Abraham said:
    By default it installs into C:\ti, but wanted to install it in D:\ti, the message stated the install path can be changed in preference. Couldn't find anything specific in Preferences, except for Product Discovery path, it had C:ti, D:\ti, C:\Progra ... unchecked both except D:\ti, tried again. Whatever I tried, it wants C:\ti.

    The Resource Explorer Preferences allows you to specify where to download the package to, as well as which directories to scan for installed packages. 

    In my screenshot below, I added the D:\ti folder and set it to be the install folder. So future package downloads will install to D:\ti instead of c:\ti.
    And all the 3 directories listed there will be scanned for packages. Did this not work as described for you?


    Manu Abraham said:
    Some warnings, not a big issue, but for the sake of completeness here it is:

    I see the same build warnings but they seem to be harmless. 

    After a successful build, you can simply click the Debug icon in the CCS toolbar to start a debug session. 

    Let us know if that works.

  • 0 in reply to AartiG
    Genius 3510 points
    Thanks, that fixes the issue.

    Thanks,
    Manu