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.

MSP430FR2633: TIDM-CAPTIVATE-64-BUTTON 64-Button Capacitive Touch Panel.

Part Number: MSP430FR2633
Other Parts Discussed in Thread: TIDM-CAPTIVATE-64-BUTTON,

Hello Everyone,

       Here I am new to this msp430FR2633 captivate touch and I get the source code from ti site for TIDM-CAPTIVATE-64-BUTTON 64-Button Capacitive Touch Panel. after ti flash on the code it s not working. So i analyse the problem where the issues are happend. when I  search regard of that issues i found the code not runs after clock initialization so i don't know why this issue on here please guide me anyone.

  • i got this code from ti sites and its not running out of the clock initialization of this function BSP_configureMCU(); so please guide me regarding of this issues

    void main(void)
    {
    //
    // Initialize the MCU
    // BSP_configureMCU() sets up the device IO and clocking
    // The global interrupt enable is set to allow peripherals
    // to wake the MCU.
    //
    WDT_A_hold(WDT_A_BASE);
    BSP_configureMCU();
    __bis_SR_register(GIE);

    //
    // Start the CapTIvate application
    //
    CAPT_appStart();

    //
    // Background Loop
    //
    while(1)
    {
    //
    // Run the captivate application handler.
    //
    CAPT_appHandler();

    #ifndef POWER_TESTING
    //
    // This is a great place to add in any
    // background application code.
    //
    if(g_uiApp.pSensorList[0]->bSensorTouch)
    {
    uint8_t cycle, element, touchCount = 0;

    for(cycle = 0; cycle < g_uiApp.pSensorList[KEYPAD_SENSOR]->ui8NrOfCycles; cycle++)
    {
    for(element = 0; element < g_uiApp.pSensorList[KEYPAD_SENSOR]->pCycle[cycle]->ui8NrOfElements; element++)
    {
    if(g_uiApp.pSensorList[KEYPAD_SENSOR]->pCycle[cycle]->pElements[element]->bTouch)
    {
    touchCount++;
    }
    }
    }

    LED1_ON;
    if(touchCount > 1)
    {
    LED2_ON;
    }
    else
    {
    LED2_OFF;
    }
    }
    else
    {
    LED1_OFF;
    LED2_OFF;
    }

    #endif
    //
    // End of background loop iteration
    // Go to sleep if there is nothing left to do
    //
    CAPT_appSleep();

    } // End background loop
    } // End main()

  • Hi Vivek,

    You can use the CCS or IAR to debug step by step and find out where it real hangs up.

    Best regards,

    Cash Hao

  • ya i followed the step by step that's why i found where the issues it not cross that BSP_configureMCU(); function
    write now i changed WDT_A_hold(WDT_A_BASE); with WDTCTL = WDTPW | WDTHOLD; i got output when i touch and led has been blink but i can't get output in UART now
  • Hello,

    Is there any update about the above question?

    with Regards,
    Vivek
  • Hello Vivek,

    The demo code for the CAPTIVATE-64-BUTTON uses I2C by default. You can change this configuration easily be editing the CAPT_UserConfig.h file.

    Change line #75 from
    #define CAPT_INTERFACE (__CAPT_BULKI2C_INTERFACE__)

    to

    #define CAPT_INTERFACE (__CAPT_UART_INTERFACE__)

    re-compile the code and program the MCU.

    Once the MCU is re-programmed, the demo will stream the sensor status and element data to the CapTIvate design center using the UART.
  • Hello Dennis Lehman,
    I had a changed on that source code to UART Interface (#define CAPT_INTERFACE (__CAPT_UART_INTERFACE__)) however it sends something. But its not related on touch sense data, even without touch the 64 button it sends may garbage value.
  • #define CAPT_INTERFACE (__CAPT_UART_INTERFACE__)
    By this configured it sends something in uart which is not related on touch.(even without touch it sends bulk of data continuously...)
  • Hello,

    Is there any update about the above question?

    with Regards,
    Vivek

**Attention** This is a public forum