Posted by saburo on 2017-02-21 15:28

Yes thanks, that works for me too, I actually started with that (except I created a separate worksspace, but the result is the same).

My issue is when I start a project with STM32CubeMX, I was trying not to include the whole shebang of the BSP, instead I was focusing on single components to better understand and learn.

I started with the display (not the easiest, I reckon, but a good start to ease debugging), enabled LCD and DMA2D in HAL then I understand I need to include the BSP libraries in my project, from ST4.

But then if I include stm32746g_discovery.h or the other BSP includes things start to go south.

So far this is where I got (in my main.h) :

/* USER CODE BEGIN Includes */
// HAL main

1. include “stm32f7xx_hal_def.h” // should not be needed, but cannot find HAL_StatusTypeDef
2. include “stm32f7xx_hal.h”

// HAL components

1. include “stm32f7xx_hal_dma.h”
2. include “stm32f7xx_hal_dma2d.h”
3. include “stm32f7xx_hal_uart.h” // needed somewhere, whatever, no big deal
4. include “stm32f7xx_hal_sdram.h”
5. include “stm32f7xx_hal_ltdc.h”
6. include “stm32746g_discovery.h”

// BSP components

1. include “stm32746g_discovery_lcd.h”
2. include “stm32746g_discovery_sdram.h”

// LCD specific component

1. include “rk043fn48h.h”

/* USER CODE END Includes */

And I still get :
.../stm32f7xx_hal_rcc_ex.h:3206:1: error: unknown type name ‘HAL_StatusTypeDef’
../stm32f7xx_hal_dma.h:162:3: error: unknown type name ‘HAL_LockTypeDef’

etc

but both are defined in “stm32f7xx_hal_def.h” which I added before anything else!

Anyhow, I agree the demo works and it’s pretty cool