Jump to content
Forum sending old emails Read more... ×

Search the Community

Showing results for tags 'eclipse'.

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.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL





Found 5 results

  1. INTRODUCTION This guide's intent and purpose is to allow a user with minimal Linux experience to successfully setup an absolutely free development environment to program the STM32F0 microcontroller with full debugging capability. PREREQUISITES A Linux distro, I used Linux Mint 13 (Ubuntu works nicely too) An Internet connection At least 2gb of spare hard drive space Familiarity with terminal A STM32F0 Discovery Board! PART 1 – Install Codesourcy PART 2 – Install OpenOCD PART 3 – Install Eclipse PART 4 – Setup File Directory PART 5 – Setup Eclipse PART 6 – Configure the gdb/OpenOCD Hope you enjoy! Any questions, comments, feedback, feel free to sound off below.Also a STM32F4 guide is on its way. When it gets here depends on how much spare time I have.... Edit: Thanks bluehash! Guide is now hosted on arm-hq. v1-2 Downloads stm32f0_v2.doc
  2. I have the Stellaris LaunchPad and I can use it successfully with CCS and IAR. Now I am trying to setup the Eclipse CDT with the GNU ARM Eclipse plug-ins, GCC ARM toolchain, and OpenOCD on my Windows system. I have been following the instructions at the GNU ARM Eclipse plug-ins website. I have successfully created and built a project from the plug-in's generic ARM Cortex-M Project template. But now I am stuck trying to run the debugger with the OpenOCD GDB Server. I created a debugger configuration as described on the GNU ARM Eclipse Plug-ins instructions, here. Except on the Debugger tab in the OpenOCD Settings groupbox I set the Other Options field to "-f board/ek_lm4f120xl.cfg". When I attempt to debug with this configuration, I get the following output in the console window. (The launchpad is connected and powered on.) Open On-Chip Debugger 0.8.0 (2014-04-28-08:39) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : This adapter doesn't support configurable speed Info : ICDI Firmware version: 9270 Info : lm4f120h5qr.cpu: hardware has 6 breakpoints, 4 watchpoints Info : accepting 'gdb' connection from 3333 undefined debug reason 7 - target needs reset target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x00002000 msp: 0x20007904 semihosting is enabled Error: memory write failed: 0x7 Error: memory write failed: 0x7 Error: memory read failed: 0x7 Error: memory read failed: 0x7 Error: memory read failed: 0x7 Error: memory read failed: 0x7 Error: memory read failed: 0x7 target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x00002000 msp: 0x20007904, semihosting Error: Memory write failure! What do I need to do to get this working? This is on a Windows 7 system. I had previously installed the Stellaris ICDI driver from TI when I was using CCS. I'm assuming that same ICDI driver is what OpenOCD uses to interface with the board. Is there a different ICDI driver I need for OpenOCD? Thanks for your help. -- Kevin
  3. I have followed the tutorial on this site for integrating Eclipse with msp430-gcc. I am running ubuntu 13.04 64 bit. msp430-gcc (GCC) 4.6.3 20120301 (mspgcc LTS 20120406 unpatched) Eclipse Platform Version: 3.8.1 Compiling manually on a Terminal works: I have a simple programme to toggle LED on the MSP430 Launchpad Rev 1.5 board. I compile this on a terminal using msp430-gcc -mmcu=msp-430g2553 -o led.elf blinkingled.c This gets compiled and I can flash the binary to my board and it works. When I have this same setup to compile on Eclipse the compilation is in two stages. The first step is creating object files and then the linker kicks in. I have included the following Library search path under GCC C Linker --> Libraries in Eclipse /usr/msp430/lib This is as per the tutorial, however this results in Building target: led.elf Invoking: GCC C Linker msp430-gcc --mmcu=msp430g2553 -Wl,-Map=led.map -L/usr/msp430/lib/ -o "led.elf" ./led.o /usr/lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: cannot open linker script file memory.x: No such file or directory collect2: ld returned 1 exit status make: *** [led.elf] Error 1 For the linker to succeed, as a work around I have given the full path in GCC C Linker --> Libraries in Eclipse /usr/msp430/lib/ldscripts/msp430g2553 With this linking succeeds and am able to create the led.elf using eclipse. Can some one throw a light on what is wrong with my setup which is preventing the linker to fail in the first setup? Problem 2 I have File1.c, File2.c and File2.h all in the same folder. I am calling a function func1 inside File1.c. File1.c has File2.h in its #include. func1 is defined in File2.h and implemented in File2.c I am able to compile this using the following command on a terminal msp430-gcc -mmcu=msp430g2553 -I/usr/msp430/include -I/usr/include -I"./" File2.c File1.c -o something.elf this compiles and I am able to flash the firmware on to the board. When I try to compile the same set of code inside Eclipse I get File2. c gets compiled to File2.0 File1.c compilation fails. File1.c (.init9+0xc): undefined reference to `func1' Again this is some configuration in Eclipse which is not set properly which is preventing it to relate to the object files. Could some one kindly throw some light . With regards Krishna
  4. I recently installed openOCD on my computer and was able to get command line debugging working. Reading the gdb tutorials, I started doubting whether this was something I wanted to learn and wanted to see if I could get a GUI debugger working instead. I started fiddling around with Eclipse on my Mac and wanted to get a complete Tiva IDE. I followed a great tutorial for installing Stellarisware on Linux at http://kernelhacks.blogspot.com/2012/11/the-complete-tutorial-for-stellaris_25.html Perhaps because of the changes from Stellarisware to Tivaware and/or Linux to Mac, there were many things that needed to be tweaked, adjusted, and fiddled with. But in the end, everything works! First, off, I have Energia.app in /Applications. I installed openOCD using macports and installed Eclipse IDE for C/C++ Developers. Make sure gdb and openOCD are working properly before trying to get it to work in eclipse. I will describe here the changes from the tutorial above-- do all the other steps in the tutorial above. I copied the TivaWare files extracted on a Windows machine (because TI distributes this as an EXE file!) to ~/Projects/TivaWare_C_Series-1.1 (you can choose elsewhere but will need to change paths accordingly). I also created a folder for openOCD in ~/Projects/openocdDir containing the file ek-lm4f230xl.cfg which contains # # TI Stellaris Launchpad ek-lm4f120xl Evaluation Kits # # http://www.ti.com/tool/ek-lm4f120xl # # # NOTE: using the bundled ICDI interface is optional! # This interface is not ftdi based as previous boards were # source [find interface/ti-icdi.cfg] set WORKAREASIZE 0x8000 #set CHIPNAME lm4f120h5qr set CHIPNAME lm4f230h5qr source [find target/stellaris_icdi.cfg] Step 6: in Cross Settings, change Prefix to arm-none-eabi- and set Path to /Applications/Energia.app/Contents/Resources/Java/hardware/tools/lm4f/bin/ Step 7: Same except define PART_TM4C123GH6PM instead of PART_LM4F120H5QR. I don't know if this makes a difference but be consistent. Step 8: set include path to /Users/pjkim/Projects/TivaWare_C_Series-1.1 Step 9: Misc section. Set other flags to "-c -fmessage-length=0 -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=softfp -ffunction-sections -fdata-sections -MD -std=c99 -Wall -pedantic" Step 9.5: Change Cross Gcc Linker to ld. I think it defaulted to gcc for some reason. Step 10: Linker Libraries. Leave Libraries blank. Change search path to /Applications/Energia.app/Contents/Resources/Java/hardware/tools/lm4f/lib/gcc/arm-none-eabi/4.7.1 Step 11: Linker Misc. Change linker flags to "--gc-sections -T../LM4F.ld" Once everything is done, check your flags. If you click on the "Cross GCC Compiler" item under Tool Settings, you can see "All options:" it should look like -DARM_MATH_CM4 -DTARGET_IS_BLIZZARD_RA1 -DPART_TM4C123GH6PM -I/Users/pjkim/Projects/TivaWare_C_Series-1.1 -O0 -g3 -Wall -c -fmessage-length=0 -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=softfp -ffunction-sections -fdata-sections -MD -std=c99 -Wall -pedantic Check the Cross GCC Linker options. They should be something like this. -L/Applications/Energia.app/Contents/Resources/Java/hardware/tools/lm4f/lib/gcc/arm-none-eabi/4.7.1 --gc-sections -T../LM4F.ld You will need to supply a linker description file LM4F.ld in the main folder of your project. You can copy any one of the .ld files from the TivaWare examples folder. You basically needs this in the file: * This is part of revision 1.1 of the EK-TM4C123GXL Firmware Package. MEMORY { FLASH (rx) : ORIGIN = 0x00000000, LENGTH = 0x00040000 SRAM (rwx) : ORIGIN = 0x20000000, LENGTH = 0x00008000 } SECTIONS { .text : { _text = .; KEEP(*(.isr_vector)) *(.text*) *(.rodata*) _etext = .; } > FLASH .data : AT(ADDR(.text) + SIZEOF(.text)) { _data = .; *(vtable) *(.data*) _edata = .; } > SRAM .bss : { _bss = .; *(.bss*) *(COMMON) _ebss = .; } > SRAM } Go back to the appropriate sections to fix any errors. My username is pjkim. Change to yours. This should give you a working IDE for compiling your projects into an .elf and .bin file. Get this working before going to the next step, "Flashing Programs." Step 3: He was flashing the Release version which doesn't include the debug symbols in the .elf file. I chose to use the Debug version for this reason. Name "Debug flash." Location "/Applications/Energia.app/Contents/Resources/Java/hardware/tools/lm4f/bin/lm4flash" Working Directory: "${workspace_loc:/${project_name}/Debug}" and Arguments: "${project_name}.bin" This should give you compile and flashing capabilities. N.B. lm4flash in the current version of Energia (0101E0010) is broken. You will need to replace it from the prior version or as I did, build from source (https://github.com/utzig/lm4tools). The last part of the puzzle is in IDE debugging. This part works now but it was tricky to get working and I am not exactly why it is so fidgety. If it is not working properly, I suggest trying to isolate the problem by running openocd in a terminal window and gdb from eclipse. If this works, do it the other way around, run openocd in eclipse and connect to the board using gdb in a terminal window. That way you can narrow down where you need to fix things. Debuggin: Step 2: Location: "/opt/local/bin/openocd" Working Directory: "/Users/pjkim/Projects/openocdDir" and Arguments: "--file ek-lm4f230xl.cfg" You will need to create a openocdDir folder and put in the file ek-lm4f230xl.cfg. The contents are: # # Comments go here # source [find interface/ti-icdi.cfg] set WORKAREASIZE 0x8000 set CHIPNAME lm4f230h5qr source [find target/stellaris_icdi.cfg] Step 7: There is a known bug in gdb or openocd that can cause connection problems. The workaround is described in http://www.verious.com/tutorial/the-complete-tutorial-for-stellaris-launchpad-development-with-gnu-linux-ii Get the target.xml file from http://pastebin.com/download.php?i=0Lu3Bu0R and rename it. Put the file in your Project/Debug folder. If anyone knows how to do this better/automatically, I would appreciate it. Change the Initialization commands to set tdesc filename ../target.xml target extended-remote :3333 monitor reset halt And you should have a working IDE. Here is a screenshot of the IDE in action: Wouldn't it be nice if TI could package all of this into a .dmg file?
  5. Energia brings the ease of use of Arduino to the MSP430 and the Stellaris / Tiva. Actually, under one single name, Energia packs different elements: a bundle with IDE, libraries and tools-chains (MSP430 and LM4F) for an easy installation a more than basic IDE based on Processing a framework based on Wiring initially and modified by Arduino I'm presently using the Energia libraries, framework and MSP430 and LM4F tools-chains with Xcode, thank to the embedXcode template I've developed. However, the main critical missing feature is debugging. How to use the Energia framework on Eclipse to enjoy the debugging facilities? Thank you for your help.