• Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1181 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.

How to create a NEW project based on example Project? (CCSv6)

Andrew Ricci
Intellectual 290 points

I've reading the forum trying to solve my question, and seems there are a lot of persons with the same problem and no one seems to really answer the questions or the problem itself.

I don't understand why TI seems aim for make things complex, the line of work on CCS is difficult, this IDE has too many sym-links on each file and whenever you go and try to find the source file looks like they are trying to hide it in such a way that you'll never find it.

when I create a new project from scratch and write a built-in instruction it doesn't offer to me the possibility of make the #include automatically (as Eclipse does).

you as a developer rejoices when using other IDE because the idea of IDE is help the developer not piss him off, In such a way results tons times better work on notepad++ and compile directly from the console (if my IDE instead of help me will make me over spend time just trying to solve library import problems).

last night I spent almost whole night trying just to build a project based on the "simpleBLEPeripheral" and trying to solve the linked files problem, and guess what? later on I noticed that all changes on the files I was doing in my project were reflected on the original project!!! .... @_@ ..... >_<  ...

if I did not work on the original project is because I didn't want to mess in the original code, why it is too difficult to just copy and paste a project without any dependency on each other so that I can really start working???.

why am I so angry? because when me and my team have been working with opensource software (like Android) we have never had any of these problems, now that I spent more than thousand dollars buying the development kits the line of development is so poor and time consuming. and added the licence of CCS is so expensive (after the trial time surely I will not buy the licence).

**************

after my complain, if someone could help me, I will really appreciate it, (sorry, I just needed to release my anger).

thank you very much in advance.

  • TI__Guru**** 450761 points
    Hello,
    I am sorry to hear of your frustrations. CCS can be complex to use at times, especially since there are many different ways (sometimes too many ways) to do the same thing. Projects can be set up in multiple ways. The default Eclipse behavior (which it sounds like you are more comfortable with) is that when files are added to a project, those files are copied into the project folder. So there is a separate copy that is part of the project and modifying the source file will only modify the copy and not the original. You can also have it so that you can "link" a file to the project, meaning that a reference to the file, in its original location, is kept by the project and any changes made to that file will be changes to the original source. The simplelink projects like the simpleBLEPeripheral example are designed this way and many users prefer this method for various reasons, one of the major ones being many other embedded development environments work in a similar way (including the legacy CCS versions) and people got used to it. Early feedback for Eclipse based CCS was to make the default to use links instead of physical copies because many people were used to that method. I suppose it really comes down to preference and people will create their project based on their desires, CCS just gives all the various options to do it which ever way and does not give preference one way or the other. But then again the fact that you can do it both ways can indeed be confusing since other environments offer just one way to avoid confusion. The question of "how do I preserve my original source tree when working with imported project, but not have to deal with version control" is a valid question and complaint. The common method is an old technique of simply creating an archive of the original source tree and going back to it as needed. I hope you continue to try to use CCS - it does have a steep learning curve but once people get used to it, most people are generally satisfied with all the options available with it

    Thanks
    ki
  • in reply to Ki
    Intellectual 290 points

    thank you very much for your answer.

    now, I'm wondering how can I make the appropiatte libraries import?

    1. import the example project, create a new file within it and start working on it

    2. write within my file the import statement in the same way the other files does and it yields error, i.e ("... can't find the scif.c ... ")... I tried writing the absolute path, if I do so the next errors are the source file's imports, example:

    #include "scif.h"
#include "scif_framework.h"
#include <inc/hw_types.h>
#include <inc/hw_memmap.h>
#include <inc/hw_aon_event.h>
#include <inc/hw_aon_rtc.h>
#include <inc/hw_aon_wuc.h>
#include <inc/hw_aux_sce.h>
#include <inc/hw_aux_smph.h>
#include <inc/hw_aux_evctl.h>
#include <inc/hw_aux_aiodio.h>
#include <inc/hw_aux_timer.h>
#include <inc/hw_aux_wuc.h>
#include <inc/hw_event.h>
#include <inc/hw_ints.h>
#include <inc/hw_ioc.h>
#include <string.h>

    all of these mark error due to unsolve dependencies...

    ..... so, how can I make the appropiate link to let CCS find the libraries as it does with the other files (the ones coming in within the imported project).

    thanks once again.

    best regards

  • in reply to Andrew Ricci
    TI__Guru**** 450761 points

    Hello,

    Jeong Kim said:
    and it yields error, i.e ("... can't find the scif.c ... ")

    When does this error appear? Is this a compile error? Can you provide your entire build output as it appears in the build console?

    Thanks

    ki

  • in reply to Ki
    Intellectual 290 points

    I've included (in theory) the rightful Links for all files or the projects I'm trying to merge and still CCS says can't open the source. :'(  ... I'm really getting so discouraged.

    I've also included this lines on the .project file under the source tree in the project folder.

    <link>
			<name>scif.c</name>
			<type>1</type>
			<location>C:/Users/xXANGELXx/Documents/Texas Instruments/Sensor Controller Studio/examples/analog_light_sensor/source/scif.c</location>
		</link>
		<link>
			<name>scif_framework.c</name>
			<type>1</type>
			<location>C:/Users/xXANGELXx/Documents/Texas Instruments/Sensor Controller Studio/examples/analog_light_sensor/source/scif_framework.c</location>
		</link>

    and still is finding the same errors.


    Thanks for your help

  • in reply to Andrew Ricci
    TI__Guru**** 450761 points

    The issue is that it is unable to find the header files listed (ex_include_tirtos.h and ti/drivers/power/PowerCC26XX.h). Check your include search paths and make sure the the paths to those files exist. For example, for the latter I think it comes with TI-RTOS CC13xx/CC26xx. In my installation, it is in C:\ti\tirtos_cc13xx_cc26xx_2_16_01_12_eng\products\tidrivers_cc13xx_cc26xx_2_16_01_12_eng\packages. Make sure a similar include search path exists in your environment. As for the other file, I'm not sure where that is from. But you need to specify the include search path for that file also in the project properties.


    thanks

    ki