• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 542 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-CC1312R1: use sysconfig tool create .syscfg some problem

Laker
Prodigy 90 points
Part Number: LAUNCHXL-CC1312R1
Other Parts Discussed in Thread: SYSCONFIG

Tool/software: Code Composer Studio

SDK verision: simplelink_cc13x2_26x2_sdk_3_40_00_02

sysconfig verison: 1.4.0+1234

I try to use SysConfig in CCS to configure the IO of my application.  but I have some doubts:

1. open SysConfig, I find RF STACKS have three items, I want quick to use sdk to connect other devices, but sdk only have EasyLink. How to quick start ?

TI 15.4

EasyLink

Custom

2. use SysConfig add uart , it will generate ti_devices_config.c, ti_drivers_config.c, ti_drivers_config.h, syscfg_c_rov.xs and untitled.syscfg.  Do I need all of these files?

if I generate all the files, how to use these file to create custom application

3. use SysConfig generate *.syscfg's format is different from SDK demo syscfg, Is I use the way not right?

-------------------------------------------------------------------------------------------------------------------generate---------------------------------------------------------------------------------------------------------------

/**
* These arguments were used when this file was generated. They will be automatically applied on subsequent loads
* via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
* @cliArgs --board "/ti/boards/CC1312R1_LAUNCHXL" --product "simplelink_cc13x2_26x2_sdk@3.40.00.02"
* @versions {"data":"2020021217","timestamp":"2020021217","tool":"1.4.0+1234","templates":"2020021217"}
*/

/**
* Import the modules used in this configuration.
*/
const UART = scripting.addModule("/ti/drivers/UART", {}, false);
const UART1 = UART.addInstance();

/**
* Write custom configuration values to the imported modules.
*/
UART1.$name = "CONFIG_UART_0";
UART1.$hardware = system.deviceData.board.components.XDS110UART;
UART1.txPinInstance.$name = "CONFIG_PIN_0";
UART1.rxPinInstance.$name = "CONFIG_PIN_1";
UART1.uart.$name = "MyUART1";

const CCFG = scripting.addModule("/ti/devices/CCFG", {}, false);
CCFG.ccfgTemplate.$name = "ti_devices_CCFGTemplate0";

/**
* Pinmux solution for unlocked pins/peripherals. This ensures that minor changes to the automatic solver in a future
* version of the tool will not impact the pinmux you originally saw. These lines can be completely deleted in order to
* re-solve from scratch.
*/
UART1.uart.$suggestSolution = "UART1";
UART1.uart.txPin.$suggestSolution = "8";
UART1.uart.rxPin.$suggestSolution = "7";
-----------------------------------------------------------------------------------------------------sdk demo -----------------------------------------------------------------------------------------
/*

* Copyright (c) 2018-2019, Texas Instruments Incorporated
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* * Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* * Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* * Neither the name of Texas Instruments Incorporated nor the names of
* its contributors may be used to endorse or promote products derived
* from this software without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
* THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
* CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
* OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
* OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
* EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
// @cliArgs --board /ti/boards/CC1312R1_LAUNCHXL

/*
* uartecho.syscfg
*/

/* ======== RTOS ======== */
var RTOS = scripting.addModule("/ti/drivers/RTOS");
RTOS.name = "TI-RTOS";

/* ======== GPIO ======== */
var GPIO = scripting.addModule("/ti/drivers/GPIO");
var gpio = GPIO.addInstance();
gpio.$hardware = system.deviceData.board.components.LED0;
gpio.$name = "CONFIG_GPIO_LED_0";

/* ======== UART ======== */
var UART = scripting.addModule("/ti/drivers/UART");
var uart = UART.addInstance();
uart.$hardware = system.deviceData.board.components.XDS110UART;
uart.$name = "CONFIG_UART_0";

  • 0
    TI__Guru 58425 points

    Hi,

    I'm a bit confused to what your are looking for here.

    1) Easylink and TI15.4 is the only stacks provided for the CC1312 device. There is examples for each of these on how to setup simple networks, have your looked at them?

    2) Yes, you want all these files in the project. They are used by TI Drivers/Stacks (depending on what you have actually configured in SysConfig).

    3) I would not worry to much of the format, what is important to you is that the generated output is OK, not how the SysConfig script looks like in terms of formatting (assuming it does what it should).