| ??? 09/04/07 11:35 Read: times |
#143983 - but how do you generate the interrupt? Responding to: ???'s previous message |
Keep in mind that I prefer not to use a PC and software running on it to perform a debug session. Assume I'm using a terminal.
Now, how do you propose to make a series of breakpoints work in the way you suggest? Yes, 10K rewrites ... how many rewrites does it take to trace through a 1k-byte code segment containing N passes through M loops? Isn't a trace just a series of repeated and moved breakpoints? If so, then there would be N rewrites per opcode per pass through each loop. There might be another way, but I've not yet seen it. Jan Waclawek said:
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). The monitor I prefer is 8KB in size and uses no "fancy" display or display features. It DOES, however, assemble and disassemble code. Since the DS89C450 has 64KB of FLASH code space, I have no problem with code size ... yet. Are you suggesting one should ship such a monitor as part of the deliverable code? I would normally be hostile to such a notion. I don't allow code that isn't directly traceable to a system requirement to be incorporated in a deliverable code set. In many cases, the serial ports aren't even used. RE |
