• Announcements

    • bluehash

      Forum Upgrade   03/11/2017

      Hello Everyone, Thanks for being patient while the forums were being fixed and upgraded. Please see details and report issues in this thread. Thanks!
jbremnant

MSP430 USB FET (JTAG + SBW)

25 posts in this topic

Gosh, it's been such a long time since I posted here...

 

Do any of you guys have experience with TI's msp430 jtag programmer?

 

https://estore.ti.com/MSP-FET430U64A-MSP430-64-Pin-Target-board-and-USB-Programmer-Pinout-A-P1643.aspx

http://focus.ti.com/docs/toolsw/folders/print/msp-fet430u64a.html

 

I wanted to try my hands at beefier msp430 mcu's and thought I needed a programmer that can cover range of products besides the ones with SBW. Let me know if this is worth getting?

Share this post


Link to post
Share on other sites

I have it. It's the only thing that will work on the older devices that only have JTAG.

 

I think it's worth it.

jbremnant likes this

Share this post


Link to post
Share on other sites

Thanks all for the feedback.

I actually ordered one. I'll post my impression of it once I play around with it.

Share this post


Link to post
Share on other sites

Hi guys

 

Has anyone managed to get fet430uif working on linux using mspdebug?

I am on Ubuntu 10.04.1 LTS, and I get the following error:

msp430-gcc -Os -Wall -mmcu=msp430x5438 -o ex.elf ex.o
mspdebug -d /dev/ttyUSB0 uif "prog ex.elf"
MSPDebug version 0.15 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer 
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Trying to open UIF on /dev/ttyUSB0...
Initializing FET...
FET protocol version is 20105000
fet: FET returned NAK
fet: init failed
Trying again...
Initializing FET...
FET protocol version is 20105000
fet: FET returned NAK
fet: init failed
make: *** [upload] Error 255

Share this post


Link to post
Share on other sites

http://www.linuxquestions.org/questions ... ost4211460

Connect to an eZ430-F2013 or a FET430UIF device. The device argument should be the filename of the appropriate tty device. The TI serial converter chips on these devices are supported by newer versions of the Linux kernel, and should appear as /dev/ttyXX when attached.

USB connection is not supported for this driver.

 

Probably not a USB but a tty

Share this post


Link to post
Share on other sites

Try using the named drivers for mspdebug, I had issues with it when i pointed it to the launchpads TTY device,but when i used just rf2500 (uif in your case) it worked with out issue. also try using the -U command

-U bus:device

Specify a particular USB device to connect to. Without this option, the first device of the appropriate type is opened.

 

http://mspdebug.sourceforge.net/manual.html

 

 

also any dmesg's or error in your sys logs may help point out what the issue is

Share this post


Link to post
Share on other sites

So mspdebug manual says the uif device is only supported via tty serial interface. -U won't do.

 

My dmesg tells me the following:

 

root@linux-desktop:/usr/lib# dmesg | grep TI
[3460489.105892] ti_usb_3410_5052_1 ttyUSB0: TI USB 3410 1 port adapter converter now disconnected from ttyUSB0
[3460489.123453] ti_usb_3410_5052 2-2:2.0: TI USB 3410 1 port adapter converter detected
[3460489.124292] usb 2-2: TI USB 3410 1 port adapter converter now attached to ttyUSB0

root@linux-desktop:/usr/lib# lsmod | grep usbs
usbserial              33019  1 ti_usb_3410_5052

root@linux-desktop:/usr/lib# lsusb | grep Tex
Bus 002 Device 015: ID 0451:f430 Texas Instruments, Inc. MSP-FET430UIF JTAG Tool

 

Looks ok as far as drivers are concerned.

 

I wonder if it has to do with the firmware on the FET430UIF...

 

Any ideas will be appreciated..

Share this post


Link to post
Share on other sites

drivers look good, nothing that i can see looks out of place.

list of things that I would try if you havent already.

 

can you access the uif-bsl? on that device

have you tried another usb cable and port?

 

are you able to test this on a windows box?

 

have you tried a different chip to program?

have you tried both SBW and jtag optioins?

have you tried the force-reset command?

 

it could be the firmware as a cause to your issue, but i couldnt find any posts or info on that

Share this post


Link to post
Share on other sites

Hey jsolarski, thanks for your response.

 

I haven't tried it on windows yet. Will do next.

I did try to toggle -j option for jtag vs sbw.

Also tried force-reset option. No luck.

 

I couldn't find much info online either.

I'll post my findings if I manage to get it working in linux.

Share this post


Link to post
Share on other sites

I also have EXACTLY the same issue:

the MSP-FET430UIF, gcc-msp430 version 20110612-1 and other commensurate .deb packages (installed on Ubuntu 11.04)

 

Here's what I get:

 

# mspdebug uif -d /dev/ttyUSB0

MSPDebug version 0.16 - debugging tool for MSP430 MCUs

Copyright © 2009-2011 Daniel Beer

This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

 

