I have seen some codes,
nop is added after bis & written in comments- set breakpoint here.
I also noted that as soon as bis instruction is executed, debugger first goes to next instrucion & then go to ISR.
Hi,
some MSP430 have an hardware bug that could corrupt the SP/PC if there was no NOP after the BIS instruction. This problem is described for example in the CC430 errata as CPU24, CPU25 and CPU26 bug.
Aamir AliI also noted that as soon as bis instruction is executed, debugger first goes to next instrucion & then go to ISR.
So if you want to set a breakpoint after a bis instruciton that enables GIE or LPM, put a NOP behind it and place a breakpoint on the next, real instruction.This ensures that the breakpoint is hit after LPM has ended and/or the ISR has been executed.
_____________________________________Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.If you cannot discuss your problem in the public, feel free to start a private conversation: click on my name and then 'start conversation'. But please do so only if you really cannot do it in a public thread, as I usually read all threads. And I prefer to answer where others can profit from it (or contribute to it) too.