• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 78 subscribers
  • Views 267 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.

MSP430F5247: Swapping MCUs of the same family, but different Flash sizes

Mark Pearson
Genius 12705 points
Part Number: MSP430F5247
Other Parts Discussed in Thread: MSP430F5249

A question from one of my customers:

"If we build our application for the 64k part, MSP430F5247, can we push that into the 128k (with the MSP430F5249)? It looks like we may need to change the programming command to use the alternate PN but it should otherwise conceptually work. We would just be ‘wasting’ the extra flash on those parts, which is fine as we don’t need it and wouldn’t have it long term on the rest of our boards."

 

Parts in question: 64k Flash MSP430F5247  and the 128k Flash MSP430F5249

Any 'Gotchas' in swapping the larger Flash device into the smaller Flash design?

 

Thanks!

  • 0
    TI__Guru 56685 points
    Hello Mark,

    Since these two parts are memory spins of one another, there should be no issue here. In fact in CCS, you could force the IDE to program as if using a MSP430F5247 when attached to a MSP430F5249 in the target board. You will get a warning as it's not the same device, but you will still be able to program and download to the MSP430. This way you could develop with the higher memory part, but restrict the memory to the lower capacity version to make sure you don't go over its limits.

**Attention** This is a public forum