From: Tim Newsome <tim@sifive.com>
Date: Mon, 3 Jul 2017 17:36:03 +0000 (-0700)
Subject: Don't clear triggers during execution.
X-Git-Url: https://git.libre-soc.org/?p=riscv-tests.git;a=commitdiff_plain;h=a744e98f528355335801d9a434fb95f8ad4a5aed

Don't clear triggers during execution.

This shouldn't affect triggers set by the debugger, because running code
can't change those. When it does affect them, it breaks Hwbp1 which sets
the breakpoint before running the program.
---

diff --git a/debug/programs/entry.S b/debug/programs/entry.S
index ff8ae30..302d409 100755
--- a/debug/programs/entry.S
+++ b/debug/programs/entry.S
@@ -64,15 +64,6 @@ handle_reset:
   # initialize stack pointer
   la sp, stack_top
 
-  # Clear all hardware triggers
-  li    t0, ~0
-1:
-  addi  t0, t0, 1
-  csrw  CSR_TSELECT, t0
-  csrw  CSR_TDATA1, zero
-  csrr  t1, CSR_TSELECT
-  beq   t0, t1, 1b
-
   # perform the rest of initialization in C
   j _init