CC1312R: SPI and UART TI driver does not configure GPIOs any more since SDK 5.30

Do you see this issue only when porting from a previous SDK or also for the examples in the newest SDK? 

I’m not sure exactly what to answer, but this change in TI driver behaviour was introduced in SDK 5.30 when the pin driver was removed. And I see no changes in the TI drivers between SDK 5.30 to 6.10 with regards to GPIO configuration.

Let me give you an example to make it more clear. The following code is from TI drivers in SDK 5.30.

The initialization function of driver /source/ti/drivers/i2c/I2CCC26XX.c   calls GPIO_setConfig, thus configuring the pins.

static int I2CCC26XX_initIO(I2C_Handle handle, void *pinCfg) {
    I2CCC26XX_Object           *object;
    I2CCC26XX_HWAttrsV1 const  *hwAttrs;

    /* Get the pointer to the object and hwAttrs */
    object = handle->object;
    hwAttrs = handle->hwAttrs;

    /* If the pinCfg pointer is NULL, use hwAttrs pins */
    if (pinCfg == NULL) {
        object->sdaPin = hwAttrs->sdaPin;
        object->sclPin = hwAttrs->sclPin;
    } else {
        object->sdaPin = ((I2CCC26XX_I2CPinCfg *)pinCfg)->pinSDA;
        object->sclPin = ((I2CCC26XX_I2CPinCfg *)pinCfg)->pinSCL;
    }

    /* Configure I2C pins SDA and SCL and set their muxes */
    GPIO_setConfig(object->sdaPin, GPIO_CFG_OUT_OD_PU);
    GPIO_setMux(object->sdaPin, hwAttrs->sdaPinMux);

    GPIO_setConfig(object->sclPin, GPIO_CFG_OUT_OD_PU);
    GPIO_setMux(object->sclPin, hwAttrs->sclPinMux);

    return I2C_STATUS_SUCCESS;
}

The corresponding function in the TI SPI driver /source/ti/drivers/spi/SPICC26X2DMA.c does not call GPIO_setConfig, only the GPIO_setMux functions, so the pins are not configured. That’s why we need to do it in our application before calling the SPI driver

static void initIO(SPI_Handle handle)
{
    SPICC26X2DMA_Object        *object = handle->object;
    SPICC26X2DMA_HWAttrs const *hwAttrs = handle->hwAttrs;

    if (object->mode == SPI_SLAVE) {
        GPIO_setMux(hwAttrs->mosiPin, hwAttrs->rxPinMux);
        GPIO_setMux(hwAttrs->misoPin, hwAttrs->txPinMux);
        GPIO_setMux(hwAttrs->clkPin, hwAttrs->clkPinMux);

        /* Configure CSN callback for optional RETURN_PARTIAL slave mode */
        if (object->csnPin != GPIO_INVALID_INDEX) {
            GPIO_setMux(object->csnPin, hwAttrs->csnPinMux);
            GPIO_setCallback(object->csnPin, csnCallback);
            GPIO_setUserArg(object->csnPin, handle);
        }
    }
    else {
        GPIO_setMux(hwAttrs->mosiPin, hwAttrs->txPinMux);
        GPIO_setMux(hwAttrs->misoPin, hwAttrs->rxPinMux);
        GPIO_setMux(hwAttrs->clkPin, hwAttrs->clkPinMux);

        /* Mux CS unless it is software-controlled */
        if (object->csnPin != GPIO_INVALID_INDEX) {
            GPIO_setMux(object->csnPin, hwAttrs->csnPinMux);
        }
    }
}

Hei Johannes,

Driver specific GPIO configurations are indeed now generated through our Sysconfig tool, since around 5.30. If you load an spi example (spimaster for instance) from the latest SDK, you will see that this pin configuration is done in Board_init() -> GPIO_init(). GPIO_init then takes into account the GPIO configuration table (gpioPinConfigs) that was generated through Sysconfig. (see code snippet).

/*
 *  ======== gpioPinConfigs ========
 *  Array of Pin configurations
 */
