Debugging STM32 clone

Sysprogs forums Forums VisualGDB Debugging STM32 clone

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #31122
    Johanan
    Participant

    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.

     

    #31131
    Gast
    Participant

    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 ….

     

    #31132
    Johanan
    Participant

    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>

    #31135
    Gast
    Participant

    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.

     

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.