2014-09-30 06:43 AM
Hello,
will ST offer a STM32F7 discovery board? If yes, when can we expect it? Regards2015-07-13 09:58 PM
2015-07-15 09:09 AM
LCD_BK_CTRL is on PK3. It is probably active low and not pulled.
2015-10-10 02:45 PM
Having read, further down the board, about the problems people have had with ST-Link I thought I'd just say how I managed to re-flash my board with this demo application.
After unpacking the zip, I discovered that the object code was in .hex format. I downloaded Hex2Bin (http://sourceforge.net/projects/hex2bin/?source=typ_redirect) and, tweaked the Makefile, and recompiled for Linux then ran it on the .hex file. I then plugged in the board, navigated to the mounted directory and copied the bin file generated by Hex2Bin into it. With one caveat, this was flawless and delightfully simple. The one problem I hit was that the board originally declared itself to have no space due to a large demo I had previously installed. Just unplugging and re-plugging the USB fixed this.2016-02-06 11:19 AM
I could not get the MCO1 pin to work on the stm32f7 disco board. I noticed the pin is not enabled in the cube demo code also. Should/Can it work?
If not can anyone recommend the best way to get a fast ( 40+ MHz ) clock output? timers/spi maybe? Thanks, Matt2016-02-06 12:02 PM
Check this topic. Errors on schematic and pin discriptions.
[DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Discovery/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Discovery/STM32F7%20MCO%20problem&FolderCTID=0x01200200770978C69A1141439FE559EB459D75800084C20D8867EAD444A5987D47BE638E0F&TopicsView=https%3a//my.st.com/public/STe2ecommunities/mcu/Lists/STM32Discovery/AllItems.aspx¤tviews=44]Link2016-02-07 03:17 AM
Many thanks. Problem solved.
Ard.D10 is PA8 (not D5)2018-06-09 12:32 PM
>>What would be a reason to use STM32F7 device for controlling some low stuff, like then servos and some stupid devices?
The future calls, and says Flight Controllers
https://oscarliang.com/betaflight-f7-fc/