Trying to open UIF on /dev/ttyUSB0...

Initializing FET...

FET protocol version is 20105000

fet: FET returned NAK

fet: init failed

Trying again...

Initializing FET...

FET protocol version is 20105000

fet: FET returned NAK

fet: init failed

----------------------------------

 

The only clue I can see is the following (from dmesg when I connect the MSP-FET430UIF):

 

[ 9383.452058] usb 3-2: new full speed USB device using uhci_hcd and address 3

[ 9383.684130] ti_usb_3410_5052 3-2:1.0: TI USB 3410 1 port adapter converter detected

[ 9383.684150] ti_usb_3410_5052: probe of 3-2:1.0 failed with error -5

[ 9383.687291] ti_usb_3410_5052 3-2:2.0: TI USB 3410 1 port adapter converter detected

[ 9383.687434] usb 3-2: TI USB 3410 1 port adapter converter now attached to ttyUSB0

 

----------------

 

Also, after running the mspdebug command, the "Mode" LED illuminates on the MSP-FET430UIF.

 

Any ideas?

Share this post


Link to post
Share on other sites

Here's a tip, based on this post, try

mspdebug -j -d /dev/ttyUSB0 uif

(that is, JTAG mode instead of SBW, -j). Does that change anything?

 

Sorry, wasn't reading the previous posts carefully enough :oops:

linuxmill likes this

Share this post


Link to post
Share on other sites

Here's what I got (exactly the same as before):

 

# mspdebug -j -d /dev/ttyUSB0 uif

MSPDebug version 0.16 - debugging tool for MSP430 MCUs

Copyright © 2009-2011 Daniel Beer

This is free software; see the source for copying conditions. There is NO

warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

 

Trying to open UIF on /dev/ttyUSB0...

Initializing FET...

FET protocol version is 20105000

fet: FET returned NAK

fet: init failed

Trying again...

Initializing FET...

FET protocol version is 20105000

fet: FET returned NAK

fet: init failed

Share this post


Link to post
Share on other sites

Hey, at least you get some response. :mrgreen:

oppa@oppa-labor ~ $ mspdebug -j -d /dev/ttyUSB0 uif
MSPDebug version 0.17 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Trying to open UIF on /dev/ttyUSB0...
uif: can't open serial device: /dev/ttyUSB0: No such file or directory

[   69.100472] usb 1-4.1: new full speed USB device using ehci_hcd and address 5
[   69.212591] usb 1-4.1: New USB device found, idVendor=0451, idProduct=f430
[   69.212595] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   69.212599] usb 1-4.1: Product: MSP-FET430UIF JTAG Tool
[   69.212601] usb 1-4.1: Manufacturer: Texas Instruments
[   69.212604] usb 1-4.1: SerialNumber: TUSB34103F2D899DC542FFA8
[   69.274804] usbcore: registered new interface driver usbserial
[   69.274819] USB Serial support registered for generic
[   69.275138] usbcore: registered new interface driver usbserial_generic
[   69.275140] usbserial: USB Serial Driver core
[   69.281033] USB Serial support registered for TI USB 3410 1 port adapter
[   69.281048] USB Serial support registered for TI USB 5052 2 port adapter
[   69.281060] ti_usb_3410_5052 1-4.1:1.0: TI USB 3410 1 port adapter converter detected
[   69.291406] usb 1-4.1: ti_download_firmware - firmware not found
[   69.291421] ti_usb_3410_5052: probe of 1-4.1:1.0 failed with error -5
[   69.291440] usbcore: registered new interface driver ti_usb_3410_5052
[   69.291442] ti_usb_3410_5052: v0.10:TI USB 3410/5052 Serial Driver

Firmware not found ?

oppa@oppa-labor ~ $ lsusb
...
Bus 001 Device 005: ID 0451:f430 Texas Instruments, Inc. MSP-FET430UIF JTAG Tool 

 

Edith: I've just received it today. A quick try with IAR on XP failed too.

Share this post


Link to post
Share on other sites

Whatever said to use -d for the MSP-FET430UIF is out of date. Use -U if you need to select a specific FET, otherwise all you should need is -j (with the current git release, at least, and only if your target uses JTAG instead of SBW).

 

linux[444]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 002 Device 012: ID 0451:f432 Texas Instruments, Inc. eZ430 Development Tool
Bus 001 Device 012: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 005 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 014: ID 0451:f430 Texas Instruments, Inc. MSP-FET430UIF JTAG Tool
linux[445]$ mspdebug -j -U 2:14 uif
MSPDebug version 0.17 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer 
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

ti3410: warning: can't detach kernel driver: No such file or directory
TI3410 device is in boot config, setting active
Initializing FET...
FET protocol version is 20405003
Configured for JTAG (2)
Set Vcc: 3000 mV
Device ID: 0x0580
Device: MSP430F5438A
Code memory starts at 0x5c00
Number of breakpoints: 8

