Update History
V2.1.2 / 02-March-2015 Main
Changes
- stm32f429i_discovery.c/.h
- Align to STM32F4xx HAL Driver V1.3.0 for
__HAL_RCC_PPP_CLK_ENABLE() .
V2.1.1 / 10-December-2014
Main
Changes
- stm32f429i_discovery.c/.h
- Change I2C_SPEED used define by BSP_I2C_SPEED
- stm32f429i_discovery_sdram.c
- BSP_SDRAM_Initialization_sequence(): Fix wrong configuration of the burst length
- stm32f429i_discovery_gyroscope.h, stm32f429i_discovery_io.h,stm32f429i_discovery_lcd.c/.h and stm32f429i_discovery_ts.h:
- Change "\" by "/" in the include path to fix compilation issue under Linux
- Miscellaneous comments update
V2.1.0 / 19-June-2014
Main
Changes
- stm32f429i_discovery.c/.h
- Add protection for double initialization of IO_Init within LCD_IO_Init()
- Enhance BSP_PB_Init() function by removing the call of __SYSCFG_CLK_ENABLE() already enabled in the HAL_GPIO_Init()
- stm32f429i_discovery_gyroscope.c/.h
- Update BSP_GYRO_Init() to support new L3GD20 device ID (I_AM_L3GD20_TR)
- stm32f429i_discovery_ts.c/.h
- Correct
wrong TS configuration BSP_TS_ITConfig() and TS IT implementation,
BSP_TS_ITClear() related to the use of IO expander STMPE1600 device not
available on stm32f429i discovery board
- Comments clean up and typo corrections
- stm32f429i_discovery_eeprom.c/.h
- Update usage of BSP_EEPROM_TIMEOUT_UserCallback() function
V2.0.1 / 26-February-2014
Main
Changes
- stm32f429i_discovery_eeprom.c/.h
- Update usage of BSP_EEPROM_TIMEOUT_UserCallback() function
V2.0.0 / 18-February-2014
Main
Changes
- Major update
based on STM32Cube specification: drivers architecture and APIs
modified vs. V1.0.2, and thus the 2 versions are not compatible.
- This version has to be used only with STM32CubeF4 based development
V1.0.2 / 06-December-2013
Main
Changes
- Update IO expander interrupt line on stm32f429i_discovery_ioe.h file.
V1.0.1 / 28-October-2013
Main
Changes
- stm32f429i_discovery_l3gd20.c,
stm32f429i_discovery_lcd.c
- Set SPI
baudrate to 5.625 MHz to fit LCD and Gyroscope timing characteristics
- ILI9341 LCD
SPI interface max baud rate is 10MHz for write and 6.66MHz for read
- Gyroscope
l3gd20 SPI interface max baud rate is 10MHz for write/read
- stm32f429i_discovery_lcd.c
- Improve SPI
low level write routines (add check on BSY flag before to deselect the
LCD)
- Remove the
__IO attribute from these function’s parameters: LCD_SetLayer(),
LCD_SetColors(), LCD_GetColors(), LCD_SetTextColor() and
LCD_SetBackColor()
- stm32f429i_discovery_i2c_ee.c,
stm32f429i_discovery_i2c_ ioe.c
- Add a test in
Init() function; if the I2C is already configured, then there is no need
to reconfigure it again
- I2C_SPEED
define moved to stm32f429i_discovery.h file
- stm32f429i_discovery_sdram.c
- Update device
refresh counter value to fit with SDRAM timing characteristics
- Miscellaneous robustness
improvement
- Miscellaneous comments update
V1.0.0 / 20-September-2013 Main
Changes - First official version of the STM32F429 Discovery Board Drivers
License
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions
in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of STMicroelectronics nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|