Well before anyone could sensibly answer those questions, you'd need to define exactly what is different about your debugging version and your production version.



I don't know, what if? Configure and use the ICE properly and it won't happen. Perhaps an example so I can understand what you're talking about?



Then clearly, you need to perform some detailed tests with your production version and consider ways of getting useful information out of the tests without using an ICE.



Well it wouldn't help at all which is why your code and procedures should be structured so you CAN debug an error found in testing.

I'm not really sure what your argument is Erik. If you can't fit unoptimized code into the available space or if it is not fast enough, then you have to optimize it. You have no choice other than going for a bigger/faster chip, which is a nice defeatist way of increasing unit cost.

If you do optimze, then an ICE isn't likely to work well, so you have to look to other methods for debugging and testing. That's just a given.

If the kind of problems you're talking about cause so much hassle, then I'm sorry to say it sounds like you're not approaching testing properly.

Out of curiosity Erik, what language do you develop most your firmware in?

Matt.