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.

Elprotronics FET MSP430 Flash Programmer Issue

Other Parts Discussed in Thread: MSP430F2617

I would like to be able to quickly program the MSP430 with FET-Pro430 by Elprotronics. The issue is that when I try to program through FET-Pro430 using the *.hex file output from CCSV4 nothing happens. It says that it has programmed  with all checks passed, but then the MSP doesn't run. Whereas when I use debug in CCSV4 to program the MSP it runs.

Are there some settings in either CCSV4 or FET-Pro430 that need to be changed?

Installation:

  1. Windows 7 x64
  2. CCS v4.2.1.00004 
  3. MSP-FET430 UIF 'V1.4a'  Firmware 2.04.07.001
  4. MSP430F2617

Thanks,

Lucas

  • Lucas,

    make sure you select the option to reset & start the application after programming. Option can be found under Setup --> Connection/Device Reset.

    Regards,

    Dung

  • Besides settign the option to start the applicaiton after programming, there are numerous settings in teh programmers that affect what is programmed and what not.
    Depending on the selected device, the programmable memory locations are different. But in addition to this (I assume you selected the correct device and the compilation fits the device too), you can limit the area to be programmed. These settigns will, if misconfigured, make the programmer not programming the full firmware, or nothing at all.

    You should check this.

    I also nothiced, that  even if everything is configured correctly, the different methods to reset the device may have different levels of success. Some experiments were necessary to let the device reset properly (well, at least most of the time), while keeping the 'try and error' time for the device reset as short as possible (else the programmer will try all methods before starting programming, and before starting the programmed application).

    I still sometimes have to tap on the socket of the experimenters board (effectively unmounting the MSP for a moment) to make the applicaiton start after a program run.

  • Thanks for the replies,

    The problem was the Post-build step in CCSv4, I should have been using the predefined Intel-Hex post-build step but was using a custom one that was not functioning correctly.

    Thanks again,

     

    Lucas

**Attention** This is a public forum