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
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...