• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 835 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.

EXP430FR5739 Unable to Flash

Salvatorre
Expert 1460 points
Other Parts Discussed in Thread: MSP430FR5739

I am using the EXP430FR5739. I have been flashing and running code on it for about 6 months now. All of a sudden, with no tinkering to hardware, I had an error when flashing software. I don't remember it exactly, but I think it said something to the effect of that the program .out file was corrupt. Now, I can't flash it again. The error message I get is: Error connecting to the target:
Could not find device (or device not supported)


Is there anyway to get it working again?

I would assume no if I were programming right to the FRAM chip via JTAG, but since it looks like the program is going through another MSP430 and getting flashed onto the FRAM chip from the other MSP430, I thought there might be something that could be done to save this board.

Thanks for your help.

  • 0
    Guru 58965 points

    Actually there is not even a single bit of Flash in that chip. Thus you have been writing to the FRAM and running code on it for the past 6 months. But now for some reason you cannot do that again.

    There is a long list of possible reasons. One of them is, you accidentally wrote one of the magic numbers in certain magic location of the FRAM and that causes the chip to disable the JTAG interface of the chip. They call these "Signatures" at 0xFF80 and above.

  • 0 in reply to old_cow_yellow
    Expert 1460 points

    Of all the possible issues that you know of, old_cow_yellow, are there any ways to regain the ability to program to the MSP? Thanks.

  • 0 in reply to Salvatorre
    Guru 58965 points

    If it is caused by the Signatures in the FRAM that disabled JTAG access but BSL is still enabled, then you could use BSL to clear all the FRAM (including the Signatures). If you do not have the interface to run BSL, SLAA535A suggests a cheap way to make one (using a G2 LaunchPad).

    If it is cause by wrong dlls in your PC to run the debugger, then you could try reinstall the IDE and make sure the correct dlls are used. Tons of people had this problem. (Not only with this FRAM chip, but using JTAG in any target.)

    If it is cause by defective USB cable or connector, then you could replace them.

    To use PC to run debugger via the JTAG on the chip goes through a long chain of software and hardware links (elements). If any link of this long chain is broken, the chain becomes unusable,

  • 0 in reply to old_cow_yellow
    Expert 1460 points

    Thanks old_yellow_cow. I bought the G2 tonight and went through SLAA535A. Looks like it has worked for the 5739 since it is listed at the bottom of SLAA535A. I had to put this project on hold until now.

  • 0 in reply to Salvatorre
    Guru 33653 points

    Here is example of unblowing JTAG fuse on MSP430FR5739 by BSL...

    http://forum.43oh.com/topic/2972-sbw-msp430f550x-based-programmer/?p=43889

  • 0 in reply to zrno soli
    Expert 1460 points

    What do you guys think is wrong if I get this message from BSL_Scripter? I used the script.txt file provided in the above 43oh link except I changed the COM port.

**Attention** This is a public forum