TC65 JAVA User's Guide Siemens Cellular Engine. Version: 02 DocID: TC65 JAVA User's Guide_V02. JAVA Users Guide

Transcription

1 TC65 JAVA Uer' Guide Siemen Cellular Engine Verion: 02 DocID: TC65 JAVA Uer' Guide_V02 JAVA Uer Guide

2 Document Name: TC65 JAVA Uer' Guide Verion: 02 Date: June 20, 2005 DocId: Statu: TC65 JAVA Uer' Guide_V02 General Note Product i deemed accepted by recipient and i provided without interface to recipient product. The documentation and/or product are provided for teting, evaluation, integration and information purpoe. The documentation and/or product are provided on an a i bai only and may contain deficiencie or inadequacie. The documentation and/or product are provided without warranty of any kind, expre or implied. To the maximum extent permitted by applicable law, Siemen further diclaim all warrantie, including without limitation any implied warrantie of merchantability, completene, fitne for a particular purpoe and non-infringement of third-party right. The entire rik ariing out of the ue or performance of the product and documentation remain with recipient. Thi product i not intended for ue in life upport appliance, device or ytem where a malfunction of the product can reaonably be expected to reult in peronal injury. Application incorporating the decribed product mut be deigned to be in accordance with the technical pecification provided in thee guideline. Failure to comply with any of the required procedure can reult in malfunction or eriou dicrepancie in reult. Furthermore, all afety intruction regarding the ue of mobile technical ytem, including GSM product, which alo apply to cellular phone mut be followed. Siemen or it upplier hall, regardle of any legal theory upon which the claim i baed, not be liable for any conequential, incidental, direct, indirect, punitive or other damage whatoever (including, without limitation, damage for lo of buine profit, buine interruption, lo of buine information or data, or other pecuniary lo) ariing out the ue of or inability to ue the documentation and/or product, even if Siemen ha been advied of the poibility of uch damage. The foregoing limitation of liability hall not apply in cae of mandatory liability, e.g. under the German Product Liability Act, in cae of intent, gro negligence, injury of life, body or health, or breach of a condition which goe to the root of the contract. However, claim for damage ariing from a breach of a condition, which goe to the root of the contract, hall be limited to the foreeeable damage, which i intrinic to the contract, unle caued by intent or gro negligence or baed on liability for injury of life, body or health. The above proviion doe 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 thi general note hall be governed and contrued according to German law without reference to any other ubtantive law. Copyright Tranmittal, reproduction, diemination and/or editing of thi document a well a utilization of it content and communication thereof to other without expre authorization are prohibited. Offender will be held liable for payment of damage. All right created by patent grant or regitration of a utility model or deign patent are reerved. Copyright Siemen AG 2005 Trademark notice MS Window i a regitered trademark of Microoft Corporation. Java and Sun Java Studio Mobility Q3 are regitered trademark of Sun Microytem Inc. Borland JBuilder i a regitered trademark of Borland Software Corporation TC65 JAVA Uer' Guide_V02 Page 2 of

3 Table of Content 1 Preamble Overview Related Document Term and Abbreviation Intallation Sytem Requirement Intallation CD Component Module Exchange Suite WTK SDK and Java Studio SMTK Intallation Intalling the Standard Development Toolkit Intalling the SMTK Environment Intalling Sun Java Studio Mobility Intalling Eclipe Intalling Borland JBuilder X and Intalling Module Exchange Suite (MES) SMTK Unintall Upgrade Software Platform Software Architecture Interface ASC0 - Serial Device General Purpoe I/O DAC/ADC ASC Digital Audio Interface (DAI) I2C/SPI JVM Interface IP Networking Media Other Data Flow of a Java Application Running on the Module Handling Interface and Data Service Reource Module State State 1: Default No Java Running State 2: No Java Running, General Purpoe I/O and I2C State 3: No Java Running, General Purpoe I/O and SPI State 4: Default Java Application Active State 5: Java Application Active, General Purpoe I/O and I2C...23 TC65 JAVA Uer' Guide_V02 Page 3 of

4 State 6: Java Application Active, General Purpoe I/O and SPI Module State Tranition Maintenance Power Saving Charging Airplane Mode Alarm Shut Down Automatic Shutdown Manual Shutdown Retart after Switch Off Special AT Command Set for Java Application Switching from Data Mode to Command Mode Mode Indication after MIDlet Startup Long Repone Configuration of Serial Interface Java Command Retriction Flah File Sytem Memory Performance Statement Java Pin-IO Data Rate on RS-232 API Plain Serial Interface Voice Call in Parallel Scenario with GPRS Connection Upload Download MIDlet MIDlet Documentation MIDlet Life Cycle Hello World MIDlet File Tranfer to Module Module Exchange Suite Window Baed Command Line Baed Over the Air Proviioning Security Iue Module Exchange Suite OTAP Over The Air Proviioning (OTAP)...39 TC65 JAVA Uer' Guide_V02 Page 4 of

5 8.1 Introduction to OTAP OTAP Overview OTAP Parameter Short Meage Format Java File Format Procedure Intall/Update Delete Time Out Value and Reult Code Tip and Trick for OTAP OTAP Tracer Security How To Compiling and Running a Program without Java IDE Build Reult Compile Run on the Module with Manual Start Run on the Module with Autotart Switch on Autotart Switch off Autotart Debug Environment Data Flow of a Java Application in the Debug Environment Emulator Java IDE Sun Java Studio Mobility Q Switching emulator Project Template Example Compile and run Borland JBuilder X Example Borland JBuilder Example Eclipe Integration Switching Emulator Example Compile and debug Breakpoint Java Security Secure Data Tranfer...68 TC65 JAVA Uer' Guide_V02 Page 5 of

6 11.2 Execution Control Principle for the change to the ecured mode Principle for the igning the java MIDlet Application and Data Protection Structure and Decription of the Java Security Command Structure of the Java Security Command Build Java Security Command Send Java Security Command to the Module Create a Java Security Environment Step by Step Create Key tore Export X.509 Root Certificate Create Java Security Command Sign a MIDlet Java Tutorial Uing the AT Command API Cla ATCommand Intantiation with or without CSD Support Sending an AT Command to the Device, the end() Method Data Connection Synchronization ATCommandReponeLitener Interface Non-blocking ATCommand.end() Method ATCommandLitener Interface ATEvent Implementation Regitering a Litener with an ATCommand Intance Programming the MIDlet Thread Example Change to TC TC65 JAVA Uer' Guide_V02 Page 6 of

7 Figure Figure 1: Overview...10 Figure 2: Interface Configuration...19 Figure 3: Data flow of a Java application running on the module...20 Figure 4: Module State Figure 5: Module State Figure 6: Module State Figure 7: Module State Figure 8: Module State Figure 9: Module State Figure 10: Module State Tranition Diagram...24 Figure 11: Tet cae for meauring Java command execution throughput...29 Figure 12: Tet cae for meauring Java MIDlet performance and handling pin-io...30 Figure 13: Scenario for teting data rate on ASC Figure 14: Scenario for teting data rate on ASC1 with a voice call in parallel...31 Figure 15: Scenario for teting data rate on ASC1 with GPRS data upload...32 Figure 16: Scenario for teting data rate on ASC1 with GPRS data download...33 Figure 17: OTAP Overview...39 Figure 18: OTAP: Intall/Update Information Flow...43 Figure 19: OTAP: Delete Information Flow...44 Figure 20: Data flow of a Java application in the debug environment...51 Figure 21: Sun Java Studio Mobility 6 - The intalled emulator...53 Figure 22: Sun Java Studio Mobility 6 - Switching Emulator...54 Figure 23: Sun Java Studio Mobility 6 - Project Manager...55 Figure 24: Sun Java Studio Mobility 6 - Selecting a template...56 Figure 25: JBuilderX JDK etting...57 Figure 26: JBuilderX Siemen Library...57 Figure 27: JBuilderX Sample Project...58 Figure 28: JBuilderX Starting the debugging eion...59 Figure 29: JBuilder2005 JDK etting...60 Figure 30: JBuilderX Siemen Library...60 Figure 31: JBuilder2005 Sample Project...61 Figure 32: Eclipe Plug-in intallation...62 Figure 33: Eclipe Plug-in intallation, retart...62 Figure 34: Eclipe IMP-NG component...63 Figure 35: Eclipe J2ME platform...63 Figure 36: Eclipe Project import...64 Figure 37: Eclipe - Example...64 Figure 38: Eclipe Create package...65 Figure 39: Eclipe - Configuration...66 Figure 40 Mode 1: Java Security not activated...68 Figure 41 Mode 2: Java Security activated...69 Figure 42 Mode 2: Java Security activated...69 Figure 43: Switch to Security Mode...71 Figure 44: Prepare MIDlet for Secured Mode...72 Figure 45: Build Java Security Command...75 Table Table 1: Download data rate with different number of timelot, CS Table 2: Download data rate with different number of timelot, CS Table 3: Download data rate with different number of timelot, CS Table 4: Download data rate with different number of timelot, CS TC65 JAVA Uer' Guide_V02 Page 7 of

8 Table 5: A typical equence of MIDlet execution...35 Table 6: Parameter and keyword...40 TC65 JAVA Uer' Guide_V02 Page 8 of

9 1 Preamble A an interim olution, ince the final documentation ha not yet been completed, thi TC65 JAVA Uer' Guide i upplied a a Draft verion. Therefore modification are likely to apply to all chapter of the document. Paragraph, written in italic are till under development. Thi document i alo valid for the TC65 Terminal with the main exception, that the terminal doe not feature the USB and ASC1 interface. For other exception and difference pleae ee [4] and [5]. TC65 JAVA Uer' Guide_V02 Page 9 of

