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.

CC1312R7: Using sysconfig without CCS

Part Number: CC1312R7
Other Parts Discussed in Thread: SYSCONFIG,

Hi,

We have a custom board with cc1312r7. We are using a third-party OS, and are therefore not using CCS, and we are only using the Simplelink CoreSDK. However, the device drivers in CoreSDK still requires misc. structures, e.g. the GPIO needs arrays of pin config,  GPIO_config struct, etc. As I understand it, the preferred way to generate these structures is by using SysConfig. However, when using standalone SysConfig, and entering our configuration, I am unable to generate the expected files: I was expecting a collection of .c and .h files containing the structs and defines, yet I am only getting .syscfg, .genlibs, etc. Files I am assuming could be utilized by CCS and its toolchain - which we don't utilize.

If someone could shed some light on using SysConfig in our use-case that would be highly appreciated.

  • Hi Andreas,

    You can check the generated files view in Sysconfig. This shows you all the files generated . 

    And in this view, you can individually save the files needed with the save button.

    Regards,

    Sid

  • Thanks for the reply Sid,

    The issue is that I am only seeing a .csv and .syscfg file being generated:

    This is my config design: 

    Tested on v1.12 and 1.14

  • Hi Andreas,

     I see the issue, you would also need to select an installed SDK to get all the generated files. 

    I see the same view as you when I do not define the software product and just select the device. 

    Regards,
    Sid

  • Hi,

    I am getting similar results even if I select an SDK - I am getting more files, but no .c or .h:

    This is my config - but I also tried different boards and different RTOS with the same result:

  • Hi Andreas, 

    I see that adding a Board module under the TI Drivers is necessary for you to generate the .c and .h files.  

    This is because board_init() function(generated in ti_driver_config.h) is used to call all the driver's initialization functions.

    Also, since you are not using a TI launchpad, you can untick the Generate Initialization Functions options which would generate the initialization function for the external flash on our launchpads. 

    Regards,

    Sid

  • Thank you very much - that solved it!

    Finally, may I ask if there is any documentation/user guide for sysconfig if available? I am only finding some old videos, bits and pieces in really old Simplelink SDK documentation, migration guides and so on.

  • Hi Andreas,

     The module specific documentation is provided in sysconfig itself within the modules. For instance in the above screenshot of mine, there is some context provided for board module. 

    But overall documentation for using it in the standalone mode is unfortunately lacking since the typical use-case is just using it as a part of projects based on examples provided for CCS or IAR tool chain.

    Regards,
    Sid