• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 488 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.

CC2652R7: Using Syscfg to assign pins

Douglas Havenhill
Prodigy 50 points
Part Number: CC2652R7
Other Parts Discussed in Thread: SYSCONFIG, CCSTUDIO, CODECOMPOSER

I have a custom design and I'm attempting to use SysConfig to assign the pins I want to use.  I started with spislave.syscfg because it looked like a simple way to start.

I first tried to assign pin 11 as a GPIO output pin.  The screenshot below shows the pin assignment.

I save the file and when I try to compile I get "cannot set '$assign to 'ball.11': No option named ball.11 defined. valid options are

If this is not the correct way to assign pins on the device how is it done?

  • 0
    TI__Guru**** 218217 points

    Hi Douglas,

    I did not experience any similar issues when applying the same changes in either the v5.30 or v5.40 SimpleLink SDK with the correct CCS/SYSCONFIG dependencies as listed in the SDK Release Notes.  What version of the SIMPLELINK-CC13XX-26XX-SDK, CCSTUDIO, and SYSCONFIG are you using?  Did you keep "Lock Pinmux" checked when selecting "Use Custom Board" in the SysConfig Device View?  Have you consulted the Custom Hardware module of the BLE5-Stack User's Guide?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 50 points

    Thanks for getting back to me.

    Versions in use

    Simplelink_cc13x2_26x2_sdk_5_20_00_52

    SysConfig (1.11.0+2225)

    CodeComposer Version 10.4.0.00006

    Yes, I kept the "Lock Pinmux" checked

    Yes, I have consulted the Custom Hardware module of the BLE5-Stack User's Guide.  I found nothing in there that was of help to me.

    Compiler objects to the reference to ball.xx in the .syscfg file

    e.g.

    GPIO1.mode              = "Output";
    GPIO1.$name             = "CONFIG_GPIO_LED_0";
    GPIO1.gpioPin.$assign   = "ball.11";
    GPIO1.pinInstance.$name = "CONFIG_PIN_2";

    I've been able to work around the issue by simply leaving the board settings in SysConfig to the LaunchPad and reassigning the header pins.

    For LauchPad the same pin is defined in .sysfg as

    GPIO1.mode = "Output";
    GPIO1.$name = "CONFIG_GPIO_LED_0";
    GPIO1.gpioPin.$assign = "boosterpack.39";
    GPIO1.pinInstance.$name = "CONFIG_PIN_2";

    Regards,

    Doug

  • +1 in reply to Douglas Havenhill
    TI__Guru**** 218217 points

    The SysConfig version should be 1.8.2 for this SDK which could be the root issue due to significant changes while adopting the newer SDK nomenclature and addition of device/utility support. I'm still not able to replicate this behavior with other similar dependencies.  Would you consider evaluating the newest SIMPLELINK-CC13XX-CC26XX-SDK and CCSTUDIO versions?  If you still have the same issue, please provide me with step-by-step changes to a new CC2652R7vspislave project which causes the problem.

    Regards,
    Ryan