10 2 Overview The TC65 module feature an ultra-low profile and low-power conumption for data (CSD and GPRS), voice, SMS and fax. With Java technology and everal peripheral interface, the module enable eay integration of your application. Thi document explain how to work with the TC65 module, the intallation CD and the tool provided on the intallation CD. Old olution: The cutomer application wa ditributed acro 2 µc, external µc and internal µc on the module New olution: The cutomer application exit only on the module µc ROM Cutomer SW RAM ROM RAM TC65 TCxx Cutomer SW Cutomer Application Cutomer Application Figure 1: Overview 2.1 Related Document In addition to the Java Doc for the development API (ee Chapter 4), the following document are included with the SMTK: [1] Multiplexer Intallation Guide [2] Application Note 23: Intalling TC65 Module on DSB75 [3] DSB75 Support Box - Evaluation Kit for Siemen Cellular Engine [4] TC65 AT Command Set [5] TC65 Hardware Interface Decription [6] Java doc \wtk\doc\html\index.html [7] IMP-NG, JSR228, Standard TC65 JAVA Uer' Guide_V02 Page 10 of

11 2.2 Term and Abbreviation Abbreviation API ASC CLDC CSD DAI DCD DSR GPIO GPRS GPS HTTP I/O IDE IP J2ME J2SE JAD JAR JDK JVM LED ME MIDP OTA OTAP PDP PDU SDK SMS SMTK TCP URC URL VBS WTK Decription Application Program Interface Aynchronou Serial Controller Connected Limited Device Configuration Circuit-Switched Data Digital Audio Interface Data Carrier Detect Data Set Ready General Purpoe I/O General Packet Radio Service Global Poitioning Sytem Hypertext Tranfer Protocol Input/Output Integrated Development Environment Internet Protocol Java 2 Mobile Edition Java 2 Standard Edition Java Application Decription Java Archive Java Development Kit Java Virtual Machine Light Emitting Diode Mobile Engine Mobile Information Device Protocol Over The Air Over The Air Proviioning of Java Application Packet Data Protocol Protocol Data Unit Standard Development Kit Short Meage Service Siemen Mobile Toolkit Tranfer Control Protocol Unolicited Reult Code Univeral Reource Locator Viual Baic Script Wirele Toolkit TC65 JAVA Uer' Guide_V02 Page 11 of

12 3 Intallation 3.1 Sytem Requirement The Siemen Mobility Toolkit (SMTK) TC65 require that you have: 1. Window 2000 or Window XP intalled 2. 40Mbyte free dik pace for SMTK 3. Adminitration privilege 4. Java 2 SDK, Standard Edition 1.4. To intall the JDK verion 1.4.2_07 provided, follow the intruction in Section If a Java IDE uch a Sun Java Studio Mobility Q3, Eclipe 3.0, JBuilder X or 2005 i intalled, it can be integrated into the SMTK environment during the intallation of the SMTK. To intall one of the IDE, follow the intallation intruction in Section and Section repectively. 3.2 Intallation CD The Siemen Mobility Toolkit TC65 Intallation CD include: Module Exchange Suite wtk bin - variou tool doc - html - java doc for API lib - clae.zip rc - variou example JDK 1.4.2_07 J2dk-1_4_2_07-window-i586-p.exe Sun Java Studio Mobility 6 jtudio_m04q3-win-ml.exe Document: DSB75_HW_Decription.pdf TC65_AT_Command_Set.pdf TC65_HW_Decription.pdf WM_AN_24_dev_guide.pdf TC65_ReleaeNote.pdf TC65_Java_UerGuide.pdf (thi document) TC65 JAVA Uer' Guide_V02 Page 12 of

13 3.2.1 Component Module Exchange Suite The Module Exchange Suite allow the developer to acce the Flah file ytem on the cellular engine from the development environment over a erial interface. File tranfer from PC to module are greatly facilitated by thi uite WTK wtk i the directory where all the neceary component for TC65 Java application creation and debugging are tored SDK and Java Studio Thi i oftware provided by SUN to upport Java application development. TC65 JAVA Uer' Guide_V02 Page 13 of

14 3.3 SMTK Intallation The SMTK come with an intallation CD. The intallation program automatically intall the neceary component and IDE integration. Software can be unintalled and updated with the intall program. The next ection cover the intallation and removal of the SMTK and the intallation of the SDK and the upported IDE Intalling the Standard Development Toolkit 1. The JDK verion 1.4.2_07 i provided on the TC65 SMTK intallation dik in the ubdirectory JDK 1.4. To begin the intallation, tart the j2dk-1_4_2_07-window-i586- p.exe and follow the intruction of the JDK etup procedure. If there i no JDK intalled on the target machine the intallation of the provided JDK will be offered automatically during the SMTK intallation proce. 2. Once the toolkit ha been intalled, the environment variable path can be altered to comfortably ue the JDK tool. Thi i not neceary for uing the Siemen SMTK. 3. Open the Control Panel. a) Open Sytem. b) Click on Advanced. c) Click on the Environment Variable button. d) Chooe path from the lit of ytem variable. e) Append the path for the bin directory of the newly intalled SDK to the lit of directorie for the path variable Intalling the SMTK Environment 1. Inert CD, tart etup.exe. If the dialog box appear imply pre the Next button to continue the procedure. 2. You will be aked to read the licene agreement. If you accept the agreement, pre Ye to continue with the intallation. 3. A file including pecial information about the intallation and ue of the SMTK i hown. Pre Next to continue. 4. You will be aked to enter a path name where Eclipe 3.0 i intalled. Pleae type in the folder where Eclipe with ME plugin i intalled and pre Next. If you don t have intalled Eclipe or don t like to integrate the SMTK into Eclipe, pleae pre Next without any typed in elected folder. 5. The intallation oftware check for the Java SDK. If there i no SDK on the ytem the intallation procedure offer the intallation of the provided JDK now. If thi tep i denied the etup proce will not continue becaue a properly intalled JDK i mandatory for uing the SMTK environment. 6. At thi point, the intallation oftware check for a Java IDE to be integrated with the SMTK. A Java IDE i not neceary to ue the TC65 SMTK. The IDE intallation can be done at any time even if the TC65 SMTK i intalled already. To integrate the SMTK into the Java IDE run the SMTK etup program in maintenance mode again. However, you can continue the etup procedure and intall the IDE intallation later or cancel the etup program at thi tage and retart it after intalling one of the upported Java IDE. In cae you wih to intall a Java IDE pleae follow the intruction in Section and the following. If no intalled IDE i found the TC65 SMTK offer the intallation of SUN Java Studio Mobility Q3 and you can intall the SUN IDE (pleae follow the intruction in Section 3.3.3), if you like. TC65 JAVA Uer' Guide_V02 Page 14 of

15 7. If the SDK and one or more Java IDE are found, you will be aked to chooe which IDE you want integrated into the TC65 development environment. Once an IDE ha been found and elected, pre "Next" to continue. Enure that your Java IDE i cloed. 8. Select the folder where the TC65 SMTK will be intalled. A folder will be uggeted to you but you may browe to elect a different one. 9. Chooe the path that TC65 will appear under in the Start Menu. 10. A brief ummary of all entrie made how up and pre Next to continue. 11. A dialog box will inform you, that the Module Exchange Suite (MES) will be intalled in the next tep. Pleae pre OK. A eparate etup wizard for Module Exchange Suite will be opened. Pleae follow the intruction of the etup wizard. 12. After tep 11, all neceary file will be copied from the CD into the target folder. 13. Thi i the final tep. Again, a liting of all intalled component appear. Pleae pre Finih to end the intallation Intalling Sun Java Studio Mobility 6 1. Sun Java Studio Mobility 6 i provided on the TC65 SMTK intallation dik in the ubdirectory SJSM6. To begin intallation, tart the jtudio_m04q3-win-ml.exe and follow the intruction of the Sun Studio etup procedure. 2. On the firt ue of Sun Studio 6 after intallation, you will be prompted to pecify a peronal Java folder when Sun Studio i tarted for the firt time. If more then one uer ue the computer, each uer may have their own Java folder. Note: The integration of the SMTK into Sun Studio 6 i only poible if the peronal uer folder i et. It can only be rolled back by the uer who intalled the SMTK. If all uer ue the ame Java folder, any uer may roll back the integration Intalling Eclipe 3.0 Eclipe can be freely downloaded from Intalling Borland JBuilder X and 2005 Borland JBuilder can be purchaed from Note: The intallation path name of JBuilder hould not include pace character. There are alo 30 day trial verion available there. Intallation intruction can be found on the web page Intalling Module Exchange Suite (MES) The Module Exchange Suite (MES) i intalled inide the intallation routine of SMTK. If you like to intall the Module Exchange Suite eparate or repair or remove it, pleae ue the Module Exchange Suite (MES) etup.exe, which i located on the TC65 SMTK intallation dik in the ubdirectory MES. TC65 JAVA Uer' Guide_V02 Page 15 of

16 3.4 SMTK Unintall The TC65 SMTK intall package come with an unintall facility. The entire SMTK or part of the package can be removed. To tart the unintall facility, open the Control Panel, elect Add/Remove Program, elect TC65 Software Development Kit and follow the intruction. The Module Exchange Suite (MES) i not unintalled automatically with the SMTK. If you like to unintall Module Exchange Suite (MES) a well, pleae tart the unintall facility, open the Control Panel, elect Add/Remove Program, elect Siemen Module Exchange Suite (MES) and follow the intruction. 3.5 Upgrade The SMTK can be modified, repaired or removed by running the etup program on the Intallation CD. TC65 JAVA Uer' Guide_V02 Page 16 of