Available commands:
   =         delbreak  gdb       load      opt       reset     simio     
   alias     dis       help      locka     prog      run       step      
   break     erase     hexout    md        read      set       sym       
   cgraph    exit      isearch   mw        regs      setbreak  

Available options:
   color           gdb_loop        iradix          
   fet_block_size  gdbc_xfer_size  quiet           

Type "help " for more information.
Press Ctrl+D to quit.

(mspdebug)

gordon and jbremnant like this

Share this post


Link to post
Share on other sites

It's running under XP now at least.


oppa@oppa-labor ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 002: ID 1bcf:05c5 Sunplus Innovation Technology Inc. SPRF2413A [2.4GHz Wireless Keyboard/Mouse Receiver]
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 006: ID 0451:f430 Texas Instruments, Inc. MSP-FET430UIF JTAG Tool
oppa@oppa-labor ~ $ mspdebug -j -U 1:6 uif
MSPDebug version 0.17 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

This driver does not support raw USB access.

This driver does not support raw USB access.

I this needed for the UIF FET ?

Share this post


Link to post
Share on other sites

I just tried using the latest version of mspdebug with my fet430uif.

Didn't work.

 

However, I noticed that my firmware version was outdated compared to the one posted by other folks here.

Mine was on 20105000.

 

Found this post that suggested that using CCSv4 will automatically update the firmware on this programmer.

And it did!

 

Try to build any example project and upload it to the target chip. Follow any of the "hello world" tutorials on this link.

Flash the target chip by CCS menu "Target -> Debug Active Project".

When your fet is plugged in, it will be automatically detected by CCS, and will prompt you for firmware upgrade if your current version is old.

 

Mine got upgraded to: 20405003

 

Here's the output for proof (using mspdebug on Ubuntu)

 

$ mspdebug -j -U 2:27 uif
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer 
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

TI3410 device is in boot config, setting active
Initializing FET...
FET protocol version is 20405003
Configured for JTAG (2)
Set Vcc: 3000 mV
Device ID: 0x0580
Device: MSP430F5438A
Code memory starts at 0x5c00
Number of breakpoints: 8

Available commands:
   =         delbreak  gdb       load      opt       reset     simio
   alias     dis       help      locka     prog      run       step
   break     erase     hexout    md        read      set       sym
   cgraph    exit      isearch   mw        regs      setbreak

Available options:
   color           gdb_loop        iradix
   fet_block_size  gdbc_xfer_size  quiet

Type "help " for more information.
Press Ctrl+D to quit.

(mspdebug)

 

Btw, some small shell trick to roll up lsusb command in one go. (I'd put this in a Makefile)

 

$ mspdebug -U `lsusb -d 0451: | grep JTAG | awk '{print $2":"$4}' | sed -e 's/:$//'` -j uif

 

example Makefile

 

TARGET=ex
CC=msp430-gcc
CFLAGS=-Os -Wall -mmcu=msp430x5438
OBJS=$(TARGET).o

DEVID := $(shell lsusb -d 0451: | grep JTAG | awk '{print $$2":"$$4}' | sed -e 's/:$$//')

all: $(OBJS)
       $(CC) $(CFLAGS) -o $(TARGET).elf $(OBJS)
%.o: %.c
       $(CC) $(CFLAGS) -c $<
clean:
       rm -fr main.elf $(OBJS)
upload: all
       mspdebug -U $(DEVID) -j uif "prog $(TARGET).elf"

 

Enjoy!

Share this post


Link to post
Share on other sites

I did have the same problems so I decided to upgrade the firmware, but after updating my firmware using CCSv5 my firmware version now is 30201009. I couldn't connect to it via the uif driver. It did work with the tilib driver though. Compiling the libmsp430.so (required for tilib driver) is described here: mspdebug [dot] sourceforge [dot] net/tilib.html.

Just thought I'd give a heads up in case someone runs into the same problems as I did. ;)

Share this post


Link to post
Share on other sites

Thanks everyone. I am a new guy to use MSP430. I had bought one MSP-FET. I tried to use it in IAR Embedded Workbench for MSP430 7.10. My launchpad was MSPEXP430G2 with MSP430G2553 chipset. I connected FET to lauchpad by spy-by-wire(SBWTDIO,SBWTCK,GND). When I pressed download and debug buttom(ctrl+D), IAR was crash. Any tip for this issue? 

Share this post


Link to post
Share on other sites
On 4/14/2017 at 9:25 PM, darrenlocust said:

I connected FET to lauchpad by spy-by-wire(SBWTDIO,SBWTCK,GND).

@darrenlocust

Maybe a dumb question, but I don't see you mentioning Vcc.  SBW is actually 4 wires, Vcc, GND, and the SBWTDIO,SBWTCK leads. How did you get from the 14 pin connector on the FET to the board? Patch wires?

Also, in IAR project options, under the FET Debugger, did you select Automatic selection, or manually select Spy-By-Wire? And, I know this is obvious, but under General Options did you select the G2553?

Edited by NurseBob
Added OP's tag

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now