• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 6024 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

eZ-FET vs MSP-FET

Olli Mannisto
Expert 1750 points
Other Parts Discussed in Thread: MSP-FET, MSP430FR5969, MSP430FR5959

I have the MSP-FET debugger and the MSP430FR5969 launchpad. Is there any advantage/disadvantage on using the JTAG adapter or the on-board emulator for debugging/testing?

Obviously for the actual product I have to use the debugger but perhaps the eZ-FET offers more/better functionality for initial development?

  • 0
    TI__Guru**** 218697 points
    Functional differences are outlined in Section 2 of the MSP Debuggers User's Guide (SLAU647): www.ti.com/.../slau647e.pdf

    In summary the MSP-FET supports MSP432Pxx devices, allows JTAG access protection (fuse blow), can adjust the target supply voltage, allows 4-wire JTAG communication, and can access BSL mode & tools. But you shouldn't need any of these features for initial development.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Expert 1750 points

    I actually read that bit myself but I can't quite see that on pro/con basis. Add on top of that that eZ-FET is not actually a MSP debugger so it may have other advantages/downsides. I guess I'd get best result if I use the MSP-FET as it connects directly to the MCU and the USB connection goes through another microcontroller on-board which has to add overhead. 

    I found something on slau320x section 1.2.1.1 http://www.ti.com/lit/ug/slau320x/slau320x.pdf

    That gives you a simple pro/con table. 2-wire Spy-BI-Wire is slower but does not require any I/O pins as the pins are dedicated test pins. Of course you could see this as not having another two I/O pins.. JTAG is faster and has additional features which you mentioned but you're sacrificing 4 I/O pins.

  • 0 in reply to Olli Mannisto
    TI__Guru**** 218697 points
    The eZ-FET is most definitely a MSP debugger and supports SBW programming & communication on all MSP430 devices. But if you require the speed benefits offered by 4-wire JTAG then you will need to use the MSP-FET.

    Regards,
    Ryan
  • 0 in reply to Olli Mannisto
    Guru 34523 points

    Olli Mannisto said:

    That gives you a simple pro/con table. 2-wire Spy-BI-Wire is slower but does not require any I/O pins as the pins are dedicated test pins. Of course you could see this as not having another two I/O pins.. JTAG is faster and has additional features which you mentioned but you're sacrificing 4 I/O pins.

    Your target device is FRAM so there is no flash writing, just quick read / write SBW / JTAG operations like with RAM, and I guess that this should go fast enough with eZ-FET Lite on FR LP board. This is related to code download, and don't know about (speed) difference in break point debugging between SBW and full JTAG using FET's.
    .
    I extend SBW interface by using one extra I/O pin leaving full JTAG at the bottom also regarding speed.
  • 0 in reply to zrno soli
    Expert 1750 points
    After checking the MSP-FET and the launcher board schematics, I can see that MSP-FET has an actual FPGA along with another MSP430 device. The eZ-FET works with the microcontroller alone. MSP-FET has the capacity to offer much higher performance as that FPGA can go up to 350MHz. It's a different story if it's actually being used. I guess on practical terms the difference for debugging is pretty minimal.
  • 0 in reply to Olli Mannisto
    Guru 34523 points

    Olli Mannisto said:
    MSP-FEThas the capacity to offer much higher performance as that FPGA can go up to 350MHz. It's a different story if it's actually being used.

    My flasher doesn't have FPGA (works with the microcontroller alone), and it can come close to MSP-FET (up to 50 KB/s, full JTAG, not specified clock speed) regarding FRAM, using SBW (Write Quick). Using SBW+ (SBW extended with 1 I/O pin) it is 4 times faster. SBW can be limited by cap / resistor combo on RST pin, but without this (or modified to isolate FET connection) it can be really fast. For my point of view, it's all about (quality / fast) software.

    C:\msp430>flash -f test_msp430fr5959.txt -wq

    File: "test_msp430fr5959.txt"
    Address: 04400  Words: 32256
    Size: 64512 bytes

    Found SBW+ at COM23

    Get Device
    # JTID Fuse Device Core Hard Soft LotWafer DieX DieY
    0  99   OK   6181  1106  30   30  C1F22407 2B00 2200
    1  99   OK   6581  1106  30   30  E1271D07 2F00 1900

    Write Quick
    Time: 1414 ms  Speed: 44,6 KB/s

    Release Device

    Total Time: 1545 ms

    C:\msp430>flash -f test_msp430fr5959.txt -w

    File: "test_msp430fr5959.txt"
    Address: 04400  Words: 32256
    Size: 64512 bytes

    Found SBW+ at COM23

    Get Device
    # JTID Fuse Device Core Hard Soft LotWafer DieX DieY
    0  99   OK   6181  1106  30   30  C1F22407 2B00 2200
    1  99   OK   6581  1106  30   30  E1271D07 2F00 1900

    Write
    Time: 311 ms  Speed: 202,0 KB/s

    Release Device

    Total Time: 375 ms

    C:\msp430>

  • 0 in reply to Olli Mannisto
    Mastermind 9125 points

    Yes, I can't feel the performance difference for program size < 64KB. In this case, I prefer SBW for simple debugger connection.

**Attention** This is a public forum