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.
Part Number: MSP430FR2632
My team is creating a board with multiple capacitive sense inputs, and plan on using the MSP430FR2632 with CapTIvate inputs.
We want to use the CapTIvate Design Center to both generate firmware for the product as well as to display real-time capture counts and all of the other graphical things you can do at run-time to fine tune the cap sense settings for our application, while the firmware is running on our custom hardware.
The TI documentation and online tutorials for using CapTIvate Design Center seem to be based on a TI evaluation board hooked up to the development PC, but we want to be able to do all of this on our own hardware.
What documentation exists that shows the entire path from our custom board all the way to the PC running Design Center? How do we design our hardware to accommodate a connection from the MSP430FR CPU on our board, through whatever adapter is necessary, to a USB port on the development PC?
What pins on the MCU do we have to reserve for communicating with with the debugger as well as relaying run-time data to Design Center?
Thanks for you post.
You need CAPTIVATE-PGMR tool to download code and on-line tuning.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Ling Zhu2:
In reply to Bob Lawson:
We just received our first boards and can't get the CCS debugger to attach to the target. I'm using CCS v8.0.0.00016.
The pins we used between the CAPTIVATE-PGMR and the target are the ones you proposed: VCC GND TXD RXD SBWTCK SBWTDIO
The CAPTIVATE-PGMR is recognized correctly and all device drivers installed automatically.
Is there anything we have to do in the debug configuration in CCS to tell the debugger to use SBW instead of JTAG signals?
Is there any technical documentation about what we should see on the SBWTCK and SBWTDIO wires with a scope during a successful connection to the debugger?
There are 2 items you can check:
1. make sure there are decouple capacitors on VCC pin
2. make sure the capacitor on RESET pin is no larger than 1000pF
Here is a reference schematic.
Thank you. I believe our design complies with the requirements you stated.
Can you provide a scope capture showing what we should see on these signals when attempting to attach to the board with a CCS debugger?
We found today that completely removing capacitor C1 shown in your schematic allows us to connect with the debugger and CapTIvate Design Studio is working with the board.
Thank you for all of your help on this matter.
I originally used a 2200pF Cap and it didn't work. Based off this I lowered it to 100pF and it still did not work. I removed the C1 cap completely and now it works. What is the risks of removing that capacitor from the design?
In reply to Nick Kloxin:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.