17 4 Software Platform In thi chapter, we dicu the oftware architecture of the SMTK and the interface to it. 4.1 Software Architecture The SMTK enable a cutomer to develop a Java application on a PC and have it be executable on the TC65 module. The application i loaded onto the module. The platform comprie: Bai i the Java 2 Micro Edition (J2ME ) The J2ME i provided by SUN Microytem, It i pecifically deigned for embedded ytem and ha a mall memory footprint. TC65 ue: CLDC 1.1 HI, the connected limited device configuration hot pot implementation. IMP-NG, the information module profile 2 nd generation, thi i for the mot part identical to MIDP 2.0 but without the lcdui package. Additional Java virtual machine interface: AT Command API File I/O API The data flow through thee interface i hown in Figure 3 and Figure 20. Memory pace for Java program: Flah File Sytem: around 1700k RAM: around 400k Application code and data hare the pace in the flah file ytem and in RAM. Additional acceible periphery for Java application A maximum of ten digital I/O pin uable, for example, a: Output: tatu LED Input: Emergency Button One I2C/SPI Interface. One Digital Analog Converter and two Analog Digital Converter. Serial interface (RS-232 API): Thi tandard erial interface could be ued, for example, with an external GPS device or a current meter. For detailed information ee chapter 4.2. TC65 JAVA Uer' Guide_V02 Page 17 of

18 4.2 Interface ASC0 - Serial Device ASC0, an Aynchronou Serial Controller, i a 9-wire erial interface. It i decribed in the Hardware Interface Decription [5]. Without a running Java application the module can be controlled by ending AT command via ASC0. Furthermore ASC0 i deigned for tranferring file from the development PC to the module and for controlling the module with AT command. When a Java application tarted, ASC0 can be ued a an RS-232 port, refer to Java doc [6] General Purpoe I/O There are ten I/O pin that can be configured for general purpoe I/O. When TC65 tart up, all 10 pin are et, by default, to high-impedance tate for ue a input. One pin can be configured a pule counter. All line can be acceed under Java by at command. See [4] and [5] about configuring the pin DAC/ADC There are two analogue input and one analogue output line. They can be acceed by at command.. See [4] and [5] for detail ASC1 ASC1 i the econd erial interface on the module. Thi i a 4-pin interface (RX, TX, RTS, CTS). It can be ued a a econd AT interface when a Java application i not running or by a running Java application a Sytem.out Digital Audio Interface (DAI) To upport the DAI function, the TC65 ha a even-line erial interface with one input data clock line and input/output data and frame line. Refer to AT Command Set [4] and Hardware Interface Decription document [5] for more information I2C/SPI There i a 4 line erial interface which can be ued a I2C or SPI interface. It i decribed in the Hardware Interface Decription [5]. The at^pi at command configure and drive thi interface. For detail ee [5]. TC65 JAVA Uer' Guide_V02 Page 18 of

19 4.2.7 JVM Interface IMP-NG File API AT Command API Connected Limited Device Configuration (CLDC) J2ME Figure 2: Interface Configuration J2ME, CLDC and MIDP were implemented by SUN. IMP-NG i a tripped down verion of MIDP 2.0 prepared by Siemen and doe not include the graphical interface LCDUI. Siemen developed the File I/O API and the AT command API. Documentation for J2ME and CLDC can be found at Documentation for the other API i found in / Java doc [6] IP Networking IMP-NG provide acce to TCP/IP like MIDP 2.0. Becaue the ued network connection, CSD or GPRS, i fully tranparent to the Java interface, the CSD and GPRS parameter mut be defined eparately either by the AT command at^jnet [4] or by parameter given to the connector open method, ee Java doc [6] Media TC65 doe not upport the media package, ee Java doc [6] Other TC65 doe neither upport the PuhRegitry interface and mechanim nor any URL cheme for the PlatformRequet method. See Java doc [6]. TC65 JAVA Uer' Guide_V02 Page 19 of

20 4.3 Data Flow of a Java Application Running on the Module AT Parer ytem.out ASC1 JVM Flah File Sytem AT Command API File I/O API IMP-NG TCP/IP GPIO DAI I2C/SPI DAC/ADC ASC0 Figure 3: Data flow of a Java application running on the module. The diagram how the data flow of a Java application running on the module. The data flow of a Java application running in the debug environment can be found in Figure 20. The compiled Java application are tored a JAR file in Flah File Sytem of module. When the application i tarted, the JVM interpret the JAR file and call the interface to module environment. The module environment conit of: Flah File Sytem: available memory for Java application TCP/IP: module internal TCP/IP tack GPIO: general purpoe I/O DAI: Digital Audio Interface ASC0: Aynchronou erial interface 0 ASC1: Aynchronou erial interface 1 I2C: I2C bu interface SPI: Serial Peripheral Interface DAC: digital analog converter ADC: analog digital converter AT parer: acceible AT parer The Java environment on the module conit of: JVM: AT command API: File API: IMP-NG: Java Virtual Machine Java API to AT parer Java API to Flah File Sytem Java API to TCP/IP and ASC0 TC65 JAVA Uer' Guide_V02 Page 20 of

21 4.4 Handling Interface and Data Service Reource To develop Java application the developer mut know which reource, data ervice and hardware acce are available. There are three AT parer available There i hardware acce over two erial interface: ASC1 (Sytem.out only) and ASC0 (fully acceible). general purpoe I/O. To configure the hardware acce, pleae refer to the AT Command Set [4] and the Hardware Interface Decription [5]. I2C/SPI All retriction of combination are decribed in ection A Java application ha: three intance of the AT command cla, one with CSD and two without, each of which would, in turn, be attached to one of the three AT parer. one intance of acce to a erial interface, ASC0, through the RS-232 API. Sytem.out over the erial interface, ASC1, for debugging Module State The module can exit in the following ix tate regarding a Java application, the erial interface, GPIO and I2C/SPI. See the AT Command Set [4] for information about any AT command referenced. A tate tranition diagram i hown in Figure 10. Thi ection how how Java application mut hare AT parer, GPIO pin and I2C/SPI reource. DAC, ADC and DAI are not mentioned here. The USB interface i alternative to ASC1, meaning when USB i plugged in the ASC1 interface i deactivated. Default configuration of module Default configuration when Java application i tarted Legend of color in following figure configured by AT Command TC65 JAVA Uer' Guide_V02 Page 21 of

22 State 1: Default No Java Running Thi i the default tate. The Java application i inactive and there i an AT interface with CSD on ASC0 a well a ASC1. All HW interface pin are configured a input. AT parer with CSD ASC 0 Figure 4: Module State 1 AT parer with CSD ASC1 or USB 10 GPIO, I2C/SPI pin (unued) State 2: No Java Running, General Purpoe I/O and I2C The Java application i inactive. There i an AT parer with CSD on ASC0 a well a ASC1. Up to ten I/0 pin are ued a general purpoe I/O plu a I2C interface. The pin are configured by at^cpin or at^pi (refer to AT Command Set [4]). AT parer with CSD AT parer with CSD ASC 0 ASC 1 or USB up to 10 GPIO pin I2C Figure 5: Module State State 3: No Java Running, General Purpoe I/O and SPI The Java application i inactive and there i an AT interface with CSD on ASC0 a well a ASC1. Up to ten I/0 pin are ued a general purpoe I/O plu a SPI interface. The pin are configured by at^cpin or at^pi (refer to AT Command Set [4]). AT parer with CSD AT parer with CSD ASC 0 ASC 1 or USB up to 10 GPIO SPI Figure 6: Module State State 4: Default Java Application Active The Java application i active and ASC1 i ued a Sytem.out and the Java intance of the RS-232 erial interface i connected to ASC1. Java intance of AT command are connected to the available AT parer. The Java application i activated with at^jra (refer to AT Command Set [4]) or autotart. Java acce to erial interface (CommConnection) Sytem.out AT parer with CSD AT parer without CSD AT parer without CSD ASC 0 ASC1 Java AT command API with CSD Java AT command API without CSD Java AT command API without CSD Figure 7: Module State 4 TC65 JAVA Uer' Guide_V02 Page 22 of

23 State 5: Java Application Active, General Purpoe I/O and I2C The Java application i active, ASC0 i ued a Sytem.out and the Java intance of the RS-232 erial interface i connected to ASC1. The Java application i activated with at^jra. The I/O pin are configured by at^cpin or at^pi. Refer to the AT Command Set [4] for AT command detail. Java acce to erial interface (CommConnection) Sytem.out AT parer 0 with CSD AT parer without CSD AT parer without CSD ASC 0 ASC 1 Java AT command API with CSD Java AT command API without CSD Java AT command API without CSD up to 10 GPIO pin: I2C: Figure 8: Module State State 6: Java Application Active, General Purpoe I/O and SPI The Java application i running, ASC0 i ued a Sytem.out and the Java intance of the RS-232 erial interface i connected to ASC1. The Java application i activated with at^jra (refer to AT Command Set [4]). Java acce to erial interface (CommConnection) Sytem.out AT parer 0 with CSD AT parer without CSD AT parer without CSD ASC 0 ASC 1 Java AT command API with CSD Java AT command API without CSD Java AT command API without CSD up to 10 GPIO pin SPI Figure 9: Module State 6 TC65 JAVA Uer' Guide_V02 Page 23 of

24 4.4.2 Module State Tranition witch on no Java autotart Java autotart State 1: Default, no Java appl. running tart java: at^jra detroy java application State 4: Default, Java active cloe I2C open I2C open I2C cloe I2C cloe SPI State 2: no Java appl. running, uing I2C tart java: at^jra detroy Java application State 5: Java active, uing I2C open SPI cloe SPI open SPI detroy java application State 6: Java active, uing SPI State 3: no Java appl. running, uing SPI tart java: at^jra Figure 10: Module State Tranition Diagram Note: No AT parer i available over erial interface ASC0 or ASC1 while a Java application i running on the module. Sytem.out i available on ASC1 for debugging while a Java application i running. TC65 JAVA Uer' Guide_V02 Page 24 of

