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.

MSP430FR2675: Unable to connect Captivate Design Center to Target

Part Number: MSP430FR2675
Other Parts Discussed in Thread: CAPTIVATE-PGMR, BOOSTXL-CAPKEYPAD, CAPTIVATE-FR2676

Captivate Design Center doesn't seem to be interacting with my target (proprietary hardware).  There are no errors displayed, and I don't see any traffic on the P1.4/P1.5 UART lines when I select the option to connect.  I am able to load code and debug without any problems from Simplicity Studio using exactly the same hardware configuration.  Regarding the HID bridge, I have pin 7 of the CAPTIVATE-PGMR connected to MCU P1.5 and pin 8 of the PGMR to MCU P1.4.  My development environment is macOS Catalina 64-bit.  I also have a Parallels (VM) Windows 10 environment where I'm experiencing similar problems.  My preference would be to get this working in the native macOS environment.  Log files are attached.

Log Files.zip

Additionally, Captivate Design Center seems to be locked into opening only the project that I started.  I am unable to open any other projects, including the example projects that are included with its installation.  This is with the latest Java runtime environment.  It would be nice to get this resolved as well.  It looks like CDC hasn't been updated in over a year.  Any plans to release an update?

  • Hello,

    Thanks for your detailed post. For this device, there seems to be two options to connect to the UCA0 TX and RX pins. Have you tried connecting the CAPTIVATE-PGMR to pins P5.1 and P5.2?

  • As stated, it's custom hardware, so I can't really move the trace.  What about the part where I can't open any project but the first one that is opened, after installing Captivate Design Center?  Even deleting the program directory and reinstalling does not resolve that issue.

  • Using only the CAPTIVATE-PGMR and BOOSTXL-CAPKEYPAD boards, I have been able to verify that the pins I am using on the programmer 20-pin JTAG are correct for communicating with the target board.  This is was done using the BOOSTXL-CAPKEYPAD demo project and a different computer (Windows 10).  Unfortunately, I have no other computers to experiment with different projects in Captivate Design Center.  The only difference is I used six (6) jumper wires to connect the two boards to confirm that my pin selections are correct.

    • Pin 7 - HID Bridge UART TXD >> MCU RXD
    • Pin 8 - HID Bridge UART RXD >> MCU TXD
    • Pin 9 - SBWTDIO_RST
    • Pin 10 - SBWTCK_TST
    • Pin 18 - 3.3V (tool supply)
    • Pin 19 - GND

    I think that the issue of only being able to load a single project occurs after the first proprietary project is loaded/saved.  After that any attempt to load any other project fails.  Being able to load only a single project is a serious design flaw and warrants an update to the tool!  

  • We are using MSP430FR2675TRHB, which is a 32-pin package.  It does not have P5.x.  According to the BOOSTXL-CAPTIVATE schematic, the CapTIvate JTAG UART lines are connected to UCA0TXD and UCA0RXD.  Those module pins on the MSP430FR2675TRHB are P1.4 and P1.5.

  • I'll need to loop in our software team about the single project issue.

    We are using MSP430FR2675TRHB, which is a 32-pin package.

    The code for this device may not know which package you're using, so the code may need to be updated to select/configure the appropriate pins for UCA0.

  • the code may need to be updated to select/configure the appropriate pins for UCA0.

    Thank you for looking into this.  I look forward to reviewing the details of how to get this working.  What TI code needs to be updated?  Where can I find it?

  •  

    I downloaded the schematic (SLAR157) for the CAPTIVATE-FR2676.  (For some reason the schematic calls out the FR2633.  However, since they appear to be in the same family, they seem to be pin-compatible.)  In fact, the part called out in the schematic is the same 32-pin RHB (VQFN) package that we are using in our design.  Additionally, the schematic has MSP_TXD and MSP_RXD connected to P1.4 and P1.5, respectively, which are the same connections we are using in our design.  I really don't think that P5.x has anything to do with it.

  • Thank you for the updates. I've pinged our software team again, and they should be replying soon. Thanks for your patience!

  • Upon further investigation I was able to get our custom board to communicate with Captivate Design Center by enabling a couple compile-time switches that were previously unknown to me.
    Thank you so much for your assistance.  The only outstanding issue at this time is the ability for CDC to open additional projects.
  • Hello pcpro178,

    For the sake of others looking to solve this same problem can you tell us what compile-time switches you enabled to get this to work for you?

    Regarding opening other CDC projects, yes, by default it will automatically open the last project you had open.  To open other projects can be a little challenging at first. 

    Start with the menu selection File>Open Project.  If you created a project in the default workspace, then you might see something like this below.  You can see my current project is "My Custom Project".  Now, if the project you are looking for is in this workspace, you should see its name.  Click once (do not click twice) on the name of the other project you want to open, the click OPEN button.

    STEP 1

    Now, if the project you are looking to open is in a different workspace, then there are a couple more steps.

    STEP 2

    Again, File>Open Project, but this time notice the CHANGE button in the dialog box.  The key is to click on the CHANGE button.

    You should see something like this below (note the title of the dialog box is Change workspace folder).  The CHANGE buttons takes you to the directory where your default workspace is located, under your window's <username>.   There you may have other workspaces and files.  You can see from my snapshots that my current workspace is CDC_1_83_00_03 located under my username <a0272918>

    STEP 3

    Now, to select a different workspace under the same <username> directory, click once on the name of the other workspace you want to open, then hit the SELECT button.  In my example my project is located in my other workspace  CDC_1_83_00_13.  I click once on the name, then hit the SELECT button.

    At this point the next dialog box shows the list of projects in this workspace.

    STEP 4

    You should see your project.  To open this project, click once on the project's name, then click the OPEN button on the bottom of the dialog box.

    Now, if by chance the project you are looking for is in a completely different workspace that is not located under your window's <username> directory, then you will need to first navigate up and out of your <usersname> directory, then repeat step #4.

    STEP 5

    You do that by File>Open Project, then click on the OPEN button (as described earlier), then select the icon that looks like a folder with an UP arrow.

    You can see here in my next snap shot, I'm no longer under my <username> directory.  You can navigate to any where on your local or network drive at this point.

    From here, select the windows directory where your other workspace  is located, then follow steps 3 and 4.

    Let me know if this does not solve your issue with opening other projects.

  • Thank you.  It seems that the problem with opening additional projects was due to the wrong "workspace" folder being selected.  Selection of the appropriate workspace directory is not intuitive at all.  This really should be addressed in the next update of Captivate Design Center.

  • Our custom project was originally based on the BOOSTXL-CAPKEYPAD demo code, so we have some conditionally compiled code in board.c that enables the UART lines on P1.4 and P1.5.  There is also a #define for CAPT_INTERFACE in CAPT_UserConfig.h that needed to be set to `__CAPT_UART_INTERFACE__`.

  • Yes, the navigation can be challenging at first.  You are not the first to comment on this.

    Thank you for responding with the required changes you needed to perform to get your project working.

**Attention** This is a public forum