ST7FLITE35F2M6 STMicroelectronics, ST7FLITE35F2M6 Datasheet - Page 18

• Manufacturer Part Number: ST7FLITE35F2M6
• Description: IC MCU 8BIT 8K FLASH 20SOIC
• Manufacturer: STMicroelectronics
• Series: ST7r

Specifications of ST7FLITE35F2M6

• Core Processor: ST7
• Core Size: 8-Bit
• Speed: 8MHz
• Connectivity: LINSCI, SPI
• Peripherals: LVD, POR, PWM, WDT
• Number Of I /o: 15
• Program Memory Size: 8KB (8K x 8)
• Program Memory Type: FLASH
• Ram Size: 384 x 8
• Voltage - Supply (vcc/vdd): 2.7 V ~ 5.5 V
• Data Converters: A/D 7x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 20-SOIC (7.5mm Width)
• Processor Series: ST7FLITE3x
• Core: ST7
• Data Bus Width: 8 bit
• Data Ram Size: 384 B
• Interface Type: LINSCI, SPI
• Maximum Clock Frequency: 8 MHz
• Number Of Programmable I/os: 15
• Number Of Timers: 4
• Operating Supply Voltage: 2.7 V to 5.5 V
• Maximum Operating Temperature: + 125 C
• Mounting Style: SMD/SMT
• Development Tools By Supplier: ST7FLITE-SK/RAIS, ST7MDT10-DVP3, ST7MDT10-EMU3, STX-RLINK
• Minimum Operating Temperature: - 40 C
• On-chip Adc: 10 bit, 7 Channel
• For Use With: 497-5858 - EVAL BOARD PLAYBACK ST7FLITE497-5085 - EVAL BOARD UNIV MOTOR CONTROL497-5049 - KIT STARTER RAISONANCE ST7FLITE
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Eeprom Size: -
• Lead Free Status / Rohs Status: Details

How to use the library
6.2.2 SPI
SPI: This part of the user manual contains the detailed description of all the functions for the
SPI. An example C program has been given at the end.
The SPI can be used as Single master (multiple slaves) and multi master systems in full du-
plex mode. This can be configured by using parallel port pins to control the SS pin by software.
The transfer of master or slave control can be implemented using a handshake method
through the I/O ports or by an exchange of code messages through the serial peripheral inter-
face system.
In order to respect the SPI protocol, you must define the configuration setting
SPI_SLAVE_CONFIG in ST7lib_config.h file as shown below, in order to be able to transmit
data in software slave mode. #define SPI_SLAVE_CONFIG To select any of the possible
communication modes described below you need to select the corresponding #define state-
ment inside the ST7lib_config.h file. These modes are applicable for all communication pe-
ripherals (SPI, SCI and I2C).
Polling:
With this mechanism the data can be transmitted or received by polling the status of the cor-
responding flag. Both single and continuous Transmission/Reception is possible. In the case
of continuous Transmission/Reception the function keeps control until all the requested data is
Transmitted/Received and hence the application software has the risk of losing control if there
is a breakdown in communication (the SCI mode is disabled). To avoid the risk, you can use
the single byte transmission with some timeout protection inside this mechanism. This mech-
anism can only be used with the SPI in half duplex mode. To use this mode, you must have se-
lected the following # define labels inside the ST7lib_config.h file:
Interrupt driven without communication buffer:
Data can be Transmitted/Received both in single as well as continuous mode through the in-
terrupt driven mechanism. In the continuous mode the user data is directly being read/written
from/to the addresses passed by the user. After each byte of data transfer an interrupt is ac-
knowledged and the control goes to the interrupt subroutine. The main advantage of using in-
terrupts rather than polling is that control does not stay in the function till the last data is Trans-
mitted/Received and hence the SPI can be used in full duplex mode. Here you should take
care not to read/write the user buffer until the Transmission/Reception completion. To use this
mode you must select the following # define labels inside the ST7lib_config.h file:
Notes:
1. If both SPI_ ITDRV_WITHOUTBUF_TX and SPI_ITDRV_WITHOUTBUF_RX are defined
in full duplex mode, then the program will perform either transmission or reception (only trans-
mission as per the present structure) since, the peripheral has a single interrupt for both
Transmission and Reception completion. Because of this correct full duplex communication
will be prevented. In order to operate the SPI in Full Duplex Mode, it is required that either the
18/235
SPI_POLLING_TX
SPI_POLLING_RX
SPI_ITDRV_WITHOUTBUF_TX
SPI_ITDRV_WITHOUTBUF_RX
-- For Transmission mode
-- For Transmission
-- For Reception
-- For Reception mode