Hi everyone, Yesterday I upload code on my board(STM32F303k8T6) one time.I use STlink V2 mini SWD programmer(SWDCLK,SWDIO,3.3v, gnd) After I try to upload new code in uc but keil say "device not found" but its connected. After I think keil try to erase code in flash so its get error.I connect nrst pin with rst pin in STlink V2 mini. After keil send error "Could not stop cortex-M device. Please check the JTAG cable". Can someone help me? Thanks.
Use ST's ST-Link Utility to confirm that you have proper connectivity & communications.
www.st.com/.../stsw-link004.html
Hi, Andrew Neil thanks for your answer. I download this program and install but it did not work. Program send "Can not connect to target" error.And say "connect under reset". I Try it but did not work. Thanks
That shows that the problem is nothing to do with Keil.
So now its down to basic electronics troubleshooting...
You haven't disabled the SWD interface on the chip, have you? eg, by fiddling with the security settings ...
Hi, Andrew Neil thanks for your answer. I only upload blink example in stm32f303.Its work and led begin blink. After I want to change blink delay.I change in keil and debug and click upload. But it did not show target. After I connect NRST pin to reset pin. After this error occur.
I did not change any configuration. I did not change any security configuration.
Thanks a lot.
Hi, When I connect nrst and rst pin my code not working and not upload new code.But when I connect nrst with 3.3v my code is working but new code is not upload to smt32.Error message is same "not found target" Dou you know what is the problem? Thanks
Hi All, I have a different environment but the same error message. I've been working on a project for several years with uVision5, ULINKpro D JTAG, and an LPC1833 processor. We have upgraded our product to use the LPC1833 Rev A processor, which fixes some peripheral issues, and when I try to download from uV5 I get the "Could not stop Cortex-M device..." error message. Using J-Flash, we determined that the LPC1833 Rev A chip has a different core id than the LPC1833 and we were able to program the Rev A chip with J-Flash by disabling the core id check.
Is there a new Device Family Pack that supports the Rev A chip?
Thanks.
Most frequently these errors occur if you break the pins the debugger is using, ie reprogramming GPIOA PA13, PA14, or going into a low power or sleep mode where the core powers down along with the gates the debugger is trying to communicate with.
Remove broken code, and look at connection settings, select "connect under reset"
In worst situations pull BOOT0 high so it doesn't run your broken code.
Make sure to select SWD and not JTAG as the communications protocol.