12-27-2018, 09:30 AM
Hello again!
The documentation for the ri5cy core, although getting better, is still a little "light" on details for the debugger hardware.
Is there any facility available for accessing memory whilst in debugging mode?
if not, how is it proposed that memory should be accessed when debugging?
what would be the suggested mechanism for implementing a breakpoint mechanism such the executing programme can be run up to a point then the debugger activated?
(I already have a simulation where I can single step the core at a specified simulation clock count, in reality this needs to be at a specified PC).
Thanks in advance
The documentation for the ri5cy core, although getting better, is still a little "light" on details for the debugger hardware.
Is there any facility available for accessing memory whilst in debugging mode?
if not, how is it proposed that memory should be accessed when debugging?
what would be the suggested mechanism for implementing a breakpoint mechanism such the executing programme can be run up to a point then the debugger activated?
(I already have a simulation where I can single step the core at a specified simulation clock count, in reality this needs to be at a specified PC).
Thanks in advance