Jump to content

Search the Community

Showing results for tags 'linux'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • Announcements
    • Suggestions
    • New users say Hi!
  • Spotlight!
    • Sponsor Spotlight
    • Sponsor Giveaways
  • Energia
    • Energia - MSP
    • Energia - TivaC/CC3XXX
    • Energia - C2000
    • Energia Libraries
  • MSP Technical Forums
    • General
    • Compilers and IDEs
    • Development Kits
    • Programmers and Debuggers
    • Code vault
    • Projects
    • Booster Packs
    • Energia
  • Tiva-C, Hercules, CCXXXX ARM Technical Forums
    • General
    • SensorTag
    • Tiva-C, Hercules, CC3XXX Launchpad Booster Packs
    • Code Vault
    • Projects
    • Compilers and IDEs
    • Development Kits and Custom Boards
  • Beagle ARM Cortex A8 Technical Forums
    • General
    • Code Snippets and Scripts
    • Cases, Capes and Plugin Boards
    • Projects
  • General Electronics Forum
    • General Electronics
    • Other Microcontrollers
  • Connect
    • Embedded Systems/Test Equipment Deals
    • Buy, Trade and Sell
    • The 43oh Store
    • Community Projects
    • Fireside Chat
  • C2000 Technical Forums
    • General
    • Development Kits
    • Code Vault
    • Projects
    • BoosterPacks


There are no results to display.

