• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 53 subscribers
  • Views 244 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.

LAUNCHXL-CC1352R1: sysconfig issue

moshe jacobson18
Expert 2090 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: SYSCONFIG

Hi

I have CCS 10.4.0.00006 on win10 & i imported the rfWsnNode project.

i notice that the sysconfig generated file "ti_drivers_config.c" there is the const PIN_Config BoardGpioInitTable[CONFIG_PIN_COUNT + 1] table.

The pin names (and other settings) used in this table bear no resemblance to the pin names (& other settings) that i had set in sysConfig..

My question is.....where are the values in this table taken from??

thanks in advance.

i reposted this in the more applicable code composer studio forum & i dont see how to remove this post.

  • +1
    TI__Guru**** 317180 points

    This looks like a device specific question and not a CCS question.

    For the CC1352 two different drivers exist to set a DIO, the PIN and GPIO driver. The latter is a driver that can be used for all simplelink products, the PIN driver is specific for the CC13xx and CC26xx products. Since the PIN driver is device specific, syscfg only supports the GPIO driver. 

    Some examples uses both drivers which is  the case with the rfWsnNode project. The DIOs controlled by the GPIO driver is defined in syscfg. The DIOs used by the PIN driver is defined in the ti_drivers_config.c

  • 0 in reply to TER
    Expert 2090 points

    Hi TER

    Thanks for your response, yes, it does clarifies the issue....having example projects that use both drivers makes it rather confusing for the uninitiated. Should one then endeavour to just stick with the sysconfig gpio driver as per the buttonled example?.

  • 0 in reply to moshe jacobson18
    TI__Guru**** 317180 points

    A bit difficult question since to some extent the answer depends on which driver you prefer to work with. Also the PIN driver has access to more of the (IOC:IOCFGn registers. If you need some of the "extra" features under "13.9.1.2 Pin Configuration" in https://www.ti.com/lit/pdf/swcu185 you should check if the driver you select supports the feature. 

    My advice would be to start using the GPIO driver and then look to the PIN driver if you are not able to handle a given DIO the way you want with the GPIO driver. 

    The APIs for the drivers can be found here: dev.ti.com/.../node

  • 0 in reply to TER
    Expert 2090 points

    Hi TER

    Seeing this is the only place i can write a response...

    Sysconfig generates the table "PIN_Config BoardGpioInitTable" & the file ti_drivers_config.c , so i f i want to give the red led pin a more meaningful name in that table like MY_RED_LED_PIN where/which file would i need to modify so that sysConfig will use it?

  • 0 in reply to moshe jacobson18
    TI__Guru**** 317180 points

    Again, you have to look into which driver you want to use since the PIN_config table is used for the PIN driver and what you set in syscfg is related to the GPIO driver.

    It looks like the red LED is defined both in the PIN_config table and in syscfg in this example but I could not find anywhere that it's used by the GPIO driver.. Since the ti_drivers_config.c is regenerated when you compile if you have enabled syscfg, changes in this file will be overwritten. Hence if you want to use this example and use the LED in your code, one option is to use a #define. 

    If you look in NodeRadioTask.h the pin has gotten a new name:

     #define NODE_ACTIVITY_LED CONFIG_PIN_RLED

    This name is used in NodeTask.c

  • 0 in reply to TER
    Expert 2090 points

    Hi Ter...i really appreciate your responses.

    Yes, i saw all that & it was what sort of started the whole confusion...& now that thats all sorted, it just begs the question " from where does sysconfig pick up those names its outputting in ti_drivers_*.* from"....maybe its hard coded in the sys_config binary?

  • 0 in reply to moshe jacobson18
    TI__Guru**** 317180 points

    The information is in the rfWsnNode.syscfg file but not in an easily readable format. The scripting.x lines runs .js scripts found in the .meta folder under the path given that point to a folder under the SDK installation path. 

    As can be seen from the .syscfg file the pins in the PIN_config table is dependent on the type of board and the resources used. 

  • 0 in reply to TER
    Expert 2090 points

    Fantastic!! You showed me the path!!.

    i went and edited the rfWsnNode.syscfg file & changed the names of the button & led pins, & viola, when sysconfig regenerated the ti_drivers.c file those new names were in the ti_drivers_config.*

    i'm sure this might be written somewhere obscure.

  • 0 in reply to moshe jacobson18
    TI__Guru**** 317180 points

    We are currently looking at how to document this. I don't think it's documented somewhere at the moment. 

  • 0 in reply to TER
    Expert 2090 points

    finally...thanks once again & i hope this thread helps others.