25 5 Maintenance Baic maintenance feature of the TC65 are decribed below. Explicit detail of thee function and mode can be found in the AT Command Set [4] and the Hardware Interface Decription [5]. 5.1 Power Saving The module upport everal power aving mode which can be configured by the AT command at+cfun [4]. Power aving affect the Java application in two way. On the one hand it limit the acce to the erial interface (RS-232-API) and the GPIO pin and on the other hand power aving efficiency i directly influenced by the way a Java application i programmed. Java hardware acce limitation: In NON-CYCLIC SLEEP mode (cfun=0) the erial interface cannot be acceed while in CYCLIC SLEEP mode (CFUN=7 or 9) the erial interface can be ued with hardware flow control (CTS/RTS). In all SLEEP mode the GPIO polling frequency i reduced, o that only ignal change which are le than 0.2Hz can be detected properly. Furthermore it hould be mentioned that the ignal mut be contant for at leat 2.12 to detect change. For further detail refer to [5]. Java power aving efficiency: A long a any Java thread i active, power conumption cannot be reduced, regardle whether any SLEEP mode ha been activated or not. So a Java application that want to be power efficient hould not have any unnecearily active thread (e.g. no buy loop). 5.2 Charging Pleae refer to [4] and [5] for general information about charging. Charging can be monitored by the running Java application. The JVM i active in Charge mode and when autotart i activated alo in Charge-Only mode. Only a limited number of AT command are available when the module i in Charge-Only mode. A Java application mut be able to handle the Charge-Only mode and reet the module to reintate the normal mode. See [5] for information about the Charge-Only mode. The Charge-Only mode i indicated by URC SYSSTART CHARGE-ONLY MODE. Note: When a Java application i tarted in Charge-Only mode only AT Command API without CSD are available. The indicating URC i created after iuing the very firt AT command on any opened channel. To read the URC it i neceary to regiter a litener (ee [6]) on thi AT command API intance before paing the firt AT command. 5.3 Airplane Mode The main characteritic of thi mode i that the RF i witched off and therefore only a limited et of AT command i available. The mode can be entered or left uing the appropriate at^cfg command. Thi AT command can alo be ued to configure the airplane mode a the tandard tartup mode, ee [5]. The JVM i tarted when autotart i enabled. A Java TC65 JAVA Uer' Guide_V02 Page 25 of

26 application mut be able to handle thi mode. The airplane mode i indicated by URC SYSSTART AIRPLANE MODE. Since the radio i off all clae related to networking connection, e.g. SocketConnection, UDPDatagramConnection, SocketServerConnection, HTTPConnection, will through an exception when acceed. 5.4 Alarm The ALARM can be et by the at+cala AT command. Pleae refer to the AT Command Set [4] and Hardware Interface Decription [5] for more information. One can et an alarm, witch off the module with at^mo, and have the module retart at the time et with at+cala. When the alarm trigger the module retart in a limited functionality mode, the airplane mode. Only a limited number of AT command i available in thi mode, though the JVM i tarted when autotart i enabled. A Java application mut be able to handle thi mode and reet the module to reintate the normal mode. A module tart by an alarm i the ame mode a the airplane mode and i therefore indicated by URC SYSSTART AIRPLANE MODE. Note: For detailed information which functionality i available in thi mode ee [5]. The mode indicating URC i created after iuing the very firt AT command on any opened channel. 5.5 Shut Down In the cae of an unexpected hut down, data that hould be written will get lot due to a buffered write acce to the flah file ytem. However, the bet and afet approach to powering down the module i to iue the AT^SMSO command. Thi procedure let the engine log off from the network and allow the oftware to enter into a ecure tate and ave all data. Further detail can be found in [5] Automatic Shutdown The module i witched off automatically in different ituation: under- or overtemperature under- or overvoltage Thi will happen without a warning notification unle the appropriate URC ha been activated. If the URC are enabled, the module will deliver an alert before witching off. To activate the URC for temperature condition ue the at^ctm command, to activate the voltage condition URC ue the at^bc command. It i recommended that thee URC be activated o that the module can be hut by the application with at^mo after etting an alarm, ee Section 5.4. The command are decribed in the AT Command Set [4], while a decription of the hutdown procedure can be found in [5] Manual Shutdown The can be witched off manually with the AT command, at^mo or in cae of the TC65 terminal by preing the ignition key for a longer period of time Retart after Switch Off When the module i witched off, without etting an alarm time (ee the AT Command Set [4]), e.g. power failure, external hardware mut retart the module with the Ignition line (IGT). The Hardware Interface Decription [5] explain how to handle a witched off ituation. TC65 JAVA Uer' Guide_V02 Page 26 of

27 5.6 Special AT Command Set for Java Application For the full AT command et refer to [4]. There are difference in the behaviour of iuing AT command from a Java application compared to uing AT command over a erial interface Switching from Data Mode to Command Mode Cancelling the data flow with +++ i not available in Java application, ee [4] for detail. To break the data flow ue breakconnection(), refer to \wtk\doc\index.html [6] Mode Indication after MIDlet Startup A on the erial interface after tarting the module without autobauding on, the module end it tate (^SYSSTART, ^SYSSTART ALARM MODE etc.) to the MIDlet. Thi i done via URC to the AT Command API intance which execute the very firt AT Command from within Java. To read thi URC it i neceary to regiter a litener (ee [6]) on thi AT Command API intance before paing the firt AT Command Long Repone The AT Command API can handle repone of AT command up to a length of 1024 byte. Some AT command have repone longer than 1024 byte, for thee repone the Java application will receive an Exception. Exiting workaround: Intead of liting the whole phone book, read the entrie one by one Intead of liting the entire hort meage memory, again lit meage after meage Similarly, read the provider lit piecewie Period of monitoring command have to be handled by Java, e.g. at^moni, at^mong. Thee AT command have to be ued without parameter, e.g. at^moni the period have to be implemented in Java Configuration of Serial Interface While a Java application i running on the module, only the AT Command API i able to handle AT command. All AT command referring to erial interface are ignored. Epecially thee are the following: AT+IPR AT\Q3 If Java i running, the firmware will ignore any etting from thee command. Repone to the read, write or tet command will be invalid or deliver ERROR. Note: When a Java application i running, all etting of the erial interface are done by the cla CommConnection. Thi i fully independent of any AT command relating a erial interface Java Command There i a mall et of pecial Java AT command: at^jra, tart of Java application TC65 JAVA Uer' Guide_V02 Page 27 of

28 at^jnet, the configuration for Java networking connection at^jotap, tart and configuration of the over the air proviioning at^jec, ecurity configuration Refer to AT command et [4]. 5.7 Retriction Flah File Sytem The maximum length of a complete path name, including the path and the filename, i limited by the Flah file ytem on the module to 124 character. It i recommended to ditinguih name of clae and file not only by cae enitivity Memory The CLDC 1.1 HI feature a jut in time compiler. That mean that part of the Java byte code which are frequently executed are tranlated into machine code to improve efficiency. Thi feature ue up RAM pace. So there i alway a trade off between code tranlation to peed up execution and RAM pace available for the application. TC65 JAVA Uer' Guide_V02 Page 28 of

29 5.8 Performance Statement Scope of the performance tudy wa getting comparable value that indicate the performance under certain circumtance Java Thi ection give information about the Java command execution throughput ( jps = Java tatement per econd). The cope of thi meaurement i only the tatement execution time, not the execution delay (Java command on AT interface Java intruction execution reaction on GPIO). Send URC (tart performance tet) Tet MIDlet ATCommandLitener.ATEvent() Reference loop (for frequency A) Generated frequency A [reference equence] ATCommand.end(...) Generated frequency B [meaurement equence] Output pin Change output pin level Meaurement loop (for frequency B) Meaurement equence ATCommand.end(...) Figure 11: Tet cae for meauring Java command execution throughput The following Java intruction wa ued for calculation of the typical jps: value = ( 2 x number of calculation tatement ) / ( ( 1 / frequencyb ) - ( 1 / frequencya ) ); Meaurement and calculation were done uing: duration of each loop = 600 number of calculation tatement = 5 reult=(constant_value/variable_value); -Intruction (executed twice per pin cycle) frequencya a meaured with univeral counter frequencyb a meaured with univeral counter The reference loop ha the ame tructure a the meaurement loop except that the meaurement equence i moved. State TC65 module in IDLE mode / Not connected CSD connection jps-value (mean) TBD TBD Thee mean value may be poradically reduced depending on dynamic condition. TC65 JAVA Uer' Guide_V02 Page 29 of

30 5.8.2 Pin-IO The pin IO tet wa defined to find out how fat a Java MIDlet can proce URC caued by Pin IO and react on thee URC. The URC are generated by feeding an input pin with an external frequency. A oon a the Java MIDlet get informed about the URC, it trie to regenerate the feeding frequency by toggling another output pin. external frequency input pin poll input pin end URC Tet MIDlet ATCommandLitener. ATEvent() et output pin ATCommand. end(...) output pin generated frequency Figure 12: Tet cae for meauring Java MIDlet performance and handling pin-io The reult of thi tet how that the delay from changing the tate on the pin to proceing the URC in the MIDlet i at leat TBD TDMA frame, but depend mainly on the amount of garbage to collect and number of thread to erve by the virtual machine. So Pin IO i not uitable to generate or detect frequencie Data Rate on RS-232 API For detail about oftware platform and interface refer to Chapter 4, "Software Platform". Thi ection ummarie limitation and precondition for performance when uing the interface CommConnection from package com.iemen.mp.io (refer to [6]). The data rate on RS232 depend on the ize of the buffer ued for reading from and writing to the erial interface. It i recommended to ue for reading from erial interface the method read (byte[ ] b). The recommended buffer ize i 2kbyte. To reach errorfree data tranmiion the flowcontrol on CommConnection ha to be witched on: <autort> and <autoct>, the ame for connected device. Below, different ue cae are lited to give an idea of reachable data rate. All application for meaurement are working with only one thread, no more activitie than thoe decribed were done in parallel Plain Serial Interface Scenario: A device i connected to ASC0 (refer to 4.2.4). The Java application ha to handle data input and output tream. A imple Java application (only one thread) which i looping incoming data directly to output reache data rate up to 180kbit/. Tet condition: hardware flow control enabled (<autort> and <autoct>), 8N1, and baud rate on ASC0 et to 230kbaud (-> theoretical maximum: 184kbit/ net data rate). TC65 JAVA Uer' Guide_V02 Page 30 of

