Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Do you have actually have " instead of " in your entry? If so change all the &qout; to " and save then unplug and replug the launchpad usb cable. -rick Well that's embarrassing :oops: . I tried to post the udev rules with my first post itself, but did not qualify the new user rules (It seemed as URL to bulletin board software). Thanks Rickta59. And yes it is now working.
  2. udev rule also seems ok to me. Here are the groups I belong to: ab-work@ubuntu:~$ groups ab-work ab-work : ab-work adm dialout cdrom plugdev lpadmin admin sambashare And my /etc/udev/rules.d/46-TI_launchpad.rules udev rule file contents ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f432", MODE="0660", GROUP="plugdev" (source: http://hackaday.com/2010/08/11/how-to-l ... ith-linux/) Am I not in plugdev group? It works with root privileges.
  3. No luck. I tried each and every workaround except upgrading my OS.
  4. Yes. That's the first thing I do when something does not work. It came in me from Window$. Here is my dmesg output after plugging Launchpad. [ 223.840024] usb 2-1: new full speed USB device using uhci_hcd and address 4 [ 224.042191] usb 2-1: configuration #1 chosen from 1 choice [ 224.052089] cdc_acm 2-1:1.0: This device cannot do calls on its own. It is not a modem. [ 224.052095] cdc_acm 2-1:1.0: No union descriptor, testing for castrated device [ 224.052120] cdc_acm 2-1:1.0: ttyACM0: USB ACM device [ 234.101528] /build/buildd/linux-2.6.32/drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed [ 234.101543] generic-usb 0003:0451:F432.0004: timeout initializing reports [ 234.101725] generic-usb 0003:0451:F432.0004: hiddev96,hidraw0: USB HID v1.01 Device [Texas Instruments Texas Instruments MSP-FET430UIF] on usb-0000:00:1d.0-1/input1[/b] Is the failing of usb_sumit_urb(ctrl) normal? I google-d it and found that it is a bug and should upgrade to the latest release. (I'm using Ubuntu 10.04 and don't want to upgrade until 12.04).
  5. You're probably missing the firmware for the TI USB chip. Do you mean that I have to burn the attached firmware to Launchpad using TI firmware update tool?
  6. I did that before but it does not work. Hmm.. Have you tried building the project? In order for Eclipse to correctly identify where the include files are, it needs the project to be build once. Ya I build the project after including the header file. But today it works magically. Any reasons? Also now I cannot upload to Launchpad (MSP430G2231). MSPDebug gives error: Trying to open interface 1 on 009 rf2500: warning: can't detach kernel driver: Operation not permitted rf2500: can't claim interface: Operation not permitted rf2500: failed to open RF2500 device I then added udev rule and restart udev as instructed on hackaday post. And still MSPDebug gives the same error. My Project MSP430 Properties are: Target: msp430g2231 Driver: rf2500 Connection: USB Protocol: SBW dmesg shows Launchpad on ttyACM0.
  7. I did that before but it does not work.
  8. xpg: I thank you for sharing the excellent work you are doing. Keep it up. I installed your plugin and extracted the mspgcc on my Ubuntu box. But some how the code builds but the symbols (ex. WDTCTL) are not resolved by Eclipse (Indigo). I created a new MSP430 cross-toolchain project (selecting the correct target, MSP430G2231 (Launchpad)) and my MSP430 preferences are set to "xpg pre-build toolchain 1.0" Any more configuration needed? I have already build mspgcc, mspdebug etc. on my machine before I saw your plugin. SOLUTION: replace the " with (actual) " in the udev rule (/etc/udev/rules.d/46-TI_launchpad.rules) ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f432", MODE="0660", GROUP="plugdev" to ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f432", MODE="0660", GROUP="plugdev"
  • Create New...