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.

CCS/MSP430FR2522: BOOSTXL-CAPKEYPAD

Part Number: MSP430FR2522
Other Parts Discussed in Thread: BOOSTXL-CAPKEYPAD, EVM430-CAPMINI

Tool/software: Code Composer Studio

Hi TI Team,

We are using BOOSTXL-CAPKEYPAD to evaluate CapacitiveTouch Technology of MSP430FR25221RHL. It working OK for us in CCS.

If we want to use the MSP430FR25221PW16 as final target, do we need to change anything in CCS compilation set-up? Please confirm.

Regards,

Walter 

  • Hi Walter,

    There is one difference in the two devices that needs to be considered.
    The demo code for the BOOSTXL-CAPKEYPAD is written for the IRHL package/pin out and remaps the primary I2C to the secondary port because the primary I2C pins are shared with CapTIvate IO pins.

    On the PW16 package the secondary I2C port pins are absent (fewer pins on the device).
    So this means if you need I2C communications for your application, P1.2, P1.3 are the only available pins and that would leave CapTIvate IO pins CAP1.2, CAP1.3 not available for capacitive touch.

    For the UART, the primary port pins are also shared with CapTIvate IO so you will need to remap to the secondary port, just like in the example code, if you want use of all the CapTIvate IO pins.

    If you tell me a little more about your application I can make some additional suggestions.
  • Hello Walter,

    regarding CCS setup.
    You will need to create a new empty project with a main.c, with a desired MCU type and probably your project uses driverlibs so with a support for a driverlibs.
    Than you need to add your existing project source files to a new project.
    I hope you have already checked that the MCU resources you need are achievable on a destination MCU.
  • Hi Dennis,

    Our hardware design based on EVM430-CAPMINI.

    Actually, our final device will be MSP430FR25121PW16 but we the development board EVM430-CAPMINI (based on MSP430FR25121RHL) not available because out of stock. We only have the BOOSTXL-CAPKEYPAD(based on MSP430FR25221RHL) development board. So we want to use only the BOOSTXL-CAPKEYPAD as starting point.

    Using the Design Center, I loaded BOOSTXL-CAPKEYPAD then change chip from MSP430FR25221RHL to MSP430FR25221PW16. Then I reconnect all sensors and proximity sensors just like the original configuration . After that, I generated the CCS code for MSP430FR25221PW16 . I noticed, that the generated code is not different when not changing chip or anything just generate CCS code.

    With this idea, we use the Design Center to load EVM430-CAPMINI to then change chip from MSP430FR25121RHL to MSP430FR25121PW16. Then reconnect all sensors and proximity sensors just like the original configuration . After that, I generate the CCS code for MSP430FR25121PW16. . I noticed, that the generated code is not different when not changing chip or anything just generate CCS code.

    Based on your documentation of porting need to start from scratch.

    Regards,
    Walter
  • Hi Dennis,

    We will use only 3 capacitive touch in our final design of MSP430FR25121PW16.
    We will not use the I2C or UART for our final application so we plan to disable communication interface to NONE.

    We will use 3 GPIOS to be configured as output to indicate touched button.

    Regards,
    Walter
  • Hi Dennis,

    Any response?

    Regards,

    Walter

  • Hi Walter,

    Since the FR2512 has only 4 CapTIvate IO pins on packages, (PW16 or iRHL), the code that is generated should be the same, so your scheme will work.

    Dennis
  • Hi Dennis,

    OK, thank you.

    Regards,
    Walter

**Attention** This is a public forum