GPIO_PinConfig gpioPinConfigs[31] = {
    0, /* Pin is not available on this device */
    0, /* Pin is not available on this device */
    0, /* Pin is not available on this device */
    0, /* Pin is not available on this device */
    0, /* Pin is not available on this device */
    GPIO_CFG_NO_DIR, /* DIO_5 */
    GPIO_CFG_OUTPUT_INTERNAL | GPIO_CFG_OUT_STR_MED | GPIO_CFG_OUT_LOW, /* CONFIG_GPIO_LED_0 */
    GPIO_CFG_OUTPUT_INTERNAL | GPIO_CFG_OUT_STR_MED | GPIO_CFG_OUT_LOW, /* CONFIG_GPIO_LED_1 */
    /* Owned by CONFIG_SPI_SLAVE as MISO */
    GPIO_CFG_INPUT_INTERNAL | GPIO_CFG_IN_INT_NONE | GPIO_CFG_PULL_NONE_INTERNAL, /* CONFIG_GPIO_SPI_SLAVE_MISO */
    /* Owned by CONFIG_SPI_SLAVE as MOSI */
    GPIO_CFG_OUTPUT_INTERNAL | GPIO_CFG_OUT_STR_MED | GPIO_CFG_OUT_LOW, /* CONFIG_GPIO_SPI_SLAVE_MOSI */
    /* Owned by CONFIG_SPI_SLAVE as SCLK */
    GPIO_CFG_OUTPUT_INTERNAL | GPIO_CFG_OUT_STR_MED | GPIO_CFG_OUT_LOW, /* CONFIG_GPIO_SPI_SLAVE_SCLK */
    GPIO_CFG_NO_DIR, /* DIO_11 */
    /* Owned by CONFIG_UART2_0 as RX */
    GPIO_CFG_INPUT_INTERNAL | GPIO_CFG_IN_INT_NONE | GPIO_CFG_PULL_DOWN_INTERNAL, /* CONFIG_GPIO_UART2_0_RX */
    /* Owned by CONFIG_UART2_0 as TX */
    GPIO_CFG_OUTPUT_INTERNAL | GPIO_CFG_OUT_STR_MED | GPIO_CFG_OUT_HIGH, /* CONFIG_GPIO_UART2_0_TX */
    GPIO_CFG_NO_DIR, /* DIO_14 */
    GPIO_CFG_INPUT_INTERNAL | GPIO_CFG_IN_INT_NONE | GPIO_CFG_PULL_NONE_INTERNAL, /* CONFIG_SPI_MASTER_READY */
    GPIO_CFG_NO_DIR, /* DIO_16 */
    GPIO_CFG_NO_DIR, /* DIO_17 */
    GPIO_CFG_NO_DIR, /* DIO_18 */
    GPIO_CFG_NO_DIR, /* DIO_19 */
    /* Owned by CONFIG_SPI_SLAVE as SS */
    GPIO_CFG_OUTPUT_INTERNAL | GPIO_CFG_OUT_STR_MED | GPIO_CFG_OUT_HIGH, /* CONFIG_GPIO_SPI_SLAVE_SS */
    GPIO_CFG_INPUT_INTERNAL | GPIO_CFG_IN_INT_NONE | GPIO_CFG_PULL_NONE_INTERNAL, /* CONFIG_SPI_SLAVE_READY */
    GPIO_CFG_NO_DIR, /* DIO_22 */
    GPIO_CFG_NO_DIR, /* DIO_23 */
    GPIO_CFG_NO_DIR, /* DIO_24 */
    GPIO_CFG_NO_DIR, /* DIO_25 */
    GPIO_CFG_NO_DIR, /* DIO_26 */
    GPIO_CFG_NO_DIR, /* DIO_27 */
    GPIO_CFG_NO_DIR, /* DIO_28 */
    GPIO_CFG_NO_DIR, /* DIO_29 */
    GPIO_CFG_NO_DIR, /* DIO_30 */
};

Hi Arthur,

Ok, I just found it a bit strange that some drivers do GPIO_config and others don’t. That seems a bit inconsistent.

In our case we cannot use Sysconfig tool with pre-compiled gpioPinConfigs table since we have to config our GPIOs in runtime dynamically. So depending on external circumstances we will initialize GPIOs for different usage after startup.

But my understanding is then that TI drivers will from now on (SDK 5.30) not configure the GPIOs any longer. It is done separately through Sysconfig and GPIO_init, and if one does not (or cannot) use Sysconfig you would have to handle the GPIO configuration from the application. Is that correct?

BR,

Johannes

Hi Johannes,

You are right. As of today, and depending on the driver, you may have to handle the GPIO configuration by yourself in your Application, when not using Sysconfig. This might change in the future, as we are continuously improving the SDK.