• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 483 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR2632: CapTIvate Software Support

Go Bravos
Expert 6090 points

Part Number: MSP430FR2632

Hi team,

I am looking for some software support for Captivate and MSP430FR2632. I seem to be missing a bunch of needed functions that I needed to provide stubs for – it this expected?

I ran Captivate for the MSP430FR2632 and created a code base with the sensors that I desired.  I am using IAR and I am unable to link due to the follow missing functions.  I assume that I missed a step, is there someone that has compiled for the 2632 that might be able to point in the right direction?

void CAPT_init(void)

void CAPT_initSensor(tSensor *pSensor)

void CAPT_calibrateSensor(tSensor *pSensor)

 and

bool CAPT_testForMaxCountRecalibration(tSensor *pSensor)

bool CAPT_testForNegativeTouchRecalibration(tSensor *pSensor)

bool CAPT_testForRecalibration(tSensor *pSensor)

void CAPT_updateSensor(tSensor *pSensor,  uint8_t ui8LPM)

uint16_t CAPT_getInterruptVector(void)

 Thank you.

  • 0
    TI__Guru 56685 points

    Hello,

    Please make sure you utilize the CapTIvate Design Center  for generating your CapTIvate project. You can setup exactly what you need from a sensor perspective, including tuning/calibration, and it will generate the code for you. 

  • 0 in reply to Jace H
    TI__Expert 6090 points

    Hi Jace,

    Thank you for your reply. Here is follow up from my customer:

    The question that we submitted stated that we used CapTIvate to create a code package.

     

    CAPT_Init for example:

     

    int main() calls CAPT_appStart()

    CAPT_appStart() calls MAP_CAPT_initUI()

    MAP_CAPT_initUI() maps to CAPT_initUI because ROM_CAPT_initUI is not defined

    CAPT_initUI() calls CAPT_Init()

     

    But I cannot find CAPT_Init() in the code base created by CapTIvate.

     

    Maybe, if we can figure this one function out the issue will be systemic, and the rest will be obvious.

    Thank you.

  • 0 in reply to Go Bravos
    TI__Guru 56685 points

    Please provide the output project from the CapTIvate Design Center.

  • 0 in reply to Jace H
    TI__Guru 56685 points

    Thanks for providing the project offline. Everything seemed to be in order. Can you try building one of the example projects that comes with the CapTIvate Design Center?

    Also as an anecdote, that you may not find all functions associated with CapTIvate within the code generated from the design center, as a lot of the CapTIvate code needed is already placed into ROM on the device. So there would be function calls, but you wouldn't necessarily be able to see the code that is in ROM in your IDE. 

  • 0 in reply to Jace H
    TI__Expert 6090 points

    Hi Jace,

    My customer was able to compile the code using that project file. They believe the difference is that they are compiling for C++. Is there a way to do this? When they compile the project out of captivate for C++ it fails for the same way.

    Thank you.

  • +1 in reply to Go Bravos
    TI__Guru 56685 points

    Hello,

    Thanks for the additional information, after speaking with a colleague we think we know what the issue is now. The output of the CapTIvate Design Center was not configured with C++ compatibility in mind. That is why you are getting this compile error. If the customer wants to continue down the path of compiling via C++, then there is an option. They would just need to add the following code to every header file in their project. 

    Code to be inserted at beginning of header file:

    //*****************************
//
// If building with a C++ compiler, maje all definitions in this header
// have a C binding.
//
//*****************************
#ifdef __cplusplus
extern "C"
{
#endif

    Code to be inserted at the end of the header file:

     

    //***************************
//
// Mark the end of the C bindings section for C++ compilers.
//
//***************************
#ifdef __cplusplus
}
#endif

**Attention** This is a public forum