Forum Replies Created
-
Posts
-
I think this problem stems from the fact that the application I write is in c++ and not everything in the HAL/BSP is c++ complaint. I guess I will have to figure out some way to handle this.
I can make the polled timer work but not the interrupt version. I have a copy of the lcd test application and I can make both work there.
I overcame the other issue of thinking the the project was looking for stm32f756 because I failed to set the macro in the assembler settings :(.
If you are unable to answer this question, it is no problem. I just don’t know where else to look.
What I have been able to do to make some progress: I created a directory BSP in the project and added the Components directory and the STM32F746G-Discovery folder. I put the Discovery directory in the path.
At first I didn’t enable hal-uart in cube-mx and the BSP required it. I went back to the cube-mx and added it and regenerated the code. The hal_uart and hal_uart_ex header files were generated in the cube-mx code. If I reran your cubemximporter the new files were not copied in so I did that by hand and that error was overcome.
Now the problem is in the BSP stm32746g_discovery_sdram.h file which can’t find ‘SDRAM_HandleTypeDef’. My suspicion is this is another cube-mx problem and I can’t tell which option to set to bring that out in the driver folder.
