HELP: stm32f4-discovery not responding - Solved

jvilaca · ‎2012-04-25

Posted on April 26, 2012 at 03:30

Hi

I have been working all day with my stm32f4discovery board.

About one hour ago, while debugging, the board stopped responding.

When I plug board into the USB port both LD2 (power) and LD1 (com) turn red and.

If I try to debug a program on the board I get: ''Error in Initializing ST-Link device'' and ''Connection to target failed'' in the pop up details.

Re-installing ST-Link didn't work.

I've no idea why this happened.. I was implementing a method with __wfi() can this break the board? I hope it's not dead because of it :(

Can anyone help?

Thanks

PS: I am using Atollic TrueSTUDIO for ARM Lite 3.0.0

PPS: I can connect to the board using ST-LINK utility, so maybe it is not dead yet. But no idea how to solve this problem.

jvilaca · ‎2012-04-25

Posted on April 26, 2012 at 04:12

Crisis averted - Problem solved

I used ST-Link utility to erase the faulty program from the board at it is now working as expect.

lmao 🙂 everything went better than expected

if anyone has this problem in the future:

in ST-Link Utility program:

1 - Target -> Connect

2 - Target -> Erase chip

worked for me

frankmeyer9 · ‎2012-04-26

Posted on April 26, 2012 at 11:24

wfi

and

wfe

are known debug breakers.

Look in the Cortex M3 reference manual what this instruction do.

If you connect with JTAG and not SWD, it should be possible to reestablish contact (if the debug probe actually uses NRST).