Loading...
 
Skip to main content

System Workbench for STM32


Discovery F7 BSP Drivers for display, stm32CubeMx, SW4

Uhm, I see from your project you are adding freeRTOS, LWIP... I am trying to keep it as minimal as possible.

Your project seems to be in a better shape than mine tho.

The main difference between your approach and mine is that, from your cube project, I see you left all the pins assinged, while I unassigned them
"I tried to create a project with CubeMX, unassigned the pis, then added LTDC and DMA2D (whcih I think it is used by the display drivers). "

I think if you keep the default discovery setup in cubeMX, you end up adding all the stuff by default, which is what I am trying to avoid

But I am breaking my head on the different error mesages I get... I really do not understand how those dependencies are resolved.
You had a good point there about the commented defines in HAL_conf, actually I worked around by including the needed modules in main.h, but I could have achieved the same (and in a cleaner way) by uncommenting the needed defines at the beginning of stm32f7xx_hal_conf.h.

I am not really sure what the procedure is supposed to be when you create a new project for the descovery, starting from cubeMX and also I think it's a pity cube does not have an option to add the BSP needed drivers, the same way you do with middlewares.
In kyle and IAR it seems a bit easier to do : you get them as available packages for your project, select them and: boom, you have them with supposedly the needed includes and stuff.

 
Collapse/expand modules below