swd debug

[almaz_1c]

[Max]

[almaz_1c]

Thank you for answer, Max. I use exactly that scheme:stm32f4-discovery board and eclipse project. I have absolutely no idea what the reason. Honestly, I was going to chip desoldering. Now I am trying to debug firmware on the stm32f103 nucleo board. If not hard please describe your circuit connection to mirkokontrolleru: what legs are involved and how the power is used? What is the output of st-flash utility when performing erase/flash operations?

[Max]

The firmware relies on the Rowley CrossWorks for ARM build chain (which is slightly modified GCC for ARM) and also on their proprietary libs (libc, libm, etc). It might be easier to get started using an eval copy of CrossWorks, and/or check the Makefile for details. If you build debug version with CW, you must debug with CW, and vice versa (build with Makefile if debugging with standard GDB).

BTW, welcome to the forums!

HTH,
-Max

[almaz_1c]

Hello, Max! Perhaps therefore my firmware, compiled using the standard GCC exceeded 100K. But can another build chain be the reason that I can not erase the firmware of the chip?

[Max]

[almaz_1c]

There is the foto of my esc32 and option bits configuration . It seems like original esc32. From once of them I desolder the chip. I can perform only few successful connecting to esc32 via ST-LINK utility. After that esc32 chip goes to inaccessible state and i can't connect to chip via ST-Link utility.

[almaz_1c]

Here is option bits.