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

SIMPLELINK-CC13XX-CC26XX-SDK: Sysconfig not updating naming according to latest CoreSDK

Andreas Urke
Expert 1460 points
Part Number: SIMPLELINK-CC13XX-CC26XX-SDK
Other Parts Discussed in Thread: SYSCONFIG

Hi,

The latest CoreSDK release notes state:

"(...) If you change a setting in the SysConfig UI, the legacy names in your .syscfg file will be updated to the appropriate name automatically, for example, spi0.mosiPin will be updated to spi0.picoPin."

I have played around with my SPI settings in SysConfig v1.15 (that is shipped with the latest Simplelink F2 SDK), and v1.16 from TI.com. Neither of the versions update the SPI pin naming. Am I missing something?

  • 0
    TI__Guru**** 208667 points

    Hi Andreas,

    Thank you for reporting this behavior.  I am observing the same behavior on my setup and am asking the SysConfig Development Team to provide further comments.

    Regards,
    Ryan

  • +1
    TI__Guru**** 208667 points

    Hi Andreas,

    It is not the SysConfig version that makes this change, instead you will need to migrate your *.syscfg file into a v7.10 SDK project to observe these changes being applied.  For example, if I take spimaster.syscfg from v6.41 and use it to replace spicontroller.syscfg from the v7.10 project, and rename the SPI and GPIOs in order to avoid application build errors, then I can observe that the original spi0.mosiPin becomes spi0.picoPin and so on.

    Regards,
    Ryan