Due to the U.S. Thanksgiving holiday, please expect delayed responses during the week of 11/22.

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.

MSP430F2619S-HT: eZ-FET firmware build

Part Number: MSP430F2619S-HT
Other Parts Discussed in Thread: MSPDS, MSP-FET, MSP430F5528, MSP-TS430RGC64USB, MSP-EXP430FR5739, ENERGYTRACE, UNIFLASH

Has anyone been able to build the eZ-FET firmware from the source files provided here: http://www.ti.com/tool/MSPDS?

I've started a 30-day trial of the most recent version of IAR and have somewhat patched up the projects (no code changes, mainly adjusting settings,etc) to get them to compile and run the srec batch file after building. However, after this I'm left with just a bunch of individual txt files and not one, ready-to-program file.

I've used srec to join all of these files into one along with the TI-provided BSL found here: http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430_ezFETLite/latest/exports/eZ-FET_lite_Release_Package_rev_1_10_20130712.zip 

I've also been having issues compiling the BSL, that's why I've used the already-compiled one from TI.

Once I flash this whole thing to an MSP430F5528, this shows up on Windows device manager as a debug probe as expected. I then try to use MSP Flasher to access a target device: MSP Flasher complains that the debug probe firmware is corrupted and immediately goes into "fixing" it. After this it says that the debug probe firmware is outdated and asks if I want to upgrade it. I say "no" and then it errors out with an error 16 when it tries to access the target.

If I allow MSP Flasher to update the firmware by itself I can access other targets with the MSP430F5528 hardware.

My end goal is to possibly modify this firmware to use 4-wire JTAG in order to create a custom probe for the MSP430F2619S-HT.

