From: Yasushi SHOJI <yashi@spacecubics.com>
Date: Sun, 29 Aug 2021 09:27:52 +0000 (+0900)
Subject: target: cortex_m: Fix a typo VECTRESET
X-Git-Tag: v0.12.0-rc1~525
X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=commitdiff_plain;h=3ae2583b48861c7cc8674b66984189e6f58dc666

target: cortex_m: Fix a typo VECTRESET

According to ARM Cortex M3 technical reference manual, it's
"VECTRESET" instead of "VECRESET".

Change-Id: Iff5534beac2b313cee6da3252d76d4d44a61eeed
Signed-off-by: Yasushi SHOJI <yashi@spacecubics.com>
Reviewed-on: https://review.openocd.org/c/openocd/+/6508
Tested-by: jenkins
Reviewed-by: Tarek BOCHKATI <tarek.bouchkati@gmail.com>
Reviewed-by: Antonio Borneo <borneo.antonio@gmail.com>
---

diff --git a/src/target/cortex_m.c b/src/target/cortex_m.c
index f3c8527cf3..08f2eb9117 100644
--- a/src/target/cortex_m.c
+++ b/src/target/cortex_m.c
@@ -1243,7 +1243,7 @@ static int cortex_m_assert_reset(struct target *target)
 		retval = ERROR_OK;
 	} else {
 		/* Use a standard Cortex-M3 software reset mechanism.
-		 * We default to using VECRESET as it is supported on all current cores
+		 * We default to using VECTRESET as it is supported on all current cores
 		 * (except Cortex-M0, M0+ and M1 which support SYSRESETREQ only!)
 		 * This has the disadvantage of not resetting the peripherals, so a
 		 * reset-init event handler is needed to perform any peripheral resets.