31 ASC1 Java application (looping data) TC65 Figure 13: Scenario for teting data rate on ASC Voice Call in Parallel Same cenario a in ection , but a voice call added. The application i reflecting incoming data directly to output and, additionally, handle an incoming voice call. The data rate are alo up to 180kbit/. Tet condition: like in incoming voice call ASC1 Java application (looping data) TC65 Figure 14: Scenario for teting data rate on ASC1 with a voice call in parallel TC65 JAVA Uer' Guide_V02 Page 31 of

32 Scenario with GPRS Connection The bigget challenge for the module performance i etting up a GPRS connection, receiving data on interface of javax.microedition.io and ending or receiving the data on the RS232 API with the help of a Java application Upload TC65 upport GPRS cla 12, thi mean up to four timelot for upload data are available. The Java application receive data over RS232 API and end them over GPRS to a erver. Table 1: Download data rate with different number of timelot, CS2 1 timelot theor. Value * % from theor. Value 2 timelot Upload data rate with x timelot Coding cheme 2 [kbit/] theor. Value * % from theor. Value 3 timelot theor. Value * % from theor. Value 4 timelot theor. Value * tbd 12 tbd 24 tbd 36 tbd 48 % from theor. Value * net tranmiion rate for LLC layer Table 2: Download data rate with different number of timelot, CS4 1 timelot theor. Value * % from theor. value 2 timelot Upload data rate with x timelot Coding cheme 4 [kbit/] theor. Value * % from theor. value 3 timelot theor. Value * % from theor. value 4 timelot theor. Value * tbd 20 tbd 40 tbd 60 tbd 80 % from theor. value * net tranmiion rate for LLC layer GPRS connection upload data ASC1 Java application (tranfer data) TC65 Figure 15: Scenario for teting data rate on ASC1 with GPRS data upload Download The data rate for downloading data over GPRS depend on the number of aigned timelot and the coding cheme given by the net. TC65 upport GPRS cla 12, thi TC65 JAVA Uer' Guide_V02 Page 32 of

33 mean the number of aigned timelot can be up to 4. For meaurement purpoe, the Java application receive data from the erver over GPRS and end them over RS232 to an external device. GPRS connection download data ASC1 Java application (tranfer data) TC65 Figure 16: Scenario for teting data rate on ASC1 with GPRS data download The table below how the download data rate that can be achieved if hardware flow control i enabled on the CommConnection interface and the port peed i et to 230k4. Table 3: Download data rate with different number of timelot, CS2 1 timelot theor. Value * % from theor. Value 2 timelot Download data rate with x timelot Coding cheme 2 [kbit/] theor. Value * % from theor. Value 3 timelot theor. Value * % from theor. Value 4 timelot theor. Value * tbd 12 tbd 24 tbd 36 tbd 48 % from theor. Value * net tranmiion rate for LLC layer Table 4: Download data rate with different number of timelot, CS4 1 timelot theor. Value * % from theor. value 2 timelot Download data rate with x timelot Coding cheme 4 [kbit/] theor. Value * % from theor. value 3 timelot theor. Value * % from theor. value 4 timelot theor. Value * tbd 20 tbd 40 tbd 60 tbd 80 % from theor. value * net tranmiion rate for LLC layer TC65 JAVA Uer' Guide_V02 Page 33 of

34 6 MIDlet The J2ME Mobile Information Device Profile (MIDP) provide a targeted Java API for writing wirele application. The MIDP run on top of the Connected Limited Device Configuration (CLDC), which in turn, run on top of the J2ME. MIDP application are referred to a MIDlet. MIDlet are controlled by the mobile device implementation that upport the CLDC and MIDP. Since IMP-NG i a ubet of MIDP 2.0, IMP include MIDlet. The MIDlet code tructure i very imilar to applet code. There i no main method and MIDlet alway extend from the MIDlet cla. The MIDlet cla in the MIDlet package provide method to manage a MIDlet life cycle. 6.1 MIDlet Documentation MIDP and MIDlet documentation can be found at and in the html document directory of the wtk, \Siemen\SMTK\TC65wtk\doc\index.html 6.2 MIDlet Life Cycle The MIDlet life cycle define the protocol between a MIDlet and it environment through a imple well-defined tate machine, a concie definition of the MIDlet tate and API to ignal change between the tate. A MIDlet ha three valid tate: Paued The MIDlet i initialied and i quiecent. It hould not be holding or uing any hared reource. Active The MIDlet i functioning normally. Detroyed The MIDlet ha releaed all of it reource and terminated. Thi tate i only entered once. State change are affected by the MIDlet interface, which conit of: paueapp() the MIDlet hould releae any temporary reource and become paive. tartapp() the MIDlet tart it execution, needed reource can be acquire here or in the MIDlet contructor detroyapp() the MIDlet hould ave any tate and releae all reource Note: detroyapp() i called when a MIDlet hould terminate caued by device. notifydetroyed() the MIDlet notifie the application management oftware that it ha cleaned up and i done Note: the only way to terminate a MIDlet i to call notifydetroyed(), but detroyapp() i not automatically called by notifydetroyed(). notifypaued() the MIDlet notifie the application management oftware that it ha paued reumerequet() the MIDlet ak application management oftware to be tarted again. getappproperty() get a named property from the MIDlet TC65 JAVA Uer' Guide_V02 Page 34 of

35 Table 5: A typical equence of MIDlet execution Application Management Software The application management oftware create a new intance of a MIDlet. The application management oftware ha decided that it i an appropriate time for the MIDlet to run, o it call the MIDlet.tartApp method for it to enter the Active tate. The application management oftware no longer need the application be active, o it ignal it to top performing it ervice by calling the MIDlet.paueApp method. The application management oftware ha determined that the MIDlet i no longer needed, or perhap need to make room for a higher priority application in memory, o it ignal the MIDlet that it i a candidate to be detroyed by calling the MIDlet.detroyApp method. MIDlet The default (no argument) contructor for the MIDlet i called; it i in the Paued tate. The MIDlet acquire any reource it need and begin to perform it ervice. The MIDlet top performing it ervice and might chooe to releae ome reource it currently hold. If it ha been deigned to do o, the MIDlet ave tate or uer preference and perform clean up. TC65 JAVA Uer' Guide_V02 Page 35 of

36 6.3 Hello World MIDlet Here i a ample HelloWorld program. /** * HelloWorld.java */ package example.helloworld; import javax.microedition.midlet.*; import java.io.*; public cla HelloWorld extend MIDlet { } /** * HelloWorld - default contructor */ public HelloWorld() { Sytem.out.println("HelloWorld: Contructor"); } /** * tartapp() */ public void tartapp() throw MIDletStateChangeException { Sytem.out.println("HelloWorld: tartapp"); Sytem.out.println("\nHello World!\n"); detroyapp(); } /** * paueapp() */ public void paueapp() { Sytem.out.println("HelloWorld: paueapp()"); } /** * detroyapp() */ public void detroyapp(boolean cond) { Sytem.out.println("HelloWorld: detroyapp(" + cond + ")"); notifydetroyed(); } TC65 JAVA Uer' Guide_V02 Page 36 of

37 7 File Tranfer to Module 7.1 Module Exchange Suite The Module Exchange Suite allow you to view the Flah file ytem on the module a a directory from Window Explorer. Make ure that the module i turned on and that any erial interface of the module i connected to the configured COM port of Module Exchange Suite. The adjutment of the configured COM port can be checked by attribute on Module directory. Pleae note that the Module Exchange Suite can be ued only if the module i in normal mode. While running the module with Module Exchange Suite ubdirectorie and file can be added in flah file ytem of module. Take in mind that only the maximum of 200 flah object (file and ubdirectorie) per directory in flah file ytem of module are recommended Window Baed The directory i called Module and can be found at the top level of workpace MyComputer. To tranfer a file to the module, imply copy the file from the ource directory to the target directory in the Module -> Module Dik (A:) Command Line Baed A uite of command line tool i available for acceing the module Flah file ytem. They are intalled in the Window Sytem directory o that the tool are available from any directory. The module file ytem i acceed with mod:. The tool included in thi uite are MESdel, MEScopy, MESxcopy, MESdir, MESmkdir, MESrmdir, MESport, MEScloe and MESformat. Entering one of thee command without argument will decribe the command uage. The tool mimic the tandard directory and file command. A path inide the module file ytem i identified by uing mod: followed by the module dik which i alway A: (e.g. MESdir mod:a: lit the content of the module root directory). 7.2 Over the Air Proviioning See Chapter 8 for OTA proviioning. 7.3 Security Iue The developer hould be aware of the following ecurity iue. Security apect in general are dicued in chapter 11. TC65 JAVA Uer' Guide_V02 Page 37 of

38 7.3.1 Module Exchange Suite The erial interface hould be mechanically protected. The copy protection rule for Java application prevent opening, reading, copying, moving or renaming of JAR file. It i not recommended to ue name of Java application (for example <name>.jar) for directorie, ince the copy protection will deny acce to open, copy or rename uch directorie OTAP A paword hould be ued to update with OTA (SMS Authentication) Parameter hould be et to fixed value (at^jotap) whenever poible o that they cannot be changed over the air. The http erver hould be ecure. (e.g. Acce control via baic authentication) TC65 JAVA Uer' Guide_V02 Page 38 of

