Nokia 3220 서비스 매뉴얼

다운로드
페이지 70
RH-37
System Module
Nokia Customer Care
Page 28
 Nokia Corporation
Issue 1 07/04
Function
FCI operation is based on a few main principles. The external module is attached to the 
terminal, application (typically Java application) is downloaded to the terminal memory 
and it is automatically started (the first time module is attached to the terminal). Con-
sumer starts the application from UI menu; application establishes a communication 
channel between external module and terminal SW execution environment (typically 
Java Virtual Machine) allowing application code to directly interact with the resources 
located in the module.
FCI is implemented by emulating I2C with general I/O pins. 
Figure 10:  FCI interface
Device detection Device is detected when it is being attached to the terminal. The 
power out supply is activated.  
Identification 
Each time a external module is attached to the terminal it is identified via I2C bus. 
Authentication ensures that the attached module is verified to be fully operational with 
Nokia terminal. If authentication fails the power supply is turned off.
Application downloading is automatically initiated right after the external module has 
been attached to the terminal and the terminal has power on. Cover checks whether the 
application is already installed before file transfer is initiated. 
A communication channel is available between the external module and the applica-
tion that has been earlier installed to the terminal.
Hot swap enables changing external module on-the-fly without re-booting the terminal.
The FCI concept has a limit of simultaneous connection of 4 covers having 256 applica-
tions (HW resources) in each cover at maximum. Each cover (module) has 10-bit address.
Fu
nc
tio
na
l C
ov
er
(s
)
GND
FCI
SCL
SDA
FCINT
VOUT
Terminal
EM
Interrupt
I2C (sw)
UPP
Ge
nI
O