• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 51 subscribers
  • Views 644 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-CC2640R2: Need a clear path/procedure to setup an "empty" project with ALL of the SDK features enabled/included and ready to use.

Marc Yaxley
Expert 1105 points
Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: CC2650

Tool/software: Code Composer Studio

Hi all.

I have the LAUNCH-CC2640R2 and CCS7  (Version: 7.1.0.00016).   I have created an empty project, pretty easy.  However there is almost no SDK drivers/driverlib or other support in the project tree.  I see all the BLE examples have much fuller project trees, especially the includes and drivers in them.  I see that many of them have 'virtual folder' as the path/source.  The 'empty project' does not see to have this stuff.

I then  want to add I2C and I2S driver resources and have been fumbling around for a couple of days trying to pull that stuff in to a build.  It is painful and moving files around and so on to do it I feel probably isn't the correct method.  My folders and project tree is a mess, not organized like the examples that have these things.

Am I missing a key procedure on doing this?  How would one setup a simple I/O to GPIO only project to begin with.

I have played with many of the examples, BLE ones and PWMLED and so on, they all work fine, download and work.

I see a ton of things in most examples "project properties" panels which are fairly diverse and wouldn't be known to do for most engineers.  I have attempted to take a BLE project and chop it down to what I need but got that so fumbled up I realized there has to be an easier way to do this?

My initial project does not need BLE so I don't want to include it until later on.  Also, I see it is weird to debug in the TIRTOS structure so I would hope to work single thread initially then bring all that other goodies in when needed when we go to the BLE model of our product.

Anybody out there have a good PDF or video I should see, or a forum write up?

I have seen many write ups which seem to not really directly answer this question, rather pointing to another forum answer of one probelm or another.

Thanks for any pointers/advice,

Marc Y.

  • 0
    TI__Guru* 86131 points
    Hi Marc

    I would strongly recommend that you go through several of the labs from the SimpleLink Academy.

    You will find an overview here:

    dev.ti.com/.../

    BR

    Siri
  • 0 in reply to Siri
    Expert 1105 points
    Hi Siri,

    Thank you for taking the time to reply.

    I had found the academy and followed some of it already.


    It shows how to just 'turn on' drivers which are in the SDK already. Usually simply un-comment

    the drivers_init() call. Visit board.h to change any pin assignments and so on.


    The MPS432 has many more drivers, the I2S one that I need so that make it look simple.

    The CC2640R2 SDK is missing the I2S and maybe other drivers it could have.


    This is the issue of how to add them in the right places so they are found by ALL of the

    files which have include statements and paths for the H and C files for the drivers.

    Some of them I see in example projects have "virtual paths" and I have no idea how those

    got set up for various drivers. Some examples have some driver H and C files in the source

    tree too, I see several techniques being used to accomplish things.


    I want to simply to this the preferred TI way of setting up a project tree. Is the answer that

    I have to bring or import some of the drivers you TI hasn't put in the board's SDK so far?

    Working through the academy pages is a great "here's how it's done" for the things that

    are in the SDK for a given board. What I need is beyond that a bit by the need to popluate

    my SDK, or build tree with the files I need. I know how to "add new" C files to the proejct

    and that sort of thing.


    I found already ported I2S driver source C&H files in an example which seem to be for

    the CC2640R2 and some for the CC2650 parts which might work, but how to I get these

    hooked into my build tree?


    Any more closer in ideas to get a full driver source tree set for my SDK which includes

    drivers that cover the various devices in this MCU?


    Thanks,

    Marc Y.
  • 0 in reply to Marc Yaxley
    Expert 1105 points
    Hi, I am looking in this tree:
    /home/marc/ti/simplelink_cc2640r2_sdk_1_50_00_58/source/ti/drivers/
    and see two levels of source, one appears the interface to RTOS and the actual lowest level driver code which are in the various folders that are in that same directory. However there is no I2S source dir4ectory. I only see the I2S.c and I2S.h files. I have found some driver like files in another director: /ble_examples-master/source/ti/drivers/i2s which I downloaded from GitHub. These came from the file ble-audio-examples.zip which I downloaded from GitHub. I would love to simply the the I2S_echo program up then I could hack from that to what I need for my initial audio speaker driver testing.
    Regards,
    Marc Y.
  • 0 in reply to Marc Yaxley
    Expert 1105 points
    Ok, seems you can't just drag and drop things needed into the project tree. They just don't get built with the build. I used Silicon Labs MCU and that is all you needed to do was drop things in the project tree and their IDE (Eclipse) would remake the make-file then do a full build.
    This picked up any new file you had created or dropped in the project tree. Anything like this in CCS7 or am I simply missing some key step?
  • 0 in reply to Siri
    Expert 1105 points
    See additional notes/questions about the issue.
  • 0 in reply to Marc Yaxley
    TI__Guru* 86131 points

    I am sorry but we do not have any such example that you are asking for. In the driver documentation ( dev.ti.com/.../index.html ) you will find all the drivers that are available in the SDK. It is also stated which files you need to include when using the driver. This, together with the examples already in the SDK, and the SimpleLink Academy is what we have to offer.

    Siri

  • 0 in reply to Siri
    Expert 1105 points
    With all the provided information, which is well done and plentiful I am one of the poor souls that has a project that doesn't have a remotely close "demo/example" case to start with. I did find I could bring an example in from the CC2650 which is closer so I will have to hack from there to get where I need to go. My last comment is that it seems hard for the "new-by" on CCS7/Eclipse to get setup. Not sure where this lack of direction comes from since Eclipse is not TIs project but layered on to provide the studio. Other mfg's do it different, some easier and some harder to build a project tree. It's better than just starting out with the data book and register assignments of years past.
    Thanks ,
    Marc Y.