Debugging STM32 clone Sysprogs forums › Forums › VisualGDB › Debugging STM32 clone This topic has 3 replies, 2 voices, and was last updated 3 years, 3 months ago by Gast. Log In Register Lost Password Viewing 4 posts - 1 through 4 (of 4 total) Author Posts August 11, 2021 at 02:47 #31122 JohananParticipant Due to chips shortage we are trying to test Chinese STM32 clone CH32F103C8T6. It looks like it has been solved with platformIO: Debugging of STM32F103 clone “BluePill” board, wrong idcode – Professional Solutions / Debugging – PlatformIO Community and I tried changing startup GDB commands in Debug settings-> advanced , but no joy. Can you help? Thanks. August 11, 2021 at 14:37 #31131 GastParticipant You must edit the stm32f1x.cfg file to add the line set CPUTAPID 0 before the first if. Look for the file in the Debug settings, Debugged device …. August 11, 2021 at 22:19 #31132 JohananParticipant Tried it but it makes no difference, still same error. Any other ideas? Thanks //————– <div> <div># script for stm32f1x family</div> <div>#</div> <div># stm32 devices support both JTAG and SWD transports.</div> <div>#</div> <div>source [find target/swj-dp.tcl]</div> <div>source [find mem_helper.tcl]</div> <div>set CPUTAPID 0</div> <div>if { [info exists CHIPNAME] } {</div> <div> set _CHIPNAME $CHIPNAME</div> <div>} else {</div> <div> set _CHIPNAME stm32f1x</div> <div>}</div> <div>//——————————-</div> </div> August 12, 2021 at 00:01 #31135 GastParticipant For me, that solved the ID-problem with cloned Blue Pills labelled as stm32f103CBT6. You might need administrative permission to replace that file. Furthermore, after an update of openOCD the changed file will be replaced. Therefore, I keep the changed cfg file in a different folder. Author Posts Log In Register Lost Password Viewing 4 posts - 1 through 4 (of 4 total) You must be logged in to reply to this topic. Log In Username: Password: Keep me signed in Log In