• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 3013 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.

EZ430-RF2500-SEH: EZ430 USB emulator damaged by IAR auto-update feature. How to recover?

EE LL
Prodigy 150 points

Part Number: EZ430-RF2500-SEH

Hello,

I need to re-visit an old project that uses the MSP430. I designed this years ago using the EZ430-RF2500 kit.

When I tried to download the project to the device IAR popped a message indicating that the EZ430 USB tool was outdated and requires an update... accepted and now the EZ430 emulator appears in device manager as an MSP-FET430UIF which is a completely distinct device.

Looking at other threads and posts I found that this was a known issue: IAR somehow confuses the EZ430 tool as an MSP-FET430UIF and uploads the FW on it rendering it useless.

My tool still can download the code to the flash but all UART and debugging capabilities are not working.

I've looked around a lot for a procedure to recover the FW into the tool.

Found a wiki showing how to re-flash it but requires precisely to have a FET430UIF programmer which would defeat the purpose of having this tool.

I don't see much sense in buying a FET430UIF at this point since it is an old tool and its new replacement is even more expensive....

I also tried IAR's updatetool.exe but it doesn't recognize the device. And it doesn't allow to force the flashing, if it doesn't recognize the tool it doesn't proceed.

I've also downloaded CCS, MSPdebug and ELP's  programmers but none is able to reflash it. they don't recognize the device and even if they would reflash, they use their own FW but it is for the wrong device. They don't let me provide the FW myself

I've read that this was a known problem in the early days of this kit and back then TI used to replace the EZ430 emulator for free but that was years ago.

So, does anyone know of any SW tool that could let me re-flash the EZ430 emulator back with its original FW to be an actual EZ430 emmulator instead of a confused FET430UIF? So, the tool must 'believe' it is talking to a FET430UIF but allow me to enter my own FW file (I have the txt file) and the tool should be able to program the device in a 'forced' mode, even if the IDs don't match.

Thanks for any input in this matter.

