Jump to content

Rock

Members
  • Content Count

    5
  • Joined

  • Last visited

  1. Thanks. I figured out the problem, although, I went down so many ratholes that I left unfilled that the final solution 'could' be a combination of all the things already outlined. However, the straw that lightned the camel's load was simply to put the user in the "tty" group. So, adding to the log file, we finally have this painfully-obvious? (in glaring hindsight?) solution: x. Googling far and wide, this Arduino page hints something about having the user in the "tty" group: http://playground.arduino.cc/Learning/Linux So, on a whim, I added my username to the "tty" group & rebooted. $ groups REPORTS: user1 tty uucp dialout lock BINGO! This worked! The serial port is no longer grayed out! [energia]Tools->Serial Port->[x]/dev/ttyACM0 It's strange, because I 'thought' the USB acted as a serial port on /dev/ttyACM0, but, a quick "ls -l" shows ttyACM0 owned by "dialout". $ ls -l /dev ... stuff ... crw--w----. 1 root tty 4, 7 Apr 4 19:53 tty7 crw--w----. 1 root tty 4, 8 Apr 4 19:53 tty8 crw--w----. 1 root tty 4, 9 Apr 4 19:53 tty9 crw-rw----. 1 root dialout 166, 0 Apr 4 19:53 ttyACM0 <===== note that it's not "tty"! crw-rw----. 1 root dialout 4, 64 Apr 4 19:53 ttyS0 crw-rw----. 1 root dialout 4, 65 Apr 4 19:53 ttyS1 crw-rw----. 1 root dialout 4, 66 Apr 4 19:53 ttyS2 crw-rw----. 1 root dialout 4, 67 Apr 4 19:53 ttyS3 ... stuff ... x. I still see warnings when I run the (modified or not) "energia" shell script. $ ./energia WARNING: RXTX Version mismatch Jar version = RXTX-2.2 http://PixelInvaders.ch low latency edition native lib Version = RXTX-2.1-7 But, at least everything is working. In summary: a) The Linux (Centos?) instructions should make it clear WHY one needs to be in the "tty" group (as /dev/ttyACM0 is in "dialout") The Linux (Centos?) instructions should make it clear how to handle rxts; specifically, WHERE should the 64-bit rxtx be obtained from (i.e., either the Centos EPEL repository or elsewhere)
  2. If it helps, here is the detailed log of what I've tried, so far: ---------------------------------------------------------------------------- Summarized, here is what I've tried so far: I determined that I'm on 64-bit X86 Centos 6. I checked to see if the libusb drivers are installed. I checked to see what version of Java is installed. I checked to see how Java is configured. I downloaded the Energia Linux binary tarball (energia-0101E0009-linux.tgz) I untarred the Energia tarball to create an energia-0101E0009 directory. I ran the energia application. I set the board to msp430g2553 (16MHz). I failed at selecting the serial port because the selection was grayed out. I ran the default "Blink" procedure, which caused the board LEDs to blink. I modified the "Blink" procedure, and tested that it was working. I tried to open the Energia Serial Monitor - but failed. Googling for how to solve this problem, I added a udev file & rebooted. Googling further, I added user1 to the various groups and rebooted. Googling further, I obtained & compiled (& presumably installed) librxtx-master. That apparently didn't work (as there was no resultant /usr/lib64/rxtx). I installed Centos 6 rxtx from EPEL (which was always there all along). And, I modified the last line of the shell script that calls energia. Unfortunately, the serial port is still grayed out. Note: I still have an rxtx version-mismatch warning ... ---------------------------------------------------------------------------- How I installed Energia for the TI Launchpad MSP430 on Centos 6 ---------------------------------------------------------------------------- x. I determined the Centos version: $ uname -a REPORTED: Linux laptop 2.6.32-279.19.1.el6.x86_64 ... x86_64 x86_64 x86_64 GNU/Linux x. On Centos, I checked to see if the libusb drivers were installed: $ sudo yum install libusb REPORTED: Package libusb-0.1.12-23.el6.x86_64 already installed and latest version x. On Centos, I checked to see what version of Java was installed: $ java -version REPORTED: java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.5) (rhel-1.50.1.11.5.el6_3-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) x. On Centos, I checked to see how Java was configured: $ sudo update-alternatives --config java REPORTED: There are 2 programs which provide 'java'. Selection Command ----------------------------------------------- 1 /usr/lib/jvm/jre-1.5.0-gcj/bin/java *+ 2 /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java x. Optionally, I registered an account for support at http://forum.43oh.com Note: You'll need the answer to the registration question: Q: Which microcontroller is this forum based on? A: MSP430 Note: Your email account will be verified by sending you an email, which, when you click on a link inside, will activate your forum account. x. I downloaded the Energia Linux binary tarball (energia-0101E0009-linux.tgz) http://energia.nu/download: Note: Strangely, there are no Linux-specific instructions at that web page. x. I untarred the Energia tarball to create an energia-0101E0009 directory: $ tar xvf energia-0101E0009-linux.tgz x. I ran the energia application: $ cd ./energia-0101E0009 $ ./energia REPORTED: Experimental: JNI_OnLoad called. WARNING: RXTX Version mismatch Jar version = RXTX-2.2 http://PixelInvaders.ch low latency edition native lib Version = RXTX-2.1-7 x. I set the Energia board settings to point to the msp430g2553 (16MHz): [energia]Tools->Board->(o)Launchpad with msp430g2553 (16MHz) Note: At the bottom of the Energia application, the GUI reported: "1 LaunchPad w/ msp430g2553 (16MHz) on COM1" x. I failed at selecting the serial port because the selection was grayed out: [energia]Tools->Board->(o)Launchpad with msp430g2553 (16MHz) x. I ran the default "Blink" procedure, which caused the board LEDs to blink: [energia]File->Examples->1.Basics->Blink [energia]File->Upload REPORTED: /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/as) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-ar) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld) /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-objcopy: /lib/libz.so.1: no version information available (required by /tmp/energia/g-0101E0009/hardware/tools/msp430/bin/msp430-objcopy) Couldnt determine program size: {0} Trying to open interface 1 on 004 rf2500: warning: can't detach kernel driver: No data available Device: MSP430G2553/G2403 Erasing... Programming... Done, 590 bytes total x. I modified the "Blink" procedure, and tested that it was working: [energia]Control + F-> (change all instances of RED to GREEN) [energia]File->Upload x. I tried to open the Energia Serial Monitor - but failed: [energia]Tools->Serial Monitor REPORTED: processing.app.SerialNotFoundException: Serial port 'COM1' not found. Did you select the right one from the Tools > Serial Port menu? at processing.app.Serial.<init>(Serial.java:165) at processing.app.Serial.<init>(Serial.java:92) at processing.app.SerialMonitor.openSerialPort(SerialMonitor.java:207) at processing.app.Editor.handleSerial(Editor.java:2477) at processing.app.Editor$17.actionPerformed(Editor.java:669) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2012) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2335) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:404) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259) at javax.swing.AbstractButton.doClick(AbstractButton.java:374) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:829) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:873) at java.awt.Component.processMouseEvent(Component.java:6389) at javax.swing.JComponent.processMouseEvent(JComponent.java:3268) at java.awt.Component.processEvent(Component.java:6154) at java.awt.Container.processEvent(Container.java:2045) at java.awt.Component.dispatchEventImpl(Component.java:4750) at java.awt.Container.dispatchEventImpl(Container.java:2103) at java.awt.Component.dispatchEvent(Component.java:4576) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4633) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4297) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4227) at java.awt.Container.dispatchEventImpl(Container.java:2089) at java.awt.Window.dispatchEventImpl(Window.java:2518) at java.awt.Component.dispatchEvent(Component.java:4576) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:672) at java.awt.EventQueue.access$400(EventQueue.java:96) at java.awt.EventQueue$2.run(EventQueue.java:631) at java.awt.EventQueue$2.run(EventQueue.java:629) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105) at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116) at java.awt.EventQueue$3.run(EventQueue.java:645) at java.awt.EventQueue$3.run(EventQueue.java:643) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105) at java.awt.EventQueue.dispatchEvent(EventQueue.java:642) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177) at java.awt.EventDispatchThread.run(EventDispatchThread.java:138) x. Googling for how to solve this problem, I added a file for udev & rebooted: $ sudo cd /etc/udev/rules.d/. $ sudo vi 46-TI_launchpad.rules I added the following line (which is the only line of the file): ATTRS{idVendor}=="0451", ATTRS{idProduct}=="f432", MODE="0660", GROUP="dialout" Note: This doesn't seem to have made any difference; the serial port was still grayed out in Energia. x. Googling further, I added user1 to the various groups and rebooted: $ sudo vi /etc/group I CHANGED IT FROM: uucp:x:14:uucp lock:x:54: dialout:x:18: I CHANGED IT TO: uucp:x:14:uucp,user1,root lock:x:54:user1,root dialout:x:18:user1,root Note: This doesn't seem to have made any difference; the serial port was still grayed out in Energia. x. Googling further, I obtained librxtx-master and tried to compile: $ cd librxtx-master/. $ make $ sudo make install Note: This doesn't seem to have made any difference; the serial port was still grayed out in Energia. But then I realized maybe I should be using the Centos 6 version of rxtx, so, I located and installed that as follows: $ yum --noplugins --showduplicates --enablerepo \* --disablerepo \ c6-media,\*-source,\*debug\* provides "*/rxtx" $ sudo yum --enablerepo epel install rxtx Which created the /usr/lib64/rxtx directory of shared object modules. Note: This doesn't seem to have made any difference; the serial port was still grayed out in Energia. x. Googling, I found this blurb about rxtx: http://playground.arduino.cc/Learning/Linux So I changed the energia script last line FROM: java -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel processing.app.Base TO: java -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel -Dgnu.io.rxtx.SerialPorts=/dev/ttyACM0 -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel processing.app.Base "$@[member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""][member=""]" Note: This doesn't seem to have made any difference; the serial port was still grayed out in Energia. x. Note: I still also see warnings when I run the (modified or not) "energia" shell script. $ ./energia WARNING: RXTX Version mismatch Jar version = RXTX-2.2 http://PixelInvaders.ch low latency edition native lib Version = RXTX-2.1-7
  3. QUESTION: Any pointers as to why the Serial Port is grayed out on 64-bit Centos 6? In the next post, is my detailed installation log (with errors) - but here is a quick summary: I determined that I'm on 64-bit X86 Centos 6. I checked to see if the libusb drivers are installed. I checked to see what version of Java is installed. I checked to see how Java is configured. I downloaded the Energia Linux binary tarball (energia-0101E0009-linux.tgz) I untarred the Energia tarball to create an energia-0101E0009 directory. I ran the energia application. I set the board to msp430g2553 (16MHz) I failed at selecting the serial port because the selection was grayed out. I ran the default "Blink" procedure, which caused the board LEDs to blink. I modified the "Blink" procedure, and tested that it was working. I tried to open the Energia Serial Monitor - but failed. Googling for how to solve this problem, I added a udev file & rebooted. Googling further, I added user1 to the various groups and rebooted. Googling further, I obtained and compiled librxtx-master. I installed the EPEL rxtx using "sudo yum install rxtx". Yet, the serial port is still grayed out! Q: How do I diagnose WHY the MSP430 serial port is grayed out? Note: Searching this forum came up with this - but it doesn't seem to apply as it's on Windows: - serial port grayed out in IDE ver E0009
  4. Thanks. I'm reading the pinned threads as we speak! And, my first question has now been solved (for the most part): - Energia serial port grayed out on Centos 6 for msp430g2553 Now we need to figure out how to update the installation instructions so all other Linux users who follow in my footsteps don't have the same 5-hour debugging procedure to chase down something that a single sentence in the instructions would have prevented! In summary: a) The Linux (Centos?) instructions should make it clear WHY one needs to be in the "tty" group (as /dev/ttyACM0 is in "dialout") The Linux (Centos?) instructions should make it clear how to handle rxts; specifically, WHERE should the 64-bit rxtx be obtained from (i.e., either the Centos EPEL repository or elsewhere)
  5. A friend, knowing that I'm interested in microcontrollers, gave me an Energia tarball along with the TI Launchpad MSP-EXP430G2 to play with on my Centos 6 laptop. At the moment, I'm executing the sample programs but the serial port is grayed out and therefore not installing correctly - so - looking for help - I first looked for an nntp USENET newsgroup - but, not having found one, I found this nice forum site instead. This seems to be the place to ask questions (this post is NOT a question!). So, in summary, looking for help is why I created this account - but that's not the purpose of this thread - which is simply to introduce myself. Hi, I'm brand new to both Linux and to the TI Launchpad - but I'm sure happy to try Energia out on Centos 6 with the MSP-EXP430G2. I'm usually a good forum citizen, posting detailed threads, with good titles and taking care to punctuate and spell properly (Am. English) - and most importantly - I generally take the time to include a picture and to update my results - and - when I get good enough - to edify others by writing DIYs and HOWTOs so that they don't have the same problems that I've had. I'm all for "paying it forward" and for "standing on others' shoulders" to improve the steps so that the NEXT person has an easier time doing the same task. That makes me worth spending effort on (i.e., investing in me), and, to pay you back, I will invest in the next user (when and if I can, of course). But, that's for later - as I don't know ANYTHING about Energia and the Launchpad just yet - since both were just handed gratis to me today. I do realize that, being on Centos, I'm probably in the minority, so, over time, I hope we can help other Centos users have the same experience with Energia on the MSP-EXP430G2 as Ubuntu users would. Here's a picture of my current setup:
×
×
  • Create New...