could not verify st device

[anupam1511]

i am working on board stm32f103c8t6 and when i am going for debugging in stm32cubeide its shows error

For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V2J44M29 (API v2) VID:PID 0483:3752
Info : Target voltage: 3.194795
Info : clock speed 4000 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x2ba01477
Info : [STM32F103C8Tx.cpu] Cortex-M3 r2p0 processor detected
Info : [STM32F103C8Tx.cpu] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for STM32F103C8Tx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Error: timed out while waiting for target halted
Error executing event gdb-attach on target STM32F103C8Tx.cpu:
/opt/st/stm32cubeide_1.15.0/plugins/com.st.stm32cube.ide.mcu.debug.openocd_2.2.0.202401261111/resources/openocd/st_scripts/gdb_helper.tcl:18: Error: TARGET: STM32F103C8Tx.cpu - Not halted
in procedure 'gdb_attach_hook' called at file "/opt/st/stm32cubeide_1.15.0/plugins/com.st.stm32cube.ide.mcu.debug.openocd_2.2.0.202401261111/resources/openocd/st_scripts/target/stm32f1x.cfg", line 185
in procedure 'first_gdb_attach_hook' called at file "/opt/st/stm32cubeide_1.15.0/plugins/com.st.stm32cube.ide.mcu.debug.openocd_2.2.0.202401261111/resources/openocd/st_scripts/gdb_helper.tcl", line 18
Info : device id = 0x20030410
Info : flash size = 128 KiB
Warn : GDB connection 1 on target STM32F103C8Tx.cpu not halted
shutdown command invoked
Info : dropped 'gdb' connection

facing errorerror facing

[STTwo-32 · Accepted solution]

Hello @anupam1511 and welcome to the ST Community.

This again looks very much like a fake STM32, More details can be found on this post. 

Best Regards.

STTwo-32

[jayanth0625]

so there is no way of using debug features if u have a fake stm32? The microchip is ofc real but the board is made by a 3rd party Chinese manufacturer. To be specific it's STM32F4VE

[Tesla DeLorean]

>>The microchip is ofc real but the board is made by a 3rd party Chinese manufacturer.

But software implies it's not real. Perhaps you could connect via Segger J-Link or use KEIL or IAR to probe further. But then would likely need different libraries and tools to work with it.

https://community.st.com/t5/stm32-mcus-boards-and-hardware/st-linkv2-quot-could-not-verify-st-device-quot/td-p/823139