STM32F40G_eval

[dorrachendoul]

Posted on April 15, 2013 at 17:31

STM32F40G-Eval

Hi, Am having this error, &sharperror ''Please select first the Evaluation board used in your application (in Project Options)''    i commented   /* &sharpdefine STM32F427X */ in STM32F44XX.h but i still have this error , how can i fix it. Thanks #understand-your-tools

[Tesla DeLorean]

Posted on April 15, 2013 at 17:58

Yeah, your not defining a BOARD that's supported, look at the #ifdef stuff above the failing line.

USE_STM324xG_EVAL, STM32F40XX, USE_STDPERIPH_DRIVER

[dorrachendoul]

Posted on April 15, 2013 at 18:11

it is resolved thank you but now i have this error :

fatal error: stm324xg_eval.h: No such file or directory  

[Tesla DeLorean]

Posted on April 15, 2013 at 18:48

Ok, so you haven't correctly defined all the Include paths needed for the project (-I command line option list). You need to point into the Utilities directories containing the files the compiler needs to find.

STM32F4xx_DSP_StdPeriph_Lib_V1.1.0\Utilities\STM32_EVAL\STM3240_41_G_EVAL

[dorrachendoul]

Posted on April 15, 2013 at 18:56

yes i have no errors now thank you

[dorrachendoul]

Posted on April 15, 2013 at 18:57 in fact i added # include ''stm32f4xx_gpio.h'' # include ''stm32f4xx_rcc.h'' in main .c so that i have no error, can i do that ?

[Tesla DeLorean]

Posted on April 15, 2013 at 19:04

There are numerous ways to achieve the desired goals, the library is designed to use

#include ''stm32f4xx.h'' Nominally in   STM32F4xx_DSP_StdPeriph_Lib_V1.1.0\Libraries\CMSIS\Device\ST\STM32F4xx\Include\stm32f4xx.h Which in turn #includes ''stm32f4xx_conf.h'', which you have in your project directory, and that lists the peripherals to #include for your project.

[Tesla DeLorean]

Posted on April 15, 2013 at 19:10

You can also control the Include path search order, here is how the projects expect things to be defined. Adapt as appropriate.

[dorrachendoul]

Posted on April 15, 2013 at 19:19 it didn't work with #include ''stm32f4xx.h''

[gfuehrer]

Posted on April 16, 2013 at 02:51

The way ''the library is designed to use'' that clive1 describes in posts 4788 above requires that USE_STDPERIPH_DRIVER be defined. You can see this at the end of stm32f4xx.h:

#ifdef USE_STDPERIPH_DRIVER 
#include ''stm32f4xx_conf.h'' 
#endif /* USE_STDPERIPH_DRIVER */ 

IMHO it is an aweful technique and should be eschewed. However, buildingSTM32F4xx_StdPeriph_Driver\src files depend on it to get a definition for assert_param (*sigh*). To work around that,I'vemade a separate makfile to buildtheminto an object library. That way I can build my projects without using USE_STDPERIPH_DRIVER. It has the additional benefit of keeping all their compiler warnings out of my project builds.