• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 81 subscribers
  • Views 3510 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.

Debugging MSP430 in Linux

FAB63476
Intellectual 530 points
Other Parts Discussed in Thread: ENERGIA, MSP430G2553

Hi! I am new using linux and I wanted to debug the MSP430 with the GCC I have downloaded from TI.

I used the stand alone GCC package.

I tried to follow the instructions in slau591a.pdf but I am getting stucked with it.


First, I want to use the terminal in order to compile and enter into a debug session.

Then I followed the instructions

I executed the gdb agent console as in 4.5.3.1

./bin/gdb_agent_console msp430.dat

Then (4.5.3.2.1)

make debug
target remote :55000

And the gdb agent quits with:

Couldn't find any connected USB FETs!
Failed to initialize FET on TIUSB port. Aborting.
   MSP430 Error :Could not find MSP-FET430UIF on specified COM port
Connection failed...exiting

I tried to use the MSP430EXPG2 (because I compiled an example for it).

I follower the troubleshooting within the document, but the result is the same

All the help that I can find in internet is based on mspdebug but not using the agent. I don't know what to do.
 

  • 0
    Expert 1400 points

    I have a written a pretty comprehensive guide for using gcc and debugging in Linux on my site: simplyembdded.org. Mostly in lessons 2 and 3, but there is a separate post http://www.simplyembedded.org/category/debugging/ 

  • 0
    Prodigy 230 points

    HI, I got the same problem !

    After "target remote :55000", I got the following message.

    Couldn't find any connected USB FETs!
    Failed to initialize FET on TIUSB port. Aborting.
       MSP430 Error :Could not find MSP-FET430UIF on specified COM port
    Connection failed...exiting

    I tried 4 different launchPads, with the same result, here is the kernel message.

    Kernel driver(dmesg)
    [ 4223.840398] usb 2-2: new full-speed USB device number 7 using ohci-pci

    [ 4224.124942] usb 2-2: New USB device found, idVendor=0451, idProduct=f432

    [ 4224.124958] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

    [ 4224.124968] usb 2-2: Product: Texas Instruments MSP-FET430UIF

    [ 4224.124977] usb 2-2: Manufacturer: Texas Instruments

    [ 4224.124986] usb 2-2: SerialNumber: 90FF42A21E965041

    [ 4224.134034] cdc_acm 2-2:1.0: This device cannot do calls on its own. It is not a modem.

    [ 4224.134610] cdc_acm 2-2:1.0: No union descriptor, testing for castrated device

    [ 4224.134645] cdc_acm 2-2:1.0: ttyACM0: USB ACM device

    [ 4234.232453] hid-generic 0003:0451:F432.0006: usb_submit_urb(ctrl) failed: -1

    [ 4234.234295] hid-generic 0003:0451:F432.0006: timeout initializing reports

    [ 4234.235224] hid-generic 0003:0451:F432.0006: hiddev0,hidraw1: USB HID v1.01 Device [Texas Instruments Texas Instruments MSP-FET430UIF] on usb-0000:00:06.0-2/input1



    Please help !!

    Thank you in advance.

  • 0 in reply to leo devel
    Expert 1400 points

    I just checked and I get exactly the same output from dmesg - but I am able to connect using mspdebug. Have you tried connecting with mspdebug? Also can you check with netstat or nmap to make sure the process has opened the port you are expecting. 

  • 0 in reply to Chris Karaplis
    Guru 11940 points

    I just checked and I get exactly the same output from dmesg - but I am able to connect using mspdebug.

    Try as root.

    If that works, enable the required permissions for your "user", most probably by adding an appropriate file in /etc/udev/rules.d .

  • 0 in reply to f. m.
    Prodigy 20 points
    I'm getting this problem also, (dmesg output matches the others who are experiencing this) even after adjusting perms. I've changed the line in msp430.dat from "msp430_port=TIUSB" to "msp430_port=ttyACM0", still no luck. Tried running the gdb_agent and "make debug" both as root, with no luck. Is this likely a firmware issue, as some have stated elsewhere (eg: Energia forum)?
  • 0 in reply to Joshua Manning
    Guru 11940 points

    Sounds like there is some other issue.

    I don't use the MSP430 (and any associated toolchain), but the LM4C and other Cortex M - mainly under Linux. And the user right issue is usually the main stumbling block...

  • 0 in reply to f. m.
    Prodigy 20 points
    Well, despite having the same issues connecting the debugger to the board, I just realized that debugging on the G2 Launchpad is not supported in Linux (at least for CCS6). Not sure if that carries over to the msp430-gcc toolchain, or not, as I can't seem to find a list of supported devices.

    The toolchain does contain an "blink.c" example for a MSP430G2553 (note that I'm using a G2231, so I've modified the example Makefile). My next step is to try using CCS6 from a Windows machine (which I don't have at my immediate disposal) in order to update the FET firmware.

**Attention** This is a public forum