• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 760 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/MSP-EXP430G2: Issue -- Inconsistent functionality with interrupts and other usage issues with CCS V7

Robert Nerison
Prodigy 30 points
Part Number: MSP-EXP430G2


Tool/software: Code Composer Studio

The board is not recognizing interrupts on button pushes and other frustrating behavior of the like. I can run a debug once and a program will work perfectly and then I can rerun the debug and there is no response from any inputs, or interrupts.  It will typically work on the first try on a fresh launch of CCS, but follow up runs will not work until CCS is closed and relaunched.  This is also causing problems with using clocks/timers as interrupts... they don't really work. In addition to this, as of today,  a new intermittent issue has arisen wherein I get an "error initializing emulation could not find MSP - FET430-UIF on specified com port" error upon running debug.  If I retry -- it works the next time.

I have read through almost the entirety of the "Programmable Microcontrollers with applications for MSP 430 CCS" and have coded out many of the projects as well as assembled the appropriate circuitry.  At this point I understand the board quite well, but I am convinced there is a software issues with the newest version of CCS.  After having lots of unexpected behavior I went ahead and redownloaded a fresh install and the issue seemed to cease for a single day (version ccs 7.2  and now the issue has returned.  I found that there was already a new update available as of this morning and I installed it hoping it might cure the issue, but it had no effect.

I have multiple new msp 430's (msp 430G2553) and they all exhibit the same issue so I am certain that it is a software issue and not a hardware issue.  I am currently running Win 10.  All settings in the CCS desktop IDE are set to the default values that they installed with and worked fine yesterday.  This has been an ongoing issue and continuously reinstalling CCS doesn't seem to be the answer.

Please assist. 

  • 0
    TI__Guru**** 473781 points

    Hi Robert,

    Robert Nerison said:
    then I can rerun the debug and there is no response from any inputs, or interrupts

    when you rerun the debug, do you mean restarting the program (set PC to entry point) and just pressing the "resume" button, or are you actually restarting a debug session (not restarting CCS but just restarting the debugger)?

    And do you ever get these issues when running the program without the debugger attached?

    Robert Nerison said:
    but I am convinced there is a software issues with the newest version of CCS.

    Are these issues a fairly recent development - after you upgraded you CCS version? If so, what version were you on when things worked without issue?

    Would it be possible to share your project with me? If you wish to share it privately, please start a private conversation with me.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 30 points
    when you rerun the debug, do you mean restarting the program (set PC to entry point) and just pressing the "resume" button, or are you actually restarting a debug session (not restarting CCS but just restarting the debugger)?

    Yes, A complete build and restart of the debugger (terminate existing run). The only time it will work again is if I close out of CCS and restart/open CCS and rerun the program again.

    And do you ever get these issues when running the program without the debugger attached? Haven't tried and not entirely certain of what you mean. All of the programs I have been making have been usb connected from my pc to the microcontroller. The only run option that CCS offers as far as I am aware is in debug mode. If you could clarify your question with a screen shot and an arrow of what one would do to acheive this that would be helpful.

    Are these issues a fairly recent development - after you upgraded you CCS version? If so, what version were you on when things worked without issue?

    These issues have been non-stop. I installed my first CCS which was v7.0 a month or two ago and it was never ending. I attempted to update yesterday and the update failed so I uninstalled and did a fresh install of the latest version (7.2) and it worked fine all day yesterday. As of this morning I attempted to run a simple program (the one below) and it worked once and then would not work again unless I completely close CCS and reopen and rebuild/run the program. As of this morning I found another update and installed it and nothing has changed.

    It won't even run something as elementary as the following more than once without exiting CCS and restarting the whole program.

    #include <msp430.h>
    #define LED BIT0
    #define BUTTON BIT3

    void main(void)
    {
    WDTCTL = WDTPW + WDTHOLD;


    // Configure LED on P1.0
    P1DIR |= LED; // P1.0 output
    P1OUT &= ~LED; // P1.0 output LOW, LED Off

    // Configure Switch on P1.2
    P1REN |= BUTTON; // P1.3 Enable Pullup/Pulldown
    P1IE |= BUTTON; // P1.3 Enable Interrupt
    P1IES |= BUTTON; // P1.3 Hi/Lo edge
    P1IFG &= ~BUTTON; // P1.3 IFG cleared just in case

    //_EINT(); // Enables global interrupts -- all 4 interrupt calls work
    //__enable_interrupt();
    //_enable_interrupts;
    __bis_SR_register(GIE);
    while(1);
    }



    // Port 1 interrupt service routine
    #pragma vector=PORT1_VECTOR
    __interrupt void Port_1(void)
    {
    P1IFG &= ~BUTTON; // P1.3 IFG cleared
    P1OUT ^= LED; // Toggle LED at P1.0

    }

    Rob
  • 0 in reply to Ki
    Prodigy 30 points
    I should also note that if I run the program that I included below and let's say it works. If I then terminate the run and rebuild it and rerun it it will typically not work again, but I just found out that once I discovered that it doesn't run if I unplug the usb from the micro controller and then replug it in, then it will start working with out having to do anything else. Maybe that my help pinpoint the issue.