• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 1433 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.

Problem debugging using the MSP-FET430UIF

Randy Yates
Expert 1940 points

FORUM MANAGER: Please do not move this thread to the MSP430 forum. This is not an MSP430 problem - it is a CCS problem and the CCS developers need to take responsibility for it and fix it.

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

I have installed CCS 5.4.0.00091 for linux,

Linux localhost.localdomain 3.9.4-200.fc18.x86_64 #1 SMP Fri May 24 20:10:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

about a week ago. I am now trying to get a debug session to connect to an MSP430-EXP5438 Experimenter's Board via a brand new MSP-FET430UIF debugger.

In all cases, lsusb reports that the MSP-FET430UIF has been recognized:

Bus 001 Device 020: ID 2047:0010 Texas Instruments

The first time I tried, I got "msp430: error initializing emulator: no usb fet was found." I found on-line where the initial firmware version in the msp430uif does not work with linux, so i connected to the device with the SmartRF flash programmer tool. That tool reported that the uif firmware was out-of-date and i updated it.

Then i tried again with linux but now am getting:

MSP430: Error initializing emulator: Could not set device Vcc

The MSP430-EXP5438 board powers on (from the battery) just fine and the preprogrammed application runs perfectly.

I'm also including some output from dmesg that looks relevent. Any help would be appreciated.

The CCS GUI seems to run great - starts up fine, license server is working, etc. However, the drivers required for debugging are part of CCS and need to be tested by the CCS team.

--Randy

