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 ?

Regards,
Stephan



------------------------------------------------------------------------------
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