SPI_FLASH

  ******************** (C) COPYRIGHT 2010 STMicroelectronics *******************
  * @file    SPI/SPI_FLASH/readme.txt 
  * @author  MCD Application Team
  * @version V3.4.0
  * @date    10/15/2010
  * @brief   Description of the SPI SPI_FLASH Example.
  ******************************************************************************
  * THE PRESENT FIRMWARE WHICH IS FOR GUIDANCE ONLY AIMS AT PROVIDING CUSTOMERS
  * WITH CODING INFORMATION REGARDING THEIR PRODUCTS IN ORDER FOR THEM TO SAVE
  * TIME. AS A RESULT, STMICROELECTRONICS SHALL NOT BE HELD LIABLE FOR ANY
  * DIRECT, INDIRECT OR CONSEQUENTIAL DAMAGES WITH RESPECT TO ANY CLAIMS ARISING
  * FROM THE CONTENT OF SUCH FIRMWARE AND/OR THE USE MADE BY CUSTOMERS OF THE
  * CODING INFORMATION CONTAINED HEREIN IN CONNECTION WITH THEIR PRODUCTS.
  ******************************************************************************
   
Example Description

This example provides a basic example of how to use the SPI firmware library and an associate SPI FLASH driver to communicate with an M25P64 or M25P128 FLASH.

The first step consist in reading the SPI Flash ID. A comparison between the ID read from SPI flash and the expected one is done and LED1 is turned on in case of success otherwise LED2 is turned on.

Using this driver the program performs an erase of the sector to be accessed, a write of a Tx_Buffer, defined in the main.c file, to the memory followed by a read of the written data. Then data read from the memory stored in the Rx_Buffer are compared with the expected values of the Tx_Buffer. The result of this comparison is stored in the "TransferStatus1" variable.

A second erase of the same sector is done at the end, and a test is done to be sure that all the data written there are erased further to the sector erase. All the data location are read and checked with 0xFF value. The result of this test is stored in "TransferStatus2" variable which is FAILED in case of error.

The SPI1 is configured as Master with an 8-bit data size. The SPI1 baudrate is set to 18 Mbit/s (for Value line devices the baudrate is set to 12 Mbit/s). The FLASH_WriteAddress and the FLASH_ReadAddress where the program start the write and the read operations are defined in the main.c file.

Directory contents
Hardware and Software environment

On STM32100E-EVAL Rev A, the SPI FLASH example is only working in standalone mode without debugger connection and just only after a POR reset.

How to use it ?

In order to make the program work, you must do the following :

Tip: You can tailor the provided project template to run this example, for more details please refer to "stm32f10x_stdperiph_lib_um.chm" user manual; select "Peripheral Examples" then follow the instructions provided in "How to proceed" section.

Note:
  • Low-density Value line devices are STM32F100xx microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes.
  • Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes.
  • Medium-density Value line devices are STM32F100xx microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes.
  • Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes.
  • High-density Value line devices are STM32F100xx microcontrollers where the Flash memory density ranges between 256 and 512 Kbytes.
  • High-density devices are STM32F101xx and STM32F103xx microcontrollers where the Flash memory density ranges between 256 and 512 Kbytes.
  • XL-density devices are STM32F101xx and STM32F103xx microcontrollers where the Flash memory density ranges between 512 and 1024 Kbytes.
  • Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers.

© COPYRIGHT 2010 STMicroelectronics

STM32F10x Standard Peripherals Library: Footer

 

 

 

      For complete documentation on STM32(CORTEX M3) 32-bit Microcontrollers platform visit  www.st.com/STM32