• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 532 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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:

MSP430F5324: Crossing between MSP430F5324/6/8

MSP430F5324: Migration from MSP430F5324 to MSP430F5326 and MSP430F5328

Kuerbis
Expert 4145 points
Part Number: MSP430F5324
Other Parts Discussed in Thread: MSP430F5326, MSP430F5328

Hi Team,

My understand is that the difference between MSP430F5324, MSP430F5326 and MSP430F5328 is only FLASH and SRAM memory size based on the Table 6-1. Device Comparison in the datasheet and E2E thread as below.   Is my understand correct?

https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/740276/msp430f5324-crossing-between-msp430f5324-6-8/2733063

The customer want to re-use software on MSP430F5326 and MSP430F5328.

Can the program files created for the MSP430F5324 be used directly on the MSP430F5326 and MSP430F5328? The load file is .d43 or .txt in TI format.

Is there anything the customer need to be aware of during a software migration?

Is there anything else they have to take care for a migration?

 

Thanks and Best regards,

Kuerbis

 

 

  • 0
    TI__Guru 56685 points

    Hello Kuerbis,

    Your understanding is correct. Code compiled for MSP430F5324 will work as is on MSP430F5326 or MSP430F5328. If you are loading that code via CCS, you may get a pop up warning stating the code was compiled for MSP430F5324, but target is MSP430F5326/8. you can "ignore" that warning and CCs will program the part. 

  • 0
    Guru 92251 points
    Kuerbis said:
    Is there anything the customer need to be aware of during a software migration?

    If the software sets the SYSRIVECT bit in SYSCTL to use the RAM as an alternate location for the interrupt vector locations, then since the vectors are remapped to the top of RAM changing to a device with a different size of RAM will move the address of the vectors in RAM. I think that will require the software to be changed to allow for the different address of the interrupt vectors in RAM.

**Attention** This is a public forum