Page Comparison

1142985 Table Row (tr) Table Cell (td) Anchor11429871142987td Anchor11429891142989 Table Row (tr) Table Cell (td) Anchor11429911142991 Table Cell (td) Anchor11429931142993 Table Row (tr) Table Cell (td) Anchor11429951142995 Table Cell (td) Anchor11429971142997

...

...

Anchor11430001143000No specification exists for SPI, a condition which invites technological divergence. So though the simplicity of the interface limits variations between implementations, the required transfer unit length, shift direction, clock frequency and clock polarity and phase do vary from device to device. Take as an example Figure C-3 the figure below which gives the bit form of a basic command/response exchange on a typical serial flash. The command and response both divide into 8-bit chunks, the transfer unit for the device. Within these units, the data is transferred from most significant bit (MSB) to least significant bit (LSB), which is the slave’s shift direction. Though not evident from the diagram—the horizontal axis being labeled in clocks rather than time—the slave cannot operate at a frequency higher than 20-MHz. Finally, the clock signal prior to slave select activation is low (clock polarity or CPOL is 0), and data is latched on the rising clock edge (clock phase or CPHA is 0). Together, those are the aspects of SPI communication that may need to be configured: Anchor11430041143004

• Transfer unit length. A transfer unit is the underlying unit of commands, responses and data. The most common value is eight bits, though slaves commonly require (and masters commonly support) between 8 and 16 bits.

...

• Shift direction. Either the MSB or LSB of each transfer unit can be the first transmitted on the data line.

...

• Clock frequency. Limits are usually imposed upon the frequency of the clock signal. Of all variable SPI communication parameters, only this one is explicitly set by the device driver.

...

• Clock polarity and phase (CPOL and CPHA). SPI communication takes place in any of four modes, depending on the clock phase and clock polarity settings:

...

• • If CPOL = 0, the clock is low when inactive.

...

• • If CPOL = 1, the clock is high when inactive.

...

• • If CPHA = 0, data is “read” on the leading edge of the clock and “changed” on the following edge.

...

• • If CPHA = 1, data is “changed” on the leading edge of the clock and “read” on the leading edge.

...

...

• The most commonly-supported settings are {CPOL, CPHA} = {0, 0} and {1, 1}.

...

• Slave select polarity. The “active” level of the slave select may be electrically high or low. Low is ubiquitous, high rare.

...

• Panel
  title Example SPI transaction

...

• Image Added

  
  

11430201143020A BSP is required that abstracts a CPU’s SPI peripheral. The port includes one code file named according to the following rubric:anchor

11430211143021FS_DEV_<dev_name>_BSP.C or FS_DEV_<dev_name>_SPI_BSP.c Anchor

11430221143022This file is generally placed with other BSP files in a directory named according to the following rubric: Anchor11430231143023

\Micrium\Software\EvalBoards\<manufacturer>\<board_name>

Anchor11430241143024\<compiler>\BSP\ Anchor11430251143025

Several example ports are included in the µC/FS distribution in files named according to the following rubric: Anchor11430261143026

\Micrium\Software\uC-FS\Examples\BSP\Dev\NAND\<manufacturer>\<cpu_name>

...

\Micrium\Software\uC-FS\Examples\BSP\Dev\NOR\<manufacturer>\<cpu_name>
 Anchor11430281143028\Micrium\Software\uC-FS\Examples\BSP\Dev\SD\SPI\<manufacturer>\<cpu_name> Anchor11430291143029
Check all of these directories for ports for a CPU if porting any SPI device; the CPU may be been used with a different type of device, but the port should support another with none or few modifications. Each port must implement the functions to be placed into a FS_DEV_SPI_API structure:anchor
 Code Block
...
 const 
 {
    FSDev_BSP_SPI_Open,

    FSDev_BSP_SPI_Close,

    FSDev_BSP_SPI_Lock,

    FSDev_BSP_SPI_Unlock,

    FSDev_BSP_SPI_Rd,

    FSDev_BSP_SPI_Wr,

    FSDev_BSP_SPI_ChipSelEn,

    FSDev_BSP_SPI_ChipSelDis,

    FSDev_BSP_SPI_SetClkFreq
 };
 HTML Table
summary
class
Code_Listing
 Table Row (tr)
 Table Cell (td)
rowspan
11
 Anchor
1143032
1143032
language
cpp
const  FS_DEV_SPI_API  FSDev_####_BSP_SPI =
 {
 Anchor
1143033
1143033
 Anchor
1143034
1143034
 Anchor
1143035
1143035
 Anchor
1143036
1143036
 Anchor
1143037
1143037
 Anchor
1143038
1143038
 Anchor
1143039
1143039
 Anchor
1143040
1143040
 Anchor
1143041
1143041
 Anchor
1143042
1143042
 Table Row (tr)
 Table Row (tr)
 Table Row (tr)
 Table Row (tr)
 Table Row (tr)
 Table Row (tr)
 Table Row (tr)
 Table Row (tr)
 Table Row (tr)
 Table Row (tr)
...

};
The functions which must be implemented are listed and described in Table C-4 the table below. SPI is no more than a physical interconnect. The protocol of command-response interchange the master follows to control a slave is specified on a per-slave basis. Control of the chip select (SSEL) is separated from the reading and writing of data to the slave because multiple bus transactions (e.g., a read then a write then another read) are often performed without breaking slave selection. Indeed, some slaves require bus transactions (or “empty” clocks) AFTER the select has been disabled.anchor
 Panel
...
 Function Description Open()
 HTML Table
summary
class
Plain_Table
 Table Row (tr)
 Table Cell (td)
 Anchor
1143070
1143070
 Table Cell (td)
 Anchor
1143072
1143072
 Table Row (tr)
 Table Cell (td)
 Anchor
1143074
1143074
 Table Cell (td)
 Anchor
1143076
1143076
title
SPI port functions

Function
Description
Open()
Open (initialize) hardware for SPI.
 Table Row (tr)
 Table Cell (td)
 Anchor
1143078
1143078
Close()