On Sun, Nov 20, 2011 at 11:16:11AM +0100, Stephan Goldenberg wrote: > Am Samstag, den 19.11.2011, 16:57 -0300 schrieb Sergio Campamá: > > Hello, sorry to interrupt, but I have a (maybe) similar problem. I also > > have the 1.4a JTAG programmer, and when I connect it to Ubuntu (11.04), it > > says that the firmware couldn't be downloaded. > > > > The Launchpads I have run perfectly, but the UIF won't even show as > > /dev/ttyUSB0. > > > > The actual output from dmesg is : > > > > [ 4807.964648] usb 2-2.2: new full speed USB device using uhci_hcd and > > address 19 > > [ 4808.360630] ti_usb_3410_5052 2-2.2:2.0: TI USB 3410 1 port adapter > > converter detected > > [ 4809.361512] usb 2-2.2: ti_download_firmware - error downloading > > firmware, -110 > > [ 4809.363834] ti_usb_3410_5052: probe of 2-2.2:2.0 failed with error -5 > > > > When I connect, this appears on screen > > > > usb 2-2.2: ti_download_firmware - error downloading firmware, -110 > > > > > > What could be the reason for this? > > > > Thanks, > > --------------------------------------- > > Sergio Campamá > > sergiocamp...@gmail.com > > The firmware is missing. > > oppa@oppa-mag:~$ locate ti_usb-3410.bin > oppa@oppa-mag:~$ fw-detect > Detected driver that requires firmware to operate > ------------------------------------------------- > > # > # There is no readily available firmware package for ti_usb_3410_5052 > # Visit the following page for information on how to obtain and > # install the required firmware: > # > http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=blob_plain;f=ti_3410.fw;hb=HEAD > > http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=blob;f=ti_5052.fw;hb=HEAD > > # > # Once the firmware files have been installed, the ti_usb_3410_5052 > # must be reloaded to activate the hardware. > # Use the following commands: > # > modprobe -r ti_usb_3410_5052 > modprobe ti_usb_3410_5052 > > There was no information to be found but it gave me ti_3410.fw and > ti_5052.fw. I've moved them to /lib/firmware aaand: > > [ 5579.358061] usb 4-2: new full speed USB device number 4 using > ohci_hcd > [ 5579.603102] usb 4-2: New USB device found, idVendor=0451, > idProduct=f430 > [ 5579.603111] usb 4-2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 5579.603118] usb 4-2: Product: MSP-FET430UIF JTAG Tool > [ 5579.603124] usb 4-2: Manufacturer: Texas Instruments > [ 5579.603129] usb 4-2: SerialNumber: TUSB3410A8FF42C59D892D3F > [ 5579.606245] ti_usb_3410_5052 4-2:1.0: TI USB 3410 1 port adapter > converter detected > [ 5579.606296] ti_usb_3410_5052: probe of 4-2:1.0 failed with error -5 > [ 5579.610249] ti_usb_3410_5052 4-2:2.0: TI USB 3410 1 port adapter > converter detected > [ 5579.610547] usb 4-2: TI USB 3410 1 port adapter converter now > attached to ttyUSB0 > > root@oppa-mag:/home/oppa# /usr/bin/mspdebug uif -j -d /dev/ttyUSB0 > 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... > Initializing FET... > FET protocol version is 20408002 > Configured for JTAG (2) > Set Vcc: 3000 mV > Device ID: 0xf149 > Device: MSP430F149 > Code memory starts at 0x1100 > Number of breakpoints: 3 > --help snipped > > (mspdebug) dis 0x1100 > 0x1100: > 01100: 31 40 00 0a MOV #0x0a00, SP > 01104: b0 12 0c 11 CALL #0x110c > 01108: b0 12 ac 11 CALL #0x11ac > 0110c: b2 40 80 5a 20 01 MOV #0x5a80, &0x0120 > 01112: f2 d0 f0 00 36 00 BIS.B #0x00f0, &0x0036 > 01118: f2 40 f0 00 35 00 MOV.B #0x00f0, &0x0035 > 0111e: f2 c0 80 00 35 00 BIC.B #0x0080, &0x0035 > 01124: b0 12 9a 11 CALL #0x119a > 01128: f2 c0 40 00 35 00 BIC.B #0x0040, &0x0035 > 0112e: f2 d0 80 00 35 00 BIS.B #0x0080, &0x0035 > 01134: b0 12 9a 11 CALL #0x119a > 01138: f2 c0 20 00 35 00 BIC.B #0x0020, &0x0035 > 0113e: f2 d0 > > looking good but then: > > (mspdebug) run > uif: read error: Connection timed out > warning: device: can't fetch registers > uif: read error: Connection timed out > fet: failed to refresh breakpoint #0 > uif: read error: Connection timed out > fet: failed to refresh breakpoint #1 > uif: read error: Connection timed out > fet: failed to refresh breakpoint #2 > warning: fet: failed to refresh breakpoints > uif: read error: Connection timed out > fet: failed to restart CPU > run: failed to start CPU > (mspdebug)
Hi Stephan, Sorry for the late reply (have been moving house). I see Sergio now has his board working -- are you still having trouble with yours? Are you also running within VMware? Cheers, Daniel -- D.L. Beer Engineering www.dlbeer.co.nz ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