[138186.053798] usb 1-5.3: new full-speed USB device number 12 using ehci-pci
[138186.151493] usb 1-5.3: New USB device found, idVendor=0451, idProduct=f430
[138186.151504] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[138186.151512] usb 1-5.3: Product: MSP-FET430UIF JTAG Tool
[138186.151518] usb 1-5.3: Manufacturer: Texas Instruments
[138186.151523] usb 1-5.3: SerialNumber: TUSB34102B0617BE1B4AFF71
[138186.288032] usbcore: registered new interface driver ti_usb_3410_5052
[138186.288073] usbserial: USB Serial support registered for TI USB 3410 1 port adapter
[138186.288103] usbserial: USB Serial support registered for TI USB 5052 2 port adapter
[138186.288143] ti_usb_3410_5052 1-5.3:1.0: TI USB 3410 1 port adapter converter detected
[138186.864306] usb 1-5.3: reset full-speed USB device number 12 using ehci-pci
[138186.948227] usb 1-5.3: device firmware changed
[138186.948490] ti_usb_3410_5052: probe of 1-5.3:1.0 failed with error -5
[138186.949218] usb 1-5.3: USB disconnect, device number 12
[138187.015377] usb 1-5.3: new full-speed USB device number 13 using ehci-pci
[138187.138827] usb 1-5.3: New USB device found, idVendor=0451, idProduct=f430
[138187.138839] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[138187.138846] usb 1-5.3: Product: MSP-FET430UIF JTAG Tool
[138187.138852] usb 1-5.3: Manufacturer: Texas Instruments
[138187.138857] usb 1-5.3: SerialNumber: TUSB34102B0617BE1B4AFF71
[138187.140183] ti_usb_3410_5052 1-5.3:1.0: TI USB 3410 1 port adapter converter detected
[138187.140215] ti_usb_3410_5052: probe of 1-5.3:1.0 failed with error -5
[138187.141959] ti_usb_3410_5052 1-5.3:2.0: TI USB 3410 1 port adapter converter detected
[138187.142223] usb 1-5.3: TI USB 3410 1 port adapter converter now attached to ttyUSB1
[149046.893520] ti_usb_3410_5052_1 ttyUSB1: TI USB 3410 1 port adapter converter now disconnected from ttyUSB1
[149046.893563] ti_usb_3410_5052 1-5.3:2.0: device disconnected
[149073.214360] ti_usb_3410_5052 1-5.3:1.0: TI USB 3410 1 port adapter converter detected
[149073.214408] ti_usb_3410_5052: probe of 1-5.3:1.0 failed with error -5
[149073.216805] ti_usb_3410_5052 1-5.3:2.0: TI USB 3410 1 port adapter converter detected
[149073.217014] usb 1-5.3: TI USB 3410 1 port adapter converter now attached to ttyUSB1
[149073.218120] ti_usb_3410_5052_1 ttyUSB1: TI USB 3410 1 port adapter converter now disconnected from ttyUSB1
[149073.218158] ti_usb_3410_5052 1-5.3:2.0: device disconnected
[149144.427168] usb 1-5.3: USB disconnect, device number 13
[149158.878953] usb 1-5.3: new full-speed USB device number 14 using ehci-pci
[149158.992777] usb 1-5.3: New USB device found, idVendor=2047, idProduct=0010
[149158.992788] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[149158.992795] usb 1-5.3: Product: Texas Instruments MSP430-JTAG
[149158.992800] usb 1-5.3: Manufacturer: Texas Instruments
[149158.992805] usb 1-5.3: SerialNumber: 71FF4A1BBE17062B
[149159.174628] cdc_acm 1-5.3:1.0: This device cannot do calls on its own. It is not a modem.
[149159.174705] cdc_acm 1-5.3:1.0: ttyACM0: USB ACM device
[149159.176693] usbcore: registered new interface driver cdc_acm
[149159.176701] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[149159.794747] usb 1-5.3: USB disconnect, device number 14
[149161.380501] usb 1-5.3: new full-speed USB device number 15 using ehci-pci
[149161.484571] usb 1-5.3: New USB device found, idVendor=2047, idProduct=0010
[149161.484582] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[149161.484589] usb 1-5.3: Product: Texas Instruments MSP430-JTAG
[149161.484595] usb 1-5.3: Manufacturer: Texas Instruments
[149161.484600] usb 1-5.3: SerialNumber: 71FF4A1BBE17062B
[149161.486328] cdc_acm 1-5.3:1.0: This device cannot do calls on its own. It is not a modem.
[149161.486371] cdc_acm 1-5.3:1.0: ttyACM0: USB ACM device
[149210.762263] usb 1-5.3: USB disconnect, device number 15
[149222.207915] usb 1-5.3: new full-speed USB device number 16 using ehci-pci
[149222.312314] usb 1-5.3: New USB device found, idVendor=2047, idProduct=0010
[149222.312325] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[149222.312333] usb 1-5.3: Product: Texas Instruments MSP430-JTAG
[149222.312339] usb 1-5.3: Manufacturer: Texas Instruments
[149222.312344] usb 1-5.3: SerialNumber: 71FF4A1BBE17062B
[149222.314077] cdc_acm 1-5.3:1.0: This device cannot do calls on its own. It is not a modem.
[149222.314119] cdc_acm 1-5.3:1.0: ttyACM0: USB ACM device
[149863.100307] usb 1-5.3: USB disconnect, device number 16
[149871.829288] usb 1-5.3: new full-speed USB device number 17 using ehci-pci
[149871.932986] usb 1-5.3: New USB device found, idVendor=2047, idProduct=0010
[149871.932997] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[149871.933005] usb 1-5.3: Product: Texas Instruments MSP430-JTAG
[149871.933011] usb 1-5.3: Manufacturer: Texas Instruments
[149871.933016] usb 1-5.3: SerialNumber: 71FF4A1BBE17062B
[149871.934729] cdc_acm 1-5.3:1.0: This device cannot do calls on its own. It is not a modem.
[149871.934769] cdc_acm 1-5.3:1.0: ttyACM0: USB ACM device
[149883.846032] usb 1-5.3: USB disconnect, device number 17
[149889.963159] usb 1-5.3: new full-speed USB device number 18 using ehci-pci
[149890.067345] usb 1-5.3: New USB device found, idVendor=2047, idProduct=0010
[149890.067357] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[149890.067364] usb 1-5.3: Product: Texas Instruments MSP430-JTAG
[149890.067370] usb 1-5.3: Manufacturer: Texas Instruments
[149890.067375] usb 1-5.3: SerialNumber: 71FF4A1BBE17062B
[149890.069178] cdc_acm 1-5.3:1.0: This device cannot do calls on its own. It is not a modem.
[149890.069219] cdc_acm 1-5.3:1.0: ttyACM0: USB ACM device
[149899.469104] usb 1-5.3: USB disconnect, device number 18
[149906.976379] usb 1-5.3: new full-speed USB device number 19 using ehci-pci
[149907.080305] usb 1-5.3: New USB device found, idVendor=2047, idProduct=0010
[149907.080317] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[149907.080325] usb 1-5.3: Product: Texas Instruments MSP430-JTAG
[149907.080330] usb 1-5.3: Manufacturer: Texas Instruments
[149907.080335] usb 1-5.3: SerialNumber: 71FF4A1BBE17062B
[149907.082126] cdc_acm 1-5.3:1.0: This device cannot do calls on its own. It is not a modem.
[149907.082172] cdc_acm 1-5.3:1.0: ttyACM0: USB ACM device
[149912.531227] usb 1-5.3: USB disconnect, device number 19
[149922.734769] usb 1-5.3: new full-speed USB device number 20 using ehci-pci
[149922.838953] usb 1-5.3: New USB device found, idVendor=2047, idProduct=0010
[149922.838965] usb 1-5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[149922.838973] usb 1-5.3: Product: Texas Instruments MSP430-JTAG
[149922.838978] usb 1-5.3: Manufacturer: Texas Instruments
[149922.838983] usb 1-5.3: SerialNumber: 71FF4A1BBE17062B
[149922.840994] cdc_acm 1-5.3:1.0: This device cannot do calls on its own. It is not a modem.
[149922.841043] cdc_acm 1-5.3:1.0: ttyACM0: USB ACM devicePS:

  • 0
    Expert 1940 points

    OK, I got it to work.Here's what I had to do:

    1. First of all note my development environment: my main OS is F18 as shown above. I also have WinXP installed as a VM using VirtualBox.

    2. I already had the SmartRF Flash Programmer installed under my WinXP VM, so I redirected the USB device to the VM and fired up the SmartRF Flash Programmer. It reported that I had an old version of firmware in the MSP-FET430UIF, and it prompted me to update the program, which I did.

    3. I then disconnected the USB device from the WinXP VM so that linux had control of the device, and tried starting a CCS/linux debug session. Again it failed.

    4. I repeated step 2, that is, I reflashed the MSP-FET430UIF again.

    5. I then disconnected the USB device from the WinXP VM so that linux had control of the device once again and tried starting a CCS/linux debug session. Again it failed, but this time it informed me that the MSP-FET430UIF needed upgrading and requested I allow it to be upgraded. I allowed the upgrade.

    6. When I tried a CCS/linux debug session a 3rd time, it then worked.

    I shouldn't have had to go through these hoops to get production-quality software running. I hope this helps the TI CCS development team fix their issues.

    --Randy

  • 0 in reply to Randy Yates
    TI__Guru*** 130875 points

    HI Randy,

    very happy to hear and thanks for both the update and tips that got you up and running.  

    Appologies there was not a response from our side in between but I was trying to coordinate this between development teams for assistance for you.  Note the msp dll and tools are actually all from and supported by the msp team.

    At any rate, great to hear and all the best.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 1940 points

    Thanks for that, Lisa. I am running under linux, so there is no msp "dll".

    It seems the problem is in the linux device driver for the 2047:0010 device in that the check for the existing firmware version in the MSP-FET430UIF is not working properly. If you would give me access to the relevent information, I would be willing to fix it for a nominal fee.Otherwise it should be  a simple fix for your people.

    --Randy

    PS: I think I met you - I was working with Susan Yim there at the Forest Dr facility?

  • 0 in reply to Randy Yates
    TI__Guru*** 130875 points

    Hi Randy,

    I am actually not US based ... but anyhow ... it is the msp430 team you need.  And thanks for flagging this.  Again .. the tools and device support behind the sceens comes from them.

    Cheers,
    Lisa