Answer the question
In order to leave comments, you need to log in
How to revive the stm32f4discovery board?
Good afternoon!
The essence of the problem is this. At some point, I connected the stm32f4discovery board to a computer (mac os x), I try to flash it and I get an error
2016-03-31T11:09:50 WARN src/stlink-usb.c: Couldn't find any ST-Link/V2 devices
No ST-LINK Detected
dfu-util -d 0483:df11 -a 0 -s 0x08000000:1024 -D .../LED.bin
dfu-util 0.8
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to [email protected]
dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08000000, size = 43340
Download [=========================] 100% 43340 bytes
Download done.
File downloaded successfully
Answer the question
In order to leave comments, you need to log in
I somehow had a similar problem - the stem was lying around for half a year in a box, the X hour came, I wanted to pick it up, and I couldn’t flash it for several hours either, in the end it turned out to be stuck - the swd jumpers were not connected that way. Navryatli you have the same, but you never know.
Yes, there the slink failed, apparently, somehow killed him with static.
I had a similar situation, only with an external Chinese stlink.
After the next upload of the firmware, it simply ceased to be.
Is it possible to try to upload the firmware to it (suddenly, this is the problem)?
Just ran into the same issue. If (!) the firmware is not correct (in my case, port A was configured strangely).
The following helped. At the moment before the firmware, the reset button is pressed. Without releasing it, we give a command to the firmware (any other), and after a second or two we release the reset. There is a flashing. Helped me.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question