Black Pill: Debugging STM32F103RCT6 in Keil Fails to Enter main()

[merose]

Title edited to highlight that this is a "Black Pill" board

---

• MCU: STM32F103RCT6

• Toolchain: Keil MDK v5.31 + DAPLink debugger

• Behavior:

  • Program flashes successfully via DAPLink.

  • Debug session starts but never enters main() – halts at address 0x200001E0 (check Disassembly/Register window).

  • All debug buttons (Step, Run) are grayed out except Reset/Stop.

• Key Observations:

  • Same code runs correctly on another STM32F103 board.

  • Rebuild/Clean did not resolve the issue.

The "Option for target" as below.

[mƎALLEm]

Hello @merose and welcome to the ST community,

Are you using Blue pill or Black pill board?

[merose]

It's Black Pill. What's the difference between them?

[mƎALLEm]

They at 99% contain a counterfeit STM32.

And this may confirm my saying:

• Same code runs correctly on another STM32F103 board.

[Andrew Neil]

Welcome to the forum.

Please give details of your two boards - see: How to write your question to maximize your chances to find a solution.

 

---

@merose wrote:

• MCU: STM32F103RCT6

---

Are you sure it's a genuine ST chip?

 

---

@merose wrote:

• • Debug session starts but never enters main() – halts at address 0x200001E0 

---

So somewhere in the startup code.

Look at the startup code to see what should be happening ?

[Ozone]

As usual, try to locate the "Run to main" setting in your debugging environment, and disable it.
The code obviously fails in the init code, most probably during clock setup.
If the same code runs properly on "another board", memory size and lication issues are unlikely - unless these are not the same kind of board.
Differently placed jumpers that affect settings might be another reason.

[merose]

Thanks.I will try this.

[mƎALLEm]

Hello,

ST resources are dedicated to supporting genuine ST products. We are not committed to ensuring that clones/fakes work properly with the firmware we provide.

Thank you for your understanding.