Sheepdoll & All,
I am attending a STM32F7xx HAL course in Cambridge (UK) this Thursday. Free to attend, and they give you a STM32F7 Discovery to take home
I really need to switch over to the HAL way of thinking, because although so far using the Standard Peripheral Libraries has worked for M3 and M4 they are not supported on the M7.
Atmel have a blistering 300MHz M7 available in a 144 pin LQFP. http://www.atmel.com/products/microcont ... sam-e.aspx
I guess that is a good candidate for a future descendant of Arduino.
I elected the HAL + CubeMX route despite pressure to use ye ole Standard Peripheral Libraries. Documentation of HAL libraries is good. After 1+ years with HAL/CubeMX, I'm glad I took this route, for a professional project.
I self-taught CubeMX. That took about a week as it was my first GUI pin-mapper and full up I/O system configuration tool. And it generates all the I/O initialization code and that's very time consuming if you go the bare metal route. That makes a HUGE difference. No more struggling with complex peripherals like DMA on UARTs, GPIO, capture timers. No more DIY driver and ISR code. Getting ST's version of ChanFS (FATFS) working with SDIO (not SPI) and MLC NAND flash was very simple. Works well with 4GB.
I do wish I could have found a decent CubeMX tutorial video. That would have helped a LOT. HAL libraries' documentation is good enough.
Prerequisite: read, read, read the STM23Fxxx reference manual so you get the big picture.
CubeMX is more complex and difficult to learn than is the HAL docs. I rarely need to look at the HAL code per se.
Gotta use a supported targeted compiler/IDE with CubeMX. Last I looked the list was
ST' distributed Eclipse + GCC for Windows/LInux, not sure about Mac. Free.
Atollic- Eclipse + GCC. Beware stability of this; see user forum.
Visual GDB claims to be able to ingest a project file generated by CubeMX.