From f1dac60894a66971ff9eeb2fe7eef1d3e151a0b6 Mon Sep 17 00:00:00 2001 From: Alamy Liu Date: Thu, 6 Aug 2015 16:17:50 -0700 Subject: [PATCH] cortex-a: Fix "Detected core" number is always '0' Problem No matter what target->coreid is, it always shows Detected core 0 dbgbase: ... In dap_lookup_cs_component(), it decreases the core index value to zero in order to find the desired core. The reference to coreidx is necessary considering "a device which has nested ROM tables, with each core described in its own table." (by Paul Fertser). Change-Id: I9b56d45d6edf6639e748a625ab27787f8e5a5776 Signed-off-by: Alamy Liu Reviewed-on: http://openocd.zylin.com/2902 Tested-by: jenkins Reviewed-by: Matthias Welwarsky Reviewed-by: Andreas Fritiofson --- src/target/cortex_a.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/target/cortex_a.c b/src/target/cortex_a.c index 8ec870b5..86bf757e 100644 --- a/src/target/cortex_a.c +++ b/src/target/cortex_a.c @@ -2978,7 +2978,7 @@ static int cortex_a_examine_first(struct target *target) return retval; } LOG_DEBUG("Detected core %" PRId32 " dbgbase: %08" PRIx32, - coreidx, armv7a->debug_base); + target->coreid, armv7a->debug_base); } else armv7a->debug_base = target->dbgbase; -- 2.39.5