Siemens TC45 User manual

Siemens Cellular Engine
JAVA™
User’s
Guide
Version: 02
DocID: TC45_JAVA User's Guide_V02

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 2 of 72 30.06.2003
Document Name: TC45 JAVA User's Guide
Version: 02
Date: June 30, 2003
DocId: TC45_JAVA User's Guide_V02
Status: Confidential / Released
General Notes
Product is deemed accepted by recipient and is provided without interface to recipient’s products. The
documentation and/or product are provided for testing, evaluation, integration and information
purposes. The documentation and/or product are provided on an “as is” basis only and may contain
deficiencies or inadequacies. The documentation and/or product are provided without warranty of any
kind, express or implied. To the maximum extent permitted by applicable law, Siemens further
disclaims all warranties, including without limitation any implied warranties of merchantability,
completeness, fitness for a particular purpose and non-infringement of third-party rights. The entire risk
arising out of the use or performance of the product and documentation remains with recipient. This
product is not intended for use in life support appliances, devices or systems where a malfunction of
the product can reasonably be expected to result in personal injury. Applications incorporating the
described product must be designed to be in accordance with the technical specifications provided in
these guidelines. Failure to comply with any of the required procedures can result in malfunctions or
serious discrepancies in results. Furthermore, all safety instructions regarding the use of mobile
technical systems, including GSM products, which also apply to cellular phones must be followed.
Siemens or its suppliers shall, regardless of any legal theory upon which the claim is based, not be
liable for any consequential, incidental, direct, indirect, punitive or other damages whatsoever
(including, without limitation, damages for loss of business profits, business interruption, loss of
business information or data, or other pecuniary loss) arising out the use of or inability to use the
documentation and/or product, even if Siemens has been advised of the possibility of such damages.
The foregoing limitations of liability shall not apply in case of mandatory liability, e.g. under the German
Product Liability Act, in case of intent, gross negligence, injury of life, body or health, or breach of a
condition which goes to the root of the contract. However, claims for damages arising from a breach of
a condition, which goes to the root of the contract, shall be limited to the foreseeable damage, which is
intrinsic to the contract, unless caused by intent or gross negligence or based on liability for injury of
life, body or health. The above provision does not imply a change on the burden of proof to the
detriment of the recipient. Subject to change without notice at any time. The interpretation of this
general note shall be governed and construed according to German law without reference to any other
substantive law.
Copyright
Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its
contents and communication thereof to others without express authorization are prohibited. Offenders
will be held liable for payment of damages. All rights created by patent grant or registration of a utility
model or design patent are reserved.
Copyright © Siemens AG 2003
Trademark notices
MS Windows® is a registered trademark of Microsoft Corporation.
Java™ and Sun™ ONE Studio 4.1 Mobile Edition are registered trademarks of Sun Microsystems Inc.
Borland® JBuilder® Enterprise MobileSet 3 and JBuilder® Personal MobileSet 3 are registered
trademarks of Borland Software Corporation

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 3 of 72 30.06.2003
Table of Contents
0Document history....................................................................................................... 9
1Introduction ...............................................................................................................10
1.1 Overview...........................................................................................................10
1.2 Related documents ..........................................................................................10
1.3 Terms and abbreviations.................................................................................11
2Installation .................................................................................................................12
2.1 System requirements.......................................................................................12
2.2 Installation CD..................................................................................................12
2.2.1 Components .........................................................................................13
2.2.1.1 WinMUX 2.1 .........................................................................................13
2.2.1.2 Module Exchange Suite........................................................................13
2.2.1.3 IMPSiemens .........................................................................................13
2.2.1.4 AT Java Open Framework (AJOF) .......................................................13
2.3 SMTK installation.............................................................................................14
2.3.1 Installing the Standard Development Toolkit.........................................14
2.3.2 Installing the SMTK environment ..........................................................14
2.3.3 Installing Sun ONE Studio 4.1 Mobile Edition .......................................15
2.3.4 Installing Borland JBuilder MobileSet 3.................................................15
2.3.4.1 JBuilder Enterprise Edition MobileSet 3................................................15
2.3.4.2 JBuilder Personal Edition MobileSet 3 ..................................................15
2.4 Uninstall............................................................................................................16
2.4.1 Uninstall WinMux..................................................................................16
2.5 Upgrades ..........................................................................................................16
3Maintenance ..............................................................................................................17
3.1 Power Saving ...................................................................................................17
3.2 Charging ...........................................................................................................17
3.3 Alarm mode ......................................................................................................18

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 4 of 72 30.06.2003
3.4 Shut down ........................................................................................................18
3.4.1 Automatic shutdown .............................................................................18
3.4.2 Restart after switch off..........................................................................18
3.5 Special AT command set for Java applications.............................................19
3.5.1 Switching from data mode to command mode......................................19
3.5.2 Mode indication after MIDlet startup .....................................................19
3.5.3 Long responses....................................................................................19
3.6 Restrictions ......................................................................................................20
3.6.1 Flash file system...................................................................................20
3.6.2 Memory ................................................................................................20
3.7 Performance statements .................................................................................20
3.7.1 Java......................................................................................................20
3.7.2 Pin-IO...................................................................................................21
4Software platform .....................................................................................................22
4.1 Software architecture ......................................................................................22
4.2 Interfaces..........................................................................................................23
4.2.1 ASC0 - Serial device ............................................................................23
4.2.2 General Purpose I/O ............................................................................23
4.2.3 ASC1....................................................................................................23
4.2.4 Digital Audio Interface (DAI) .................................................................23
4.2.5 JVM interfaces......................................................................................24
4.2.5.1 IMP 1.0 API to TCP/IP..........................................................................24
4.3 Data flow of a Java application running on the module................................25
4.4 Handling interfaces and data service resources ...........................................26
4.4.1 Module states .......................................................................................26
4.4.1.1 State 1: default – no Java application is running...................................27
4.4.1.2 State 2: no Java application is running, general purpose I/O................27
4.4.1.3 State 3: no Java application is running, AT interface on ASC1.............27
4.4.1.4 State 4: default – Java application active..............................................27
4.4.1.5 State 5: Java application active, general purpose I/O...........................28
4.4.1.6 State 6: Java application active, Java interface to ASC1 ......................28
4.4.2 Module state transitions........................................................................29
5MIDlets .......................................................................................................................31
5.1 MIDlet documentation......................................................................................31
5.2 MIDlet life cycle ................................................................................................31
5.3 Hello World MIDlet ...........................................................................................32

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 5 of 72 30.06.2003
6AT Java Open Framework (AJOF)............................................................................34
6.1 AT Commands..................................................................................................34
6.1.1 Mobile engine status.............................................................................34
6.1.2 Voice call handling................................................................................34
6.1.3 CSD call and GPRS connection handling .............................................34
6.1.4 Short Message Service ........................................................................34
6.1.5 Phonebook features .............................................................................35
6.1.6 Pin I/O ..................................................................................................35
7File transfer to module .............................................................................................36
7.1 Module Exchange Suite...................................................................................36
7.1.1 Windows based....................................................................................36
7.1.2 Command line based............................................................................36
7.2 Over the Air Provisioning ................................................................................36
7.3 Security issues.................................................................................................36
7.3.1 Module Exchange Suite........................................................................37
7.3.2 OTAP ...................................................................................................37
8Over The Air Provisioning (OTAP) ...........................................................................38
8.1 Introduction to OTAP.......................................................................................38
8.2 OTAP overview.................................................................................................38
8.3 OTAP Parameters.............................................................................................39
8.4 Short message format .....................................................................................40
8.5 Java file format.................................................................................................41
8.6 Procedures .......................................................................................................42
8.6.1 Install/Update .......................................................................................42
8.6.2 Delete...................................................................................................43
8.7 Time out values and result codes...................................................................44
8.8 Notes .............................................................................................................44
8.9 How to .............................................................................................................45

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 6 of 72 30.06.2003
9Compiling and running a program without a Java IDE ..........................................46
9.1 Build results .....................................................................................................46
9.1.1 JAD file.................................................................................................46
9.2 Compile and run on a PC.................................................................................47
9.3 Run on the module with manual start ............................................................47
9.4 Run on the module with Autostart..................................................................47
9.4.1 Switch on Autostart...............................................................................48
9.4.2 Switch off Autostart ..............................................................................48
10 Debug environment...................................................................................................49
10.1 Data flow of a Java application in the debug environment...........................49
10.1.1 Serial port and pin I/O handling differences..........................................50
10.1.2 Restrictions...........................................................................................50
10.1.3 RS-232 emulator ..................................................................................50
10.2 Java IDE............................................................................................................50
10.2.1 Sun ONE Studio 4.1 Mobile Edition ......................................................51
10.2.1.1 Switching emulators .............................................................................52
10.2.1.2 Projects ................................................................................................53
10.2.1.3 Templates ............................................................................................54
10.2.1.4 Examples..............................................................................................54
10.2.1.5 Compile and run ...................................................................................54
10.2.2 JBuilder Mobile Edition .........................................................................54
10.2.2.1 TC45 SMTK in Personal Edition ...........................................................54
10.2.2.1.1 Integration of TC45 SMTK ...............................................................55
10.2.2.1.2 Restoring original settings................................................................57
10.2.2.2 TC45 SMTK in Enterprise Edition.........................................................58
10.2.2.3 Examples..............................................................................................59
10.2.2.4 Projects and templates.........................................................................60
10.2.2.5 Compile and run ...................................................................................61
10.3 Breakpoints ......................................................................................................61
11 Java Tutorial ..............................................................................................................62
11.1 Using the AT command API ............................................................................62
11.1.1 Class ATCommand ..............................................................................62
11.1.1.1 Instantiation with or without CSD support .............................................62
11.1.1.2 Sending an AT command to the device, the send() method .................63
11.1.1.3 Data connections..................................................................................63
11.1.1.4 Synchronization....................................................................................64
11.1.2 ATCommandResponseListener interface .............................................65
11.1.2.1 Non-blocking ATCommand.send() method...........................................65
11.1.3 ATCommandListener interface.............................................................65

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 7 of 72 30.06.2003
11.1.3.1 ATEvents..............................................................................................66
11.1.3.2 Implementation.....................................................................................66
11.1.3.3 Registering a listener with an ATCommand instance............................67
11.2 Programming the MIDlet..................................................................................68
11.2.1 Threads ................................................................................................68
11.2.2 Example ...............................................................................................68
11.3 AJOF .............................................................................................................70
11.3.1 Example ...............................................................................................70

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 8 of 72 30.06.2003
Figures
Figure 1: Overview ...............................................................................................................10
Figure 2: Test overview ........................................................................................................21
Figure 3: Interface Configuration..........................................................................................24
Figure 4: Data flow of a Java application running on the module..........................................25
Figure 5: Module State 1 ......................................................................................................27
Figure 6: Module State 2 ......................................................................................................27
Figure 7: Module State 3 ......................................................................................................27
Figure 8: Module State 4 ......................................................................................................27
Figure 9: Module State 5 ......................................................................................................28
Figure 10: Module State 6 ....................................................................................................28
Figure 11: Module State Transition Diagram ........................................................................29
Figure 12: OTAP Overview...................................................................................................38
Figure 13: OTAP: Install/Update Information Flow The messages in brackets are optional..42
Figure 14: OTAP: Delete Information Flow...........................................................................43
Figure 15: Data flow of a Java application in the debug environment ...................................49
Figure 16: Sun ONE Studio - The installed emulators. .........................................................51
Figure 17: Sun ONE Studio - Switching to the Siemens emulator. .......................................52
Figure 18: Sun ONE Studio - Project Manager.....................................................................53
Figure 19: Sun ONE Studio - Selecting a template...............................................................54
Figure 20: Different JDK must be set in User Home.............................................................55
Figure 21: Dialog box after changing the JDK to Siemens IMP Wireless Toolkit. .................56
Figure 22: Original setting for User Home ............................................................................57
Figure 23: JBuilder - JDK settings........................................................................................58
Figure 24: JBuilder - Siemens Library ..................................................................................58
Figure 25: JBuilder - Sample Projects ..................................................................................59
Figure 26: JBuilder - Configuring a new project....................................................................60
Figure 27: JBuilder - Project Properties................................................................................61
Tables
Table 1: Java AT commands................................................................................................30
Table 2: A typical sequence of MIDlet execution is:..............................................................32
Table 3: Parameters and keywords......................................................................................39

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 9 of 72 30.06.2003
0 Document history
Preceding document: "TC45 JAVA User's Guide" Version 01
New document: "TC45 JAVA User's Guide" Version 02
Chapter Page What is new
11.3.1 70 Revised example

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 10 of 72 30.06.2003
1 Introduction
1.1 Overview
The TC45 module features an ultra-low profile and low-power consumption for data, voice,
SMS and fax. With Java technology and up to nine digital I/O ports, the module enables
easy integration of your application.
This document explains how to work with the TC45 module, the installation CD and the tools
provided on the installation CD.
Customer Application
TC45
ROM
Customer SW
RAM
Customer Application
ROM
RAM
TCxx
µC
Customer SW
Old solution:
The customer application was
distributed across 2 µC, external µC
and internal µC on the module
New solution:
The customer application
exists only on the module
Figure 1: Overview
1.2 Related documents
In addition to the Java Docs for the development API (see Chapter 4), the following
documents are included with the SMTK:
[1] Multiplexer Installation Guide
[2] Application Note 23: Installing TC45 Module on DSB45
[3] DSB45 Support Box - Evaluation Kit for Siemens Cellular Engines
[4] TC45 AT Command Set
[5] TC45 Hardware Interface Description
[6] Java doc \IMPSIEMENS\doc\html\index.html

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 11 of 72 30.06.2003
1.3 Terms and abbreviations
Abbreviation Description
API Application Program Interface
ASC Asynchronous Serial Connection
CLDC Connected Limited Device Configuration
CSD Circuit-Switched Data
DAI Digital Audio Interface
DCD Data Carrier Detect
DSR Data Set Ready
GPIO General Purpose I/O
GPRS General Packet Radio Service
GPS Global Positioning System
HTTP Hypertext Transfer Protocol
I/O Input/Output
IDE Integrated Development Environment
IMP Information Module Profile
IP Internet Protocol
J2ME™ Java 2 Mobile Edition
J2SE™ Java 2 Standard Edition
JAD Java Application Description
JAR Java Archive
JDK Java Development Kit
JVM Java Virtual Machine
LED Light Emitting Diode
ME Mobile Engine
MIDP Mobile Information Device Protocol
OTA Over The Air
OTAP Over The Air Provisioning of Java Applications
PDP Packet Data Protocol
PDU Protocol Data Unit
SDK Standard Development Kit
SMS Short Message Service
SMTK Siemens Mobile Toolkit
TCP Transfer Control Protocol
URC Unsolicited Result Code
URL Universal Resource Locator
VBS Visual Basic Script

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 12 of 72 30.06.2003
2 Installation
2.1 System requirements
The Siemens Mobility Toolkit (SMTK) TC45 requires that you have:
1. Windows 2000 or Windows XP installed
2. 35 Mbytes free disk space
3. Administration privileges
4. Java 2 SDK, Standard Edition version 1.3 or 1.4. To install the JDK version 1.4.1
provided, follow the instructions in Section 2.3.1. In case you wish to use the Java 2 SDK
version 1.3 please download the version from http://java.sun.com/j2se/1.3/download.html
If a Java IDE such as Sun ONE Studio 4.1 Mobile Edition, Borland JBuilder Enterprise
MobileSet 3 or JBuilder Personal MobileSet 3 is installed, it can be integrated into the SMTK
environment during the installation of the SMTK. To install Sun ONE Studio or Borland
JBuilder, follow the installation instructions in Section 2.3.3 and Section 2.3.4 respectively.
2.2 Installation CD
The Siemens Mobility Toolkit TC45 Installation CD includes:
· MuxInstall.pdf
- mux_driver_installation_guide_vxx.pdf
· Module Exchange Suite
· IMPSiemens
- bin
- classes
- doc
· html
· javadocs for STMK APIs
- lib
· classes.zip
- src
· diverse examples
· AT Java Open Framework
· JDK 1.4.1_02
- J2sdk-1_4_1_02-windows-i586.exe
· Sun One Mobile Edition
- ffj_me_win32.exe
· Documents:
- dsb_45_an23_inst_tc45_vxx.pdf
- dsb45_hd_vxx.pdf
- tc45_atc_vxx.pdf
- tc45_hd_vxx.pdf
· java_user_guide_v01.pdf (this document)
Please note that “vxx” refers to the version number of the document.

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 13 of 72 30.06.2003
2.2.1 Components
2.2.1.1 WinMUX 2.1
The multiplexer mode enables one serial interface to transmit data to three different
customer applications. This is achieved by providing three virtual channels using a
multiplexer. The multiplexer is necessary for the SMTK environment. Information how to
install the provided multiplexer sources can be found in [1].
2.2.1.2 Module Exchange Suite
The Module Exchange Suite allows the developer to access the Flash file system on the
cellular engine from the development environment over a serial interface. File transfers from
PC to module are greatly facilitated by this suite.
2.2.1.3 IMPSiemens
IMPSiemens is the directory where all the necessary components for the SMTK are stored.
The virtual machine, all necessary interfaces and packages, the RS-232 emulator and the
Flash file system emulator are included. The AT Command API is the Java interface to the
module’s AT command interpreters. It allows AT commands to be sent, as strings, directly to
the AT command interpreters.
2.2.1.4 AT Java Open Framework (AJOF)
The AJOF sits on top of the AT Command class API and allows the developer to write Java
applications for the module without dealing directly with AT Commands.

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 14 of 72 30.06.2003
2.3 SMTK installation
The SMTK comes with an installation CD. The installation program provided automatically
installs the necessary interfaces and emulators. Software can be uninstalled and updated
with the install program. The next sections cover the installation and removal of the SMTK
and the installation of the SDK, Sun ONE Studio or Borland JBuilder.
2.3.1 Installing the Standard Development Toolkit
1. The JDK version 1.4.1_02 is provided on the TC45 SMTK installation disk in the
subdirectory “JDK 1.4.1”. To begin the installation, start the j2sdk-1_4_1_02-windows-
i586.exe and follow the instructions of the JDK setup procedure.
2. Once the toolkit has been installed, the environment variable “path” can be altered to
comfortably use the JDK tools.
3. Open the Control Panel.
a) Open System.
b) Click on Advanced.
c) Click on the Environment Variables button.
d) Choose path from the list of system variables.
e) Append the path for the bin directory of the newly installed SDK to the list of
directories for the path variable
2.3.2 Installing the SMTK environment
1. Insert CD, start setup.exe. If the dialog box appears simply press the “Next” button to
continue the procedure.
2. You will be asked to read the license agreement. If you accept the agreement, press
“Next” to continue with the installation.
3. A file including special information about the installation and use of the SMTK is shown.
Press “Next” to continue.
4. The installation software checks for the SDK. If there is no SDK on the system the
installation procedure will not continue. Please follow the instructions in Section 2.3.1
above for installing the SDK.
5. At this point, the installation software checks for a Java IDE to be integrated with the
SMTK. A Java IDE is not necessary to use the TC45 SMTK. The IDE installation can be
done at any time even if the TC45 SMTK is installed already. To install the Java IDE run
the setup program in maintenance mode again. However, you can continue the setup
procedure and install the IDE installation later or cancel the setup program at this stage
and restart it after installing one of the supported Java IDEs. In case you wish to install a
Java IDE please follow the instructions in Section 2.3.3 for installing Sun ONE Studio
Mobile Edition, Section 2.3.4 for installing Borland JBuilder Enterprise Mobile Set 3 or
Section 2.3.4.2 for installing Borland JBuilder Personal Mobile Set 3.
6. If the SDK and one or more Java IDE’s are found, you will be asked to choose which IDE
you want integrated into the TC45 development environment. Once an IDE has been
found and selected, press next to continue. Ensure that your Java IDE is closed.
7. Select the folder where the TC45 SMTK will be installed. A folder will be suggested to
you but you may browse to select a different one.
8. Choose the path that TC45 will appear under in the Start Menu.
9. A brief summary of all entries made shows up.
10. After step 9, all necessary files will be copied from the CD into the target folder.

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 15 of 72 30.06.2003
11. The installation of WinMux 2.1 is started.
a) Ensure that the module is connected to a serial port and turn the module power on.
b) Press the “Scan” button of the application. All Siemens modems found will be listed in
a box. The virtual ports are shown. If at least one modem is found, the “Install” button
becomes active. The selected modems are installed if this button is pressed.
c) The Device Manager can be used to check if the installation was successful. The
driver instances are visible in the device manager class “Multi-port serial Adapters”.
12. This is the final step. Again, a listing of all installed components appears.
2.3.3 Installing Sun ONE Studio 4.1 Mobile Edition
1. Sun ONE Studio 4.1 Mobile Edition is provided on the TC45 SMTK installation disk in the
subdirectory “SunOne ME” To begin installation, start the ffj_me_win32.exe and follow
the instructions of the Sun ONE setup procedure.
2. On the first use of Sun™ ONE Studio 4 Update 1 Mobile Edition after installation, you will
be prompted to specify a personal Java folder when Sun ONE is started for the first time.
If more then one user uses the computer, each user may have their own Java folder.
Note: The integration of the SMTK into Sun™ ONE Studio 4 Update 1 Mobile Edition is
only possible if the personal user folder is set. It can only be rolled back by the user who
installed the SMTK. If all users use the same Java folder, any user may roll back the
integration.
2.3.4 Installing Borland JBuilder MobileSet 3
Borland JBuilder and MobileSet can be purchased from http://www.borland.com/jbuilder.
JBuilder must be installed before installing the MobileSet. MobileSet 3 for Personal Edition is
the same as for Enterprise Edition.
Note: The installation path name of JBuilder should not include space characters. Otherwise
MobileSet is not working.
2.3.4.1 JBuilder Enterprise Edition MobileSet 3
A free version of JBuilder Enterprise Edition is available for 30 days. JBuilder must be
installed before installing the MobileSet. Installation instructions can also be found on the
web page.
2.3.4.2 JBuilder Personal Edition MobileSet 3
A free version for non-commercial use can be downloaded from Borland’s website.
Installation is similar to Enterprise Edition. JBuilder must be installed before installing the
MobileSet. The integration of TC45 SMTK into the JBuilder Personal Edition is somewhat
tricky and therefore briefly explained chapter 10.2.2.1 TC45 SMTK in Personal Edition.

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 16 of 72 30.06.2003
2.4 Uninstall
The TC45 SMTK install package comes with an uninstall facility. The entire SMTK or parts of
the package can be removed. To start the uninstall facility, open the Control Panel, select
Add/Remove Programs, select TC45 and follow the instructions.
2.4.1 Uninstall WinMux
The WinMux multiplexer must be manually uninstalled with the Hardware Manager.
It can also be uninstalled with Control Panel->Add/Remove Hardware. Choose the uninstall
options and select the Serial Multiplexer to be uninstalled.
2.5 Upgrades
The SMTK can be modified, repaired or removed by running the setup program on the
Installation CD.

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 17 of 72 30.06.2003
3 Maintenance
Basic maintenance features of the TC45 are described below. Explicit details of these
functions and modes can be found in the AT Command Set [4] and the Hardware Interface
Description [5].
3.1 Power Saving
The module supports several power saving modes which can be configured by the at
command at+cfun [4]. Power saving affects the Java application in two ways. On the one
hand it limits the access to the serial interface (RS-232-API) and the GPIO pins and on the
other hand power saving efficiency is directly influenced by the way a Java application is
programmed.
Java hardware access limitations:
· In NON-CYCLIC SLEEP mode (cfun=0) the serial interface cannot be accessed while
in CYCLIC SLEEP mode (CFUN=5, 6, 7 or 8) the serial interface can be used with
hardware flow control (CTS/RTS).
· In all SLEEP modes the GPIO polling frequency is reduced, so that only signal
changes which are less than 0.2Hz can be detected properly. Furthermore it should
be mentioned that the signal must be constant for at least 2.12s to detect changes.
For further details refer to [5].
Java power saving efficiency:
· As long as any Java thread is active, power consumption cannot be reduced,
regardless whether any SLEEP mode has been activated or not. So a Java
application that wants to be power efficient should not have any unnecessarily active
threads (e.g. no busy loops).
3.2 Charging
Please refer to [4] and [5] for general information about charging. Charging can be
monitored by the running Java application. The JVM is active in Charge mode and when
autostart is activated also in Charge-Only mode. Only a limited number of AT commands are
available when the module is in Charge-Only mode. A Java application must be able to
handle the Charge-Only mode and reset the module to reinstate the normal mode. See [5]
for information about the Charge-Only mode.
The Charge-Only mode is indicated by URC “SYSSTART CHARGE-ONLY MODE”.
Note: When a Java application is started in Charge-Only mode only AT Command API’s
without CSD are available. The indicating URC is created after issuing the very first AT
command on any opened channel. To read the URC it is necessary to register a listener
(see [6]) on this AT command API instance before passing the first AT command.

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 18 of 72 30.06.2003
3.3 Alarm mode
The ALARM can be set by the at+cala AT command. Please refer to the AT Command Set
[4] and Hardware Interface Description [5] for more information. One can set an alarm,
switch off the module with at^smso, and have the module restart in ALARM mode at the time
set with at+cala. Only a limited number of AT commands are available when the module is in
ALARM mode. The JVM is active in ALARM mode when autostart is activated. A Java
application must be able to handle the ALARM mode and reset the module to reinstate the
normal mode.
The ALARM mode is indicated by URC “SYSSTART ALARM MODE”.
Note: When a Java application is started in ALARM mode only AT Command API’s without
CSD are available. The indicating URC is created after issuing the very first AT command on
any opened channel.
3.4 Shut down
In the case of an unexpected shut down, data that should be written will get lost due to a
buffered write access to the flash file system. However, the best and safest approach to
powering down the module is to issue the AT^SMSO command. This procedure lets the
engine log off from the network and allows the software to enter into a secure state and save
all data. Further details can be found in [5].
3.4.1 Automatic shutdown
The module is switched off automatically in different situations:
· under- or overtemperature
· under- or overvoltage
This will happen without a warning notification unless the appropriate URC has been
activated. If the URC is activated, the module will deliver the URC before switching off. The
AT command at^sctm is used to activate and configure the overheating URC. It is
recommended that this URC be activated so that the module can be shut by the application
with at^smso after setting an alarm, see Section 3.3. Please note that there is no URC
function available for overvoltage conditions, i.e. no alert will be sent before shutdown. The
conmands are described in the AT Command Set [4] while a description of the shutdown
procedure can be found in [5].
3.4.2 Restart after switch off
The module can be switched off with the AT command, at^smso without setting an alarm
time, see the AT Command Set [4].A power failure will also switch off the module. When the
module is switched off, external hardware must restart the module with the Ignition line
(IGT). The Hardware Interface Description [5] explains how to handle a switched off
situation.

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 19 of 72 30.06.2003
3.5 Special AT command set for Java applications
For the full AT command set refer to [4]. There are differences in the behaviour of issuing AT
commands from a Java application compared to using AT commands over a serial interface.
3.5.1 Switching from data mode to command mode
Cancelling the data flow with “+++” is not available in Java applications, see [4] for details.
To break the data flow use breakConnection(), refer to \IMPSIEMENS\doc\index.html [6].
3.5.2 Mode indication after MIDlet startup
As on the serial interface after starting the module without autobauding on, the module
sends its state (^SYSSTART, ^SYSSTART ALARM MODE etc.) to the MIDlet. This is done
via URC to the AT Command API instance which executes the very first AT Command from
within Java. To read this URC it is necessary to register a listener (see [8]) on this AT
Command API instance before passing the first AT Command.
3.5.3 Long responses
The AT Command API can handle responses of AT commands up to a length of 1024 bytes.
Some AT commands have responses longer than 1024 bytes, for these responses the Java
application will receive an Exception.
Existing workarounds:
· Instead of listing the whole phone book, read the entries one by one
· Instead of listing the entire short message memory, again list message after message
· Similarly, read the provider list piecewise
· Periods of monitoring commands have to be handled by Java, i.e. at^moni, at^smong.
These AT commands have to be used without parameters, i.e. at^moni the periods have
to be implemented in Java.

