LAUNCHXL-CC1310: Changes required to remap SPI pins

An indirect answer but consider using SYSCONFIG for your project. Managing pins is much easier that way.

Hi Kier

Thanks for the response, but I believe there is no support for the CC1310 on SysConfig. Also, I am making changes to an existing project where all reference to the SPI peripheral and usage was removed.

OK but according to the SYSCONFIG product page anyway, CC1310 is supported:

Thats correct, But I'm unable to integrate the board files into Code composer as Sysconfig isnt supported by CC13x0 SDK. See the following post. Unless I am missing something, on how I can use Sysconfig?

I see your point. The ZC answer points to other questions that are two years old. It's maybe worth challenging that answer again citing the SYSCONFIG product page info. Since the SDK is essential to SYSCONFIG either the SYSCONFIG product is wrong or ZC's answer is out of date.

From the documentation on how to import a .syscfg file, it is only possible to generate a project from the CC13x2 / CC26x2 SDK, where the accompanying configuration (.c/.h) files will be provided, along with the .syscfg file, in CCS. I tried generating a project from this SDK and that checks out. 

The "support" for the CC1310 you have referred to, is merely to provide an overview of the chip and to configure whatever pins you want and the sysconfig will indicate if the current configuration is possible, and it generates the board.h and board.c in sysconfig, if it is. Beyond this, i.e. the LAUNCHXL.c and LAUNCHXL.h files are not provided, nor is the chance to import the .syscfg file you save, into CCS. So the product page is not wrong, but just does not provide all the info.

Hi Suvashan,

You are correct about CC1310 not supporting SysConfig.

As of your actual question, it seems like you are already know where to change.

In CC1310_LAUNCHXL.h, replace that line, for instance:

#define CC1310_LAUNCHXL_SPI0_MISO             IOID_8          /* RF1.20 */

With the actual IOID you need for your custom board.

Regards,

Arthur

Arthur R☑️ said:

You are correct about CC1310 not supporting SysConfig.

Then please remove CC1310 from the list of devices supported on the SYSCOFNIG product page.

Hi Kier,

Yes, I am in contact with the ti.com team and this should happen soon.

Regards,

Arthur

Hi Arthur. 

I don't believe this is the full solution. If one does this, and it clashes with pins that are added to the gpioPinConfigs array in LAUNCHXL.h, pin assignment will not be succesful. Thats what I am encountering now and my SPI0 initialisation is failing. 

Hi Suvashan,

Let me provide you with an example where we can change the default SPI pins.

What is certain is that you must not change ioc.h.

Regards,

Arthur