39 8 Over The Air Proviioning (OTAP) 8.1 Introduction to OTAP OTA (Over The Air) Proviioning of Java Application i a common practice in the Java world. OTAP decribe mechanim to intall, update and delete Java application over the air. The TC65 product implement the Over The Air Application Proviioning a pecified in the IMP-NG tandard (JSR228). The OTAP mechanim decribed in thi document doe not require any phyical uer interaction with the device; it can be fully controlled over the air interface. Therefore it i uitable for Java device that are not uppoed to have any manual interaction like vending machine or electricity meter. 8.2 OTAP Overview To ue OTAP, the developer need, apart from the device fitted with the TC65 module, an http erver, which i reachable through a TCP/IP connection either over GPRS or CSD, and an SMS ender, which can end Cla1, PID $7d hort meage. Thi i the PID reerved for module data download. Java Application Server (HTTP Server).jar file.jad file HTTP/TCP/IP over GPRS/CSD Device containing TC65.jad file.jar file SMS Cla1, Pid $7d OTAP Controller (SMS Sender) Figure 17: OTAP Overview The Java Application Server (http Server) contain the.jar and the.jad file, which are to be loaded on the device. Acce to thee file can be protected by http baic authentication. The OTAP Controller (SMS Sender) control the OTAP operation. It end SM, with or without additional parameter, to the device that are to be operated. Thee device then try to contact the http erver and download new application data from it. The OTAP Controller will not get any repone about the reult of the operation. Optionally the erver might get a reult repone through http. There are two type of OTAP operation: Intall/Update: A new JAR and JAD file are downloaded and intalled. Delete: A complete application (.jar,.jad, all application data and it directory) i deleted. TC65 JAVA Uer' Guide_V02 Page 39 of

40 8.3 OTAP Parameter There i a et of parameter that control the OTAP procedure. Thee parameter can either be et by AT command (at^jotap, refer to AT Command Set [7]) preumably during the production of the device, or by SM (ee Section 8.4) during operation of the device in the field. None of the parameter, which are et by AT command, can be overwritten by SM. JAD File URL: the location of the JAD file i ued for intall or update procedure. The JAD file need to be located on the net (e.g. or ). Application Directory: thi i the directory where a new application (JAD and JAR file) i intalled. The delete operation delete thi directory completely. When entering the application directory by at^jotap or hort meage be ure that the path name i not terminated with a lah. For example, type "a:" or "a:/otap" rather than "a:/" or "a:/otap/". See example provided in Chapter 8.4. http Uer: a uername ued for authentication with the http erver. http Paword: a paword ued for authentication with the http erver. Bearer: the network bearer ued to open the HTTP/TCP/IP connection, either GPRS or CSD. APN or Number: depending on the elected network bearer thi i either an acce point name for GPRS or a telephone number for CSD. Net Uer: a uername ued for authentication with the network. Net Paword: a paword ued for authentication with the network. DNS: a Domain Name Server IP addre ued to query hotname. NotifyURL: the URL to which reult are poted. Thi parameter i only ued when the MIDlet-Intall-Notify attribute or MIDlet-Delete-Notify attribute i not preent in the decriptor. There i one additional parameter that can only be et by AT command: SM Paword: it i ued to authenticate incoming OTAP SM. Setting thi paword give an extra level of ecurity. Note: If there wa a paword et by AT command, all SM have to include thi paword Table 6: Parameter and keyword Parameter Max. Length AT Keyword SM Intall/update delete JAD File URL 100 JADURL mandatory unued Application Directory 50 APPDIR mandatory mandatory HTTP Uer 32 HTTPUSER optional unued HTTP Paword 32 HTTPPWD optional unued Bearer -- BEARER mandatory optional/p APN or Number 65 APNORNUM mandatory for CSD optional/p Net Uer 32 NETUSER optional optional/p Net Paword 32 NETPWD optional optional/p DNS -- DNS optional optional/p Notify URL 100 NOTIFYURL optional optional/p SM Paword 32 PWD optional optional The length of the tring parameter in the AT command i limited (ee Table 6), the length in TC65 JAVA Uer' Guide_V02 Page 40 of

41 the SM i only limited by the maximum SM length. The minimum et of required parameter depend on the intended operation (ee Table 6). optional/p mean that thi parameter i only neceary when a POST reult i deired. 8.4 Short Meage Format An OTAP control SM mut be a Submit PDU with Cla1, PID $7d and 8 bit encoding. A a fallback for unuual network infratructure the SM can alo be of Cla0 and/or PID $00. The content of the SM conit of a et of keyword and parameter value. Thee parameter might be ditributed over everal SM. There i one ingle keyword to tart the OTAP procedure. For parameter that are repeated in everal SM only the lat value ent i valid. For example, an SM could look like thi: Intall operation: Firt SM: OTAP_IMPNG PWD:ecret JADURL: APPDIR:a:/work/appdir HTTPUSER:uer HTTPPWD:anotherecret Second SM: OTAP_IMPNG PWD:ecret BEARER:gpr APNORNUM:acce.to-thenet.net NETUSER:nobody NETPWD:nothing DNS: START:intall Delete operation: OTAP_IMPNG PWD:ecret APPDIR:a:/work/appdir START:delete The firt line i required: it i ued to identify an OTAP SM. All other line are optional and their order i inignificant, each line i terminated with an LF: '\n' even the lat one. The keyword, in capital letter, are cae enitive. A colon eparate the keyword from their value. The value of APPDIR, BEARER and START are ued internally and have to be lower cae. The paword (PWD) i cae enitive. The cae enitivity of the other parameter value depend on the erver application or the network. It i likely that not all parameter can be ent in one SM. They can be ditributed over everal SM. Of coure, every SM need to contain the identifying firt line and the PWD parameter, if neceary. The OTAP i tarted when the keyword START, poibly with a parameter, i contained in the SM and the parameter et i valid for the requeted operation. It alway end with a reboot, either when the operation i completed, an error occurred, or the afety timer expired. Thi alo mean all parameter previouly et by SM are gone. TC65 JAVA Uer' Guide_V02 Page 41 of

42 Apart from the firt and the lat line in thi example, thee are the parameter decribed in the previou ection. Poible parameter for the START keyword are: intall, delete or nothing. In the lat cae, an intall operation i done by default. The network doe not guarantee the order of SM. So when uing multiple SM to tart a OTAP operation their order on the receiving ide might be different from the order in which they were ent. Thi could lead to trouble becaue the OTAP operation probably tart before all parameter are received. If you dicover uch problem, try to wait a few econd between ending the SM. 8.5 Java File Format In general, all Java file have to comply with the IMP-NG and TC65 pecification. There are certain component of the JAD file that the developer mut pay attention to when uing OTAP: MIDlet-Jar-URL: make ure that thi parameter point to a location on the network where your latet JAR file will be located, e.g. not in the fileytem like file://a:/java/mytet/mytet.jar. Otherwie thi JAD file i uele for OTAP. MIDlet-Intall-Notify: thi i an optional entry pecifying a URL to which the reult of an update/intall operation i poted. That i the only way to get any feedback about the outcome of an intall/update operation. The format of the poted URL complie with the IMP-NG OTA Proviioning pecification. In contrat to the jar and jad file thi URL mut not be protected by baic authentication. MIDlet-Delete-Notify: thi i an optional entry pecifying a URL to which the reult of a delete operation i poted. That i the only way to get any feedback about the outcome of a delete operation. The format of the poted URL complie with the IMP-NG OTA Proviioning pecification. In contrat to the jar and jad file thi URL mut not be protected by baic authentication. MIDlet-Name, MIDlet-Verion, MIDlet-Vendor: are mandatory entrie in the JAD and Manifet file. Both file mut contain equal value, otherwie reult 905 (ee 8.7) i returned. MIDlet-Jar-Size mut contain the correct ize of the jar file, otherwie reult 904 (ee 8.7) i returned. Example: MIDlet-Name: MyTet MIDlet-Verion: MIDlet-Vendor: TLR Inc. MIDlet-Jar-URL: MIDlet-Decription: My very important tet MIDlet-1: MyTet,, example.mytet.mytet MIDlet-Jar-Size: 1442 MicroEdition-Profile: IMP-NG MicroEdition-Configuration: CLDC-1.1 A uitable Manifet file for the JAD file above might look like: Manifet-Verion: 1.0 MIDlet-Name: MyTet MIDlet-Verion: MIDlet-Vendor: TLR Inc. MIDlet-1: MyTet,, example.mytet.mytet MicroEdition-Profile: IMP-NG MicroEdition-Configuration: CLDC-1.1 TC65 JAVA Uer' Guide_V02 Page 42 of

43 8.6 Procedure Intall/Update OTAP Controller Java Application Server Parameter SMS... Parameter SMS with "START:intall" TC65 -SMS paword check -Parameter collection - Combination of SMS parameter et and AT parameter et - If parameter et complete: Cloe running Java application Cloedown Timeout HTTP requet for.jad file (HTTP baic authentication) HTTP.jad file download Start intall/update procedure Download.jad file (HTTP Pot Error) HTTP requet for.jar file (HTTP baic authentication) HTTP download of.jar file (HTTP Pot Reult) If Error, pot and reboot Download.jar file -Pot reult, -If ucce, intall and change autotart -Reboot Safety Timeout Reboot Figure 18: OTAP: Intall/Update Information Flow (The meage in bracket are optional) When an SM with keyword START:intall i received and there i a valid parameter et for the operation, the module alway reboot either when the operation completed, an error occurred or the afety timer expired. If there i any error during an update operation the old application i kept untouched, with one exception. If there i not enough pace in the file ytem to keep the old and the new application at the ame time, the old application i deleted before the download of the new one, therefore it i lot when an error occur. If intall/update wa ucceful the autotart i et to the new application. TC65 JAVA Uer' Guide_V02 Page 43 of

44 8.6.2 Delete OTAP Controller Java Application Server Parameter SMS... TC65 -SMS paword check -Parameter collection Parameter SMS with "START:delete" - Combination of SMS parameter et and AT parameter et - If parameter et complete: Cloe running Java application Cloedown Timeout (HTTP Pot Reult) Start delete procedure Delete application dir reboot Safety Timeout Reboot Figure 19: OTAP: Delete Information Flow (The meage in bracket are optional) When an SM with keyword START:delete i received and there i a valid parameter et for thi operation, the module reboot either when the operation completed, an error occurred or the afety timer expired. If there i any error the application i kept untouched. Autotart i not changed. TC65 JAVA Uer' Guide_V02 Page 44 of

