2024-11-04 08:25 PM - last edited on 2024-11-09 02:28 AM by Andrew Neil
When vscode+stm32cubeclt+openocd was developing stm32f103c8t6, this problem appeared on a board. openocd detects that the board idcode should be 0x1ba01477, but the actual detected idcode is 0x2ba01477. Then I can't burn it or debug it. However, keil can also recognize 0x2ba01477 and can be burned and debugged normally. Related pictures are as follows
2024-11-09 02:29 AM
@haimianxx wrote:developing stm32f103c8t6, this problem appeared on a board.
What board?
Are you sure that it's really an stm32f103c8t6, and that it is genuine?
See this thread:
In particular: