• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1320 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Creating projects for a custom board with CCS (v11)

Pat Deegan
Prodigy 10 points
Other Parts Discussed in Thread: CC1352P

Greetings,

We have some code built around the rfWsnNode sample (sub 1-GHz is what we're using most at the moment, planning on some 2.4GHz band use later) running on dev board, currently built using the relevant CC1352P1_LAUNCHXL sample from the resource explorer. Now it's time to move to our own hardware.

Though there are similarities,  the actual target is a custom PCB built around the CC1352P and there are a number of differences (e.g. the pins used for an RF switch, changes to LEDs/buttons, additional peripherals, etc) and I've been having a hard time locating anything actionable in terms of how you move from playing with dev kits to your own hardware.

There's a ton of stuff being magically generated and it's hard to tell where all this is coming from.

I tried File -> New -> CCS project just to see what a minimal system would look like, and that doesn't even build.  "We recommend using a sample from the resource explorer"... fine, but how exactly do we make code work on anything other than the launchpad dev boards?

After some digging around, I finally managed to find that hidden deep (in a hidden directory!) under

simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/boards/.meta

there are the actual files that the .syscfg file is referring to with

 @cliArgs --board /ti/boards/CC1352P1_LAUNCHXL --rtos tirtos7

and it's some bundle of node meta info that gets transformed into syscng/ti_*.(c|h) files in the build directory.

So, the questions are:

  • are we supposed to create our own versions of this JS meta info to add our own custom board, and edit the syscfg file to point to it?
  • if so, where are the docs on this?
  • if not, where is the process for adding a board we can use in CCS, to use with RTOS (and the Sub 1-GHz radio and all the things), documented?

I don't actually care if it's command line or in CCS, don't care if we have to start a new project and move our code into it, just want to be able to focus on our functionality and have the platform side integrated same as the dev kits are.

Thanks for any assistance and feel free with any questions of your own.

PatD

  • +1
    TI__Guru**** 317180 points

    If you want to start a new project the easiest is to start from one of the examples. Typically the empty example can be used. If you have developed an application on a Launchpad, copy the application files into the project and remove the example files. Select the Launchpad that is closest to the board you are going to use. Use syscfg to setup the driver you want to use. When you have setup what is possible in syscfg, you can use this:

    Then you are able to setup your custom board. 

    It is possible to make your own syscfg files but we don't have any documentation for this. I have done small changes a couple of times in the syscfg files but that has been based on copy/ paste from other files. For LEDs it's reasonable easy to change the pin number they are assigned to if you search the js files (I have done it once for a LED on a custom board).The RF switch pins could be setup in rfDriverCallbackAntennaSwitching   

  • 0 in reply to TER
    Prodigy 10 points

    Ah, perfect... managed to set everything up

    Looks like it put all the config into project.syscfg as entries like:

    Fullscreen
    1
    2
    3
    4
    GPIO9.$name = "CONFIG_GPIO_ACC_CSN";
    GPIO9.mode = "Output";
    GPIO9.initialOutputState = "High";
    GPIO9.gpioPin.$assign = "ball.38";
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    so we can add to versioning and edit sans the GUI.

    Thanks!

    PatD