Hi all,
based on previous problem description, with software breakpoint being
constantly hit and not allowing single stepping. Memory has been
changed and replaced back with correct instruction (breakpoint does
not exist in memory anymore, this can be see by memory dump). Caches
were flashed by commands :
printf ("Invalidate I$\n");
retval = arm966e_write_cp15(target, 0x0f, 0);
printf ("Invalidate D$\n");
retval = arm966e_write_cp15(target, 0x0e, 0);
These commands for cache flushing are based on ARM946E scan chain 15,
as presented:
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.set.arm9/index.html
This makes me think that problem is not in caches.
Question is:
can anybody with some more experience in OpenOCD give some hints of
software breakpoint placing and removing mechanisms and SIGINT
handling. Where to look at in the code and inspect why the same
(non-existing) breakpoint is hit over and over again.
In short, which part of OpenOCD code handles software berakpoints management.
BR,
Drasko
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
