• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 79 subscribers
  • Views 1493 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.

Using eZ-FET lite from MSP-EXP430F5529LP

Victor1
Prodigy 230 points
Other Parts Discussed in Thread: MSP430F2013, MSP-EXP430F5529LP

Hello. I want to use eZ-FET lite from LP to debug my own board with MSP430F2013. Previously I used MSP-FET430UIF and it works fine.

I made cable to connect from LP to JTAG header on my PCB. The schematic is:

LP                 JTAG on my PCB

GND----------9 GND

3.3V-----------2 VCCTOOL

SBW RST----1 TDO/TDI

SBW TST----7 TCK

I am not sure about connection of  pin 8 TEST/VPP on JTAG header, so I left it unconnected.

Cable is 20 cm long.

The problem is that IAR EW MSP430 5.50.2 doesn't see eZ-FET lite. I check it in Project->Options->FET Debugger->Setup->Connection->...

There is only "Automatic" and not COM port of MSP Debug Interface. Although on wiki page of EZ-FET lite is said that it needs "IAR Embedded Workbench 5.50 or higher".

I tried to program my PCB with IAR EW MSP430 6.10.2. This version is not convenient for me now, but it sees eZ-FET lite and looks like it works good. I programmed and debugged my PCB with it.

How can I use IAR EW MSP430 5.50.2 with eZ-FET lite on  MSP-EXP430F5529LP?

  • 0
    Prodigy 230 points

    Does anyone have any suggestions? Or it would be better to send a letter to TI support?

  • 0
    Guru 92251 points

    Victor1 said:
    How can I use IAR EW MSP430 5.50.2 with eZ-FET lite on  MSP-EXP430F5529LP?

    According the Releases table on the MSP430 Debug Stack support for the eZ-FET was only added in IAR version "5.52.1 + 5.51.6".

    Support for the eZ-FET is in the MSP430.dll which IAR uses. To make IAR 5.50.2 use the eZ-FET you *may* be able to copy the MSP430.dll from 6.10.2 into your 5.50.2 installation directory (saving a back-up of the original MSP430.dll in 5.50.2).

    I haven't got IAR to be able to check if that will work - perhaps you should ask IAR support?

  • 0 in reply to Chester Gillon
    Prodigy 230 points

    Looks like it doesn't working. After replacement I can see COM of eZ-FET in list, but when I try to connect to MSP it throws me an error "Unknown device".

    Perhaps it was a typo in min IAR version to use with eZ-FET.

  • 0 in reply to Victor1
    Guru 227245 points
    These are two different things. Seeing the eZ-FET in the device manager (and using it in the IDE) means you have connected the PC with the FET. The error you see means the FET cannot connect (or doesn't know) the target processor.
    I'm not sure whether the 5529LP's eZ-FET knows the F2013. Only the FET430UIF knows all the MSPs. The eZ-FETs usually only know the targets on their own boards and close relatives. IIRC, there's a compatibility list somewhere in the MSP430 Wiki.
  • 0 in reply to Jens-Michael Gross
    Prodigy 230 points

    Jens-Michael Gross said:
    These are two different things. Seeing the eZ-FET in the device manager (and using it in the IDE) means you have connected the PC with the FET. The error you see means the FET cannot connect (or doesn't know) the target processor.
    I'm not sure whether the 5529LP's eZ-FET knows the F2013. Only the FET430UIF knows all the MSPs. The eZ-FETs usually only know the targets on their own boards and close relatives. IIRC, there's a compatibility list somewhere in the MSP430 Wiki.

    eZ-FET knows the F2013. As I was saying:

    "I tried to program my PCB with IAR EW MSP430 6.10.2. This version is not convenient for me now, but it sees eZ-FET lite and looks like it works good. I programmed and debugged my PCB (which include MSP430F2013) with it."

  • 0 in reply to Victor1
    Guru 227245 points
    The two versions of the compiler/IDE use different versions of the MSP430 DLL. And the DLL and the FET need to have matching versions. Else anything can happen. Usually, you're prompted to updat the FET firmware when a newer DLL verison detects an older FET firmware. I'm not sure about the opposite direction (older DLL with newer FET). Chester already suggested trying to copy the newer DLL over to the older compiler. As long as the DLL interface matches, this should work. (but keep a backup)

**Attention** This is a public forum