ST7FLITE25M6TR STMicroelectronics, ST7FLITE25M6TR Datasheet - Page 25

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

Specifications of ST7FLITE25M6TR

• Core Processor: ST7
• Core Size: 8-Bit
• Speed: 8MHz
• Connectivity: 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.4 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: ST7FLITE2x
• Core: ST7
• Data Bus Width: 8 bit
• Development Tools By Supplier: ST7FLITE-SK/RAIS, ST7MDT10-DVP3, ST7MDT10-EMU3, STX-RLINK
• For Use With: 497-5858 - EVAL BOARD PLAYBACK ST7FLITE
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Eeprom Size: -
• Lead Free Status / Rohs Status: Details

7. rx_stdid - This declares the memory for storing the standard id part of the message to be re-
c e i v e d . T h e l e n g t h o f t h e t a b l e i s t h e s a m e a s d e f i n e d b y t h e p a r a m e t e r
NO_OF_RX_HANDLES in the file user.h.
8. rx_extid - This declares the memory for storing the extended id part of the message to be re-
c e i v e d . T h e l e n g t h o f t h e t a b l e i s t h e s a m e a s d e f i n e d b y t h e p a r a m e t e r
NO_OF_RX_HANDLES in the file user.h.
9. rx_dlc[ ] - This table stores the length for the message/s to be received. The length of the
table is the same as defined by the parameter NO_OF_RX_HANDLES and the value/s stored
inside the table is/are the same as defined by the parameter TX_MSGx_DLC in the file user.h.
1 0 . r x _ d a t a _ p t r [ ] - T h i s p o i n t e r t a b l e s t o r e s t h e a d d r e s s o f r e c e i v e b u f f e r / s
(MSGx_Rx_Buffer). The length of the table is the same as defined by the parameter
NO_OF_RX_HANDLES in the file user.h.
6.2.4.6 Tx & Rx BUFFER USAGE
Data can be accessed through the Tx & Rx buffers using the tx_handle & rx_handle as an
index. For example, data can be written into the MSGx_Tx_Buffer using the pointer
tx_data_ptr[x], where x = tx_handle for the message. Similarly, data can be received from
MSGx_Rx_Buffer using the pointer rx_data_ptr[x], where x = rx_handle for the message.
6.2.4.7 IMPLEMENTATION HINTS
– CanSleep( ) service must not be called when message transmission is in progress otherwise
– Confirmation flag is set by the driver after the successful transmission of a message and flag
– Indication flag is set by the driver for a message received and this flag has to be cleared by
– Overflow flag is set by the driver if the indication flag is not cleared by the application or mes-
If the overflow is set it means that the new message has been overwritten over the previous
message. Overflow flag has to be cleared by the application. Application must call CanInter-
ruptDisable( ) and CanInterruptRestore( ) services when clearing the overflow flag in order to
avoid CAN interrupt.
– While copying data from receive buffer, application must call CanInterruptDisable( ) and
sleep mode is not entered and service returns KCANFAILED. Also CanTransmit( ) service
shall not be called while the CAN driver is in sleep mode.
has to be cleared by the application. Application must call CanInterruptDisable( ) and Can-
InterruptRestore( ) services when clearing the confirmation flag in order to avoid CAN inter-
rupt.
the application. Application must call CanInterruptDisable( ) and CanInterruptRestore( )
services when clearing the indication flag in order to avoid CAN interrupt.
sage is not copied by the application from the global buffer into the application buffer.
CanInterruptRestore( ) services in order to avoid a CAN interrupt. Similarly, while copying
How to use the library
25/235