CuVoodoo

the sorcery of copper

User Tools

Site Tools


jtag

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
jtag [2017/09/06 14:32] – [Black Magic Probe] kingkevinjtag [2024/01/07 17:49] (current) – external edit 127.0.0.1
Line 61: Line 61:
 {{:jtag:mb936_case-front.jpg?0x150|case front}} {{:jtag:mb936_case-front.jpg?0x150|case front}}
 {{:jtag:mb936_case-back.jpg?0x150|case back}} {{:jtag:mb936_case-back.jpg?0x150|case back}}
-{{:jtag:mb936_internal-front.jpg?0x150|internal front}} 
 {{:jtag:mb936_internal-front2.jpg?0x150|internal front}} {{:jtag:mb936_internal-front2.jpg?0x150|internal front}}
 {{:jtag:mb936_internal-back.jpg?0x150|internal back}} {{:jtag:mb936_internal-back.jpg?0x150|internal back}}
Line 68: Line 67:
 It comes in the same box, with the same cables, the enclosure is the same, even the board name has been taken over (MB936), but the board isn't the same. It comes in the same box, with the same cables, the enclosure is the same, even the board name has been taken over (MB936), but the board isn't the same.
 The BOM doesn't match with the [[http://www.st.com/resource/en/bill_of_materials/st-link_v2_bom.zip|original]].\\ The BOM doesn't match with the [[http://www.st.com/resource/en/bill_of_materials/st-link_v2_bom.zip|original]].\\
-The original adapter come with ESD protection, protection resistors, and a transceiver to allow operating with target signal levels of 1.65V to 5.5V.+The original adapter comes with ESD protection, protection resistors, and a transceiver to allow operating with target signal levels of 1.65V to 5.5V.
 This is completely missing on the clone since the connector pins are directly connected to the micro-controller. This is completely missing on the clone since the connector pins are directly connected to the micro-controller.
 Thus it only supports target signal levels of 3.3V and sometimes 5V since the pins are 5V tolerant. Thus it only supports target signal levels of 3.3V and sometimes 5V since the pins are 5V tolerant.
Line 74: Line 73:
 For $9 you can't expect more, and if you want a cheap adapter I recommend the other ones (see below). For $9 you can't expect more, and if you want a cheap adapter I recommend the other ones (see below).
  
-==== ST-LINK V2 aluminium ====+==== mini ST-LINK V2 ====
  
 These adapters come in a small dongle sized aluminium case. These adapters come in a small dongle sized aluminium case.
 They supports SWD, and SWIM (for STM8), but not JTAG. They supports SWD, and SWIM (for STM8), but not JTAG.
 +Also the RST signal (required for SWIM) is not controllable as SRST in SWD mode (at least not by OpenOCD).
  
-At $2.5 they are the cheapest clones you can find.\\ +For less than $2they are the cheapest SWD programmer you can find. 
-One trick to get this ridiculously low price is to use STM32F101 micro-controllers. +I also like to use them as development board when I just need a USB dongle with just few signals (up to 4).
-Compared to the STM32F103 micro-controllers they offer less functionalities, like USB ... yet this is a USB dongle+
-Well this is because these micro-controllers use the same die, but if not all STM32F103 feature tests pass after production they get packages as STM32F101, but it seems that USB still works well enough. +
-At least this is my guess. +
-It would be interesting to check if the other STM32F103 peripherals normally not present on the STM32F101 work as well, but I wouldn't rely on these. +
-After all, they are probably marked as STM32F101 for good reason.\\ +
-Similarly the STM32F103C8 is only rated having 64 kB of flash because it didn't pass the flash test, compared to the 128 kB for the STM32F103CB, but they very often have more (you can verify by read/writing and check for errors).+
  
-Several board versions exist and it is hard to know what you will get. +Numerous board variants exist and it is hard to know what you will get. 
-Always check the pinout on the aluminium case since this also varies.+Always check the pinout on the aluminium case and on the PCB since this also varies
 +Here are the board variants I got, in chronological order.
  
 === 2014-06-22 ST-LINK V2 === === 2014-06-22 ST-LINK V2 ===
Line 97: Line 92:
 {{:jtag:alu_board_back.jpg?0x100|}} {{:jtag:alu_board_back.jpg?0x100|}}
  
-I've also reversed the {{:jtag:alu.pdf|schematic}} for this board.+I've reversed the {{:jtag:alu.pdf|schematic}} for this board
 + 
 +One trick to get this ridiculously low price is to use STM32F101 micro-controllers. 
 +Compared to the STM32F103 micro-controllers they offer less functionalities, like USB ... yet this is a USB dongle! 
 +Well this is because these micro-controllers use the same die, but if not all STM32F103 feature tests pass after production they get packages as STM32F101, but it seems that USB still works well enough. 
 +At least this is my guess. 
 +It would be interesting to check if the other STM32F103 peripherals normally not present on the STM32F101 work as well, but I wouldn't rely on these. 
 +After all, they are probably marked as STM32F101 for a good reason.\\ 
 +Similarly the STM32F103C8 is only rated having 64 kB of flash because it didn't pass the flash test, compared to the 128 kB for the STM32F103CB, but they very often have more (you can verify by read/writing and check for errors).
  
 One other nice trick they used is to have twos LEDs on the same pin (PA9): One other nice trick they used is to have twos LEDs on the same pin (PA9):
Line 105: Line 108:
   * when PWM output is used, you can mix the two colors (red and blue) quite well due to the persistence of vision (also because the LEDs are next to each other and the small hole in the case is in the center).   * when PWM output is used, you can mix the two colors (red and blue) quite well due to the persistence of vision (also because the LEDs are next to each other and the small hole in the case is in the center).
  
-=== swapped ===+=== alternative pinout ===
  
 {{:jtag:reverse-gnd_case-front.jpg?0x100|}} {{:jtag:reverse-gnd_case-front.jpg?0x100|}}
Line 121: Line 124:
  
 This one has an "M" logo instead of the ST logo, probably corresponding to the "MX-LINK V2" marking on the board. This one has an "M" logo instead of the ST logo, probably corresponding to the "MX-LINK V2" marking on the board.
 +
 +=== SWDIO/SWCLK swap ===
 +
 +{{:jtag:stlink_swap_case.jpg?0x100|}}
 +{{:jtag:stlink_swap_front.jpg?0x100|}}
 +{{:jtag:stlink_swap_back.jpg?0x100|}}
 +
 +This variant uses an STM32F103.
 +It seems this micro-controller got so popular that it is now cheaper than the STM32F101 (with less features).
 +The annoying details of this variant is that the SWDIO and SWCLK signal described on the pinout engraved in the aluminium case are swapped.
 +This shows again the importance of also checking the pinout on the board itself, else you can waste a couple of hours debugging.
 +
 +=== QFN ===
 +
 +{{:jtag:stlink_qfn_case.jpg?0x100|}}
 +{{:jtag:stlink_qfn_front.jpg?0x100|}}
 +{{:jtag:stlink_qfn_back.jpg?0x100|}}
 +
 +This variant uses an STM32F103 in the UFQFN-48 package.
 +This is just a couple of cents cheaper than the more traditional TQFP-48 package, but this is enough en mass to change the footprint on the board.
 +
 +=== MINI ST-Link V2E ===
 +
 +{{:jtag:mini_st-link_v2e-case.jpg?0x100|}}
 +{{:jtag:mini_st-link_v2e-front.jpg?0x100|}}
 +{{:jtag:mini_st-link_v2e-back.jpg?0x100|}}
 +
 +Instead on an STM32F103, this dongle uses a [[http://www.cksic.com/en/|CKS]] [[http://www.cksmcu.com/cn/promcu-14.html|CKS32F103]] (sometimes CS32F103)  ({{ :jtag:ic_mcu_cks_cks32f103xb.pdf|chinese datasheet}}, {{ :jtag:ic_mcu_cks_cks32f103xb_en.pdf|datasheet translated to english}}).
 +I've seen pin compatible alternatives (ST STM8S003 vs Nuvoton N76E003), even architecture compatible (ST STM32F103 vs GigeDevice GD32F103), but they always had some differences (architecture, electrical pin properties, registers, ...).
 +The CS32F103 seems like a complete clone of the STM32F103 (exact same pinout, architecture, registers).
 +So far I could not not see any difference (I tested flash, USB, SWD).
 +I guess this micro-controller is so popular that it was just a question of time until it was ripped-off.
 +To check if this is a complete clone you could decapsulate the chip and compare the silicon die, or check the errata behaviour (I can't imagine they re-implemented it themselves, up to the mistakes).
 +The next step would be to have a CS32F103 chip in a package marked as STM32F103.
 +
 +== GC ==
 +
 +{{:jtag:stlink_gc_case.jpg?0x100|}}
 +{{:jtag:stlink_gc_top.jpg?0x100|}}
 +{{:jtag:stlink_gc_bottom.jpg?0x100|}}
 +
 +Most ST-LINK minis which I get now use the CKS32 chip.
 +I'm a bit sad because the CS32F103C8 really only has the advertised 64 KB of flash, while the STM32F103C8 actually has 128 KB (e.g. what the STM32F103CB has), and when you have a lot of debugging strings in your firmware, you very soon reach the limit of the 64 KB.
 +Thus, on my quest to find ST-LINK minis with STM32F103 (e.g. where the ground pin is not between SWDIO and SWCLK) I landed on this one.
 +Sadly it also does not use a STM32F103, but a STM32GC102C8.
 +I have no idea what this chip is.
 +The GC series does not exist (at least ST doesn't mention it anywhere), and it predates the new G series.
 +I'm not sure if this was to save cost, because this is the first board I see with 2 ESD protections (one for USB, the other for SWDIO/SWCLK in addition to the inline protection resistors, and none for RST/SWIM).
 +
 ==== Baite ==== ==== Baite ====
  
Line 130: Line 182:
 The [[http://betemcu.cn/|Baite]] [[https://www.aliexpress.com/store/product/Best-Quality-ST-Link-stlink-V2-for-STM8S-STM8L-STM32-Cortex-M0-Cortex-M3-SWIM-JTAG/213957_32676015777.html|ST-Link V2]] is my favorite clone since it supports JTAG, SWD, and SWIM (for STM8). The [[http://betemcu.cn/|Baite]] [[https://www.aliexpress.com/store/product/Best-Quality-ST-Link-stlink-V2-for-STM8S-STM8L-STM32-Cortex-M0-Cortex-M3-SWIM-JTAG/213957_32676015777.html|ST-Link V2]] is my favorite clone since it supports JTAG, SWD, and SWIM (for STM8).
  
-The seem to use the same board also for several other programmers, and since the pinout is not on the case I've decided to make my own sticker.+They seem to use the same board also for several other programmers, and since the pinout is not on the case I've decided to make my own sticker.
  
 {{:jtag:dsc02406.jpg?0x100|pinout sticker}} {{:jtag:dsc02406.jpg?0x100|pinout sticker}}
Line 141: Line 193:
 {{:jtag:baite-v2a-board_back.jpg?0x100|board front}} {{:jtag:baite-v2a-board_back.jpg?0x100|board front}}
  
-There is a newer version marked as "V2A" (under the crystal), but the {{:jtag:baite-v2a.pdf|schematic}} is pretty much the small with the following changes:+There is a newer version marked as "V2A" (under the crystal), but the {{:jtag:baite-v2a.pdf|schematic}} is pretty much the same with the following changes:
   * all pads for the micro-controller are present (there is even solder mask between them)   * all pads for the micro-controller are present (there is even solder mask between them)
   * they added a SWD port   * they added a SWD port
Line 165: Line 217:
 It has been [[https://medium.com/@paramaggarwal/converting-an-stm32f103-board-to-a-black-magic-probe-c013cf2cc38c|ported]] on the [[stm32f1xx#blue_pill|blue pill]], but I don't find this board as handy as a dongle.\\ It has been [[https://medium.com/@paramaggarwal/converting-an-stm32f103-board-to-a-black-magic-probe-c013cf2cc38c|ported]] on the [[stm32f1xx#blue_pill|blue pill]], but I don't find this board as handy as a dongle.\\
 It has also been [[http://blog.linuxbits.io/2016/02/15/cheap-chinese-st-link-v-2-programmer-converted-to-black-magic-probe-debugger/|ported]] to the [[#st-link_v2_aluminium|ST-Link V2 clone]], but then there is no additional UART anymore.\\ It has also been [[http://blog.linuxbits.io/2016/02/15/cheap-chinese-st-link-v-2-programmer-converted-to-black-magic-probe-debugger/|ported]] to the [[#st-link_v2_aluminium|ST-Link V2 clone]], but then there is no additional UART anymore.\\
-So I decided to port it to the [[#baite|baite]]. +===== Altera USB-Blaster =====
-This has less power pins (who needs 2xGND, 2x5V, 3x3.3V anyway), but provides enough function pins to add UART (and SRST). +
- +
-To build the firmware ([[https://github.com/blacksphere/blackmagic/pull/274|patch]] integration pending): +
-<code bash> +
-git clone https://github.com/tsaitgaist/blackmagic.git +
-cd blackmagic +
-git submodule init +
-git submodule update +
-git checkout baite-platform +
-# if you are usgin GCC >+
-git cherry-pick 2ebcffa2a4911090b43c36594dae6b58d4bb2f27 +
-make +
-cd src +
-make clean +
-make PROBE_HOST=baite +
-</code> +
- +
-Now we need to re-flash the Baite dongle.\\ +
-As you can see on the {{:jtag:baite.pdf|schematic}} the JTAG and SWD pins of the micro-controller are not connected (there even are no pads on the board for the pins to be soldered on). +
-But on the back of the board you can find test points so to program the device using the serial bootloader: +
- +
-^ pin ^ signal ^ +
-| 1 (square) | RX | +
-| 2 | TX | +
-| 3 | BOOT0 | +
-| 4 | +5V | +
-| 5 | GND | +
- +
-Use any USB to UART converter and connect the corresponding pins to this port. +
-Don't power the Baite dongle over USB since it might then boot the normal application. +
-Instead let the USB to UART converter power it. +
-To start the serial bootloader when powering the dongle you need to set BOOT0 high by connecting it to +3.3V or DTR (or any high signal present on the USB to UART converter). +
- +
-To flash the Black Magic firmware I used [[https://sourceforge.net/p/stm32flash/wiki/Home/|stm32flash]]. +
-Since the flash is read/write protected you first need to clear these option bits. +
- +
-<code bash> +
-# disable flash read protection +
-stm32flash -k /dev/ttyUSB0 +
-# disable flash write protection +
-stm32flash -u /dev/ttyUSB0 +
-# erase flash +
-stm32flash -o /dev/ttyUSB0 +
-# flash the DFU bootloader +
-stm32flash -w src/blackmagic_dfu.bin -v /dev/ttyUSB0 +
-# flash the main firmware +
-stm32flash -w src/blackmagic.bin -v -S 0x08002000 /dev/ttyUSB0 +
-</code> +
- +
-Since this adapter is based on an STM32F103C8 micro-controller with 64 kB of flash the DFU bootloader only advertises 56 kB of flash available for the main application. +
-Because the blackmagic firmware exceeds this size it will not be possible to flash it through if the DFU software doesn't ignore this restriction. +
-STM32F103C8 micro-controllers often have 128 kB of flash though, thus it is still possible to flash the blackmagic firmware using the serial bootloader (at address 0x08002000). +
-Verification during flashing ensured the whole firmware has been written successfully. +
- +
-Unplug and re-plug the Baite dongle. +
-The adapter should be running the main application and two USB CDC ACM ports will appear. +
- +
-You can re-flash the device from the main application using dfu-util (if you can bring dfu-util to ignore the size restriction): +
-<code bash> +
-dfu-util -d 1d50:6018 -s 0x08002000:leave -D blackmagic.bin +
-</code>+
  
-Here is the new "BMP Baite" {{ :jtag:bmp_baite.pdf |pinout}}+{{ :jtag:dsc02418.jpg?0x150|device front}}
-^ signal ^ pin ^ pin ^ signal ^ +
-| SRST | 1 | 2| +3.3V | +
-| +5V | 3 | 4 | JTCK/SWCLK | +
-| RX | 5 (key) | 6 | JTMS/SWDIO | +
-| GND | 7 | 8 | JTDO/TRACESWO | +
-| TX | 9 | 10 | JTDI | +
- +
-**note**: the RX pin is pulled up by a 620 ohms resistor. Thus the TX connected to BMP Baite must by strong enough to drive it low (e.g. not like with the CH340 USB to UART converter). +
- +
-If you connect SRST to the target NRST, it is even possible to reset the target board without having to press on the on-board reset button (of there is any): +
-<code bash> +
-gdb --eval-command="target extended-remote /dev/ttyACM0" --eval-command="monitor hard_srst" --eval-command="quit" +
-</code> +
-===== Altera USB-Blaster =====+
  
 The [[https://www.buyaltera.com/PartDetail?partId=1212940|USB-Blaster]] is from Altera. The [[https://www.buyaltera.com/PartDetail?partId=1212940|USB-Blaster]] is from Altera.
 It is often used to flash FPGA, but is a general purpose JTAG adapter. It is often used to flash FPGA, but is a general purpose JTAG adapter.
- 
-I have a cheap [[http://www.aliexpress.com/item/Free-shipping-New-Mini-Usb-Blaster-Cable-For-CPLD-FPGA-NIOS-JTAG-Altera-Programmer-in-stock/806527241.html|Rev.c clone]]. 
-The original uses FTDI FT245 and MAX CPLD chips. 
-This one uses a Silicon Labs C8051F321 micro-controller and a 74LVC125 quad buffer, but there are many other clone variants. 
- 
-{{:jtag:dsc02418.jpg?0x100|device front}} 
-{{:jtag:dsc02419.jpg?0x100|device back}} 
-{{:jtag:dsc02420.jpg?0x100|PCB front}} 
-{{:jtag:dsc02424.jpg?0x100|PCB back}} 
  
 :!: be aware that here the VCC{TARGET} pin has to be connected to a reference voltage used for the JTAG communication, generally provided by the target device on the board (often 3.3V or 1.8V). :!: be aware that here the VCC{TARGET} pin has to be connected to a reference voltage used for the JTAG communication, generally provided by the target device on the board (often 3.3V or 1.8V).
Line 267: Line 235:
 </code> </code>
  
-To be able to use it I had to recompile OpenOCD for the USB-Blaster to use libftdi (probable because it's a clone).+To be able to use it I had to recompile OpenOCD for the USB-Blaster to use libftdi (maybe because it's a clone).
 <code bash> <code bash>
 git clone http://git.code.sf.net/p/openocd/code openocd-code git clone http://git.code.sf.net/p/openocd/code openocd-code
Line 331: Line 299:
 Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
 </code> </code>
 +
 +The original uses FTDI FT245 and MAX CPLD chips.
 +There are numerous clone variants, with various quality and voltage support.
 +
 +==== SiLabs USB-Blaster ====
 +
 +This one uses a Silicon Labs C8051F321 micro-controller and a 74LVC125 quad buffer (for signal voltages from 1.65 to 3.6 V).
 +
 +{{:jtag:mini_silabs_front.jpg?0x150|SiLabs USB-Blaster front}}
 +{{:jtag:mini_silabs_back.jpg?0x150|SiLabs USB-Blaster back}}
 +
 +==== PIC USB-Blaster ====
 +
 +This one uses a Microchip PIC18F14 micro-controller (with embedded 3.3V LDO) and has no buffer (thus only supporting 3.3 V signals).
 +
 +{{:jtag:mini_pic_front.jpg?0x150|PIC USB-Blaster front}}
 +{{:jtag:mini_pic_back.jpg?0x150|PIC USB-Blaster back}}
 +
 +==== ARMJISHU USB-Blaster ====
 +
 +This one uses a ST STM32F101 (as a STM32F103 with USB support) micro-controller and a 74HC244 octal-buffer (for signal voltages from 2.0 to 6.0 V).
 +
 +{{:jtag:mini_stm32_front.jpg?0x150|ARMJISHU USB-Blaster front}}
 +{{:jtag:mini_stm32_back.jpg?0x150|ARMJISHU USB-Blaster back}}
 +
 +I also reversed the {{:jtag:bus_blaster-stm32.pdf|schematic}}.
 +It shows that the hardware can also drive the signals (at 3.3 V) in case Vcc_target is not connected, and you can add an uSD card slot or SPI flash.
 +I don't know if these features are supported in software.
 +
 +{{:jtag:mini_stm32_front-board.jpg?0x150|ARMJISHU board USB-Blaster front}}
 +{{:jtag:mini_stm32_back-board.jpg?0x150|ARMJISHU board USB-Blaster back}}
  
 ===== SEGGER J-Link ===== ===== SEGGER J-Link =====
  
-The [[http://www.aliexpress.com/item/FREE-SHIPPING-V8-ARM-Emulator-supports-ARM7-ARM9-ARM11-Cortex-M3-core-ADS-IAR-STM32-Emulator/32262570128.html|O-Link-ARM V8]] is a [[https://www.segger.com/jlink_base.html|SEGGER J-Link]] clone.+The [[https://www.segger.com/jlink_base.html|SEGGER J-Link]] supports JTAG, SWD, SWO, RTCK, and voltage reference (or provide 3.3V). 
 +That makes it one of the most complete JTAG adapter. 
 +The differences between the versions are documented [[https://wiki.segger.com/Software_and_Hardware_Features_Overview|here]]. 
 + 
 +There are plenty of different J-Link v8 and v9 clones available, from light version with the minimum number of components, to full version with all features. 
 +But v8 and v9 are not supported anymore by J-Link, meaning no new feature will be added to them. 
 +Instead I recommend to get the [[https://www.segger.com/products/debug-probes/j-link/models/j-link-edu/|J-Link EDU]] which is a supported v10 and not expensive. 
 + 
 +Here pictures from devices not from official distributors, thus they might not be genuine but only clones. 
 + 
 +They come in the same case:
  
 {{:jtag:imag0403.jpg?0x150|device front}} {{:jtag:imag0403.jpg?0x150|device front}}
 {{:jtag:imag0404.jpg?0x150|device back}} {{:jtag:imag0404.jpg?0x150|device back}}
-{{:jtag:imag0406.jpg?0x150|PCB front}} 
  
-It supports JTAG, SWD, SWORTCK, and voltage reference+Here a J-Link v8 with large passives: 
-That makes it the most complete JTAG adapter I have.+ 
 +{{:jtag:jlink-v8-large-front.jpg?0x150|board front}} 
 +{{:jtag:jlink-v8-large-back.jpg?0x150|board back}} 
 + 
 +Here a J-Link v8 with smaller and a bit less passives: 
 + 
 +{{:jtag:jlink-v8-thin-front.jpg?0x150|board front}} 
 +{{:jtag:jlink-v8-thin-back.jpg?0x150|board back}} 
 + 
 +Here a light J-Link v9. 
 +v9 uses a STM32F205 (providing 20 MHz JTAG/15 MHz SWD) while v8 uses a AT91SAM7S (providing 10 MHz JTAG/4 MHz SWD): 
 + 
 +{{:jtag:jlink-v9-front.jpg?0x150|board front}} 
 +{{:jtag:jlink-v9-back.jpg?0x150|board back}} 
 + 
 +Here a J-Link v10. 
 +It uses a NXP LPC4337 which supports USB high speed, and allows faster debugging speeds. 
 +In addition to the others, it adds cJTAG support: 
 + 
 +{{:jtag:jlink-v10_board_top-mini.jpg?0x150|board front}} 
 +{{:jtag:jlink-v10_board_bottom-mini.jpg?0x150|board back}} 
 + 
 +Here a [[https://www.segger.com/products/debug-probes/j-link/models/j-link-ob/|J-Link OB]]. 
 +It is supposed to be embedded on development board and provide an easy way to flash the main micro-controller. 
 +It have much less capabilities (no JTAG, only SWD, ...) and less protectionsbut is a lot smaller and sufficient for most tasks. 
 +Additionally it provides a UART interface, ideal for printf debugging. 
 +I actually can be implemented on several micro-controller, and in my case a STM32F072
 + 
 +{{:jtag:jlink-ob_front.jpg?0x150|board front}} 
 +{{:jtag:jlink-ob_back.jpg?0x150|board back}} 
 + 
 + 
 +===== Texas Instruments XDS100v3 ===== 
 + 
 +The [[http://processors.wiki.ti.com/index.php/XDS100|XDS100v3]] supports cJTAG (aka. IEEE 1149.7, or SWD alternative), but I have not been able to successfully use it yet. 
 + 
 +Note: this adapter uses the [[http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html|TI 20-pin (cTI) pinout]]. 
 + 
 +{{:jtag:xds100v3_case.jpg?0x150|device}} 
 +{{:jtag:xds100v3_front.jpg?0x150|board front}} 
 +{{:jtag:xds100v3_back.jpg?0x150|board back}} 
 + 
 +===== DISTORTEC JTAG-lock-pick Tiny 2 ===== 
 + 
 +The [[http://www.distortec.com/jtag-lock-pick-tiny-2/|JTAG-lock-pick Tiny 2]] is just a very fast (using a FT232H chip), and compact (although it could be even more compact if the component were on both sides) JTAG adapter supporting 1.4V to 3.6V signals (5.5V tolerant), multiple pinouts possible (using a CPLD), RTCK, SRST, and TRST.
  
 +{{:jtag:jtag-lockpick_front.jpg?0x150|board front}}
 +{{:jtag:jtag-lockpick_back.jpg?0x150|board back}}
 ====== tricks ====== ====== tricks ======
  
jtag.1504708320.txt.gz · Last modified: 2024/01/07 17:49 (external edit)