| ??? 05/17/06 09:45 Read: times |
#116361 - breakpoints in monitors Responding to: ???'s previous message |
Matthias Arndt said:
a) breakpoint definable in memory by the monitor
This will mean using selfmodifying code and implies use on systems with RAM. ... or internal FLASH with IAP or external, mcu-programmable FLASH. And, speaking of "selfmodifying code" in this case is exagerration. Caveats as usually: in '51, there is no single-byte instruction to accomplish the "trap", so one is always in the risk of overwriting the following bytes if the "breakpointed" instruction is single-byte (the usual example is a breakpoint on a ret, followed by an another routine). I hope you have made a research of available monitors with their pluses and minuses before you started to make your own. It would be nice to see a comparison here. Jan Waclawek |
| Topic | Author | Date |
| amon52 (work in progress) | 01/01/70 00:00 | |
| v0.4 released | 01/01/70 00:00 | |
| implementing breakpoints | 01/01/70 00:00 | |
| breakpoints in monitors | 01/01/70 00:00 | |
| breakpoints | 01/01/70 00:00 | |
| more | 01/01/70 00:00 | |
| good idea with the EI0 | 01/01/70 00:00 | |
| no and yes | 01/01/70 00:00 | |
| why not for rapid prototyping? | 01/01/70 00:00 | |
| how would you prototype something that | 01/01/70 00:00 | |
| I agree | 01/01/70 00:00 | |
| the smarter monitors work like this | 01/01/70 00:00 | |
| not quite as smart | 01/01/70 00:00 | |
| yep | 01/01/70 00:00 | |
SBC monitor? | 01/01/70 00:00 | |
| do you want a REAL challenge? | 01/01/70 00:00 | |
| It's enough of a challenge | 01/01/70 00:00 | |
| I agree | 01/01/70 00:00 | |
| monitors ... have a look here ... | 01/01/70 00:00 | |
| cheers | 01/01/70 00:00 |