• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 189 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.

MSP430F6779: Migration From the Non-A MSP430F67xx Devices to the MSP430F67xxA Devices (with IAR object .r43)

TinK
Intellectual 815 points
Part Number: MSP430F6779


Tool/software:

I am evaluating to Migration From the Non-A MSP430F67xx Devices to the MSP430F67xxA Devices

From TI application note (SLAA666A) said below.

"Migration From the Non-A MSP430F67xx Devices to the MSP430F67xxA Devices
To migrate from a non-A MSP430F67xx device to its corresponding MSP430F67xxA device, minimal
changes are necessary. A MSP430F67xx device and its corresponding MSP430F67xxA device are pin-topin
compatible, so a non-A chip can physically be replaced with an A version. Additionally, the software on
a MSP430F67xx device should also run on a MSP430F67xxA device as long as the software is updated
to correspond to the proper header files and device name in the IDE project settings."

I have another question about using our .r43 library for metrology and communication protocol (IAR MSP430 compiler).

Is it necessary to recompile for the .r43 library (since the MCU memory address and structure seem to not need to be recompiled)?

Thank you,

  • 0
    TI__Mastermind 26280 points

    Hi TinK,

    If you have the source code I would recommend replacing the files to use the MSP430F67xxA header file, there is an addition of the RTCLOCK feature between the devices which will impact registers. The bit is in a reserved location for other devices and will read as a 0. Aside from this register change, other changes should not impact a memory organization, but if you can recompile I do still recommend that approach to prevent any missed differences.

  • 0 in reply to Luke Ledbetter
    Intellectual 815 points

    Hi Luck, Thank you, 

    Regarding the related header files, I found the following files:

    io430f6779.h
    io430f6779a.h

    msp430f6779.h
    msp430f6779a.h

    Is there another one?

  • 0 in reply to TinK
    TI__Mastermind 26280 points

    Hi TinK,

    There is also the linker file that needs to be changed, although the memory makeup should be the same, it is better to use the appropriate one to prevent missing any small detail. If you change the target device in IAR it should populate the correct file.

**Attention** This is a public forum