David Brownell pisze:
With "this" being the warning about "-irmask 1" ... since
you have that particular hardware, you can test to see if
the config files even need to include those two optional
parameters for those TAPs.
I thought it was more complicated than "trial & error" <: If the results
like the one below show that it's fine, then... well... it's fine [;
When I use the current stm32.cfg file I get the runtime warning:
Warn : stm32.bs: nonstandard IR mask
but everything seems to work (OpenOCD connects, can flash, erase, halt
and run the chip). When I remove "-ircapture 0x1 -irmask 0x1" from the
cfg file the warning is gone and everything still works.
And if they don't ... you know how to submit patches. :)
Creating patches is simple, but other things in git are not [;
See the attachment.
4\/3!!
>From 4eed2f825b792ce46ebcc9e33d2e371c8ef8248c Mon Sep 17 00:00:00 2001
From: Freddie Chopin <freddie_cho...@op.pl>
Date: Sun, 1 Nov 2009 11:58:48 +0100
Subject: [PATCH] remove "-ircapture 0x1 -irmask 0x1" from stm32.cfg to get rid
of the runtime warning "stm32.bs: nonstandard IR mask"
---
tcl/target/stm32.cfg | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tcl/target/stm32.cfg b/tcl/target/stm32.cfg
index b5a8652..3473b1c 100644
--- a/tcl/target/stm32.cfg
+++ b/tcl/target/stm32.cfg
@@ -55,7 +55,7 @@ if { [info exists BSTAPID ] } {
# Connectivity line devices, Rev A and Rev Z
set _BSTAPID5 0x06418041
}
-jtag newtap $_CHIPNAME bs -irlen 5 -ircapture 0x1 -irmask 0x1 -expected-id
$_BSTAPID1 -expected-id $_BSTAPID2 -expected-id $_BSTAPID3 -expected-id
$_BSTAPID4 -expected-id $_BSTAPID5
+jtag newtap $_CHIPNAME bs -irlen 5 -expected-id $_BSTAPID1 -expected-id
$_BSTAPID2 -expected-id $_BSTAPID3 -expected-id $_BSTAPID4 -expected-id
$_BSTAPID5
set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME cortex_m3 -endian $_ENDIAN -chain-position
$_TARGETNAME
--
1.6.5.1.1367.gcd48
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
