jtag
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
jtag [2016/01/13 08:57] – [scan chain] kingkevin | jtag [2016/01/18 17:08] – no SWO kingkevin | ||
---|---|---|---|
Line 33: | Line 33: | ||
This is newer variant of JTAG which requires only 2 signal lines instead of 4+. | This is newer variant of JTAG which requires only 2 signal lines instead of 4+. | ||
But but aware, they both have different pinouts on the connector. | But but aware, they both have different pinouts on the connector. | ||
+ | The second one offers 2 more power ports at the expense of JTAG TDI and TDO/SWO. | ||
- | These JTAG adapter | + | These JTAG adapters |
And ironically enough I in turn use them to program and debug STM32F1xx ARM Cortex M3 micro-controllers. | And ironically enough I in turn use them to program and debug STM32F1xx ARM Cortex M3 micro-controllers. | ||
Line 133: | Line 134: | ||
</ | </ | ||
+ | Now you can also use it, here with an STM32F1 micro-controller: | ||
+ | <code bash> | ||
+ | openocd --file interface/ | ||
+ | |||
+ | Open On-Chip Debugger 0.10.0-dev-00189-g554313b (2016-01-12-16: | ||
+ | Licensed under GNU GPL v2 | ||
+ | For bug reports, read | ||
+ | http:// | ||
+ | Warn : Adapter driver ' | ||
+ | Info : only one transport option; autoselect ' | ||
+ | adapter speed: 1000 kHz | ||
+ | adapter_nsrst_delay: | ||
+ | jtag_ntrst_delay: | ||
+ | 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' | ||
+ | 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: | ||
+ | </ | ||
===== tricks ===== | ===== tricks ===== | ||
Line 144: | Line 168: | ||
Thus it sometimes is useful to just list the TAPs available on a chain to know which devices are present. | 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 |
<code bash> | <code bash> | ||
jtag | jtag | ||
Line 190: | Line 214: | ||
Warn : AUTO auto1.tap - use "jtag newtap auto1 tap -irlen 5 -expected-id 0x16410041" | Warn : AUTO auto1.tap - use "jtag newtap auto1 tap -irlen 5 -expected-id 0x16410041" | ||
Warn : gdb services need one or more targets defined | Warn : gdb services need one or more targets defined | ||
+ | </ | ||
+ | |||
+ | '' | ||
+ | |||
+ | 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:// | ||
+ | <code bash> | ||
+ | openocd --file interface/ | ||
+ | |||
+ | Open On-Chip Debugger 0.10.0-dev-00189-g554313b (2016-01-12-16: | ||
+ | Licensed under GNU GPL v2 | ||
+ | For bug reports, read | ||
+ | http:// | ||
+ | hla_jtag | ||
+ | adapter speed: 100 kHz | ||
+ | Info : clock speed 100 kHz | ||
+ | Error: BUG: current_target out of bounds | ||
</ | </ |
jtag.txt · Last modified: 2024/01/07 17:49 by 127.0.0.1