• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 78 subscribers
  • Views 2121 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.

MSP430F5438A: :MSP-TS430PZ5X100 with MSP430F5438A rev F/rev H - CPU jumps to an undefined address at run time

AnBer
Mastermind 28880 points
Part Number: MSP430F5438A

Team,

Testing custom code on MSP430F5438A rev F and rev H with using TI MSP-TS430PZ5X100 Rev. 1.3:
At run time the CPU jumps to an undefined address and the execution breaks.
-> This happen with 7 out of 10 of the MSP430F5438A rev F devices
-> 3 out of 10 of the MSP430F5438A rev F and 10 out of 10 of the MSP430F5438A rev H work well/as expected.

The TI MSP-TS430PZ5X100 HW is un-modified.
PMM and DMA are not being used in the SW.
Some investigation are being done on the SW side to narrow down the issue as much as possible. PMM and UCS config will be checked.
Some further information will be provided later on (if MSP430 drivers are used, CCS and compiler version,..etc).

Any comments/advise for narrowing the issue you can provide already?
Thanks in advance,

Anthony

  • 0
    TI__Genius 15370 points

    Hi AnBer,

    Can you try loading a simple blinky program on all revisions and see if the CPU jumps to the wrong location? Is this only happening when the parts are connected to a debugger or does it happen regardless?  

    Finally these symptoms sounds similar to JTAG27. Take a look at this in the MSP430F5438A Device Erratasheet and let me know if this is what you're experiencing and if the workarounds get you back on track.

    Best regards, 
    Caleb Overbay

  • 0 in reply to Caleb Overbay
    TI__Mastermind 28880 points

    Hi Caleb,

    Thanks for the feedback.

    The issue was happening as well without JTAG connected. I got feedback from customer and it seems to be solved now:
    "It seems we needed to make improvements in our firmware regarding the Vcore setting at higher clock frequencies. We have done this and tested the new firmware on “failing” devices. These devices are running without problem now."

    Thanks again.

    A.

  • 0 in reply to AnBer
    TI__Genius 15370 points
    Hi AnBer,

    Insufficient core voltage can certainly cause these types of issues. Thanks for the update!

    Best regards,
    Caleb Overbay

**Attention** This is a public forum