From: Cory Tusar <Cory.Tusar@zii.aero>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
Chris Healy <Chris.Healy@zii.aero>
Subject: [PATCH] Documentation: zii-imx7d-dev: Fix errors with openocd configuration script
Date: Thu, 29 Aug 2019 19:10:25 +0000 [thread overview]
Message-ID: <20190829191007.13644-1-cory.tusar@zii.aero> (raw)
When attempting to use the existing configuration file to bootstrap an
RMU2 board, openocd would consistently fail in the 'safe_reset' function
with a number of errors.
Disabling the internal reset handling (similar to what's done on the
i.MX7 Sabre boards) allowed barebox to download and run successfully.
Tested with openocd-0.10.0+dev-00924-g16496488 on a Zodiac RMU2.
Signed-off-by: Cory Tusar <cory.tusar@zii.aero>
Tested-by: Andrey Smirnov <andrew.smirnov@gmail.com>
---
Documentation/boards/imx/zii-imx7d-dev/openocd.cfg | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/boards/imx/zii-imx7d-dev/openocd.cfg b/Documentation/boards/imx/zii-imx7d-dev/openocd.cfg
index f971c3fb2..6056b8957 100644
--- a/Documentation/boards/imx/zii-imx7d-dev/openocd.cfg
+++ b/Documentation/boards/imx/zii-imx7d-dev/openocd.cfg
@@ -138,6 +138,12 @@ proc start_barebox { } {
resume $MX7_DDR_BASE_ADDR
}
+# disable internal reset-assert handling to
+# allow reset-init to work
+$_TARGETNAME.0 configure -event reset-assert ""
+$_TARGETNAME.1 configure -event reset-assert ""
+$_TARGETNAME_2 configure -event reset-assert ""
+
# hook the init function into the reset-init event
${_TARGETNAME}.0 configure -event reset-init { board_init }
--
2.23.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-08-29 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 19:10 Cory Tusar [this message]
2019-09-02 7:17 ` 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=20190829191007.13644-1-cory.tusar@zii.aero \
--to=cory.tusar@zii.aero \
--cc=Chris.Healy@zii.aero \
--cc=andrew.smirnov@gmail.com \
--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