From 20de5f43f2fd89208b3dffd5d4d52d4bb7135f87 Mon Sep 17 00:00:00 2001 From: Oystein Knauserud Date: Thu, 22 Dec 2022 11:32:41 +0100 Subject: [PATCH] Removed figures 14 and 15 from the debug chapter. Added not about level sensitivity of debug_req_i and that it should be kept asserted until the core can be observed to be halted. Signed-off-by: Oystein Knauserud --- docs/user_manual/source/debug.rst | 19 ++++--------------- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/docs/user_manual/source/debug.rst b/docs/user_manual/source/debug.rst index d3cf743d..14a8eab8 100644 --- a/docs/user_manual/source/debug.rst +++ b/docs/user_manual/source/debug.rst @@ -130,21 +130,6 @@ cycle(s) after ``rst_ni`` has been deasserted and ``fetch_enable_i`` has been sa core will transition between having its ``debug_halted_o`` or ``debug_running_o`` pin asserted depending whether the core is in debug mode or not. Exactly one of the ``debug_havereset_o``, ``debug_running_o``, ``debug_halted_o`` is asserted at all times. -:numref:`debug-running` and show :numref:`debug-halted` show typical examples of transitioning into the ``running`` and ``halted`` states. - -.. figure:: ../images/debug_running.svg - :name: debug-running - :align: center - :alt: - - Transition into debug ``running`` state - -.. figure:: ../images/debug_halted.svg - :name: debug-halted - :align: center - :alt: - - Transition into debug ``halted`` state The key properties of the debug states are: @@ -154,6 +139,10 @@ The key properties of the debug states are: point in time, then the |corev| might transition through the ``running`` state on its ways to the ``halted`` state. * If ``debug_req_i`` is asserted during the ``running`` state, the core will eventually transition into the ``halted`` state (typically after a couple of cycles). + .. note:: + Due to ``debug_req_i`` being level sensitive, it is not guaranteed that a short pulse on ``debug_req_i`` will cause |corev| to enter its ``halted`` state in any of the bullets above. + To achieve (eventual) transition into the ``halted`` state, ``debug_req_i`` must be kept asserted until ``debug_halted_o`` has been asserted. + .. _ebreak_behavior: EBREAK Behavior