| ??? 09/04/07 07:37 Read: times |
#143973 - trace in monitor Responding to: ???'s previous message |
Richard Erlacher said:
Aren't you now debugging one thing and delivering another? You can do that, but you can't claim the system is debugged as delivered. This is absolutely the same kind of monitor as you advocate to use (except in the limited code space you couldn't fit the fancy stuff like disassembly or fancy registers display, so you need to offload it to the PC). Richard Erlacher said:
Consider, BTW, how many times you would have to rewrite a given sector of the FLASH. Aren't they limited to some finite number of rewrites? In contemporary '51s this is in the order of 10k. Richard Erlacher said:
How many times would you have to rewrite a sector if you were running a trace? Zero. I in http://www.8052.com/forum/read.phtml?id=143895 said:
It's enough to rewrite the code space to establish the static breakpoints. Trace/singlestep shall be performed via the "one instruction after reti while interrupt pending" mode, hence does not require any code memory rewrite. Richard Erlacher said:
I haven't yet delivered an 805x system that required the code space be rewritten as part of its task. The only time it's necessary is in development or debugging. It may someday be necessary, and then, I would probably include, amopng the deliverables, some code that's associated with writing the code space, but only if it's necessary to accomplish the assigned task, and not as a debugging aid. I don't understand. Do you normally count the debugging tool you've used during development as a deliverable? Further, if I'd develop sort of a formal proof that the code running with a "disarmed" monitor performs absolutely the same way as the code completely without the monitor, would you see any problem of using the monitor during development? This is easy: if the monitor code just sits there and gets never called, it must have been a very flaky application code which would take its presence into account. Does it make any difference then, whether the monitor wrote to code space during development or not? JW |
