• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 319 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

Design resource of CC430F6147

CC430F6147: Libraries for system development

Anveshka Maurya
Prodigy 20 points
Part Number: CC430F6147
Other Parts Discussed in Thread: MSP430FR4133

I am trying to interface a peripheral using SPI  protocol and I am not able to find design resources for the board.Are there any generic libraries available for cc430f6147? How to know which msp430 device is supported by a given cc430 device?

  • 0
    TI__Genius 17960 points

    Hello Anveshka,

    you can find code examples for every MSP430 in the TI-Resource Explorer of the Code Composer Studio, please see the screen shot.

    In addition, for each and every MSP430 also code examples and other code related sources can be found on the device specific landing page under "tools & software"

    I am not sure how to understand your question on

    "How to know which msp430 device is supported by a given cc430 device?".

    Could your please explain what you mean?

    Best regards

    Peter

  • 0 in reply to Peter Spevak
    Prodigy 20 points
    Previously, I have interfaced the peripheral with msp430fr4133. I want to port the system now to a cc430f6147. The code example for the same makes use of interrupt for receiving the data, while my design doesn't. As there are header and c files for eusci already available for msp430, I am not able to get the same files for cc430 family.
  • 0 in reply to Anveshka Maurya
    TI__Genius 17960 points
    Hi Anveshka,
    you're correct. There are differences in the peripherals between some families. Thus you need to adapt your code accordingly, in case you want migrate between such families or derivatives having different peripherals integrated. We're sorry for this inconvenience, resulting from evolution of the MSP430 family over time.

    Best regards
    Peter