mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Cory Tusar <Cory.Tusar@zii.aero>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Cc: Chris Healy <Chris.Healy@zii.aero>
Subject: [PATCH] Documentation: zii-vf610-dev: Fix 'halt' in openocd configuration script
Date: Tue, 20 Aug 2019 22:17:36 +0000	[thread overview]
Message-ID: <20190820221638.19492-1-cory.tusar@zii.aero> (raw)

When attempting to use the existing configuration file to bootstrap
an SCU4 AIB board, openocd would consistently fail on the 'halt' command
with a "Target not examined yet" error.  Dumping target information
showed that vf610.cpu1 was the active target, rather that vf610.cpu0.

Adding a command prior to the halt to explicitly set the target core
resulted in proper operation.

Tested with openocd-0.10.0+dev-00924-g16496488 on a Zodiac SCU4 AIB.

Signed-off-by: Cory Tusar <cory.tusar@zii.aero>
---
 Documentation/boards/imx/zii-vf610-dev/openocd.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/boards/imx/zii-vf610-dev/openocd.cfg b/Documentation/boards/imx/zii-vf610-dev/openocd.cfg
index 222f48711..5127c7623 100644
--- a/Documentation/boards/imx/zii-vf610-dev/openocd.cfg
+++ b/Documentation/boards/imx/zii-vf610-dev/openocd.cfg
@@ -258,6 +258,7 @@ proc safe_reset {} {
 proc start_barebox { } {
 	set VF610_DDR_BASE_ADDR 0x80000000
 	echo "Bootstrap: Loading Barebox"
+	targets vf610.cpu0
 	halt
 	load_image images/barebox-zii-vf610-dev.img $VF610_DDR_BASE_ADDR bin
 	arm core_state arm
-- 
2.23.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2019-08-20 22:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 22:17 Cory Tusar [this message]
2019-08-20 22:25 ` Andrey Smirnov
2019-08-23  8:58 ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190820221638.19492-1-cory.tusar@zii.aero \
    --to=cory.tusar@zii.aero \
    --cc=Chris.Healy@zii.aero \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox