Differences

This shows you the differences between two versions of the page.

--- jtag [2016/01/13 08:57] – [scan chain] kingkevin
+++ jtag [2016/01/13 10:19] – [scan chain] kingkevin
@@ Line 133: / Line 133: @@
 </code>
+Now you can also use it, here with an STM32F1 micro-controller:
+<code bash>
+openocd --file interface/altera-usb-blaster.cfg --file target/stm32f1x.cfg
+Open On-Chip Debugger 0.10.0-dev-00189-g554313b (2016-01-12-16:26)
+Licensed under GNU GPL v2
+For bug reports, read
+	http://openocd.org/doc/doxygen/bugs.html
+Warn : Adapter driver 'usb_blaster' did not declare which transports it allows; assuming legacy JTAG-only
+Info : only one transport option; autoselect 'jtag'
+adapter speed: 1000 kHz
+adapter_nsrst_delay: 100
+jtag_ntrst_delay: 100
+none separate
+cortex_m reset_config sysresetreq
+Info : No lowlevel driver configured, will try them all
+Info : usb blaster interface using libftdi
+Error: unable to get latency timer
+Info : This adapter doesn't support configurable speed
+Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
+Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020, part: 0x6410, ver: 0x1)
+Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
+</code>
 ===== tricks =====
@@ Line 144: / Line 167: @@
 Thus it sometimes is useful to just list the TAPs available on a chain to know which devices are present.
-This is easily done with urJTAG:
+This is easily done with urJTAG (here with the USB Blaster):
 <code bash>
 jtag
@@ Line 190: / Line 213: @@
 Warn : AUTO auto1.tap - use "jtag newtap auto1 tap -irlen 5 -expected-id 0x16410041"
 Warn : gdb services need one or more targets defined
+</code>
+''0x3ba00477'' corresponds to the Cortex-M3 TAP, and ''0x16410041'' to the boundary scan TAP, as documented in the [[http://www.st.com/web/en/resource/technical/document/reference_manual/CD00171190.pdf|STM32F1xx reference manual]].
+While the ST-Link v2 is mainly meant to be used as SWD adapter, it also supports JTAG. Both are implemented with the High Level Adapter (HLA) driver. But it seems scan chain is [[http://sourceforge.net/p/openocd/mailman/message/31038247/|not supported by the HLA]].
+<code bash>
+openocd --file interface/stlink-v2.cfg -c "transport select hla_jtag" -c "adapter_khz 100"
+Open On-Chip Debugger 0.10.0-dev-00189-g554313b (2016-01-12-16:26)
+Licensed under GNU GPL v2
+For bug reports, read
+	http://openocd.org/doc/doxygen/bugs.html
+hla_jtag
+adapter speed: 100 kHz
+Info : clock speed 100 kHz
+Error: BUG: current_target out of bounds
 </code>