LAUNCHXL-CC26X2R1: SDK3.20 to SDK 5.10 Migration PIN Snag

Hi Folks,

I am in the process of migrating two SDK3.20 projects to SDK5.10 and reviewing overall design and reliability. I have completed hardware bring up for one project, but have encountered a SPI interface problem in the other.

Overview

The SPI display operates correctly on the SDK3.20 binaries and debug but does not work on the SDK 5.10 verion of the same project. The problem most likely has to do with the transition from Pre-SysConfig to SysConfig, but after modifying the SysConfig the problem persists. I identified the source of the bug but am not really sure what changes are necessary.

Progress to Date

I compared the SPI configuration generated by SysConfig (SDK5.10/ti_drivers_config.c) against the original modified board file (SDK3.20/CC26X2R1_LAUNCHXL.c). I made changes to SysConfig to mirror the SDK5.10 SPI Config to match the SDK3.20 SPI Config.

This appears to eliminate the SysConfig as the root of the problem since the configurations appear consistent.

I reviewed the relevant APIs to develop a method to debug the issue.

extern SPI_Handle SPI_open(uint_least8_t index, SPI_Params *params);

/*!
 *  @brief  Function to initialize the #SPI_Params struct to its defaults
 *
 *  @param  params      An pointer to #SPI_Params structure for
 *                      initialization
 *
 *  Defaults values are:
 *  * SPI_Params.transferMode        = #SPI_MODE_BLOCKING
 *  * SPI_Params.transferTimeout     = #SPI_WAIT_FOREVER
 *  * SPI_Params.transferCallbackFxn = NULL
 *  * SPI_Params.mode                = #SPI_MASTER
 *  * SPI_Params.bitRate             = 1000000 (Hz)
 *  * SPI_Params.dataSize            = 8 (bits)
 *  * SPI_Params.frameFormat         = #SPI_POL0_PHA0
 */

extern PIN_Handle PIN_open(PIN_State *state, const PIN_Config pinList[]);


/** @brief  Add pin to pin set for open PIN handle
 *
 *  If the requested pin is unallocated it will be added, else an error code
 *  will be returned.
 *  @param handle   handle retrieved through an earlier call to PIN_open().
 *  @param pinCfg   Pin ID/configuration for pin to add.
 *  @return Error code if unsuccessful, else PIN_SUCCESS
 */

This appears to be the only code that could affect the startup of the display, so I added debugging code to check the state of the PINs and SPI interface based on SPI_open and PIN_open.

#include <ti/drivers/SPI.h>
#include <ti/drivers/PWM.h>
#include "ti_drivers_config.h"

// Display Configuration
#include <ti/display/Display.h>
extern Display_Handle dispHost;

PIN_Handle h_display_pins = NULL;
PIN_State  display_pins_state;
const PIN_Config display_pins_table[] = {
    POWER_ENABLE     | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MIN,
    DISPLAY_RESET    | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MIN,
    DISPLAY_BUSY     | PIN_INPUT_EN | PIN_PULLDOWN,
    PIN_TERMINATE
};

void EPD_bus_init(void){
  h_display_pins = PIN_open(&display_pins_state, display_pins_table);
  if(h_display_pins != PIN_SUCCESS){
      Display_printf(dispHost, 0, 0, "Display PIN: Initialization Error\n");
  }
  EPD_DelayMs(5);
  pwm_init();
  SPI_init();
  SPI_Params_init(&SPIparams);
  SPIparams.transferMode        = SPI_MODE_BLOCKING;
  SPIparams.bitRate             = 4800000;
  SPIparams.mode                = SPI_MASTER;
  SPIparams.dataSize            = 9;
  SPIparams.frameFormat         = SPI_POL0_PHA0;
  SPIhandle = SPI_open(SPI_EPD_DISPLAY, &SPIparams);
  if(!SPIhandle) {
      Display_printf(dispHost, 0, 0, "Display SPI: Initialization Error\n");
  }
}
SPI_Handle      SPIhandle = NULL;
SPI_Params      SPIparams;

PWM_Handle hPWM = NULL;

When the display initialization code is called, the following messages appear:

Display: Display Init EVT
Display SPI: Initialization Error
Display PIN: Initialization Error

The h_display_pins variable returns after PIN_open:

When I changed the PIN table slightly to use names directly from ti_drivers_config.c as follows:

const PIN_Config display_pins_table[] = {
    CONFIG_PIN_4     | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MIN,
    CONFIG_PIN_6     | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MIN,
    CONFIG_PIN_7     | PIN_INPUT_EN | PIN_PULLDOWN,
    PIN_TERMINATE
};

the following messages appear:

Display: Display Init EVT
Display PIN: Initialization Error

This change seems strange to me because I would assume correcting the PIN table would improve the result of PIN_open. Instead, I observe that the SPI_open stops truning null. 

Question

• How can I further investigate this problem?
• Is there an API violation that makes the SDK3.20 method invalid for the SDK5.10?