TC45 TC45 JAVA User's Guide
Confidential / Released
TC45_JAVA User's Guide_V02 Page 20 of 72 30.06.2003
3.6 Restrictions
3.6.1 Flash file system
The maximum length of a complete path name, including the path and the filename, is
limited by the Flash file system on the module to 124 characters.
3.6.2 Memory
The memory model of the modules operating system uses 16kByte memory pages. Due to
this architecture there are two restrictions:
· It is not possible to create an object that needs more than 16 Kbytes linear (i.e. non-
fragmented) memory. If an object has to be created whose size exceeds these 16kByte
an OutOfMemoryError will be thrown.
· If the memory is unfavourably fragmented it might not be possible to create an object
that needs a larger amount of memory (smaller than 16kBytes) even though the
reported amount of free memory is larger than the amount needed by the object. If this
happens an OutOfMemoryError will be thrown.
3.7 Performance statements
Scope of the performance study was getting comparable values that indicate the
performance under certain circumstances.
3.7.1 Java
This section gives information about the Java command execution throughput (“jPS”= Java
statements per second). The scope of this measurement is only the statement execution
time, not the execution delay (Java command on AT interface èJava instruction execution
èreaction on GPIO).
Generated frequency A
[reference sequence]
Test MIDlet
Output pin
Change
output
pin level Measurement loop (for frequency B)
Send URC (start performance test) ATCommandListener.ATEvent()
Generated frequency B
[measurement sequence]
ATCommand.send(...)
Measurement sequence
Reference loop (for frequency A)
ATCommand.send(...)