Found 17 results

  1. I am running an older version of Linux (CentOS 6, glibc 2.12) and the x86_64 gcc cross compilers used by energia were built on a Linux system with glibc 2.14. Where can I get a version built with an older version of glibc or alternitively, a source tree that I can build myself?
  2. I'm trying to bring up a CLI/Makefile based toolset under Ubuntu. Ubuntu version 17.04 MSPDebug version 0.24 My two Launchpads are both MSP-EXP430G2, Rev1.5, and are about three years old. One has a 2553 chip and the other is a 2452. Result of 'mspdebug --usb-list' includes: Devices on bus 001: 001:010 0451:f432 eZ430-RF2500 [serial: FEFF467AF9CB2548] Running mspdebug gives: randy@corvette: mspdebug/0.24$ ./mspdebug -U '001:010' rf2500 MSPDebug version 0.24 - debugging tool for MSP430 MCUs Copyright (C) 2009-2016 Daniel Beer <dlbeer@gmail.com> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. Trying to open interface 1 on 010 rf2500: warning: can't detach kernel driver: No data available Initializing FET... rf2500: can't send data: Resource temporarily unavailable fet: open failed Trying again... Initializing FET... rf2500: can't send data: Resource temporarily unavailable fet: open failed After I plug the Launchpad into USB, dmesg shows: [80373.763698] usb 1-9.3: USB disconnect, device number 10 [80387.054044] usb 1-9.3: new full-speed USB device number 11 using xhci_hcd [80387.363746] usb 1-9.3: New USB device found, idVendor=0451, idProduct=f432 [80387.363749] usb 1-9.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [80387.363751] usb 1-9.3: Product: Texas Instruments MSP-FET430UIF [80387.363752] usb 1-9.3: Manufacturer: Texas Instruments [80387.363753] usb 1-9.3: SerialNumber: FEFF467AF9CB2548 [80387.389816] cdc_acm 1-9.3:1.0: No union descriptor, testing for castrated device [80387.389829] cdc_acm 1-9.3:1.0: ttyACM0: USB ACM device [80397.690445] hid-generic 0003:0451:F432.000A: usb_submit_urb(ctrl) failed: -1 [80397.690462] hid-generic 0003:0451:F432.000A: timeout initializing reports [80397.696344] hid-generic 0003:0451:F432.000A: hiddev0,hidraw4: USB HID v1.01 Device [Texas Instruments Texas Instruments MSP-FET430UIF] on usb-0000:03:00.0-9.3/input1 I've installed and activated the udev rules in /etc/udev/rules.d/71-ti-permissions.rules This feels like a driver problem to me. I haven't been able to find any information on what drivers are used, just vague and unhelpful statements like 'if you are running a current version of Linux it probably has the correct drivers already installed.' I've tried running as root to bypass any permissions issues with no change in results. I've installed energia, it uses mspdebug for it's connection so it gives the same result. I've run out of things to try. The MSP430 is a nice processor to work with but if I can't get the tools to work I'll have to pick a different MCU. Thanks All Randy
  3. cdc-acm issues with Linux

    It seems this is the problem that will never go away. I am asking here because anything on Google appears to be many years old, and I don't know if patches were applied to the Linux code base in that time or not. My Linux version (from /proc/version): "Linux version 4.9.56 (gleepy@clyde) (gcc version 6.3.0 (GCC) ) #1 SMP Sun Oct 15 14:54:08 EDT 2017" as an x86_64 system with no 32 bit libraries anywhere, I am causing the cdc-acm module to be loaded when either Launchpad is attached: two /dev/ttyACMx ports with the MSP-EXP430FR5994, as is expected; one with the '430G2. The '430G2 has its TXD/RXD jumpers oriented horizontally for hardware serial communication. I have no issues with using mspdebug rf2500 to flash and verify any code I compile with MSP430 GCC. When flashing noForth onto the board, there was absolutely no communications with the computer when running minicom 2.7.1 at the recommended settings of 9600 baud, 8 bits, no parity, 1 stop, and no flow control. None. Even when I followed some old advice of using the stty command to set the speed and flush the port immediately after plugging in the Launchpad. Even the "out of the box" firmware on the '430FR5994 will not communicate with the GUI program which is run. No indication of any extant serial ports show up on the selector in the GUI program. This does not appear to be a privilege or permissions issue as even as root, the communications problems exist. Since people seem to be able to use the Launchpad with Linux to invoke serial communications, as it is implied in the TI documentation and what the noForth people say. Therefore, there exists a set of users which do not have this communications problem. Could it be a lost cdc-acm patch that was supposed to work its way to the Linux maintainers and had gotten lost in code checkins?
  4. Hi Everybody, I've been developing some code on Linux using CCSV7.2 and I already know that CCS will not program the g2553 like it would on a Windows box. But, I know that you guys are clever! How have you been programming and debugging the g2553 on Linux these days? Are you using a different LaunchPad and hot wiring it over to the G2553 LaunchPad?
  5. Hey all! Finicky issue, and I've been up for way too many hours so I'm breaking from usual habit and posting after only doing minimal digging. Hopefully it's a simple solution. Fingers crossed. Board: TM4C1294NCPDT IDE: CCSv6.1 OS: Ubuntu 16.04 Compiler: GNU v4.9.3 (Linaro) So here's what's up: I'm versed using timers and setting up my vector table properly, or so I thought. Code Composer Studio isn't finding my interrupt handler... It's confuzzling me to say the least... Here's what I'm doing: In startup_gcc.c //......Skipping top of file for readability, all is stock // External declarations for the interrupt handlers used by the application. extern void Timer1AIntHandler(void); //......Skipping a bunch of nonsense for readabilities sake //Beginning of vector table (NOT Blizzard, but Snowflake/RA0) #else __attribute__ ((section(".isr_vector"))) void (* const g_pfnVectors[])(void) = { (void *)&_estack, // The initial stack pointer ResetISR, // The reset handler NmiSR, // The NMI handler FaultISR, // The hard fault handler IntDefaultHandler, // The MPU fault handler IntDefaultHandler, // The bus fault handler IntDefaultHandler, // The usage fault handler 0, // Reserved 0, // Reserved 0, // Reserved 0, // Reserved IntDefaultHandler, // SVCall handler IntDefaultHandler, // Debug monitor handler 0, // Reserved IntDefaultHandler, // The PendSV handler SysTickIntHandler, // The SysTick handler GPIOAIntHandler, // GPIO Port A GPIOBIntHandler, // GPIO Port B GPIOCIntHandler, // GPIO Port C GPIODIntHandler, // GPIO Port D GPIOEIntHandler, // GPIO Port E UARTStdioIntHandler, // For UARTStdio - UART0 Rx and Tx UARTIntHandler1, // UART1 Rx and Tx IntDefaultHandler, // SSI0 Rx and Tx IntDefaultHandler, // I2C0 Master and Slave IntDefaultHandler, // PWM Fault IntDefaultHandler, // PWM Generator 0 IntDefaultHandler, // PWM Generator 1 IntDefaultHandler, // PWM Generator 2 IntDefaultHandler, // Quadrature Encoder 0 ADC0IntHandler, // ADC Sequence 0 IntDefaultHandler, // ADC Sequence 1 IntDefaultHandler, // ADC Sequence 2 IntDefaultHandler, // ADC Sequence 3 IntDefaultHandler, // Watchdog timer IntDefaultHandler, // Timer 0 subtimer A IntDefaultHandler, // Timer 0 subtimer B Timer1AIntHandler, // Timer 1 subtimer A (Thar she blows...) And then in my main project file: // Only showing relevant pieces... // // Prototypes // ========== // Bunch of skipped out-of-scope stuff... void init_Timer(void); void Timer1AIntHandler(void); void init_Timer(void) { // Enable interrupts to the processor. ROM_IntMasterEnable(); // Enable Timer Peripheral ROM_SysCtlPeripheralEnable(SYSCTL_PERIPH_TIMER1); // Configure Timer1 to be Periodic, with a 100Hz interrupt ROM_TimerConfigure(TIMER1_BASE, TIMER_CFG_PERIODIC); ROM_TimerLoadSet(TIMER1_BASE, TIMER_A, g_ui32SysClock / 100); // Setup the interrupts for Timer1 timeout. ROM_IntEnable(INT_TIMER1A); ROM_TimerIntEnable(TIMER1_BASE, TIMER_TIMA_TIMEOUT); // Enable Timer1A. ROM_TimerEnable(TIMER1_BASE, TIMER_A); } // void loop() is there somewhere, but it's HUGE, doesn't use the timer anyway. void Timer1AIntHandler(void) { // Clear the timer interrupt. ROM_TimerIntClear(TIMER1_BASE, TIMER_TIMA_TIMEOUT); // Call the FatFs tick timer. disk_timerproc(); } I need the timer for FatFS by ChaN. CCS gives me this on building (skipped everything until the linker output): Sooo what's going on here? Does the Energia part of CCS do something different with the timer section of the vector table? I have a custom ADC0IntHandler which works just fine... If anyone needs more info, I'm more than glad to provide it. Frustrations abound, and it especially sucks 'cuz after a 20 hour coding marathon, a problem like this is just... Awful.
  6. Can anyone help on this issue please ? On Ubuntu 14.04 64 bit, I am unable to get the serial port to work with Energia 16 and MSP430G2. I have exactly followed the install instructions for Linux : http://energia.nu/guide/guide_linux/ including setting udev rules. The MSP430G2 can be programmed ok however any attempt to open the serial port monitor causes Energia to hang up/freeze. FYI, I also have an Arduino board with the latest Arduino IDE which has no problems with serial output on this same evironment (and setting that up was a breeze). It's a pity that getting Energia to work on Linux is so hard. I have seen previous postings on this issue suggest a custom build of the cdc_acm driver; is that really necessary given Arduino works fine ? Below is the output of dmesg: [42439.494174] usb 1-1.2: new full-speed USB device number 4 using ehci-pci [42439.609479] usb 1-1.2: New USB device found, idVendor=0451, idProduct=f432 [42439.609484] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [42439.609487] usb 1-1.2: Product: Texas Instruments MSP-FET430UIF [42439.609489] usb 1-1.2: Manufacturer: Texas Instruments [42439.609491] usb 1-1.2: SerialNumber: E7FF4D53F4181B50 [42449.663054] hid-generic 0003:0451:F432.0004: usb_submit_urb(ctrl) failed: -1 [42449.663078] hid-generic 0003:0451:F432.0004: timeout initializing reports [42449.663362] hid-generic 0003:0451:F432.0004: hiddev0,hidraw3: USB HID v1.01 Device [Texas Instruments Texas Instruments MSP-FET430UIF] on usb-0000:00:1a.0-1.2/input1 [42449.758556] cdc_acm 1-1.2:1.0: This device cannot do calls on its own. It is not a modem. [42449.758564] cdc_acm 1-1.2:1.0: No union descriptor, testing for castrated device [42449.758591] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device [42449.760730] usbcore: registered new interface driver cdc_acm [42449.760735] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
  7. Installing Energia on Linux

    As a relative novice Linux user, my beef with Energia is the same as with a lot of other software packages: the installation instructions basically end at "download it". OK, I downloaded it. Now what? Where do I put it? How do I launch it? And so forth. Using Ubuntu 14.04 (32-bit). Java is installed and working (at least it works for Eclipse). Any kind souls willing to help? (I guess this would be moot if somebody created an installer package for the Ubuntu Software Center, but I have no idea how much work that involves.)
  8. I'm currently working on cross platform build tool named PlatformIO. It has pre-built MSP430 GCC toolchain & mspdebug for Mac, Linux 32/64 & Windows OS. 1. How often do you use external standalone toolchain to build your code? In which case? 2. What is your favourite IDE+Toolchain? 3. What would you like to have in paltformio tool? Thanks a lot for answers! P.S: The main idea of this tool is to compile code with different platforms. See Wiring Framework (Arduino + Energia) Blink Example.
  9. Hello everyone, FIrst - its not the permission issue of not having a proper udev rule. I am on Debian Wheezy with all the msp related packages installed from the official repos - including mspdebug. But after I connect the launchpad and give: mspdebug rf2500 I get usbutil: unable to find a device matching 0451:f432 My computer is not detecting the board. The output of lsusb is: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 1210:25f4 DigiTech Bus 002 Device 003: ID 04f3:0232 Elan Microelectronics Corp. Mouse I get *no* information at dmesg while I plug in or disconnect the launchpad. Absolutely nothing. The output of lsmod | grep ti confirms that the ti's usb driver module has not been loaded. So I manually loaded that one with modprobe ti_usb_3410_5052 Now I see something in dmesg: [ 1496.709197] usbcore: registered new interface driver usbserial [ 1496.709227] USB Serial support registered for generic [ 1496.709266] usbcore: registered new interface driver usbserial_generic [ 1496.709273] usbserial: USB Serial Driver core [ 1496.722267] USB Serial support registered for TI USB 3410 1 port adapter [ 1496.722313] USB Serial support registered for TI USB 5052 2 port adapter [ 1496.722733] usbcore: registered new interface driver ti_usb_3410_5052 [ 1496.722741] ti_usb_3410_5052: v0.10:TI USB 3410/5052 Serial Driver Now I plugged in the board again. But absolutely *no* change in the dmesg or lsusb output. The board is a fresh one, and its working well - when I plug in into USB, I can see its demo program blinking those red and green leds. Now, as mentioned in http://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Getting_Started_with_Debugging, I looked for the firmware file to copy, but the file ti_3410.fw doesnt exist anywhere in my /lib/firmware. But I do have a file ti_3410.fw.ihex in /usr/lib/mspdebug which obviously came with mspdebug. What's wrong? What should I do to get the USB port detected? It might be irrelevant, but I can connect an Arduino board on the same port, and it works well. Thanks in advance!
  10. Just wanted to share a project that I got compiling last night (doesn't necessarily work yet). If anyone is curious about it, it's located here.
  11. Software selection

    guys how do i choose which platform to work on? Ångström Linux Android Ubuntu Cloud9 IDE I knw C/C++, JAVA lang....but i m ready to learn another if needed I want to build real time OCR project using BBB as processing device.....
  12. hi guys, i am new here. i am a linux user, so i have my inhibitions of going back to windows just so that this kit could work as i beleive it is very much possible in windows too. so the thing is.. i used CCSv5.2 to make a blinking LED Project and used the 'debug' option to get the code into the device. my device is msp430 Launchpad. the error message is as folows. //------------------------------------------ Error initializing emulator: No USB FET was found //------------------------------------------ to look into things i disconnected the Launchpad from the USB and reconnected it. the kernel message log gave the following message. //---------------------------------------------------------------------------------------------------------- [ 3077.760134] usb 3-4: new full-speed USB device number 3 using xhci_hcd [ 3077.796775] usb 3-4: New USB device found, idVendor=0451, idProduct=f432 [ 3077.796783] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3077.796788] usb 3-4: Product: Texas Instruments MSP-FET430UIF [ 3077.796792] usb 3-4: Manufacturer: Texas Instruments [ 3077.796795] usb 3-4: SerialNumber: 2EFF426C50144B46 [ 3077.797050] usb 3-4: ep 0x82 - rounding interval to 1024 microframes, ep desc says 2040 microframes [ 3077.802856] cdc_acm 3-4:1.0: This device cannot do calls on its own. It is not a modem. [ 3077.802865] cdc_acm 3-4:1.0: No union descriptor, testing for castrated device [ 3077.802891] cdc_acm 3-4:1.0: ttyACM0: USB ACM device [ 3087.862748] hid-generic 0003:0451:F432.0003: usb_submit_urb(ctrl) failed: -1 [ 3087.862790] hid-generic 0003:0451:F432.0003: timeout initializing reports [ 3087.863722] hid-generic 0003:0451:F432.0003: hiddev0,hidraw0: USB HID v1.01 Device [Texas Instruments Texas Instruments MSP-FET430UIF] on usb-0000:00:14.0-4/input1 //------------------------------------------------------------------------------------------------------------- and when i run the lsusb command. //----------------------------------------------------------------------------------------------------------------- Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 003: ID 0451:f432 Texas Instruments, Inc. eZ430 Development Tool Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 15d9:0a4f Trust International B.V. Bus 001 Device 003: ID 8087:07da Intel Corp. Bus 001 Device 004: ID 147e:1002 Upek Bus 002 Device 003: ID 05ca:1823 Ricoh Co., Ltd //-------------------------------------------------------------------------------------------------------------------- is the msp430 Launchpad an ez430 development tool? i didnt knw that.... also... if it shows it as a device.. why cant i connect to it.. anybody has any idea... if any more data is needed, i am happy to provide that too...
  13. Hi all well I got a problem with my Serial comunication, when I conect my launchpad with the jumpers in the default (software uart position) parallel like: || || || || almost everything works ok, i can programm my launchpad with energia I can see the Serial port is right But when i try to test the serial comunication with de serial monitor it can not send anything or recieve. then I desconect and change the jumpers for a Hardware UART like: = || || || then i conect my launchpad and i can not see my serialport name on energia and can not open the serial monitor. Im working on UBUNTU 12.04 Any Ideas? thanks. Valery
  14. I'm trying to start working with a TI Launchpad on my Mac (I also have a Ubuntu virtual machine I can work in), and I want to program it in assembly using mspgcc. However, I'm getting confused with a lot of the information I'm finding about how to actually write code for this! Any assembly tutorials I find (even in the MSP430 Microcrontroller Basics book) use references such as #WDTPW|WDTHOLD, &WDTCTL or &P2OUT, and whenever I try to compile assembly files with those, mspgcc throws a bunch of errors about how it can't refernce those. So, what is the best way for a beginner looking to program in assembly on a TI Launchpad to get started? What am I doing wrong when I compile all of these test files? (If I didn't provide enough information, feel free to ask for more)
  15. If you are a Linux enthusiasts, you will love this! You can develop for the stellaris launchpad using command-line tools on Linux; check out: http://recursive-lab...etting-started/
  16. Hi Everyone,What are the speculated list of OSes / RTOSes which might run on the Stellaris Launchpad ? Do FreeRTOS, eCos, or Linux (or armlinux) figure in them ? I am presuming if Linux or armlinux can be ported, it would need external flash which is absent on the board. Can this be overcome with a booster pack ? What kind of changes should one anticipate while porting the above ? And what should anyone watch out for ?Regards,Pixelhaze