Keil Logo

StdPeriph_Driver

Next Thread | Thread List | Previous Thread Start a Thread | Settings

Details Message
Author
sameena shaikh
Posted
9-Oct-2017 13:06 GMT
Toolset
ARM
New! StdPeriph_Driver

Can any one tell me how to resolve this issue???

*** Using Compiler 'V5.06 update 5 (build 528)', folder: 'C:\Keil_v5\ARM\ARMCC\Bin'
Build target 'Target 1'
compiling stm32f4xx_spi.c...
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_spi.c(182): warning: #47-D: incompatible redefinition of macro "SPI_CR2_FRF" (declared at line 12969 of "C:\Keil_v5\ARM\PACK\Keil\STM32F4xx_DFP\2.11.0\Drivers\CMSIS\Device\ST\STM32F4xx\Include\stm32f429xx.h") #define SPI_CR2_FRF ((uint16_t)0x0010)
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_gpio.c(395): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_GPIO_ALL_PERIPH(GPIOx));
xx_gpio.c(439): error: #136: struct "<unnamed>" has no field "BSRRH" GPIOx->BSRRH = GPIO_Pin;
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_gpio.c(458): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_GPIO_ALL_PERIPH(GPIOx));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_gpio.c(464): error: #136: struct "<unnamed>" has no field "BSRRL" GPIOx->BSRRL = GPIO_Pin;
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_gpio.c(468): error: #136: struct "<unnamed>" has no field "BSRRH" GPIOx->BSRRH = GPIO_Pin ;
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(1330): error: #20: identifier "HSI_VALUE" is undefined RCC_Clocks->SYSCLK_Frequency = HSI_VALUE;
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(1333): error: #20: identifier "HSE_VALUE" is undefined RCC_Clocks->SYSCLK_Frequency = HSE_VALUE;
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(1475): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_RTCCLK_SOURCE(RCC_RTCCLKSource));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(1505): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_FUNCTIONAL_STATE(NewState));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(1522): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_FUNCTIONAL_STATE(NewState));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(1808): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_PLLI2S_DIVQ_VALUE(RCC_PLLI2SDivQ));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(1840): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_PLLSAI_DIVQ_VALUE(RCC_PLLSAIDivQ));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(1939): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_PLLSAI_DIVR_VALUE(RCC_PLLSAIDivR));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4 assert_param(IS_RCC_APB2_PERIPH(RCC_APB2Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2320): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_AHB1_RESET_PERIPH(RCC_AHB1Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2349): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_AHB2_PERIPH(RCC_AHB2Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2430): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_APB1_PERIPH(RCC_APB1Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2477): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_APB2_RESET_PERIPH(RCC_APB2Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2526): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_AHB1_LPMODE_PERIPH(RCC_AHB1Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2558): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_AHB2_PERIPH(RCC_AHB2Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2645): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_APB1_PERIPH(RCC_APB1Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2697): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_APB2_PERIPH(RCC_APB2Periph));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2721): warning: #223-D: function "assert_param" declared implicitly assert_param(IS_RCC_LSE_MODE(RCC_Mode));
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2725): error: #20: identifier "RCC_BDCR_LSEMOD" is undefined

ET_BIT(RCC->BDCR, RCC_BDCR_LSEMOD);
..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c(2729): error: #20: identifier "RCC_BDCR_LSEMOD" is undefined

LEAR_BIT(RCC->BDCR, RCC_BDCR_LSEMOD);

..\..\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\STM32F4xx_StdPeriph_Driver\src\stm32f4xx_rcc.c: 40 warnings, 5 errors
. compiling stm32f4xx_hal_rcc.
".\Objects\adxl345.axf" - 11 Error(s), 78 Warning(s).
Target not created.
Build Time Elapsed: 00:01:57

Author
Westonsupermare Pier
Posted
9-Oct-2017 16:55 GMT
Toolset
ARM
New! RE: StdPeriph_Driver

Try building the Template example project.
Then review the compiler command line settings, ie Defines and Include Paths, and reflect those into your project.
Look at which files you are #including, vs those listed in the project tree.

Author
a a
Posted
10-Oct-2017 16:04 GMT
Toolset
ARM
New! RE: StdPeriph_Driver

I had this problem too and rather than being lazy and just sending the output to this forum expecting others to fix it, I spent some time doing the obvious things that Andrew Neil suggests.

Author
a a
Posted
10-Oct-2017 16:05 GMT
Toolset
ARM
New! RE: StdPeriph_Driver

If only I'd spent more time reading the previous post :)

Author
Andrew Neil
Posted
10-Oct-2017 19:53 GMT
Toolset
ARM
New! RE: spend some time doing the obvious things


:-)

Author
sameena shaikh
Posted
11-Oct-2017 06:33 GMT
Toolset
ARM
New! RE: StdPeriph_Driver

I dont expect others to fix my issues. I've tried many things and then when i could get through it i've posted it here. I ain't lazy too FYI.

Author
wanger meoff
Posted
11-Oct-2017 08:20 GMT
Toolset
ARM
New! I ain't lazy too FYI.

I sussed it. i will post solution when i found da energy.

Author
Andrew Neil
Posted
11-Oct-2017 10:09 GMT
Toolset
None
New! RE: I've tried many things

Go on, then - what, exactly, have you tried?

And what was the result?

And what did you learn from that?

Eg, the very first message in your list, if we take out the clutter of the really long paths:

compiling stm32f4xx_spi.c...
src\stm32f4xx_spi.c(182): warning: #47-D: incompatible redefinition of macro "SPI_CR2_FRF"
(declared at line 12969 of Include\stm32f429xx.h")

Think what "redefinition" means.

Think why it is possibly a bad idea? ie, why would the compiler think it should warn you about it?

Think about how to stop it happening ...

Author
Sameena Shaikh
Posted
11-Oct-2017 10:21 GMT
Toolset
None
New! RE: I've tried many things

My bad! That I even asked here for help. Sorry. Deleting the post.

Author
Andrew Neil
Posted
11-Oct-2017 10:31 GMT
Toolset
None
New! RE: I've tried many things

In any form of debugging - including debugging compiler messages - it is important to have a method or strategy; not just "try many things".

The key strategy for compiler diagnostics is: Start with the first message - especially when you have a huge number of messages, as here.

This is because the first message will very often be either the cause of the following messages, or symptomatic of their cause.

Therefore, once you have solved the first message, you will almost certaily be well on your way to solving the rest.

As Westonsupermare Pier suggested, your first message suggests that you have mis-configured the project...

Next Thread | Thread List | Previous Thread Start a Thread | Settings

  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.