2026-02-18 6:39 AM - last edited on 2026-02-19 1:39 AM by Andrew Neil
Title edited to flag that a Blue Pill is being used.
Info : [STN32F103c8Tx.cpu] Examination succeed
Info : starting gdb server for STN32F103C8Tx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Error:[STM32F103C8Tx.cpul clearing lockup after double fault Polling target STM32F103C8Tx.cpu failed, trying to reexamine Infò : (STM32F103C8Tx.cpu] cortex-M3 rlp1 processor detected
Info : [STN32F103c8Tx.cpuj target has 6 breakpoints, 4 watchpoints
Info :[STM32F103C8Tx.cpuj Examination succeed Info : accepting 'gdb' connection on tcp/3333Info : device id = 0x20036410
Info :flash size = 64 KiB
Info : accepting 'gdb' connection on tcp/3333
[STM32F103C8Tx.cpu] halted due to debug-request, current mode: Handler HardFault
XPSR: 0x21000003 pc: 0xfffffffe msp: 0x200008be
[STN32F103C8Tx.cpu] halted due to undefined, current mode: Thread XPSR: 0x61000000 pc: 0x2000003a msp: 0x200008b0.
Error: Fail reading CTRL/STAT register. Force reconnect
Info : dropped 'gdb' connection
Error: Fail reading CTRL/STAT register. Force reconnect
Error: [STM32F103C8Tx.cpu] not halted (gdb fileio)
Error:Fail reading CTRL/STAT register. Force reconnect
Polling target STN32F103C8Tx.cpu failed, trying to reexamine
Error: Fail reading CTRL/STAT register. Force reconnect
Erron:[STN32F103C8Tx.cpu] Examination failed
Examination failed, GDe will be halted. Polling again in 100ms
Error: Fail reading CTRL/STAT register, Force reconnect Error: Fail reading CTRL/STAT register. Force reconnect
Error: Failed to read memóry and, additionally, failed to find out where
shutdown command invoked
Info: dropped 'gdb'’ connection
Error: Error closing APs
Solved! Go to Solution.
2026-02-19 12:55 AM - edited 2026-02-19 3:50 AM
@dv4 wrote:
I am using a Blue Pill (STM32F103C8T6) development board.
That could be an issue. As I said previously, for Blue Pill boards, most probably they contain a counterfeit chip.
@dv4 wrote:
I am using an ST-Link V2
This one? (a post from @Andrew Neil from this knowledge base article:(
If yes, that could be also another problem.
So please use one of the ST boards that contains a genuine chip and STLINK.
You can purshase: the nucleo board: NUCLEO-F103RB
It contains a STM32F103 genuine chip as well as a genuine ST-LINK:
Hope that helps.
2026-02-19 12:40 AM - edited 2026-02-19 12:44 AM
Hello,
First, please review How to write your question to maximize your chances to find a solution.
Second, as "STM32F103C8T" is shown in the log, what board are you using? Blue Pill? If Blue Pull most probably the board contains a counterfeit chip.
What ST-LINK are you using? as there is a possibility you are using a cloned ST-LINK please read How to recognize a genuine ST-LINK/V2 versus a cloned one
What IDE Tool are you using? CubeIDE?
PS: from the trace:
Info : [STN32F103c8Tx.cpu] Examination succeed
That typo is a bit strange!
2026-02-19 12:48 AM
2026-02-19 12:55 AM - edited 2026-02-19 3:50 AM
@dv4 wrote:
I am using a Blue Pill (STM32F103C8T6) development board.
That could be an issue. As I said previously, for Blue Pill boards, most probably they contain a counterfeit chip.
@dv4 wrote:
I am using an ST-Link V2
This one? (a post from @Andrew Neil from this knowledge base article:(
If yes, that could be also another problem.
So please use one of the ST boards that contains a genuine chip and STLINK.
You can purshase: the nucleo board: NUCLEO-F103RB
It contains a STM32F103 genuine chip as well as a genuine ST-LINK:
Hope that helps.