4 handling interfaces and data service resources, 1 module states, 1 state 1: default - no java running – Siemens XT65 User Manual
Page 33: Module states 4.4.1.1, State 1: default – no java running, Figure 8, Module state 1, 1 state 1: default – no java running
Java User’s Guide
4.4 Handling Interfaces and Data Service Resources
35
s
wm_java_usersguide_v12
Page 33 of 123
2008-02-25
Confidential / Released
4.4
Handling Interfaces and Data Service Resources
To develop Java applications the developer must know which resources, data services and
hardware access are available.
•
There are multiple AT parsers available
•
There is hardware access over
- two serial interfaces: ASC1 and ASC0 (both fully accessible).
- general purpose I/O. To configure the hardware access, please refer to
.
- I2C/SPI
- All restrictions of combinations are described in
•
A Java application has:
- instances of the AT command class, one with CSD and the others without, each of which
would, in turn, be attached to one of the AT parsers.
- two instances of access to a serial interface, ASC0 and ASC1, through the CommCon-
nection API. Access to the control lines of these interfaces through CommConnection-
ControlLines (TC65 only).
- System.out over any serial interface or into the file system
4.4.1
Module States
The module can exist in the following six states in relation to a Java application, the serial inter-
faces, GPIO and I2C/SPI. See
for information about the AT commands referenced. A state
transition diagram is shown in
This section shows how Java applications must share AT parsers, GPIO pins and I2C/SPI
resources. DAC, ADC and DAI are not discussed here.
Color legend for the following figures:
4.4.1.1
State 1: Default – No Java Running
This is the default state. The Java application is inactive and there is an AT interface with CSD
on ASC0 as well as ASC1. The initial state of the pins is according to [4].
Figure 8: Module State 1