WethaGuy 1 Posted December 9, 2012 Share Posted December 9, 2012 I've followed the cdcacm directions and have the MSP430 working with Energia! Well, I can upload Blinky example anyway. But, I can't get the Stellarpad to work. Upon upload I get "No ICDI device with USB VID:PID 1cbe:00fd found! Failed!" error. Linux Mint 3.2.0-23 kernel, fresh install yesterday Energia latest version downloaded and installed today Any suggestions? Quote Link to post Share on other sites
energia 485 Posted December 10, 2012 Share Posted December 10, 2012 Can you post the output of dmesg? Open up a terminal window. Plug in the LaunchPad and in a terminal window type dmesg. Post the last say 20 lines. Alternatively, you can also post a question on the lm4flash issue page here to see if the maintainers have an idea: https://github.com/utzig/lm4tools/issues?state=open Quote Link to post Share on other sites
udif 1 Posted December 10, 2012 Share Posted December 10, 2012 I had a similar problem - Under Windows 7 on a Thinkpad W510 laptop, lm4flash did not recognized the board when it was plugged into any of the two USB 3.0 sockets, but worked fine on any other USB sockets, including the docking station. The error message is the same as yours - "No ICDI device with USB VID:PID 1cbe:00fd found! Failed!" Try connecting to a different USB port. Quote Link to post Share on other sites
chopc 0 Posted December 10, 2012 Share Posted December 10, 2012 Can you post the output of dmesg? Open up a terminal window. Plug in the LaunchPad and in a terminal window type dmesg. Post the last say 20 lines. Alternatively, you can also post a question on the lm4flash issue page here to see if the maintainers have an idea: https://github.com/utzig/lm4tools/issues?state=open Same problems in Ubuntu 12.02 dmesg results :- [ 134.392399] usb 2-6: USB disconnect, device number 19 [ 146.708025] usb 2-2: new low-speed USB device number 20 using ohci_hcd [ 146.888019] usb 2-2: device descriptor read/64, error -62 [ 147.172024] usb 2-2: device descriptor read/64, error -62 [ 147.452043] usb 2-2: new low-speed USB device number 21 using ohci_hcd [ 147.632021] usb 2-2: device descriptor read/64, error -62 [ 147.916020] usb 2-2: device descriptor read/64, error -62 [ 148.196021] usb 2-2: new low-speed USB device number 22 using ohci_hcd [ 148.604024] usb 2-2: device not accepting address 22, error -62 [ 148.780020] usb 2-2: new low-speed USB device number 23 using ohci_hcd [ 149.188027] usb 2-2: device not accepting address 23, error -62 [ 149.188044] hub 2-0:1.0: unable to enumerate USB device on port 2 [ 149.364017] usb 2-4: new full-speed USB device number 24 using ohci_hcd [ 149.544024] usb 2-4: device descriptor read/64, error -62 [ 149.828042] usb 2-4: device descriptor read/64, error -62 [ 150.108028] usb 2-4: new full-speed USB device number 25 using ohci_hcd [ 150.288024] usb 2-4: device descriptor read/64, error -62 [ 150.576027] usb 2-4: device descriptor read/64, error -62 [ 150.856019] usb 2-4: new full-speed USB device number 26 using ohci_hcd [ 151.264022] usb 2-4: device not accepting address 26, error -62 [ 151.440014] usb 2-4: new full-speed USB device number 27 using ohci_hcd [ 151.848035] usb 2-4: device not accepting address 27, error -62 [ 151.848056] hub 2-0:1.0: unable to enumerate USB device on port 4 [ 152.024038] usb 2-6: new full-speed USB device number 28 using ohci_hcd [ 152.242224] cdc_acm 2-6:1.0: This device cannot do calls on its own. It is not a modem. [ 152.242255] cdc_acm 2-6:1.0: ttyACM0: USB ACM device Quote Link to post Share on other sites
chopc 0 Posted December 10, 2012 Share Posted December 10, 2012 Can you post the output of dmesg? Open up a terminal window. Plug in the LaunchPad and in a terminal window type dmesg. Post the last say 20 lines. Alternatively, you can also post a question on the lm4flash issue page here to see if the maintainers have an idea: https://github.com/utzig/lm4tools/issues?state=open Same problem , dmesg results :- usb 2-6: USB disconnect, device number 19 usb 2-2: new low-speed USB device number 20 using ohci_hcd usb 2-2: device descriptor read/64, error -62 usb 2-2: device descriptor read/64, error -62 usb 2-2: new low-speed USB device number 21 using ohci_hcd usb 2-2: device descriptor read/64, error -62 usb 2-2: device descriptor read/64, error -62 usb 2-2: new low-speed USB device number 22 using ohci_hcd usb 2-2: device not accepting address 22, error -62 usb 2-2: new low-speed USB device number 23 using ohci_hcd usb 2-2: device not accepting address 23, error -62 hub 2-0:1.0: unable to enumerate USB device on port 2 usb 2-4: new full-speed USB device number 24 using ohci_hcd usb 2-4: device descriptor read/64, error -62 usb 2-4: device descriptor read/64, error -62 usb 2-4: new full-speed USB device number 25 using ohci_hcd usb 2-4: device descriptor read/64, error -62 usb 2-4: device descriptor read/64, error -62 usb 2-4: new full-speed USB device number 26 using ohci_hcd usb 2-4: device not accepting address 26, error -62 usb 2-4: new full-speed USB device number 27 using ohci_hcd usb 2-4: device not accepting address 27, error -62 hub 2-0:1.0: unable to enumerate USB device on port 4 usb 2-6: new full-speed USB device number 28 using ohci_hcd cdc_acm 2-6:1.0: This device cannot do calls on its own. It is not a modem. cdc_acm 2-6:1.0: ttyACM0: USB ACM device Hope that helps and gets through complete Energia 9 works with no problems on my XP boxes Quote Link to post Share on other sites
Rickta59 589 Posted December 10, 2012 Share Posted December 10, 2012 > First thing to do is make sure the device is being recognized by the linux kernel. Open a terminal window and try the lsusb command: # lsusb -d 1cbe:00fd Bus 003 Device 022: ID 1cbe:00fd Luminary Micro Inc. the lsusb command is used to list usb devices. If you see an entry for the VID:PID (1cbe:00fd) then your linux kernel has enumerated your device. So that is a good first step > Next, did you setup a udev entry? This changes the permissions on the usb device so non-root users can read and write it. I named my entry /etc/udev/rules.d/61-stellapad.rules: # This file allows non-root access to TI stellaris launchpad # See udev(7) for syntax. # SUBSYSTEM=="usb",ATTRS{idVendor}=="1cbe",ATTRS{idProduct}=="00fd",MODE="0666" # When you add the entry you need to restart udev or just unplug your launchpad, wait, then replug. While you are doing this you can do a 'tail -f /var/log/syslog' ( or multiple dmesg commands ) to see the kernel messages. You should look for any suspicious errors. > Next step is to see if you can use lm4flash. The lm4flash program is in your Energia install directory: $ ls -l energia-0101E0009/hardware/tools/lm4f/bin/lm4flash $ energia-0101E0009/hardware/tools/lm4f/bin/lm4flash /tmp/build4630516746846355870.tmp/Blink_blue.cpp.bin !Success I turned on verbose in the Energia IDE and using a simple blink step I ran the "Verify" aka compile button. It puts the .bin file in a /tmp/buildxxxxx/ directory. You will have to substitute the name used on your compile. If that works you can then try the Energia IDE. It should be working at this point. > Next if steps above didn't work it could be that the libusb I used to compile lm4flash isn't working with your linux. Try downloading compiling lm4flash from source. https://github.com/RickKimball/lm4tools Follow the steps listed there to get a working lm4flash and try it with the /tmp/buildxxx/*.bin file you created. Note: my version is based on an earlier version of lm4flash from https://github.com/utzig/lm4tools Mine is bare bones. You might try that later version if you have problems with mine. If none of the steps there work, then someone else has suggested that you try a different usb port. If that doesn't work, you'll have to explain more about the errors you are seeing. In any case, let us know how it works out for you. This is our first release of the stellarpad Energia, there are bound to be glitches. -rick WethaGuy and bluehash 2 Quote Link to post Share on other sites
Rickta59 589 Posted December 10, 2012 Share Posted December 10, 2012 Same problem , dmesg results :- usb 2-6: USB disconnect, device number 19 usb 2-2: new low-speed USB device number 20 using ohci_hcd usb 2-2: device descriptor read/64, error -62 usb 2-2: device descriptor read/64, error -62 usb 2-2: new low-speed USB device number 21 using ohci_hcd usb 2-2: device descriptor read/64, error -62 usb 2-2: device descriptor read/64, error -62 usb 2-2: new low-speed USB device number 22 using ohci_hcd usb 2-2: device not accepting address 22, error -62 usb 2-2: new low-speed USB device number 23 using ohci_hcd usb 2-2: device not accepting address 23, error -62 hub 2-0:1.0: unable to enumerate USB device on port 2 usb 2-4: new full-speed USB device number 24 using ohci_hcd usb 2-4: device descriptor read/64, error -62 usb 2-4: device descriptor read/64, error -62 usb 2-4: new full-speed USB device number 25 using ohci_hcd usb 2-4: device descriptor read/64, error -62 usb 2-4: device descriptor read/64, error -62 usb 2-4: new full-speed USB device number 26 using ohci_hcd usb 2-4: device not accepting address 26, error -62 usb 2-4: new full-speed USB device number 27 using ohci_hcd usb 2-4: device not accepting address 27, error -62 hub 2-0:1.0: unable to enumerate USB device on port 4 usb 2-6: new full-speed USB device number 28 using ohci_hcd cdc_acm 2-6:1.0: This device cannot do calls on its own. It is not a modem. cdc_acm 2-6:1.0: ttyACM0: USB ACM device Hope that helps and gets through complete Energia 9 works with no problems on my XP boxes Bizzare... I can't see your response unless I respond to it Quote Link to post Share on other sites
Rickta59 589 Posted December 10, 2012 Share Posted December 10, 2012 It doesn't look like the kernel knows what to do with your stellarpad device. This seems like a mint linux question. A quick google search led me to this posting: http://ubuntuforums.org/archive/index.php/t-797789.html Not sure if that will help, seems like you might look around on the mint linux help boards. -rick Quote Link to post Share on other sites
WethaGuy 1 Posted December 11, 2012 Author Share Posted December 11, 2012 ... > Next, did you setup a udev entry? This changes the permissions on the usb device so non-root users can read and write it. I named my entry /etc/udev/rules.d/61-stellapad.rules: # This file allows non-root access to TI stellaris launchpad# See udev(7) for syntax.#SUBSYSTEM=="usb",ATTRS{idVendor}=="1cbe",ATTRS{idProduct}=="00fd",MODE="0666"#When you add the entry you need to restart udev or just unplug your launchpad, wait, then replug. While you are doing this you can do a 'tail -f /var/log/syslog' ( or multiple dmesg commands ) to see the kernel messages. You should look for any suspicious errors.... udev....facepalm After fighting for weeks trying to get CCS+linux+StellarPad working I thought I already had everything installed and configured. Then, I did a fresh install of Mint and didn't go back to the basics. A quick add to the udev rules makes the StellarPad work. THANKS! Both MSP430 and StellarPad are happily blinking RED_LED via Energia! Quote Link to post Share on other sites
WethaGuy 1 Posted December 11, 2012 Author Share Posted December 11, 2012 Mods: Please cross-post or copy this thread to the new Energia forum under Stellarisiti. There's a lot of good info here. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.