Hi!
Hmm... I think I have the same problem but with different reason...
I have a board (custom) and want to attach the FET430UIF to it. Using
Windows it works. But with mspdebug ti does not... neither using raw USB
nor ttyUSB mode.

This is what happens using the serial port (yes, ttyUSB1 is correct):

Trying to open UIF on /dev/ttyUSB1...
Initializing FET...
FET protocol version is 20408002
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
fet: FET returned error code 4 (Could not find device (or device not
supported))
fet: command C_IDENT1 failed
fet: identify failed
Trying again...
Initializing FET...
FET protocol version is 20408002
Configured for Spy-Bi-Wire
Sending reset...
uif: read error: Connection timed out
warning: fet: reset failed
fet: FET returned error code 4 (Could not find device (or device not
supported))
warning: fet: set VCC failed
fet: reply type mismatch
fet: command C_IDENT1 failed
fet: identify failed


And this using the raw interface:

TI3410 device is in boot config, setting active
Initializing FET...
FET protocol version is 20408002
Configured for Spy-Bi-Wire
ti3410: can't receive data: No such device
warning: fet: set VCC failed
ti3410: can't send data: No such device
fet: command C_IDENT1 failed
fet: identify failed
Trying again...
Initializing FET...
ti3410: can't send data: No such device
fet: open failed
ti3410: warning: TI_CLOSE_PORT failed: No such device


Any ideas?

Cheers
  nils

Am 13.11.2011 11:52, schrieb Stephan Goldenberg:
> Am Sonntag, den 13.11.2011, 09:56 +1300 schrieb Daniel Beer:
>> On Sat, Nov 12, 2011 at 06:57:34PM +0100, Stephan Goldenberg wrote:
>>> Am Samstag, den 12.11.2011, 12:29 +1300 schrieb Daniel Beer:
>>>
>>>> The "uif" driver is just for the FET430UIF (v2) and eZ430-F2013 tools.
>>>
>>> UH-HUH...I got V1.4a
>>>
>>>> The eZ430-RF2500, Launchpad and Chronos use a slightly different
>>>> protocol, which the "rf2500" driver supports.
>>>
>>> Hi,
>>>
>>> thanks for the new version but it's still not working with FET430UIF
>>> connected to 430F149 board (Itead) running Debian sid.
>>>
>>> oppa@oppa-mag:~$ /usr/bin/mspdebug -j uif
>>> MSPDebug version 0.18 - debugging tool for MSP430 MCUs
>>> Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
>>> This is free software; see the source for copying conditions.  There is
>>> NO
>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>>> PURPOSE.
>>>
>>> Searching for firmware for TI3410...
>>>     - checking /usr/local/lib//mspdebug/ti_3410.fw.ihex
>>> Loaded 13765 byte firmware image (checksum = 0xb5)
>>> Starting download...
>>> ti3410: warning: can't detach kernel driver: Operation not permitted
>>> ti3410: can't claim interface: Operation not permitted
>>> ti3410: firmware download failed
>>> oppa@oppa-mag:~$ su -c '/usr/bin/mspdebug -j uif'
>>> Passwort: 
>>> MSPDebug version 0.18 - debugging tool for MSP430 MCUs
>>> Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
>>> This is free software; see the source for copying conditions.  There is
>>> NO
>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>>> PURPOSE.
>>>
>>> Searching for firmware for TI3410...
>>>     - checking /usr/local/lib//mspdebug/ti_3410.fw.ihex
>>> Loaded 13765 byte firmware image (checksum = 0xb5)
>>> Starting download...
>>> ti3410: warning: can't detach kernel driver: No data available
>>> ti3410: warning: reset failed: No such device
>>> Waiting for TI3410 reset...
>>> TI3410 device is in boot config, setting active
>>> Initializing FET...
>>> FET protocol version is 20408002
>>> Configured for JTAG (2)
>>> ti3410: can't receive data: No such device
>>> warning: fet: set VCC failed
>>> ti3410: can't send data: No such device
>>> fet: command C_IDENT1 failed
>>> fet: identify failed
>>> Trying again...
>>> Initializing FET...
>>> ti3410: can't send data: No such device
>>> fet: open failed
>>> ti3410: warning: TI_CLOSE_PORT failed: No such device
>>> oppa@oppa-mag:~$ lsusb
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 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 004 Device 017: ID 0451:f430 Texas Instruments, Inc. MSP-FET430UIF
>>> JTAG Tool
>>>
>>> Does this mean V1.4a is not supported ?
>>
>> Hi Stephan,
>>
>> Under Linux, the FET430UIF should appear as /dev/ttyUSB0 (or similar),
>> so try this instead:
>>
>>     mspdebug -j uif -d /dev/ttyUSB0
>>
>> Without the -d argument, the raw USB interface is used, which is only
>> suitable for systems without kernel drivers for the TI3410.
>>
>> Cheers,
>> Daniel
>>
> Hi,
> 
> that's even worse. There is no /dev/ttyUSB* :
> 
> oppa@oppa-mag:~$ su -c '/usr/bin/mspdebug -j uif -d /dev/ttyUSB0'
> Passwort: 
> MSPDebug version 0.18 - debugging tool for MSP430 MCUs
> Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
> 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
> oppa@oppa-mag:~$ ls /dev/ttyU*
> ls: Zugriff auf /dev/ttyU* nicht möglich: Datei oder Verzeichnis nicht
> gefunden
> oppa@oppa-mag:~$ ls /dev/tty*
> /dev/tty    /dev/tty19  /dev/tty3   /dev/tty40  /dev/tty51  /dev/tty62
> /dev/tty0   /dev/tty2   /dev/tty30  /dev/tty41  /dev/tty52  /dev/tty63
> /dev/tty1   /dev/tty20  /dev/tty31  /dev/tty42  /dev/tty53  /dev/tty7
> /dev/tty10  /dev/tty21  /dev/tty32  /dev/tty43  /dev/tty54  /dev/tty8
> /dev/tty11  /dev/tty22  /dev/tty33  /dev/tty44  /dev/tty55  /dev/tty9
> /dev/tty12  /dev/tty23  /dev/tty34  /dev/tty45  /dev/tty56  /dev/ttyS0
> /dev/tty13  /dev/tty24  /dev/tty35  /dev/tty46  /dev/tty57  /dev/ttyS1
> /dev/tty14  /dev/tty25  /dev/tty36  /dev/tty47  /dev/tty58  /dev/ttyS2
> /dev/tty15  /dev/tty26  /dev/tty37  /dev/tty48  /dev/tty59  /dev/ttyS3
> /dev/tty16  /dev/tty27  /dev/tty38  /dev/tty49  /dev/tty6
> /dev/tty17  /dev/tty28  /dev/tty39  /dev/tty5   /dev/tty60
> /dev/tty18  /dev/tty29  /dev/tty4   /dev/tty50  /dev/tty61
> 
> Stephan

-- 
kernel concepts GbR      Tel: +49-271-771091-12
Sieghuetter Hauptweg 48  Fax: +49-271-771091-19
D-57072 Siegen           Mob: +49-176-21024535
http://www.kernelconcepts.de

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to