This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP-EXP430G2: Debugging process

Part Number: MSP-EXP430G2

For the stuff I do with MSP430 parts, I've just used the conTEXT editor, the Naken assembler, the command line Flasher and the G2 Launchpad.  No IDE.  But after spending three hours yesterday trying to find why my code was causing a reset, and not seeing the error the first 100 times I looked at it, I'm thinking that some form of single-stepping would be nice to have.  But I've never underdstood what software and hardware is needed to do that.  This would be for the MSP430G parts like the G2553.  Can I get there from here without installing CCS or IAR?

  • Hi George,

    It is recommended to download the latest version of Code Composer Studio or other supported IDE's for single-stepping.

    With regards to your issue, If you're using interrupts, take a look at this resolved thread - this user encountered a similar obstacle with an unwanted reset occurring on the G2553.

    Best,

    - Chris

  • Christopher Vendette said:

    Hi George,

    It is recommended to download the latest version of Code Composer Studio or other supported IDE's for single-stepping.

    With regards to your issue, If you're using interrupts, take a look at this resolved thread - this user encountered a similar obstacle with an unwanted resent happening on the G2553.

    Best,

    - Chris

    Thanks Christopher.  I was hoping for something smaller and lighter than CCS.  Would the Cloud version work?

    I am using interrupts.  In fact all activity takes place in service routines.  But my problem was a lot simpler than that.  It was typing "CALL Display" instead of the correct "CALL #Display".  So it was trying to call to an illegal address (probably FFFF) that caused the reset.  Just a dumb mistake.

    It turns out that my Naken assembler comes with a utility file that will step through a program, but it does that from the .hex file, not from the chip actually running the program.  That might be fine for some things, but when testing a GPIO port in input mode, and branching depending on the result, I don't think that would work.  You would need to do the debugging in-circuit.

  • George,

    CCS Cloud should also work as it allows for single step and breakpoints.

    Please see the key differences between the CCS Desktop and Cloud version here.

    - Chris

**Attention** This is a public forum