Jump to content
43oh

Search the Community

Showing results for tags 'debug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Sparkfun


Github

Found 14 results

  1. 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?
  2. Hello all! So, this is happening on BOTH my Ubuntu 16.04 AND Windows 8.1 systems. This is for a TM4C1294NCPDT. To reduce potential variables, I've reverted to using the EK-TM4C1294XL Development Board. To reproduce: Fresh install of CCSv7.1, Fresh install of Energia 18. Open CCSv7, Create a new workspace, select 'Project > New Energia Sketch', Energia Version set to 18, select 'Built-in Examples > 01.Basics > Blink.ino', selected device: 'LaunchPad (Tiva C) w/ tm4c129 (120MHz), select 'Finish'. Right Click 'Blink" project in the Project Explorer, select "Build Pr
  3. 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
  4. Good morning. I've been using the MSP430 launchpad and programming it using Energia 18. Anyway, for the whole time I've been using Energia, it very often have to unplug and plug back in my device in order to send it another build. Have any of you seen this problem before? Sometimes it works without having to unplug the hardware, however, over 50% of the time, I have to unplug the LaunchPad in order to upload new code to it from Energia. It seems to get hung while attempting the upload. So, to overcome this, I unplug the Launchpad, click the Upload button again, usually get an
  5. Hi All, A few days ago we release a new version of the free Visual Micro plugin for Energia 0014 and Visual Studio 2013 Community Edition. Currently build and upload appears to work identically to the Energia Ide but it would be useful for others to test. One windows users report the upload not working which we guess is related to the start path that Visual Micro uses when running the upload command. It would be really useful for a few others to test especially with the cc3200. http://www.visualmicro.com/ Here is a screen-shot from earlier Energia releases in Visual Stu
  6. 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) 7.6.0.20140731-cvs Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http:
  7. Hi all, I am trying to debug the bootloader example in eclipse with the jlink debugger. And I am not sure about how to configure the jlink plugin in eclipse correctly, where to point the stack and the pc register due to the fact that the gcc linker script uses the VMA and the LMA for the sections and the bootcode is copied into RAM in the reset handler. The download seems to work correctly, but breakpoints are not reached correctly. I would like to start debugging at the beginning in the assembler code, to see the first steps of copying the bootloader code into RAM. Is it pos
  8. Hi 43oh folks! I wrote a quick blog post & tutorial on the www.energia.nu website. I wanted to walk through the process of setting up Code Composer Studio v6 to enable Energia sketch imports. This is a cool new feature that takes full advantage of the on-board hardware debugger that is available on our LaunchPad kits & allows developers to go beyond Serial.print(). This provides a nice migration path from Energia to CCS. Energia is great for rapid prototyping, but there are times when a true debugger could be helpful. With CCSv6, we can now import Energia sketches & get ful
  9. Hi all, I use TI's Debug Interface Box MSP-FET430UIF with a MSP430G2252. On the spy Bi wire I/O line is the High and Low level of the data. What I cannot understand is, why no a low level does not generate a RST of the controller. Can anyone give me an answer? Kindly Regards Ulrich.
  10. So you now build all of your projects on breadboard, and the Launchpad just gets used as a progammer/debugger adaptor. The 20 pin DIP socket gahters dust. I have put this to use by writing a SPI-UART adaptor that runs on a 2553 in the DIP socket, while using the Launchpad to debug my project. The project code can thus output console data using a bit-banged SPI output. This only consumes port pins, no timers or UARTS, and is not timing-critical, as the data output is synchronous. This shows how you would use it: ... and here it is on my desk... Code is at https://github.com
  11. Hello, I am using mspgcc to develop code and mspdebug to load to mcu. Now, I am trying to debug some code, and it seems to me that it is very hard to step through lines of code and set breakpoints on C code with mspdebug and console. I was wondering if there is a way to debug the mcu with some kind of debugging software with a UI such as the Hi-wave debugger. I would love to be able to develop my code using gVim and if possible also debug it with gVim. Thanks
  12. 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/Ja
  13. Hi, Since I started programming for MSP430 I've been looking for the MSP equivalent of "__asm int 3" (aka DebugBreak). I've come up with this fragment, tested on CCS 5.3.0: #ifndef NDEBUG // If debugger is attached and software breakpoints are enabled, DEBUG_BREAK will pause execution #define DEBUG_BREAK _op_code(0x4343) #else // Strip out DEBUG_BREAKs in final/release builds #define DEBUG_BREAK #endif Put this in a header file and you can then embed breakpoints in your code with a DEBUG_BREAK; statement. To reiterate what it says in the comment above: DEBUG_BREAK onl
  14. Hi, what do people suggest to use for debugging on Mac OSX when writing programs in Energia? Is using MSPDebug with the embedded msp430-gcc the best way to go? Or is perhaps a more complete solution like bsp430 a better way to go, with more controllable makefiles, etc? Cheers, H
×
×
  • Create New...