Jump to content

Search the Community

Showing results for tags 'gdb'.

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 6 results

  1. 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 most recent version of mspgcc from the old sourceforge site, but this is 2 years out of date now, and the development has moved to a project hosted by texas instruments: http://www.ti.com/tool/msp430-gcc-opensource . I would like to use the most recent version from ti if possible; I've tried compiling it and it builds OK, but I can't find a compatible libc and set of device specific header files which will work with it. When I try to use the libc that comes with ubuntu, it says it's incompatible. Also, when I pass the flag '-mmcu=msp430f5510', which used to work before, msp430-gcc throws an error. I've also noticed that the msp430 support appears to have been merged back into the upstream mspgcc (and presumably the other gnu tools), which is another way I've thought of going. So my question is, given all this, what's the best way to go to set up an up to date open source toolchain for the msp430? I could just compile the most recent version from the old sourceforge project, but would rather use something more up to date if that is possible.
  2. Hi, I am trying to learn debugging Stellaris launchpad using gcc. I am using the GCC arm embedded toolchain. And I am trying to debug the blinky example project in the stellarisware. But GDB complains that it can't find the debuggin symbols. I have tried defining the symbol "DEBUG" in the source code, but that failed. Please tell me how I can fix this issue? Akhils-MacBook-Pro:blinky akhil$ arm-none-eabi-gdb gcc/blinky.axf GNU gdb (GNU Tools for ARM Embedded Processors) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-apple-darwin10 --target=arm-none-eabi". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /Users/akhil/work/blinky/gcc/blinky.axf...(no debugging symbols found)...done.
  3. I got a bit tired of not being able to debug on the NXP LPC1114, which supports SWD only (no JTAG). I discovered Black Magic Probe (http://www.blacksphere.co.nz/main/blackmagic), which is an open source project that uses an STM32 to export a GDB server via an USB serial device. It support both JTAG and SWD and should support a wide range of Cortex-M0, M3, and M4 targets. It can be used both for debugging and flashing of the target device. There is dedicated hardware for this, and it can be run on the F4-discovery boards as well. Unfortunately, I do not have any F4-discovery boards lying around. But I do have a couple of Stellaris Launchpads that do nothing but sit in their box. So I added the necessary code to allow the Black Magic Probe firmware to be flashed on the Stellarpad (which really wasn’t that much). Currently, UART0 on the LM4F is used, which is connected to the on-board debugger module that exports it via USB as a CDC ACM serial device. The pinout is as follows: JTAG TMS / SWD IO - PB5 JTAG TCK / SWD CLK - PB0 JTAG TDI - PB1 JTAG TDO - PE4 TRST - PA5 SRST - PA6 IDLE LED - PF2 / Blue LED ERROR LED - PF3 / Green LED You can grab the code from GitHub and try it out yourself: https://github.com/xpgdk/blackmagic/tree/stellaris_launchpad Please try it out, and let me know if there are any issues. The quick build instructions (for Linux) are: src$ git clone https://github.com/xpgdk/blackmagic.git Cloning into 'blackmagic'... remote: Counting objects: 1858, done. remote: Compressing objects: 100% (763/763), done. remote: Total 1858 (delta 1230), reused 1704 (delta 1084) Receiving objects: 100% (1858/1858), 610.80 KiB | 324 KiB/s, done. Resolving deltas: 100% (1230/1230), done. src$ cd blackmagic src/blackmagic$ git checkout stellaris_launchpad Branch stellaris_launchpad set up to track remote branch stellaris_launchpad from origin. Switched to a new branch 'stellaris_launchpad' src/blackmagic$ git submodule init Submodule 'libopencm3' (https://github.com/xpgdk/libopencm3.git) registered for path 'libopencm3' src/blackmagic$ git submodule update Cloning into 'libopencm3'... remote: Counting objects: 12626, done. remote: Compressing objects: 100% (6494/6494), done. remote: Total 12626 (delta 6511), reused 11757 (delta 5726) Receiving objects: 100% (12626/12626), 3.25 MiB | 733 KiB/s, done. Resolving deltas: 100% (6511/6511), done. Submodule path 'libopencm3': checked out 'f5c15fe74e438dc9cceac6543d2c180957a3dd9b' src/blackmagic$ cd libopencm3 src/blackmagic/libopencm3$ make … src/blackmagic/libopencm3$ cd ../src src/blackmagic/src$ make PROBE_HOST=stellaris-launchpad … src/blackmagic/src$ lm4flash blackmagic.bin Now, you should be able to connect to the GDB server: $ arm-none-eabi-gdb (gdb) target extended-remote /dev/ttyACM0 (gdb) monitor swdp_scan Target voltage: not supported Available Targets: No. Att Driver 1 lpc11xx (gdb) attach 1 Attached to Remote target 0x00001066 in ?? ()
  4. Can I use gdb to debug programs on the Stellaris (or Tiva) Launchpad under Windows? If so, where do I find the instructions on how to set it up? I find lots of things for using gdb under Linux, or even under cygwin, but somehow I am missing the bit about how to use gdb with the launchpad under windows. (I have used CCS for debugging, but dealing with a larger project here with its own build system would be a bit of a bother to try to convert it to CCS, and the problem might even be gcc specific.) Figure I am probably either missing the obvious, or trying to do something that can't be done, but don't know which. Thanks Edit: Some other freely available debugger would be okay also (just as long as works with gcc).
  5. Hello I am Manish .I am doing ARM cortex M4 Programming with STM32F4 discovery ,code flashes properly but it having problem when debgging with GDB.Following result i have found.please guide me how to slove that. manish@manish-Inspiron-1501:~/my-wow-adc$ arm-none-eabi-gdb obj/STM32F4_Test.elf GNU gdb (Sourcery CodeBench Lite 2013.05-23) Copyright © 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-none-eabi". For bug reporting instructions, please see: <https://sourcery.mentor.com/GNUToolchain/>... Reading symbols from /home/manish/my-wow-adc/obj/STM32F4_Test.elf...done. (gdb) target extended-remote localhost:4242 Remote debugging using localhost:4242 0x080077fc in Reset_Handler () (gdb) monitor reset init (gdb) load Loading section .isr_vector, size 0x188 lma 0x8000000 Loading section .text, size 0x7e34 lma 0x8000188 Loading section .ARM, size 0x8 lma 0x8007fbc Loading section .init_array, size 0x4 lma 0x8007fc4 Loading section .fini_array, size 0x4 lma 0x8007fc8 Loading section .data, size 0x5b0 lma 0x8007fcc Start address 0x80077fc, load size 34172 Transfer rate: 6 KB/sec, 4881 bytes/write. (gdb) b main Breakpoint 1 at 0x80073f2: file src/main_temp.c, line 4. (gdb) c Continuing. Note: automatically using hardware breakpoints for read-only addresses. then program halts I am not getting why Note: automatically using hardware breakpoints for read-only addresses. above line prints and how to caime from that.
  6. Is there any chance to implement debugging with Energia? The manual procedure works fine with Terminal windows on Mac OS X, although everything is manual. One of the unparalleled key feature of the LaunchPad is the built-in hardware debugger. Alas, how to use in an easy way? I'd like to set breakpoint and monitor variables. Here's the manual procedure. On a first Terminal window, launch /Applications/Energia.app/Contents/Resources/Java/hardware/tools/msp430/mspdebug/mspdebug rf2500 gdb On a second Terminal window, launch /Applications/Energia.app/Contents/Resources/Java/hardware/tools/msp430/bin/msp430-gdb /var/folders/kd/70m4ltxn14l086ddy860ff3c0000gn/T/build2770014008396495792.tmp/mySketch.cpp.elf with mySketch being the name of the sketch on Energia and /var/folders/kd/70m4ltxn14l086ddy860ff3c0000gn/T/build2770014008396495792.tmp/ the name of the path. To know the name of the path, check the Show verbose output during compilation on the preference pane of Energia and have a look at the console. Something like /var/folders/kd/70m4ltxn14l086ddy860ff3c0000gn/T/build2770014008396495792.tmp/mySketch.cpp.elf should appear at the end after a successful compilation. On the second window of the Terminal, a prompts appears: (gdb) Type (gdb) tar rem localhost:2000 Now you can type commands like (gdb) list For more information about the gdb commands, please refer to the manual available at the http://sourceware.org/gdb/download/onlinedocs/'>GDB: The GNU Project Debugger
  • Create New...