45 8.7 Time Out Value and Reult Code Timeout: Cloedown Timeout: 10 econd Safety Timeout: 10 minute Reult Code: Supported tatu code in body of the http POST requet: 900 Succe 901 Inufficient memory in fileytem 902 -not upported not upported- 904 JAR ize mimatch, given ize in JAD file doe not match real ize of jar file 905 Attribute mimatch, one of the mandatory attribute MIDlet-name, MIDlet-verion, MIDlet-Vendor in the JAD file doe not match thoe given in the JAR manifet 906 invalid decriptor, omething i wrong with the format of the.jad file 907 invalid JAR, the JAR file wa not available under MIDlet-Jar-URL, file could not be extracted from JAR archive, or omething ele i wrong with the format of the file. 908 incompatible configuration or profile 909 application authentication failure, ignature did not match certificate 910 application authorization failure, tried to replace igned with unigned verion 911 -not upported- 912 Delete Notification All HTTP packet (GET, POST) end by the module contain the IMEI number in the Uer- Agent field, e.g. Uer-Agent: TC65/ Profile/IMP-NG Configuration/CLDC-1.1 Thi i for eay device identification at the HTTP erver. 8.8 Tip and Trick for OTAP For ecurity reaon it i recommended to ue an SMS paword. Otherwie the delete operation can remove whole directorie without any authentication. For extra ecurity, et up a private CSD/PPP Server and et it phone number a a fixed parameter. Thi way, application can only be downloaded from one pecial erver. A a ide effect, OTAP can be ued to imply reboot the module. Jut tart an OTAP procedure with a parameter et which doe not really do anything, like a delete operation on a nonexitent directory. If you don t want to tart OTAP by SMS let your Java application do it by iuing the at^jotap command. That trigger a intall/update operation a decribed in chapter but without the SMS part. Note: If a malfunctioning Java application i loaded the SM method will till be needed for another update. The OTAP procedure cannot be teted in the debug environment Be aware that the module need to be booked into the network to do OTAP. That mean that either the Java application ha to enter the PIN, the PIN need to be diabled or Autopin (ee AT Command Set [4]) ha to be ued. The OTAP procedure might fail due to call colliion, e.g. a incoming call when OTAP trie to tart a CSD connection. TC65 JAVA Uer' Guide_V02 Page 45 of

46 8.9 OTAP Tracer For eay debugging of the OTAP cenario the OTAP procedure can be traced over the erial interface. The trace output how detail of the OTAP procedure and the ued parameter. To enable the OTAP trace output ue the at command at^cfg, e.g. AT^SCFG=Trace/Sylog/OTAP,1 The erial interface on which you iue thi command i then excluively ued for the OTAP tracer. All other functionality which i normally preent (AT command or in Java mode : CommConnection, Sytem out) i not available then. Thi feature i intended to be ued during development phae not in deployed device Security Java Security a decribed in chapter 11 ha alo conequence for OTAP. If the module i in ecured mode the midlet ignature i alo relevant for the OTAP procedure. That mean: if the application i a unigned verion of a intalled igned verion of the ame application then tatu code 910 i returned if the application ignature doe not match the module certificate then tatu code 909 i returned TC65 JAVA Uer' Guide_V02 Page 46 of

47 8.11 How To Thi chapter i uppoed to be a tep-by-tep guideline for uing OTAP. 1. Do you need OTAP? I there any chance that it might be neceary to update the Java application, intall a new one or delete it? The reaon might be that your device i in the field and you cannot or do not want to do it over the erial line. If the anwer i ye then read through the following tep, if the anwer i no then jut conider etting the OTAP SMS paword to protect your ytem. Then you are done with OTAP. 2. Take a look at the parameter (chapter 8.3), which control OTAP. You have to decide which of them you want to allow to be changed over the air (by SMS) and which you do not. Thi i mainly a quetion of ecurity and what you can fit into a hort meage. Then et the unchangeable parameter with the AT command (at^jotap). 3. Prepare the http erver. The erver mut be reachable by your device over TCP/IP. That mean there i a route from your device over the air interface to the http erver and back. When in doubt, write a mall Java application uing the httpconnection Interface to tet it. 4. Prepare the JAR and JAD file which are to be loaded over the air. Make ure that thee file conform to the requirement named in chapter 8.5 and that they repreent a valid application which can be tarted by at^jra. 5. Put the file (JAR and JAD) on the http Server. The file can either be publicly available or protected through baic authentication. When in doubt try to download the file from the erver by uing a common web brower on a PC, which can reach your http erver through TCP/IP. 6. Prepare the SM ender. The ender mut be able to end SM, which conform to chapter 8.4, to your device. When in doubt try to end normal SM to your device which can than be read out through the AT command interface. 7. Tet with a local device. Send a uitable hort meage to your device, which complete the neceary parameter, et and tart the operation. The operation i finihed when the device reboot. You can now check the content of the file ytem, if the correct jar and jad file wa loaded into the correct location. 8. Analyze error. If the above tet failed, looking at your device behavior and your http erver acce log can give you ome hint on what went wrong: If the device did not terminate the running Java application and did not reboot, not even after the afety timeout, either your SM wa not undertood (probably wrong format) or did not properly authenticate (probably wrong paword) or your parameter et i incomplete for the requeted operation. If the device terminated the running Java application, but did not acce your http erver, and rebooted after the afety timeout, there were mot likely ome problem when opening the network connection. Check your network parameter. If the device downloaded the jad and probably even the jar file but then rebooted without aving them in the file ytem, mot likely one of the error named in chapter 8.5 occurred. Thee are alo the only error condition, which can alo be reported back. They are poted to the http erver if the jad file contain the required URL. 9. Start update of remote device. If you were able to uccefully update your local device, which i hopefully a mirror of all your remote device, you can tart the update of all other device. TC65 JAVA Uer' Guide_V02 Page 47 of

48 9 Compiling and Running a Program without Java IDE Thi chapter explain how to compile and run a Java application without a Java IDE. 9.1 Build Reult A JAR file ha to be created by compiling an SMTK project. A JAR file will contain the cla file and auxiliary reource aociated with an application. A JAD file contain information (file name, ize, verion, etc.) on the actual content of the aociated JAR file. It mut be written by the uer. The JAR file ha the.jar extenion and the JAD file ha the.jad extenion. A JAD file i alway required no matter whether the module i proviioned with the Module Exchange Suite, a decribed in Section 7.1, or with OTA proviioning. OTA proviioning i decribed in Chapter 8. In addition to cla and reource file, a JAR file contain a manifet file, which decribe the content of the JAR. The manifet ha the name manifet.mf and i automatically tored in the JAR file itelf. An IMP manifet file for: package example.mytet; public cla MyTet extend MIDlet include at leat: Manifet-Verion: 1.0 MIDlet-Name: MyTet MIDlet-Verion: MIDlet-Vendor: Siemen MIDlet-1: MyTet, example.mytet.mytet MicroEdition-Profile: IMP-NG MicroEdition-Configuration: CLDC-1.1 A JAD file mut be written by the developer and mut include at leat: MIDlet-Name: MyTet MIDlet-Verion: MIDlet-Vendor: Siemen MIDlet-1: MyTet, example.mytet.mytet MIDlet-Jar-URL: MIDlet-Jar-Size: 1408 MicroEdition-Profile: IMP-NG MicroEdition-Configuration: CLDC-1.1 A detailed decription of thee attribute and other can be found in the Java/MIDlet documentation TC65 JAVA Uer' Guide_V02 Page 48 of

49 9.2 Compile Launch a Command Prompt. Thi can be done from the Program menu or by typing cmd at the Run prompt in the Start menu. Change to the directory where the code to be compiled i kept. Compile the program with the SDK. Example of build batch file can be found in each ample program found in the example directory, \Siemen\SMTK\TC65\wtk\rc\example. If the compile wa ucceful the program can be run from the command line. Example of run batch file can be found in the example directorie lited above a well. The batch file for compiling and running the ample refer to mater batch file in the \Siemen\SMTK\TC65\wtk\bin directory and are uing the ytem environment variable IMPNG_JDK_DIR that point to the root directory of the intalled JDK and IMPNG_DIR which point to the root directory of the Siemen-SMTK-TC65-IMPNG intallation. The intallation proce et thee environment variable. A modification i uually not neceary. They might be modified (e.g. for witching to a different JDK) via the advanced ytem propertie a requeted. 9.3 Run on the Module with Manual Start The application can be compiled at the prompt a dicued in Section 9.2 or in an IDE. Tranfer the.jar and.jad file from the development platform to the deired directory on the module uing the Module Exchange Suite or OTA proviioning. Chapter 7 explain how to download your application to the module. Start a terminal program and connect to ASC0. The command at^jra i ued to tart the application and i ent to the module via your terminal program. Either the application can be tarted by.jar or by.jad file. Example: In your terminal program enter: at^jra=a:/java/jam/example/helloworld/helloworld.jar If you prefer to tart with.jad file: at^jra=a:/java/jam/example/helloworld/helloworld.jad The Flah file ytem on the module i referenced by a:. 9.4 Run on the Module with Autotart The application can be compiled at the prompt a dicued in Section 9.2 or in an SMTK integrated IDE. Tranfer the.jar and.jad file from the development platform to the deired directory on the module uing the Module Exchange Suite or OTA proviioning. See Chapter 7. TC65 JAVA Uer' Guide_V02 Page 49 of

50 9.4.1 Switch on Autotart There i an AT command, at^cfg, to configure the autotart functionality. Pleae refer to the AT Command Set [4]. Retart the module Switch off Autotart To witch off autotart functionality there are two poibilitie: AT command at^cfg tool autotart_off.exe (included in the Intallation CD oftware under wtk/bin) To diable the automatic tart of a uer application in a module thee tep have to be done: 3. Connect the module to the PC 4. Make ure, that the module i witched off 5. Start the Autotart_Off program 6. Select the COM-Port 7. Pre the Autotart Off button TC65 JAVA Uer' Guide_V02 Page 50 of

