• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 40 subscribers
  • Views 742 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/CC3220: Some questions about examples, project setup and the new "syscfg" file

Salvatore Castellano
Prodigy 160 points

Part Number: CC3220

Tool/software: Code Composer Studio

Hi,

I have experimented with a CC3220S-LAUNCHXL board, run some examples, and everything works fine.

Because the CC3220S seemed a good solution for my final product, I have designed a custom board with the CC3220S on it.

I can program the board, and run code on it; it seems to work fine. However, I ran into a small problem now...

First off, I created a new project based on the UARTECHO example project, and made the changes along the way.

I imported this example project in CCS, and automatically it was added with the new "syscfg" file; which by the way looks pretty cool and easy to configure.

Now, somewhere in my case I wished to use the "Timestamp_get32()" function, but for that I have to "include the Timestamp" module (xdc.runtime.Timestamp module). Normally I would do that in the .cfg file, however I do not have this file anymore.

So, some questions I have;

1. Where do I need to specify I wish to use the "xdc.runtime.Timestamp" module if my project does not have a .cfg file but rather the new .syscfg ?

Figured this one out myself; it seems the "example" project I imported (which contains the syscfg file) depends on another project, in which there are no source files but there is a cfg file. By adding the line 'var Timestamp = xdc.useModule('xdc.runtime.Timestamp'); in the release.cfg file, it worked !

2. What is the "best" way to create a new/clean project? (if possible, not based on the CC3220S-LAUNCHXL board, because it is not based on that hardware?)

3. What is the "lastest" best practice of setting up a project; using the new .syscfg file or rather the .cfg for before ?

Please advise... ?

FYI; I am using CCS Version: 8.1.0.00011, Uniflash Version: 4.4.0.1922, Simplelink CC32XX SDK 2.20.00.10 and XDCTools 3.50.07.20.core 

Salvatore

  • 0
    TI__Genius 16270 points
    Hi Salvatore,

    Good to see you are trying out the configuration tool! As you probably noticed, the tool is currently in "preview" and still subject to change.

    With the current version, there is an assumption you will be starting with an example and modifying it to suite your needs. If you are not using a launchpad, the easiest example to start with is the "empty" example as it does not have any board dependencies. You can start with one of the other examples, but a little extra editing will be required to get it to work on a different board.

    Once you have imported an example, you will want to edit the project properties in CCS. In the System Configuration tool node, change the -d flag to -b <your device>. In your case change the -d <lp path> to -b "CC3220S". If your .syscfg file has no board dependencies, that should be all you need. If your .syscfg file has board dependencies, you will get a compile error when building. If you look carefully at the compile error message, it will tell you what line number to look at in the .syscfg file (this is just a text file you can open). Comment out the offending line and try again.

    Board dependencies are usually going to be assigning a hardware component present on a board to a specific device peripheral. Commenting out the syscfg line in error, will just allow the tool to assign the device peripheral to any available pin(s).

    Tool improvements will be made to allow users to more easily migrate from one of the pre-defined boards to other boards and devices in the Simplelink family. The starting point will generally be an example though.

    There will be a new version of CCS (v8.2.0) and the SDKs out in a few weeks that has some improvements, although the features I referred to above are not there yet.