• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 196 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TIDM-1021: Support Software Package Seems Incomplete

Austin Tallentire
Prodigy 10 points
Part Number: TIDM-1021
Other Parts Discussed in Thread: MSP430FR2633, , CAPTIVATE-BSWP, MSP430F5528

Hello,

I am looking to test out the performance of the TIDM-1021 evaluation board. To this end I built a PCBA based off the hardware design files and ordered in the CAPTIVATE PGMR. I downloaded the TIDCET6 software package and generated the IAR code through CapTIvateDesignCentre, but when I programmed the MSP430FR2633 none of the LEDs would light up.

While running the project with CapTIvateDesignCentre allows me to see which button is pressed, it appears that the actual code running on the MSP430FR2633 is more closely related to the CAPTIVATE-BSWP Firmware. This can be seen through the main.c and CAPT_BSP.c files, as the TIDM-1021 does not set up the right I/O for its peripherals but instead sets up for those of the BSWP.

Has anyone found the right files to use with the TIDM-1021 evaluation board?

Thanks

  • +1
    TI__Guru 61921 points

    Hi Austin,

    The configuration for the sensor is in CAPT_UserConfig.c file, not the CAPT_BSP.c.  Looking in the CAPT_UserConfig.c I see the sensor structs are setup with correct button assignments for RX and TX when compared to the schematic.  Likewise, line #66 in main registers only one sensor callback function.  Application.c contains the code to turn on/off the LEDs when a button is touched.

    You say you do see the measurements change in the Design center when you touch the buttons, correct?  What are you using for the target conversion count and how much delta do you see?  In the design center, sensor channel table view, do you see the LEDs turn/off when touching the buttons?

    Have you tried setting a breakpoint somewhere in the callback function and see that the code eventually gets there?  If the code never breaks there, then something went wrong in the calibration process.  Also, can you manually turn on one or more of the LEDs in your code just to make sure they were installed correctly?

  • 0 in reply to Dennis Lehman
    Prodigy 10 points

    Hi Dennis,

    I see where my problem is now. I could not get the CCS project to actually impact the MSP430FR2633 on the keypad as it for some reason can only see the MSP430F5528. To get around this I had read that you need to use the IAR project generated through the Design center, and through IAR you can directly program the FR2633. This is the project I was using, which is not the same one you are describing. It has the same general structure, but seems more generic. With that project I could flash LEDs on the keypad (after adjusting the pin assignment) whenever an event caused he keypad to wake up.

    I will go back to the CCS project and try to get that to program the FR2633. Thank you for your quick response.

    Cheers.

  • 0 in reply to Austin Tallentire
    TI__Guru 61921 points

    Glad to hear you got past this hurdle.  I'll go ahead and mark this issue resolved.

**Attention** This is a public forum