‎2024-07-16 2:56 AM
‎2024-07-16 3:02 AM
On a Blue Pill it's (virtually) certain that the STM32 chip is fake:
https://community.st.com/t5/stm32-mcus-products/blue-pill-stm32f1-board-gets-programmed-through-arduino-ide-but/m-p/667923#M242505
Are you using a genuine ST-Link, or is that also fake?
https://community.st.com/t5/stm32-mcus-products/blue-pill-stm32f1-board-gets-programmed-through-arduino-ide-but/m-p/668483/highlight/true#M242662
Is the PC actually detecting the ST-Link:
https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/tac-p/698105/highlight/true#M956
but in stm32F3 discovery, it's possible to debug
only in BluePill (f103c8t6) i cant debug
‎2024-07-16 3:05 AM - edited ‎2024-07-16 3:29 AM
@Srisudarsan wrote:in stm32F3 discovery, it's possible to debug
in stm32F3 discovery, it's possible to debug
That will be a genuine STM32 chip
@Srisudarsan wrote:only in BluePill (f103c8t6) i cant debug
That will not be a genuine STM32 chip!
EDIT:
See also:
https://community.st.com/t5/stm32cubeide-mcus/can-t-connect-stm32f103c8t6/td-p/696712
