CKS32: Add support for CKS32 micro-controller

[VictorLamoine]

Fixes #756

I'm pretty sure the name CS32_CORE_ID is not appropriate so tell me what I should use.
I have tested and it works, I can upload the STM32duino bootloader on the CS32F103C8T6 board just fine.

[eugenesia]

Fixes #756

I'm pretty sure the name CS32_CORE_ID is not appropriate so tell me what I should use.
I have tested and it works, I can upload the STM32duino bootloader on the CS32F103C8T6 board just fine.

Tested and this works for me too, on two CS32F103C8T6 microcontrollers.

After some digging around I think the CS32 microcontroller is made by China Key System, a company based in Wuxi, China: http://www.cksic.com/en/about/217.html

Here's a Chinese user manual for a development board making use of the CS32 microcontroller, from another of CKS's websites (CKS Cup, an electronics competition for university students) http://www.ckscup.com/upload/yonghushouce.pdf

Someone else on the EevBlog forum encountered a similar issue https://www.eevblog.com/forum/beginners/unexpected-idcode-flashing-bluepill-clone/

I think CS32_CORE_ID is as good a name as any!

[rojer]

@eugenesia this breaks flashing of STM32F2 and F4 - #761 (comment)
please roll back.

[eugenesia]

It seems that #805 was merged which enables support for the CS32 Blue Pill clone. I just compiled the latest version on the master branch v1.5.1-31-g625f4cd, commit 625f4cd5 and it appears that CS32 MCU support has been re-enabled:

Successful flash to CS32 MCU:

$ st-flash --version
v1.5.1-31-g625f4cd

$ st-info --probe
Found 1 stlink programmers
 serial: 563f6f06513f52481953253f
openocd: "\x56\x3f\x6f\x06\x51\x3f\x52\x48\x19\x53\x25\x3f"
  flash: 0 (pagesize: 1024)
   sram: 20480
 chipid: 0x0410
  descr: F1 Medium-density device

$ st-flash write generic_boot20_pc13.bin 0x8000000
st-flash 1.5.1-31-g625f4cd
2019-07-27T18:43:38 INFO usb.c: -- exit_dfu_mode
2019-07-27T18:43:38 INFO common.c: Loading device parameters....
2019-07-27T18:43:38 INFO common.c: Device connected is: F1 Medium-density device, id 0x20036410
2019-07-27T18:43:38 INFO common.c: SRAM size: 0x5000 bytes (20 KiB), Flash: 0x20000 bytes (128 KiB) in pages of 1024 bytes
2019-07-27T18:43:38 INFO common.c: Attempting to write 21140 (0x5294) bytes to stm32 address: 134217728 (0x8000000)
Flash page at addr: 0x08005000 erased
2019-07-27T18:43:38 INFO common.c: Finished erasing 21 pages of 1024 (0x400) bytes
2019-07-27T18:43:38 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2019-07-27T18:43:38 INFO flash_loader.c: Successfully loaded flash loader in sram
 21/21 pages written
2019-07-27T18:43:39 INFO common.c: Starting verification of write complete
2019-07-27T18:43:39 INFO common.c: Flash written and verified! jolly good!

I encountered other connection issues with the CS32 Blue Pill clone and have documented some fixes on my blog: http://eugenesia.co.uk/2019/07/cs32-blue-pill-clone-connection-problems/

[Nightwalker-87]

Finally closed by #805.