I was using the I2C example from "slac463a" >> "msp430g2x21_usi_16.c" with a handful of slight modifications. Everything was working swimmingly and then suddenly when debugging everything went haywire (I think I might have put my computer to sleep without terminating debugging). I stepped away for approximately an hour and when I returned everything seemed to be broken. Ultimately, when everything went haywire I went back to the original I2C example sans any modifications to ensure that it worked. Alas, it did not. The CPU or Debugger was resetting itself - every time I looked at PORIFG or OFIFG they were set and the normal current draw of my circuit was cut approximately in half. Also, I wasn't getting to any breakpoints past my initializations. Funny thing is I went back and tested one of the PWM examples "msp430g2xx1_ta_16.c" and everything seemed to work fine sans the I2C. I didn't investigate past this - was too busy tearing my hair since I had my application working just fine only a short hour ago.
Long story short I re-installed Code Composer and what do you know I was pulling my hair out for nothing. Everything works fine again.
I wanted to ask the questions: What would cause the "resetting" behavior in CC and/or the MSP430 USB Debugging tool? And, is there anything anyone could suggest short of re-installing everything to solve this type of problem in the future? I apologize in advance if there is an answer floating out there on E2E - I haven't found it yet.
Other note: Outside of the Power On Reset flag and Oscillator Fault flag at one point I moved over to FET-PRO430 from Elprotronics to just program the part and I got a funny error: DCO calibration constants could not be verified. I'd never seen that before. When using CC I found the constants to contain values that seemed reasonable (not 0xFF). My motivation for moving over to FET-PRO430 was I suspected there might have been a conflict with my logic analyzer and the MSP-FET430UIF debugger. Also should mention I have not hooked up my logic analyzer while debugging this go around. I've been watching the variables of interest in the CC which is slower, but removed one of the unknowns from the situation. Anyone know of a conflict between Saleae Logic and the MSP-FET430UIF?
