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@xxxxxxxx>
---
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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
