Which stm32 should I use about stm32-vserprog

[dword1511]

Thanks for pointing the error out, I did not notice it for years!
The difference between STM32F103Cxxx is just different amount of Flash and RAM available. Since STM32F103C8T6 has the least amount, firmware built for it should also run on others.
If you have a board at hand, please send the schematics to me so I can write the board.h for it and compile the firmware you will need.

[relax79]

I am not have a board, only have STM32F103R8T6 mcu "http://urun.gittigidiyor.com/ev-elektronigi/st-stm32f103r8t6-200855568" (I just bought a new). If you say buy a new mcu or board please chose for me in the links in my previus message then i am bought new one, not problem if it is working properly. Thanks,regards.

[relax79]

I am confuse first place because you say "just with minor modifications in the source code to assign correct GPIO for USB D+ pullup and LEDs." I thought editing requires different mcu's.like c8t6, cbt6, r8t6.

[dword1511]

If you do not have a board and need one, then just go for the cheapest STM32F103 board. Any MCU in the series will work without problem.

If you do have the board to solder the MCU you have just bought, please refer to https://github.com/dword1511/stm32-vserprog/blob/master/pcb/v2/sch.pdf for correct connection. R2/R4 in this schematic is 20ohm or so, PB2 and BOOT0 just need some pull down, C4/C5 are 15 or 22pF, C1/C2/C3 0.1uF, C6/C9 10uF, C7/C10 0.1uF. R6 is a fuse. LED can be omitted if you wish. Then just use "make BOARD=stm32-vserprog-v2" to compile the firmware.

STM32F103 series are pin-to-pin compatible when the package is the same. When package is not same, the pinout is different, but firmware sees no difference in terms of pin name.

[relax79]

I have to decide which one to buy then i am prepare everything, If i happen some trouble i will let you know.I am really thanks your kind support,answers and effort to build this good project.