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
Next revisionBoth sides next revision
jtag [2019/04/04 21:24] – [ST-LINK V2 aluminium] re-arrange kingkevinjtag [2020/06/12 16:45] – [mini ST-LINK V2] kingkevin
Line 73: 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.
Line 108: 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 124: 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]] {{ :jtag:ic_mcu_cks_cks32f103xb.pdf|CS32F103}} (sometimes CKS32F103)  ({{ :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 366: Line 414:
 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. 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.
  
-The come in the same case:+They come in the same case:
  
 {{:jtag:imag0403.jpg?0x150|device front}} {{:jtag:imag0403.jpg?0x150|device front}}
Line 386: Line 434:
 {{:jtag:jlink-v9-front.jpg?0x150|board front}} {{:jtag:jlink-v9-front.jpg?0x150|board front}}
 {{:jtag:jlink-v9-back.jpg?0x150|board back}} {{:jtag:jlink-v9-back.jpg?0x150|board back}}
 +
 +Here a J-Link v10.
 +This is currently the only version being developed on.
 +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}}
 ===== Texas Instruments XDS100v3 ===== ===== Texas Instruments XDS100v3 =====
  
jtag.txt · Last modified: 2024/01/07 17:49 by 127.0.0.1