2016-03-31 02:20 AM
I'm using a STM32F407VG Discovery board in a test rig, and have noticed an issue when the board is powered with 5V on the pins. It appears that the MCU is held in reset after power is applied. This is fixed by plugging in a USB cable. It seems that ST Link part of the board causes this.
I've used Discos in this way before, and there was no similar problem. The latest boards I have are marked DISC1 MB997D. Is this a bug? A deliberate change? I think I can chop out SB11 to make the thing work, but then I probably can't program the board over the USB. I'd be grateful for any suggestions. Al2016-03-31 08:38 AM
Couple of related threads, check you have the most current firmware.
https://community.st.com/0D50X00009XkgH6SAJ
EDIT: Fixed DEADLINK, original post from March 31 2016
Note, there is a known issue with the ST-LINK firmware shipping on the DISC1 versions of the STM32F4 and STM32F429I which holds the board in reset when a USB Charger or Battery pack (ie non-computer) is attached to the ST-LINK USB connectors. This will occur if you push 5V in via U5V or 5V (EXT_5V) also.
Based of current feedback I'm thinking V2J25M14 is a prime suspect, I have long since upgraded my boards, but would suspect large stocks of these boards exist at Mouser, DigiKey, etc so people will keep rediscovering this issue.
Update to current firmware and drivers, V2J28M18 at time of this edit August 19 2017
/external-link.jspa?url=https%3A%2F%2Fmy.st.com%2Fcontent%2Fmy_st_com%2Fen%2Fproducts%2Fembedded-software%2Fdevelopment-tool-software%2Fstsw-linkhtml
2016-04-05 03:13 AM
Hi chambers.alan.001,
You should upgrade your ST-LINK firmware to ST-LINK/V2-1 through
http://www.st.com/web/en/catalog/tools/PF260217
.-Hannibal-
I'm using a STM32F407VG Discovery board in a test rig, and have noticed an issue when the board is powered with 5V on the pins. It appears that the MCU is held in reset after power is applied. This is fixed by plugging in a USB cable. It seems that ST Link part of the board causes this.
I've used Discos in this way before, and there was no similar problem. The latest boards I have are marked DISC1 MB997D. Is this a bug? A deliberate change? I think I can chop out SB11 to make the thing work, but then I probably can't program the board over the USB. I'd be grateful for any suggestions. Al