Search the Community
Showing results for tags 'gcc'.
Found 18 results
-
The open-source RTOS called "NUFR" has been ported to the MSP430/MSP430X CPUs. NUFR is a full featured RTOS--not just a simple scheduler. Features: MSP430 and MSP430X 16- and 20-bit models Make system included; all free/open-source tools Prioritized & Preemptive multitasking; Round-Robin multitasking; context switching from interrupt handlers Low-power extensions: tickless OS; special logic for low power mode RNET IPv4/IPv6/UDP stack runs on NUFR Message-based, event-driven Example project for Launchpad board Small RAM footprint: OS itself co
-
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? -
I was not able to use realloc using energia so I imported the proyect to CSS v7. It seems there is something wrong or not done about realloc under Energia. CSS v7 is using the Ti compiler instead of GCC and it has realloc and it works. But when using CCSv7 with the imported sketch, the Serial.print commands do nothing. Even If I debug step by step it just ignores Serial.print commands without showing anything anywhere. I activated the serial terminals inside CCSv7 to see the output and I also have the normal output and the console. I can work around if I fi
-
Hi, I needed a way to see how much of my C++ stack was being consumed in my MSP application - the traditional way is to "poison" the stack with a known pattern, and then to see how much of it gets burnt away. So I wrote the following - hope folk find it useful: The following code allows you to simply do this and to check at any point how much of the pre-allocated stack was consumed during peak usage, i.e. how close your app got to the bottom of the stack, or indeed, whether it over-ran. The TI CCS documentation is completely wrong in the names it gives for the global symbols tha
-
Hello, I have a problem with strange behavior of gcc compiler, which does not seem to generate interrupt vectors correctly. I tried to search for hints on the forum, but could not find any helpful information. I have the following C code: void __attribute__((interrupt(TIMER0_A0_VECTOR))) timer0_isr(void) { //IMPORTANT !!!!!!! //Clear TAIV by reading it !!!! (void) TAIV; /* ... */ } void __attribute__((interrupt(TIMER0_A1_VECTOR))) timer0_a1_isr(void) { P1OUT ^= PIN0; } volatile int qq; __attribute__((interrupt(USCIAB0TX_VECTOR))) void usci_tx_isr(void) { qq=1; P1OUT ^=
-
I noticed that if you use the TI arm compiler in CCS 6.x you can easily run code from ram. Unfortunately, it doesn't seem like they have implemented that for the arm-none-eabi-gcc compiler. Attached is a zip file project you can import into CCS. It is configured to run the msp432 at 48MHz using the high frequency crystal. It is also configured to generate small code using the nano.specs newlib configuration. In the default linker script, the data segment uses all the available ram starting at the base address of 0x20000000. The msp432 provides another bus address for SRAM at the base
-
I'm trying to set up an eclipse / gcc / gdb / mspdebug based development environment to work on a custom msp430 based board that the company I work for produce. I have set up eclipse with the tools which come with ubuntu 15.04, and it's almost working apart from a weird bug in the debugger. When you watch a local variable in the main function, eclipse displays an incorrect value. This bug has been around for a while, as I've noticed it before (see this and the following page: http://forum.43oh.com/topic/1419-eclipse-plugin-for-mspdebug-and-msp430-gcc/page-3). The bug has been fixed in the -
I have a program of about 40 KB (I use FAT32 through FatFs, that takes a lot of memory) that I developed using msp430-gcc 4.6.3 for a MSP430F5529 (that has 128 KB Flash). I am trying to move it to msp430-gcc 4.9.1 (downloaded from TI) but am getting the following errors upon linking: /opt/ti/gcc/bin/msp430-elf-gcc -I /opt/ti/gcc/include -mmcu=msp430f5529 -Os -g -c -o main.o main.c /opt/ti/gcc/bin/msp430-elf-gcc -I /opt/ti/gcc/include -mmcu=msp430f5529 -Os -g -c -o ccsbcs.o ccsbcs.c /opt/ti/gcc/bin/msp430-elf-gcc -I /opt/ti/gcc/include -mmcu=msp430f5529 -Os -g -c -o delay.o delay.c -
I'm port some code over to GCC (GNU_4.6.3:MSPGCC compiler inside CCS6.1) to take advantage of existing driver code for some of my devices. After clearing all basic errors, my build fails with this error: .../energia-0101e0014/hardware/tools/msp430/bin/../lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld.exe: error: no memory region specified for loadable section `.noinit.crt0' gmake: *** [main.o] Error 1 gmake: Target `all' not remade because of errors. How do I fix that? NOTE/CLUE: I tried making a new, blank GNU_4.6.3:MSPGCC project in CCS, and it gets identical compile errors. Ho
-
I know that the first word is the address of the top of the stack. In startup_gcc.c file in the stellarisware projects, the address of the reset_isr subroutine is stored in the second word space in the _text section. In the objdump of the blinky.axf file, a value of 0x2d1 is stored at address 0x04 in _text section. But the reset_isr subroutine is stored at address 0x2d0. This is confusing me. Isn't a value of 0x2d0 supposed to be at address 0x04 in _text section? Please explain me where I am wrong. I have attached the objdump of blinky.axf here. Akhils-MacBook-Pro:blinky akhil$ arm-none-eabi
-
How can I add a switch to the g++/gcc command line (or do something equivalent) in Energia? I am importing a library (FastLED) which generates a bunch of warnings about needing -std=c++11 Example warning message: FeatureDemo.ino:655:98: warning: extended initializer lists only available with -std=c++11 or -std=gnu++11 [enabled by default] I would like to make those warnings go away (both for me, and be able to tell anyone else using the library how to make them go away). I have hunted through the menus, through the customization file and looked at the gcc documentation (for
-
I'm getting this error: main.c: In function 'Timer_A': main.c:150:28: error: MSP430 builtin functions only work inside interrupt handlers __bic_SR_register_on_exit(CPUOFF); // Clear CPUOFF bit from 0(SR) ^ makefile:23: recipe for target 'main.o' failed With this code: // TimerA interrupt __attribute__((__interrupt__(TIMERA0_VECTOR))) Timer_A (void) { iflag |= BIT0; // Set BIT0 flag __bic_SR_register_on_exit(CPUOFF); // Clear CPUOFF bit from 0(SR) } For some reason msp430-elf-gcc thinks my ISR isn't an ISR Any ideas? I emailed one of the r
-
Greetings, I am currently working on a personal project using Tiva Launchpad together with Eclipse Kepler IDE and GNU ARM Embedded Tools (gcc version 4.8.2). Last week my efforts were focused on making the "usb_dev_serial" example (Tivaware 2.0.1.11577) work with that development setup (also i'm using it all on Windows 8). So far, a simple I2C master + button interrupt + LED toggling example I've made with this development configuration is working OK. When the USB module was added ("usb_dev_serial" skeleton added to my project), some compiling issues arised, but got fixed after I put "
-
I have recently received my Stellaris Launchpad and I'm building a toolchain to code for it using GNU+Linux. So far I have the cross compiler+lm4tools+stellarisware running. I can build the stellaris examples and flash them without problems. As I want to do some signal processing with my board, I'd like to build the CMSIS library. At least the DSPLib part (I don't need the RTOS right now). The library zip file has some scripts to build it using Keil, but as I'm a GNU+Linux user, I can't run Keil IDE. Also unfortunately, I'm a total noob when talking about autotools, so... Has a
-
Hi, I've never noticed that the license for the examples of the stellaris launchpad were closed, they say explicitly that: # Texas Instruments (TI) is supplying this software for use solely and # exclusively on TI’s microcontroller products. The software is owned by # TI and/or its suppliers, and is protected under applicable copyright # laws. You may not combine this software with “viral” open-source # software in order to form a larger program. I wasn't very comfortable with this and I finally decided to write the needed linker script, startup file and the useful Makefile from sc -
I didn't see any posts on whether or not cygwin was a usable environment. I figured I would give it the college effort and see if I could build up a toolchain that allows me to compile and flash from within my editor of choice (Vim). The basic groundwork is laid out, and I have to say that I really didn't have to do any original work as it was basically all adapted from linux tutorials. If anyone is interested, I wrote up my experience at http://underwaterwhistler.blogspot.com/2013/01/getting-started-with-stellaris-launchpad.html
-
I'm new here so hi. I have a problem compiling stellarisware with a custom build of gcc. I'm using the custom build because I want to learn how to build an arm toolchain on linux. I used buildroot to build everything. The problem I'm having is that on the qs_rgb example there is an error: In function `__aeabi_ldiv0': undefined reference to `raise' I think this has to do with floating point division used in the example. the makedefs file for stellarisware is set up to use software floating point. I'm using gcc 4.7.1 and it is set to use software fpu by default. Has a
-
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/
