SPI Overview
SPI, abbreviation of Serial Peripheral Interface, is defined by Motorola on its processors of MC68HCXX Series first. The SPI interface is mainly applicable to EEPROM, FLASH, real-time clock, AD converter, digital signal processor and digital signal decoder. SPI, as a high-speed, full-duplex, synchronous communication bus, imports the principle of “master” and “Slave” devices. In any explicit SPI communication, there will be a master device and one or more slave devices. The master device is responsible for starting and ending communication sessions. The cellular module is the master device in SPI communication by default, while the external device is the slave device. If you need the cellular module to be the slave device, please contact the manufacturer.
A general SPI interface generally contains 4 communication lines:
• SCK: Its main function is to transmit clock signals from the master device to the slave device and control the timing and rate of data exchange.
• SS/CS: Chip select between the slave device and the master device, as a result, the selected slave device can be accessed by the master device;
• SDO/MOSI: Also called Tx-Channel on the master device. As a data output port, it is mainly used for sending data in SPI device;
• SDI/MISO: Also called Rx-Channel on the master device, As a data input port, it is mainly used for receiving data in SPI device;
The SPI communication is full-duplex, which means the data can be transmitted in both directions simultaneously. For SPI, this is implemented via the MOSI (Master Out, Slave In) and MISO (Master In, Slave Out).
In SPI, it owns a total of 4 working modes, which are determined by different configurations of clock polarity (CPOL) and phase (CPHA), see following table:
SPI Applications on different platforms
The BC25PA platform only supports SPI working modes 0 and 3, and other platforms support all working modes.
SPI Bus Applications
Interact with MCU#
When interacting with the MCU, the cellular module acts as the Master device and the MCU acts as the Slave device. Before that, relevant corresponding protocol which defines the connotation of data read and written by cellular module clearly shall be provided by MCU side. At this time, the MCU side is similar to an ordinary SPI peripheral and needs to provide the reading and writing meaning of the register. When the cellular module writes a value into the register, the MCU can obtain the commands of the cellular module; meanwhile, the MCU can independently update the register (analog) value and wait for the cellular module to read and obtain the MCU data.
Examples are as follows:：
Virtual register table in MCU
The protocol is defined as follows：
The cellular module sends: 0x7F (packet header) + 8-bit control segment (0: read command, 1: write command) + 8-bit register number + 8-bit data length + N bytes of data (That will be empty when reading the command)
When the MCU receives the cellular module data and determines that the data is legal, the MCU will reply: 0x7E (packet header) + 8-bit register number + 8-bit data length + N bytes of data (That will be empty when reading the command)
Example：
Cellular module -> MCU: 0x7F 0x00 0x01 0x01 (read 1 data from register) MCU -> Cellular module: 0x7E 0x01 0x01 0x01 (MCU initialization is complete)
SPI LCD Display
It owns two methods to connect SPI LCD based on cellular modules, one is a dedicated LCD SPI interface and the other is general SPI. The connection lines between the cellular module and the LCD display are shown in the figure below:
The DOUT pin is used for serial data transmission. It is a bilateral data communication line between the LCD display and external device such as a controller or micro-controller.
• The SCL/CLK pin is used for clock synchronization during serial data transmission. It provides the clock signal for data transmission for sake of ensuring the proper data synchronization and transmission.
• The RS/DC pin is used to indicate the type of data sent to the LCD, i.e. data or command. When the RS/DC pin is low, it means a command is sent; when the RS pin is high, it means data is sent.
• The RST pin is used to reset the LCD display to its initial state. When the RST pin receives a reset signal, the display will re-initialize and clear the previous status and data.
• The CS pin is used to select or activate the LCD chip. When the CS pin is low, which indicates that the chip is aimed at communication or operation.
When the LCD SPI pin connects to the LCD, the RS, RST and CS pins can only select as specified in the hardware manual. For example, in EC600U series, the CS pin, RST pin and RS pin will be 65, 64 and 63 respectively. See LCD SPI interface initialization as follows:
lcd.lcd_init(lcd_init_data, lcd_width, lcd_hight, lcd_clk, data_line, line_num, lcd_type, lcd_invalid, lcd_display_on, lcd_display_off, lcd_set_brightness)
When the general SPI pin connects to the LCD, the RS, RST and CS pins can be selected according to actual demand, but the pin number needs to be specified in initialization. See following contents in detail:
lcd.lcd_init(lcd_init_data, lcd_width, lcd_hight, lcd_clk, data_line, line_num, lcd_type, lcd_invalid, lcd_display_on, lcd_display_off, lcd_set_brightness, lcd_interface, spi_port, spi_mode, cs_pin, dc_pin, rst_pin)
Compared with LCD SPI pins, SPI mode, SPI port, CS, DC, and RST pins are added to the initialization parameters.
MCP2515 CAN Controller
Most CAN controllers in market use SPI bus communication, among which, the MCP2515 is the most widely used. Therefore, in this chapter, it will introduce how to use the Quecpython SPI module to communicate with MCP2515.
The MCP2515 connection diagram is as follows：
The following contents display the codes for the SPI interface used in the MCP2515 driver.
SPI Bus FAQ and Error Investigation
1.Hardware connection problem: The SPI interface requires four lines (MISO, MOSI, SCLK and CS) for connection. If these lines are not connected correctly, it may cause communication failure.
2.Power and GND issues: If the power and the GND of the SPI device are not connected correctly, it may also cause failed comminication.
3.SPI mode error: SPI has four modes, which are determined by clock polarity and phase. If the SPI modes of the master and slave devices do not match, the communication error may occur.
4.Clock frequency is unduly high: If the clock frequency of SPI is set unduly high, which exceeds the capability of the device, data transmission errors will appear.
5.Mismatch of data bits: The SPI data is usually 8 or 16 bits. If the number of data bits sent and received do not match, data errors may occur as well.
6.Chip selection line control error: In a system with multiple slave devices, if the chip select line is not controlled correctly, communication chaos may occur.
7.Level mismatch problem: If the levels of the master device and the slave device (i.e., 3.3V and 5V) do not match, it may cause communication problems or device damage.
**8.Device compatibility issues: **Since there is no official standard for SPI, the implementation of different devices may be varied， which may cause compatibility issues between devices.
9.Line Noise and Interference: If the SPI line is too long or there exists high-frequency noise in the environment, it may affect the SPI signal quality and cause communication errors.
