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 <redacted>
Tested-by: Andrey Smirnov <redacted>
---
 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