2013-06-19 04:20 AM
hey all
when i include the header stm32f4_discovery.h it recognizes it well , but it dont recognize ''GPIO_InitTypeDef'' !! and ''RCC_AHB1PeriphClockCmd'' and all GPIO_Pins! and to be sure of the header i attached it for u to see if it's good or not and thnx2013-06-19 07:26 AM
A typical STM32F4-Discovery would have at least these include paths
..\; ..\..\..\Libraries\CMSIS\Include; ..\..\..\Libraries\CMSIS\ST\STM32F4xx\Include; ..\..\..\Libraries\STM32F4xx_StdPeriph_Driver\inc; ..\..\..\Utilities\STM32F4-Discovery; The CMSIS ones probably being particularly important, otherwise Keil will pull in files from it's OWN include paths instead of those contemporaneous with the ST library2013-06-19 07:31 AM
To start in a clean way with pre-configured environment, you can use the examples available in the DISCOVERY board firmware package.
Or more specifically the TEMPLATE projects for each tool chain, until the OP becomes familiar with project structures and tool chains being used. Hacking around randomly probably won't achieve the level of understanding and clarity required.2013-06-19 08:10 AM
thnx for all
but here i switched to IAR and i used the following paths $PROJ_DIR$\ $PROJ_DIR$\app\ $PROJ_DIR$\modules\ $PROJ_DIR$\board\ $PROJ_DIR$\..\Libraries\STM32F4xx_StdPeriph_Driver\inc2013-06-19 08:20 AM
even i downloaded a project from st and i tried RCC_AHB1PeriphClockCmd(RCC_AHB1Periph_GPIOD, ENABLE); and it gives the same error
2013-06-19 09:14 AM
Try to follow Clive1's recommendation, just take template example as it is, compile & load it. If ok, then make your own updates.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2013-06-19 09:38 AM
thank u all it worked :)