Problems when using Interrupts to configure a Button on TiRTOS

Hi Leandro,

It seems like you may be passing in the incorrect parameters to the gpioPinConfigs array. If you look at the GPIO interrupt example you can see that the entries OR'ed together include defines from the GPIOTiva.h and GPIO.h header files. You must use these, so I suggest starting with the GPIO interrupt example's Board.c file and using those structures to base your code off of.

It looks like the EK_TM4C1294XL.h file is correct, but again the gpioPinConfigs array should have a single entry per pin.

Eg:

    /* EK_TM4C129EXL_USR_SW2 */
    GPIOTiva_PJ_1 | GPIO_CFG_IN_PU | GPIO_CFG_IN_INT_RISING,

And use a similar approach for all of your button inputs.

Best,

Alexander

Hi Alex,

  Tks for your answer. I started from gpiointerrupt program and, as a small test, I changed the program adding more one "button" and configuring the interrupt. I choosed the pin PM_3 and with a Jumper, I can connect the 3.3V in the Pin, acting as a button.

Well, I had no success.

The changes I did, below:

gpiointerrupt.c

void gpioButtonFxnM(void)
{
    /* Clear the GPIO interrupt and toggle an LED */
	if (GPIOPinRead(GPIO_PORTN_BASE, GPIO_PIN_1) != 0)
		GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_1, 0);
	else
		GPIOPinWrite(GPIO_PORTN_BASE, GPIO_PIN_1, GPIO_PIN_1);

    //GPIO_toggle(Board_LED1);
    GPIO_clearInt(Board_BUTTON2);

    if (count++ == 100) {
        count = 0;
    }
}


int main(void) {
...
GPIO_setupCallbacks(&Board_gpioCallbacks2);
GPIO_enableInt(Board_BUTTON2, GPIO_INT_RISING);
...
}

Board.h

#define Board_BUTTON2               EK_TM4C1294XL_USR_SW3
#define Board_gpioCallbacks2        EK_TM4C1294XL_gpioPortMCallbacks

EK_TM4C1294XL.h

typedef enum EK_TM4C1294XL_GPIOName {
    EK_TM4C1294XL_USR_SW1=0,
    EK_TM4C1294XL_USR_SW2,
	EK_TM4C1294XL_USR_SW3,

    EK_TM4C1294XL_GPIOCOUNT
} EK_TM4C1294XL_GPIOName;

EK_TM4C1294XL.c

#include <ti/drivers/GPIO.h>

/* Callback functions for the GPIO interrupt example. */
void gpioButtonFxn0(void);
void gpioButtonFxn1(void);
void gpioButtonFxnM(void);

/* GPIO configuration structure */
const GPIO_HWAttrs gpioHWAttrs[EK_TM4C1294XL_GPIOCOUNT] = {
    {GPIO_PORTJ_BASE, GPIO_PIN_0, GPIO_INPUT},  /* EK_TM4C1294XL_USR_SW1 */
    {GPIO_PORTJ_BASE, GPIO_PIN_1, GPIO_INPUT},   /* EK_TM4C1294XL_USR_SW2 */
    {GPIO_PORTM_BASE, GPIO_PIN_3, GPIO_INPUT}   /* EK_TM4C1294XL_USR_SW3 */
};

/* Memory for the GPIO module to construct a Hwi */
Hwi_Struct callbackPortJHwi, callbackPortMHwi;

const GPIO_Callbacks EK_TM4C1294XL_gpioPortJCallbacks = {
    GPIO_PORTJ_BASE, INT_GPIOJ, &callbackPortJHwi,
    {gpioButtonFxn0, gpioButtonFxn1, NULL, NULL, NULL, NULL, NULL, NULL}
};
const GPIO_Callbacks EK_TM4C1294XL_gpioPortMCallbacks = {
    GPIO_PORTM_BASE, INT_GPIOM, &callbackPortMHwi,
    {gpioButtonFxnM, NULL, NULL, NULL, NULL, NULL, NULL, NULL}
};

const GPIO_Config GPIO_config[] = {
    {&gpioHWAttrs[0]},
    {&gpioHWAttrs[1]},
    {&gpioHWAttrs[2]},
    {NULL},
};

/*
 *  ======== EK_TM4C1294XL_initGPIO ========
 */
void EK_TM4C1294XL_initGPIO(void)
{
    /* Setup the LED GPIO pins used */
    GPIOPinTypeGPIOOutput(GPIO_PORTN_BASE, GPIO_PIN_0 | GPIO_PIN_1);

    /* Setup the button GPIO pins used */
    GPIOPinTypeGPIOInput(GPIO_PORTJ_BASE, GPIO_PIN_0 | GPIO_PIN_1);
    GPIOPadConfigSet(GPIO_PORTJ_BASE, GPIO_PIN_0 | GPIO_PIN_1, GPIO_STRENGTH_2MA,
                     GPIO_PIN_TYPE_STD_WPU);
    GPIOPinTypeGPIOInput(GPIO_PORTM_BASE, GPIO_PIN_3);
    GPIOPadConfigSet(GPIO_PORTM_BASE, GPIO_PIN_3, GPIO_STRENGTH_2MA,
                     GPIO_PIN_TYPE_STD_WPU);


    /* Once GPIO_init is called, GPIO_config cannot be changed */
    GPIO_init();
}

The both functions gpioButtonFxn0 and gpioButtonFxn1 continue to work but the new one, gpioButtonFxnM, unhapply, is not called when I put 3.3 V and remove the contact 1 second later, for example. 

How can I solve this? Any clue?

Best Regards

Leandro

Hi Alex,

I was checking last night the new version 2.16 and the way that GPIO is handled is very different. All code wrote with 2.10 must be changed to fit new version.
I worry about that because, besides GPIO access, I have a Display (using GPIO), Sockets, UART communication, FLASH, SD, PWM, Semaphores and multitask, I mean, a lot of code depending of RTOS. I am afraid I have no time to change it. For sure I will update to a new version but it is a kind of work that must be done carefully and, of course, I will do in a way I can isolate the specific code from the generic code (in fact, I should have done it, but, you know...)

In a nutshell, I need to launch the product with version 2.10 and, after stable and running, plan the RTOS migration to 2.16 version.
I will still investigate why it is not working the new Pins I added.

Any advance I will let you know

Thanks and Best regards
L.