e.

  • 0
    TI__Genius 15370 points
    Hi Ezequiel,

    I need to get in contact with our team responsible for this emulator to discuss the best course of action. I'll update you as soon as we come to a solution or have more questions for you. Thank you for your patience!

    Best regards,
    Caleb Overbay
  • 0 in reply to Caleb Overbay
    Prodigy 150 points

    Thanks a lot Caleb  for your response. I'll be waiting for a solution. I'm sure somebody must have found a work around this issue.

  • 0 in reply to EE LL
    TI__Genius 15370 points

    Hi Ezequiel,

    I apologize for the delay in reply. First I'd like to recommend that if you will be working on any further MSP430 projects to purchase an MSP-FET. The MSP-FET works with any MSP430 device.

    I spoke with our team responsible for the MSP430 programming tools and was informed that you should be able to use the MSP430.dll and it's API to update the firmware using MSP430_FET_FwUpdate(). Using this method, you can try to recover the tool using your own txt file. However, this is something we have not tested because we do not have this particular board on hand. I can help guide you through this process but I can't guarantee the end result. 

    You can download the MSP Debug Stack which includes the dll, example code, and documentation on how to use the APIs. Please take a look through them and read the MSPDebugStack Developer's Guide provided in the download. Let me know if you have any questions. 

    Best regards, 
    Caleb Overbay

  • 0 in reply to EE LL
    TI__Genius 15370 points
    Hi Ezequiel,

    Were you able to make any progress with the information I provided?

    Best regards,
    Caleb Overbay
  • 0 in reply to Caleb Overbay
    Prodigy 150 points

    Hello Caleb,

    thanks for your support in this matter.

    I downloaded the package and tried. I must say the same package was already in my computer too, which means that this was one of the -many- options I tried already. However following your advice I gave it another try.

    I use the "UifUpdate" example as base.

    I modified a few lines to use my own .txt file (which btw I downloaded from http://processors.wiki.ti.com/index.php/EZ430_Emulator_Upgrade

    void CMSP_FET430UIF_SetupDlg::OnUpdate()
    {
    // Firmware Update
    STATUS_T Ret = STATUS_ERROR;
    LONG RetErrorNumber = NO_ERR;
    int32_t version = 0;
    char ez430[] = "ezFW_V30394216.txt";    /* MY CHANGE */

    m_ctrlBlProgress.SetRange(0,100);
    m_ctrlBlProgress.SetPos(0);

    if((Ret = MSP430_Initialize("COM37"/*TIUSB"*/,&version)) == STATUS_OK)     /* MY CHANGE */
    {

    if((Ret = MSP430_FET_FwUpdate(ez430,MY_MSP430_FET_NOTIFY_FUNC,(int32_t)this)) == STATUS_OK)    /* MY CHANGE */
    {
    m_strPercent = "100";
    m_ctrlBlProgress.SetPos(100);
    m_strDllVersion = m_strDllVersion;
    }
    else
    {
    RetErrorNumber = MSP430_Error_Number();
    m_strStatus = MSP430_Error_String(RetErrorNumber);
    }
    // End of Update
    }

    UpdateData(FALSE);
    }

  • 0 in reply to EE LL
    Prodigy 150 points
    Hi Caleb,
    In my previous post I added photos and more comments however for some reason they are not shown... I tried twice and both posts have same problem so I'm adding here some of the missing part
    =======
    - I tried with both "COM37" and "TIUSB", according to the documentation this should make no difference.

    - As indicated in the documentation, I create the file cdc.log with the line "True" only (without this the tool fails).

    - I copied the msp430.dll and my .txt file to the execution folder.


    Then I run it (I use the debugger to step by step check the process):

    the MSP430_Initialize() returns Ok. The dialog opens and shows the DLL version 2.04.09.001 and MSP_FET430UIF version: 1.00.02.000.

    Then the dialog shows "Initializing Bootloader..." and then it displays "Could not initialize device interface" and stops there.

    Attached you'll find the dialog when it stops and also a pic of the device manager showing my device.


    The procedure seems straightforward and easy however doesn't work. The documentation about MSP430_FET_FwUpdate() is short and concise, maybe there's an undocumented option that I need to use.



    Thanks for your support again.



    e.
  • 0 in reply to EE LL
    TI__Genius 15370 points
    Hi Ezequiel,

    Thanks for the update. I'll need to pass this information on to our team responsible for the programming tools as its a little beyond my expertise. They're currently out of office until next week, so there will be a delay in communication. I'll continue to keep you updated on the progress of this thread. Thanks again for your patience!

    Best regards,
    Caleb Overbay
  • 0 in reply to EE LL
    TI__Genius 15370 points

    Hi Ezequiel, 

    Thank you for your patience. I've been informed that the eZ430 based debugging tools do not have the capability to be updated. Can you post a picture of the device you're using so we can verify what you are using?

    Best regards, 

    Caleb Overbay

  • 0 in reply to Caleb Overbay
    Prodigy 150 points

    Thanks for your support Caleb, attached are the photos.

    (note: I soldered the vertical pins, they were not originally).

    Thanks again

    e.

  • 0 in reply to EE LL
    TI__Genius 15370 points

    Hi Ezequiel, 

    Unfortunately the tool you're using is very old and there is not much support for it anymore. After discussing this with our internal team we've come to the conclusion that there is little chance for recovering this device. 

    However, there is an alternative to purchasing the MSP-FET. You could instead purchase one of our LaunchPads such as the MSP-EXP430FR2433 that contains an on-board ez-FET that will be compatible with all MSP430 devices. This option is significantly less expensive than purchasing the MSP-FET and should get you back on track. 

    Best regards, 
    Caleb Overbay

  • 0 in reply to Caleb Overbay
    Prodigy 150 points

    Thanks for your support Caleb.

    My main concern is the compatibility with my licensed IAR IDE 5.6.

    For example, if I were to buy the MSP-FET, your website indicates that it requires IAR 7.1 minimum.

    Your website also advises "The preferred solution is to update to the latest version of CCS or IAR"

    I could buy the programmer but getting a new IAR license would go way beyond budget

    Thanks again for your assistance. My team will seek other alternatives to resolve this matter

  • 0 in reply to EE LL
    TI__Genius 15370 points
    Hi Ezequiel,

    I'd like to point out that the full version CCS is now completely free to use and the TI compiler is now comparable in performance to the IAR compiler. This could be an option rather than upgrading your IAR license to work latest version of IAR.

    Additionally, the ez-FET on the LaunchPads only supports spy-bi-wire (SBW) communication and not full JTAG. The ez-FET will also work with your version of IAR but the SBW limitation might not fit with your application's needs.

    Best regards,
    Caleb Overbay
  • 0 in reply to Caleb Overbay
    Prodigy 150 points

    Thanks a lot Caleb, you've been of much help in this matter. We'll consider your advise for our case.

**Attention** This is a public forum