51 10 Debug Environment Pleae note that thi ection i not intended a a tutorial in debugging or how to ue Sun Java Studio, Borland JBuilder or Eclipe. Document for thee IDE can be found on their repective homepage. Once the proper emulator ha been elected (a decribed in the relevant IDE ection below), your Java application can be built, debugged and executed Data Flow of a Java Application in the Debug Environment ytem.out ASC1 JVM Flah File Sytem AT parer AT command API File I/O API IMP NG TCP/IP ASC0 ASC0,1 or USB GPIO DAI I2C/SPI DAC/ADC Module PC Com Port TC65 emulator IDE/Debug environment Figure 20: Data flow of a Java application in the debug environment In the debug environment the module i connected to a PC via a erial interface. Thi can be USB or a RS232 line. The application can then be edited, build and debugged within an IDE on the PC. When running the MIDlet under debugger control it i executed on the module (on-device debugging) not on the PC. Thi enure that all interface behave the ame no matter if in debugging mode or not. TC65 JAVA Uer' Guide_V02 Page 51 of

52 10.2 Emulator The TC65 emulator i part of the SMTK. Though called emulator it doe not emulate anything. Intead it i the controlling entity of the on-device debugging. Before the emulator can be ued ome configuration work ha to be done: The emulator ha to acce the module by AT command. In order to do thi i ha to know the COM port and bit rate to ue. Thi can be configured in the file wtk/bin/wm_debug_config.ini. There you have to et the parameter Port and Baudrate. In order to etablih an IP connection between PC and the module the emulator need a pecial DUN connection configured: ISP name: IP connection for remote debugging Modem: either Standard bp Modem or TC bp Modem Phone number: *88# Uername and paword: any will do, it i recommended to ave uername and paword for re-uage. Make ure that the DUN ue the ame COM port and bit rate a the emulator doe. You can ue any of the three erial interface (ASC0, ASC1, USB) to connect with module, but you will looe the functionality which i normally preent on thi interface. So becaue of thi and becaue of peed it i recommended to ue the USB interface. If neceary, the IP addree ued for the debug connection can alo be changed. Thi i done in the file wtk/bin/wm_debug_config.ini. See documentation of at^cfg with parameter uerware/debuginterface for detail Java IDE The SMTK i integrated into your Java IDE during intallation. Pleae note that the IDE integration i intended to create midlet uitable for TC65 module and for debugging purpoe uing the emulator. JAR file ued in the module mut be configured according to the batch file example given. If the SMTK intall ucceeded, one hould be able to eaily witch between the Siemen environment and Standard-JDK environment. Thi mean that the pecial librarie/api are available, the emulator are available, AT command can be ent to module. Regular function of the IDE for non-siemen project i unchanged. Uing the debugger pleae keep in mind, that the MIDlet-URL, included in the Jad file, ha to indicate and tore the location where the TC65 emulator will find the correponding Jar file. Generally the location will only be the file name for the Jar file. In cae of uing Eclipe IDE the location where the Jar file i located i deployed\<filename>.jar Sun Java Studio Mobility Q3 Thi ection indicate the change to your IDE you will ee after integrating the SMTK and decribe how to exploit thee feature to build and debug your application. In the Runtime Explorer, Figure 21, the intalled emulator can be een under the Device Emulator Regitry. The Default Emulator i et to the Siemen Emulator. TC65 JAVA Uer' Guide_V02 Page 52 of

53 Figure 21: Sun Java Studio Mobility 6 - The intalled emulator TC65 JAVA Uer' Guide_V02 Page 53 of

54 Switching emulator You can eaily witch to the SMTK emulator by uing the combo box in the main menu bar and chooing IMP_NG_DefaultDevice, ee Figure 22. Any project built and run when the Siemen emulator i elected will be compiled and run with the Siemen emulator. Directly after executing the IDE integration with the SMTK etup program the IMP_NG_DefaultDevice i activated by default. Figure 22: Sun Java Studio Mobility 6 - Switching Emulator TC65 JAVA Uer' Guide_V02 Page 54 of

55 Project After integration, there i a new project in the Project Manager. Thi project contain the example and the additional librarie. The Project Manager i acceed through the Project menu. Directly after executing the IDE integration with the SMTK etup program the Siemen TC65 project i opened by default. Figure 23: Sun Java Studio Mobility 6 - Project Manager TC65 JAVA Uer' Guide_V02 Page 55 of

56 Template Template for a Siemen MIDlet can be found in the file explorer and under File->New. The MIDlet template provide the keleton of a MIDlet application. Figure 24: Sun Java Studio Mobility 6 - Selecting a template Example There are ample MIDlet in the /IMPNGSiemen/rc/example directory. Thi directory i mounted in Sun ONE Studio and can be een in the Explorer window Compile and run Enure that the proper emulator will be ued and compile the project a normal. Any output will be hown in the output window in the IDE. By preing Alt-F1 the html help file of the SMTK can be acceed directly Borland JBuilder X If JBuilderX i not intalled, pleae intall firt JBuilderX and follow the intruction of the intallation wizard. Ue the intallation routine of TC65 SMTK in maintenance mode. The SMTK will found the intalled JBuilderX IDE. Select JBuilderX for integrate the SMTK into JBuilderX. After integration of TC65 SMTK into JBuilderX you can examine the integration by opening the menu Tool -> Configure JDK (ee Figure below) TC65 JAVA Uer' Guide_V02 Page 56 of

57 Figure 25: JBuilderX JDK etting The librarie included with the TC65 SMTK can be examined by opening the menu Tool Configure Librarie (ee Figure below) Figure 26: JBuilderX Siemen Library TC65 JAVA Uer' Guide_V02 Page 57 of

58 Example There are ample project provided with the TC65 SMTK. Thee project can be found in the JBuilderSample directory of the TC65 SMTK intallation directory. Thi directory i acceed by opening a project uing the menu File Open Project (ee Figure below) Figure 27: JBuilderX Sample Project TC65 JAVA Uer' Guide_V02 Page 58 of

59 Open the Project (e.g. HelloWorld.jpx ), rebuild the ource and tart the debugger uing the micro edition (context menu HelloWorld.jad Micro Debug uing HelloWorld ). Figure 28: JBuilderX Starting the debugging eion TC65 JAVA Uer' Guide_V02 Page 59 of

60 Borland JBuilder 2005 If JBuilder2005 i not intalled, pleae intall firt JBuilder2005 and follow the intruction of the intallation wizard. Ue the intallation routine of TC65 SMTK in maintenance mode. The SMTK will found the intalled JBuilder2005 IDE. Select JBuilder2005 for integrate the SMTK into JBuilder2005. After integration of TC65 SMTK into JBuilder2005 you can examine the integration by opening the menu Tool -> Configure JDK (ee Figure below) Figure 29: JBuilder2005 JDK etting The librarie included with the TC65 SMTK can be examined by opening the menu Tool Configure Librarie (ee Figure below) Figure 30: JBuilderX Siemen Library TC65 JAVA Uer' Guide_V02 Page 60 of

61 Example There are ample project provided with the TC65 SMTK. Thee project can be found in the JBuilderSample directory of the TC65 SMTK intallation directory. Thi directory i acceed by opening a project uing the menu File Open Project (ee Figure below) Figure 31: JBuilder2005 Sample Project Starting the debugging eion i done in the ame way a for JBuilderX (ee chapter for JBuilderX above) Eclipe 3.0 If Eclipe i not intalled, pleae unpack eclipe-sdk win32.zip Integration Before you can run the intallation routine of TC65 SMTK in maintenance mode, you have to intall the EclipeME Plugin. Thi plug-in can normally be downloaded from A long a the cutomization neceary for TC65 are not part of and official releae thi cutomized verion come with the SMTK cd in the directory EclipeMEplugin. Start Eclipe and open the menu Help Software Update Find and Intall Select in the following window Search for new feature to intall and click Next Now you have to elect the plugin.zip after clicking the New Archived Site button. (ee figure below). TC65 JAVA Uer' Guide_V02 Page 61 of

62 Figure 32: Eclipe Plug-in intallation If the intallation of the plugin wa ucceful you have to retart your IDE. (ee figure below). Figure 33: Eclipe Plug-in intallation, retart Cloe the IDE! Now tart the intallation routine of TC65 SMTK to automatically configure Eclipe. After the integration you can ee the configuration in Window Preference J2ME Platform Component (ee figure below) TC65 JAVA Uer' Guide_V02 Page 62 of

63 Figure 34: Eclipe IMP-NG component Switching Emulator You can eaily witch between intalled SMTK by uing the preference of a project and chooing IMP_NG_DefaultDevice, ee figure below. Figure 35: Eclipe J2ME platform Example After the integration you can import one example. Open menu: File Import Exiting Project into Workpace and chooe the root directory of the example. (ee figure below) TC65 JAVA Uer' Guide_V02 Page 63 of

64 Figure 36: Eclipe Project import The following figure how the Hello World example in the IDE. Figure 37: Eclipe - Example TC65 JAVA Uer' Guide_V02 Page 64 of

65 Compile and debug To build the jar and jad file you have rebuild the project with the create package function. Open the context menu of the project and go to J2ME Create Package Figure 38: Eclipe Create package Now you are ready to debug your project. Run Debug A TC65 launcher with pre etting i provided for tarting the debugging eion. Pleae enure that you have elected the right project and executable midlet. TC65 JAVA Uer' Guide_V02 Page 65 of

66 Figure 39: Eclipe - Configuration Retriction: The integration of SMTK i depend on election the default offered workpace \workpace of Eclipe Breakpoint Breakpoint can be et a uual within the IDE. The debugger cannot tep through method or function whoe ource code i not available. TC65 JAVA Uer' Guide_V02 Page 66 of