Other Parts Discussed in Thread: UNIFLASH, CODECOMPOSER
Tool/software: Code Composer Studio
odd things do happen to me these days.
I was playing around with the voltage supervisor, had the following code:
SVSCTL |= 0x60; // 2,5V SVSCTL |= 0x80; // 2,8V SVSCTL |= PORON;
I did not comment out the first line so in aggregation the bits were set to 3,7 V PORON generation,
so of course if i treat my MSP normally with 3,3V the PORON is always set, holding the device in the reset state!!!
I did try the uniflash tool, and different settings in CodeComposer, it will simply not detect my module anymore, could I really brick my device this halarious way?
I thought the JTAG debug interface would recover the device from almost any state.
Maybe someone has an easy answer, or maybe my problem is related to something different.
Thanks a lot.
Turns out, you can lock yoursefl out permanently from flashing your device via JTAG if setting the POR and the level too high, I just had to rise the Vcc to aorund 3,9V (higher than my 3,8 V level)
and I can now debug my device again. I thought or assumed i could always write on my device no matter what I did set in software to it.