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: MSP430FR2522
I am trying to get comfortable with the Captivate Keypad , Captivate PGMR and the Captivate design center (CDC). While the documentation is great I am running into troubles with the advertised I2C communication capabilities of the captivate programmer. If I am opening the captivate keypad example, leave everything unchanged and use UART as default communication, generate the source out of captivate design center and upload it to the keypad everything is working as expected. If I am just changing the communication channel from UART to BULK_I2C, create the source and upload it again I can connect to the HID but am not getting any data within the captivate design center nor on the device. Am I am missing something here?
According to the documentation the HID (programmer) should automatically switch to I2C when selected as preferred communication in the CDC. I have the same behavior also on a custom sensor board with the same MCU as on the Keypad as well as on a Windows and Mac computer.
I hope someone can give me a hint or explain to me why the generated source with selected I2C is not working ootb as stated in the documentation. Thank you for your help!
I assume you are using the Touch Keypad BoosterPack.
In the specific Design the I2C signal (SDA, SCL, IRQA) are connected to booster pack connectors only and not on the programmer head. That is the reason for not being able to communicate in BULK-I2C mode with the CDC.
I understand that you have also an issue with you own HW. Would you like to share some details to better understand the issue also on your design?
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 Kostas Aslanidis:
thank you very much for the fast answer. Yes, indeed I am using the Touch Keypad BoosterPack with the Cativate-PGMR attached to it. I now do understand why CDC won´t show any data. Obvious enough if the I2C signal is not routed to the MSP. I understood the block diagram wrong as there the I2C connection to the msp430fr2522 is visible but you are right - not to the programmer.
Anyway, as the keypad is not responding to touch at all (when I have uploaded the demo code just changed to BULK_I2C) is this also related to the fact that the slave is waiting for host communication that will never happen? I was expecting the Keypad is also working independently when it comes to touch recognition / LED control?
About my custom HW:
I just figured out a glitch in the design. Used the wrong PIN for I2C clock (11 instead of 9). This can not work at all. Will fix this first and believe this should solve things.
Thank you again for a short answer.
All the best,
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.