Any help? I've kept the post somewhat high-level in order to make it an easier read.

  • Hi,

    This is the EZ-FET lite:  http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430_ezFETLite/latest/exports/eZ-FET_lite_Release_Package_rev_1_10_20130712.zip Can't it meet your requirement?

    You seem to combine the code from MSPDS and EZ-FET lite? Is it right?

    Here is another source REP430F:http://www.ti.com/tool/REP430F?keyMatch=REP430F&tisearch=Search-EN-everything&usecase=part-number. It is open source, you can use it to program MSP430 through JTAG.


  • Hi there, I've checked the eZ-FET release package and no, it doesn't meet my requirement because I would like to modify the HIL calls to use 4-wire JTAG instead of Spy-by-Wire.

    I am using the code from MSPDS as a starting point (currently trying to compile it with IAR per the "Read me" file in that package), but I've not been able to compile that project successfully (without modifications to the source).

    The replicator is another neat tool but unfortunately will not meet my needs. I definitely leveraged some ideas from that project, but it is not my ideal end solution.

    Thank you for responding. I'd like to know if anyone out there has successfully compiled the source code for eZ-FET or even MPS-FET using the package from MSPDS in IAR.

  • Hi,

    OK. I will consult our expert to see if it is possible to extract MSP-FET code or EZ-FET code from MSPDS.

    Are you do it for self-learning or based some projects?

    Why do you choose JTAG not SBW? What your want to output in the final?


  • eZ-FET lite and eZ-FET run the same code base. The only difference is the Voltage generation on between the FETs. So if you want to use JTAG, you can only get the code from MSP-FET. But MSP-FET won’t works since it has an FPGA on it. We do not share the FPGA VHDL code due to license reasons. Also you won’t be able to compile it.


  • Thanks for that. Now, back to the question at hand: how does one successfully compile the eZ-FET firmware from the source package provided in MSPDS? I've followed the instructions on the "readme" file provided in there but the instructions are minimal and I don't get the same output as the already-compiled code from TI.

  • Hi there, if you read my original post, you can see that I am wanting to make a custom emulator/programmer for a part that does not support SBW. I've perused through the HIL code in the MSPDS package and it seems that at least the intent of having it support 4-wire JTAG was there at some point. Is there any documentation available on this software project? The "readme" file provided in the package contains only minimal instructions.

  • Hi,

    1. Get it. The problem is that 4 wire JTAG is for MSP-FET, EZ-FET only support SBW, but for MSP-FET it means you need to work with FPGA. Even you can extract the MSP-FET code out, it still can't work.

    2. I must tell you that there is no any more document external or internal of TI. It is also the same condition when I learn it!

    3. One reason that you don't get the same output as the already-compiled code from TI is the IAR version. 

    4. MSPDS is really a nightmare. If you want to make your own programmer works under msp430.dll, I can't give you much help.  


  • :) not what I was hoping for, but thank you for getting back to me.

    Why is the project in IAR and not in CCS?

    I'll keep playing with it and see what else I can learn before giving up.

  • Eason Zhou said:

    1. Get it. The problem is that 4 wire JTAG is for MSP-FET, EZ-FET only support SBW, but for MSP-FET it means you need to work with FPGA. Even you can extract the MSP-FET code out, it still can't work.

    If I remember right, there is also FET430-UIF source inside MSPDS, that support 4 wire JTAG and don't have FPGA.

  • That's correct. This could be another alternate route for me, though the 1612 doesn't natively support USB like the 5528. Thank you!

  • Jesus Perez said:

    That's correct. This could be another alternate route for me, though the 1612 doesn't natively support USB like the 5528. Thank you!

    You are right in case if you are building exact copy, but I guess that you can take only 4 wire JTAG functions in C from there and use them with recalculated timing (strobe cycles for 2xx flash family should be adjusted).

  • The reason why use IAR is that:

    1. At that time, CCS is not good enough, ease use or even not existed, as you know MSP430 almost have 30 years old.

    2. The code size using IAR will be smaller than using CCS.

    3. Writing a document for MSPDS is not a high priority, as fewer customer need this function. My advice is that if you want to extract FET430-UIF. I advice you to use code on REP430F. And you can refer to this doucument:slaa754.pdf. It moves code from REP430F and make it work with only a MSP432 chip. Alough it is based on SBW, I think it can give you some idea how to realize you own JTAG programmer.

  • Is it possible to get the latest source files for the projects in MSPDS? The files currently on there have an old rev. of the com layer and when I build the project this is not compatible with the current version of the DLL.

  • Hi,

    Please double check, it is updated last week.


  • Hi there, thanks for getting back to me.

    I downloaded the new package and compiled it (perhaps not correctly) using the following version of IAR: 

    After compiling each project in the eZ-FET_Bios.eww workspace and both of the eZ-FET configurations of BSL.eww I used srec_cat to join all the memory images into one. I end up with the attached firmware file.custom_eZ-FET.txt

    I then use MSP430Flasher with the following command line to program this file onto an MSP430F5528 with an MSP-FET430UIF:

    MSP430Flasher.exe -n MSP430F5528 -w custom_eZ-FET.txt -u -b -v -z [VCC] (-i USB) (-e ERASE_ALL)

    I then try to access the newly flashed MSP430F5528 as an emulator via USB with MSP Flasher but I get the following error:

    Any help? What am I missing here?



    Let me provide bit more background: I'm using an MSP-TS430RGC64USB, a breadboard and some passives to realize the circuit presented in this document.

    I am using an MSP-EXP430FR5739 as a test target (that will be emulated by the custom eZ-FET lite).

    If I flash the MSP430F5528 with the eZ-FET firmware I compile from source code I encounter the error above.

    I I allow MSP430Flasher to update the MSP430F5528 with the factory firmware image from the dll, everything works as expected:

    Again, the question is: how can I successfully build the eZ-FET firmware from source?

  • Hi,

    If you want to realize ez-FET function, what don't you try to use ez-FET lite?

    ez-FET includes energytrace and programming function. I am not sure if it can works fine on only one F5528.


  • Hi there, I would like to successfully compile the sources. Would it be possible to get help from the team maintaining this project?

  • Let me consult them. Please wait for some time.


  • I've continued doing some testing while I wait for the development team to get back.

    Turns Code Composer Studio is able to succesfully debug the target on the MSP-EXP430FR5739 through the MSP430F5528 running the eZ-FET firmware compiled from source.

    CCS still complains about the probe firmware being out of date but it can program/emulate the target successfully. I guess another question is: is this blind luck or maybe MSP430Flasher and UniFlash do things in a way that is incompatible with the firmware compiled from source?

  • The problem is that msp430.dll in CCS and MSP430 flasher is different version. I think this week my colleague can give a conclusion.