• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 1592 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.

MSP430F167 Programming question

Cliff Wold
Prodigy 135 points
Other Parts Discussed in Thread: MSP430F167, MSP-TS430PM64

Our customer is using the MSP430F167. He is having problems programming it.

 

"Much of the time now it just says the fuse has been blown, but there's no way for my emulators to do that. The rest of the time it says the device isn't communicating. I have tried IAR 4.21, 4.20, 4.11B with the MSP-FET430UIF, MSPFET-P430IF, and J-Link. When I use elprotronic's free software for the thing, it says the firmware on the USB FET is out of date and if I try to upload the most current version, it just freezes. I've tried a brand new computer from I.T. with IAR 4.21 and 4.11B and that doesn't work either"

Can you please advise?

Thanks

  • 0
    TI__Genius 10830 points

    Try going back to a known good state and changing one variable at a time to isolate where the problem is.

    For example, start by trying to program the closest evaluation board, or whatever is on-hand:

    • MSP430 64-Pin Target board  MSP-TS430PM64
    • MSP430F167IPM (LQFP package)
    • MSP430 USB Debugging Interface  MSP-FET430UIF
    • IAR or CCS
    • MSP430F16x Code Examples (Rev. N)

    Compile fet140_1.c and see if you can run it on the target board.  Report back with your results.

  • 0
    Guru 227245 points

    'fuse blown' is another word for 'device seems to be there but does not react on JTAG commands'. Which can have various reasons.
    If you blow the fuse, then the JTAG interface is switched to permanent transparent mode and ignores all commands. So if it ignores the commands for any other reason, then it is as if the fuse had been blown.

    Is the device connected to a separate power supply while being programmed? Switching power supplies may introduce potential differences and prohibid proper communication. In  a recent thread we had a voltage difference of 12V which even fried the target MSP. If it is 1V or so, it can easily disturb the communication.
    Only connect the FET or the external power supply (except if it is battery or plain transformer based, as then there is a perfect galvanic separation)

  • 0
    TI__Genius 10830 points

    Using Code Composer Studio, try to update the MSP-FET430UIF firmware.  This is done by clicking the, "Debug Launch" button once you've got your project set up.

    For example here are the results from upgrading a MSP-FET430UIF from firmware version 2.04.07.001 to version 2.04.08.002

     

     

     

    Having something connected to the side of the MSP-FET430UIF labeled, "Target," is not necessary.  I did this with firmware upgrade with only the USB cable connected to the MSP-FET430UIF and nothing connected to the target side.

**Attention** This is a public forum