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.

  • TI Thinks Resolved

CCS/MSP430FR2522: BOOSTXL-CAPKEYPAD to a CAPTIVATE-PGMR flashing generated code

Genius 3230 points

Replies: 7

Views: 884

Part Number: MSP430FR2522

Tool/software: Code Composer Studio

HI TI Team.  

Using this BOOSTXL-CAPKEYPAD to a CAPTIVATE-PGMR module connected via usb to evaluate capacitive touch of MSP430.

From Design Center I used CapTIvateDesignCenterWorkspace\BOOSTXL-CAPKEYPAD sample to generate CCS code,.

I can compile but I cannot flash to BOOSTXL-CAPKEYPAD. I got this screens. Is there any configuration needed?

 code, I can import and build  code in CCS.

  

  • Hi Walter,
    no problem. The resolution is very simple. We're regularly updating the IDE including the DLLs etc. This sometimes requires a firmware update on the debug HW of our tools. This is the case here. The firmware of your debugger does not match the IDE version.
    Please just click on update button and wait until it's completed. Then the code download should start automatically.

    Best regards
    Peter

  • In reply to Peter Spevak:

    Hi T Team, 

    Thank you.

    Rergards,

    Walter

  • In reply to Walter Macamos:

     Hi TI Team,

    Follow up for generating code. The  orig demo is different from my generated code from Design Center. 

    The demo has board.c, board.h or system.h files while generated from Design Center do not have. 

    Is this normal?

    Regards,

    Walter

  • In reply to Walter Macamos:

    Hi TI Team,

    I connected the J6/J7 to COM port not HID as described in

    software-dl.ti.com/.../ch_evm_boostxl_capkeypad.html

    What is the baud rate to use t o observe the uart data?

    Regards,
  • In reply to Walter Macamos:

    Hello Walter,
    I understand, that from your perspective this belongs to your activities of the same project, but from the forum perspective it is better to have separate threads with respective headlines. This makes the search for other users, with potentially same problems, easier. So please open in future a new thread, if the original problem of the thread is solved, and mark the original one as resolved. Many thanks in advance.

    For now, let's for sake of time look into your current issues. The board.c/.h files, yes this is fine. This just related to how the example project has been structured, storing the HW related functions in separate source files, making adaptation to other HW easier.

    In terms of the UART documentation, with the CapTIvate Design Center installation, there comes also the documentation for the technology and all related topics, including the detailed description on the Target-CDC communication. You can find this in the Installation folder of CDC >> CapTIvateDesignCenter >> docs >> users_guide >> html then clicking on the "index.html" will start your browser displaying the content. In the chapter of the FR2633 EVM description, you can find all the details.

    Best regards
    Peter

  • In reply to Peter Spevak:

    Hi Peter,

    Thank  you.

    Best Regards,

    Walter

  • In reply to Walter Macamos:

    Hi Walter,
    under the assumption of no further need for support for this, I am closing this thread. If it is not the case, you can reopen it or open a new one, if there should be new questions on your side.

    Best regards
    Peter

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.