This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
jtag [2019/08/19 06:26] – [mini ST-LINK V2] kingkevin | jtag [2020/06/16 13:47] – [mini ST-LINK V2] update CKS link kingkevin | ||
---|---|---|---|
Line 147: | Line 147: | ||
=== MINI ST-Link V2E === | === MINI ST-Link V2E === | ||
- | {{:jtag:stlink_cks_case.jpg? | + | {{:jtag:mini_st-link_v2e-case.jpg? |
- | {{:jtag:stlink_cks_front.jpg? | + | {{:jtag:mini_st-link_v2e-front.jpg? |
- | {{:jtag:stlink_cks_back.jpg? | + | {{:jtag:mini_st-link_v2e-back.jpg? |
- | Instead on an STM32F103, this dongle uses a [[http:// | + | Instead on an STM32F103, this dongle uses a [[http:// |
- | I've seen pin compatible alternatives (ST STM8S003 vs Nuvoton N76E003), but they always had some differences (architecture, | + | 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, |
- | The CS32F103 seems like a complete clone of the STM32F103 (exact same pinout | + | 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). | 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. | 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). | 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. | The next step would be to have a CS32F103 chip in a package marked as STM32F103. | ||
+ | |||
+ | == GC == | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | 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' | ||
+ | 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 ==== | ||