If the prototype is powered up with nothing attached, nothing works.
If the prototype is powered up with the BDM already attached, but no debugger running, nothing works.
If the prototype is powered up, and then the BDM is attached (no debugger), then it seems to work correctly.
If the prototype is powered up with the BDM already attached, and then the debugger is launched using "Hotsync", then it will sometimes work. (If I then have the debugger stop the prototype, the debugger shows the prototype in a sane place, suggesting it is/was executing code correctly.)
Can anyone offer insights as to what we might have done wrong?
Schwab
peg wrote:Sometimes this can be that you only single step in the debugger and don't run for long enough to trip the COP.
I don't believe so. I've done hours-long continuous runs within the debugger, and the COP is reset in several places.
Or that you are displaying variables in the debugger (and so reading them) that you are not doing properly in your code (e.g. status registers neccesary to clear interrupt flags)
That is an interesting thought. Will closing the memory and data windows be sufficient to test this hypothesis? (That may not explain the starts-working-after-attaching-BDM-pod observation, however.)
Schwab