AMay 15, 2007Initial release
BJune 21, 2007Updated due to software updates
CFebr ua ry 15, 2008Appendix E added (IP Director) due to software updates. Additional minor
1.7 PROBLEM REPORTING INSTRUCTIONS................................................................................................................3
1.8 HOW THIS GUIDE IS ORGANIZED..........................................................................................................................3
2.3 TYPICAL USE CASE...................................................................................................................................................7
3.1.2 Power Supply Installation.............................................................................................................................10
3.2.2 Available Memory........................................................................................................................................11
3.2.3 USB PC Driver.............................................................................................................................................12
3.2.5 Query System Information ...........................................................................................................................12
6.3 STANDARD CLASSES DEVIATIONS.................................................................................................................... 41
6.3.1 Comm Connections......................................................................................................................................41
6.3.2 Server Socket Connection........................................................................................ .................................... 41
B.4 OTA PROVISIONING...............................................................................................................................................50
B.6.1 Message Format .......................................................................................................................................... 51
E.1 USING THE IPD FEATURE ........................................... .......................................................................................... 61
E.5 OTA (OVER THE AIR) OVER SERIAL PPP LINK................................................................................................ 63
6802981C50-C v
vi 6802981C50-C
1. CHAPTER 1 - PREFACE
1.1PURPOSE
This guide gives an overview of the G24 KJAVA product and its capabilities.
1.2INTENDED AUDIENCE
This guide is intended for G24 KJAVA customers, developers and support groups.
1.3DISCLAIMER
Motorola reserves the right to make changes without notice to any of the products or services described herein. "Typical" parameters, which may be provided in Motorola Data sheets and/or specifications can and do vary in different applications and actual
performance may vary. Customer's technical experts will validate all "Typicals" for each customer application.
Motorola makes no warranty in regard to the products or services contained herein. Implied warranties, including without limitation, the implied warranties of merchantability and fitness for a particular purpose, are given only if specifically required by
applicable law. Otherwise, they are specifically excluded.
No warranty is made as to coverage, availability, or grade of service provided by the products or services, whether through a
service provider or otherwise.
No warranty is made that the software will meet your requirements or will work in combination with any hardware or application software products provided by third parties, that the operation of the software products will be uninterrupted or error free,
or that all defects in the software products will be corrected.
In no event shall Motorola be liable, whether in contract or tort (including negligence), for any d a mages resulti ng from use of
a product or service described herein, or for any indirect, incidental, special or consequential damages of any kind, or loss of
revenue or profits, loss of business, loss of information or data, or other financial loss arisi ng out of or in connection with the
ability or inability to use the Products, to the full extent these damages may be disclaimed by law.
Some states and other jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, or limitation
on the length of an implied warranty, therefore the above limitations or exclusions may not apply to you.
This warranty gives you specific legal rights, and you may also have other rights, which vary from jurisdiction to jurisdiction.
Motorola products or services are not designed, intended, or authorized for use as components in systems intended for surgical
implant into the body, or other applications intended to support or sustain life, or for any other application in which the failure
of the Motorola product or service could create a situation where personal injury or death may occur.
Should the buyer purchase or use Motorola products or services for any such unintended or unauthorized application, the buyer
shall release, indemnify and hold Motorola and its officers, employees, subsidiaries, affiliates, and distributors harmless against
all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal
injury or death associated with such unintended or unauthorized use, even if such claim alleges that Motorola was negligent
regarding the designing or manufacturing of the product or service.
Motorola recommends that if you are not the author or creator of the graphics, video, or sound, you obtain sufficient license
rights, including the rights under all patents, trademarks, trade names, copyrights, and other third party proprietary rights.
6802981C50-C1
CHAPTER 1 - PREFACE
1.4ABBREVIATIONS, ACRONYMS AND DEFINITIONS
AbbreviationFull Name
AMSApplication Management Software
APNAccess Point Name
AutoupdateA user settable feature that synchronizes the local clock with the time received from the network
CPHSCommon PCN Handset Specification
CSDCircuit Switch Data
DMDefault MIDlet
DNSDomain Name Server
EVBEValuation Board
Flash1. G24 software
2. The process of replacing the G24 software
FlexG24 configuration file, allows product flexibility
GCFGeneric Connection Framework
GIDxGroup Identifier level x
GPIOGeneral Purpose Input Output
GPSGlobal Positioning System
HAPIHardware Application Program Interface
HMIHuman Machine Interface. G24 with display and keypad support
ICCIDIntegrated Circuit Card ID
IDEIntegrated Development Environment
IMEIInternational Mobile Equipment Identity
JADJava Application Descriptor
JARJava Archive
JALJava Application Loader
JPDAJava Platform Debugger Architecture
KDWPKVM Debug Wire Protocol
KjavaKilobyte Java
KMgr pinKJAVA Manager GPIO pin
KVMKilobyte VM. Java VM for limited systems such as embedded ones
Local ClockThe unit's clock. This clock may be synchronized with the network or set by the user with the OSC
class methods
M2MMachine to Machine
MIDletAn application that conforms to the MIDP standard.
MIDPMobile Information Device Profile
MOMobile Originated
Motorola MDMotorola Mobile Devices Business
MTMobile Terminated
2 6802981C50-C
AbbreviationFull Name
NITZNetwork Identity and Time Zone
NMEANational Marine Electronics Association
NVMNon Volatile Memory
OEMOriginal Equipment Manufacturer
OSCOEM System Control
OTAOver The Air
OTA ProvisioningThe process by which the carrier configures the device
PCPersonal Computer
PCNPersonal Communication Network
PKIPublic Key Infrastructure
RTCReal Time Clock
TBDTo Be Defined
SAShip Acceptance
SCLSerial CLock line of I2C bus
SDASerial DAta line of I2C bus
UARTUniversal Asynchronous Receiver/Transmitter
UMUser MIDlet
URLUniform Resource Locator
USSDUnstructured Supplementary Service Data
Web SessionHolds Internet conne ction settings, also known as Internet Settings.
WSWeb Session
CHAPTER 1 - PREFACE
1.5TRADEMARKS
MOTOROLA and the Stylized M Logo are registered in the U.S. Patent and Trademark Office. All other product or service
names are the property of their respective owners.
1.6APPLICABLE DOCUMENTATION
[1] Motorola G24 Developer's Guide, Module Hardware Description, at G24-J MOTODEV Web Page
[2] Motorola G24 Developer's Guide, Developer's Kit, at G24-J MOTODEV Web Page
[3] Motorola G24 Developer’s Guide, AT Commands reference manual, at G24-J MOTODEV Web Page
Problems or corrections to this guide should be reported to G24 customer care by mail: M2MCare@motorola.com
1.8HOW THIS GUIDE IS ORGANIZED
This guide contains the following chapters:
• Chapter 1 - Preface
6802981C50-C 3
CHAPTER 1 - PREFACE
• Chapter 2 - Product Overview
• Chapter 3 - Development Environment Setup
• Chapter 4 - Java Architecture
• Chapter 5 - Development and Maintenance
• Chapter 6 - Java API
• Appendix A - GPIO Lines
• Appendix B - Default MIDlet Features
• Appendix C - GPIO Interrupt Latency
• Appendix D - MIDlet Signing
• Appendix E - IP Director
4 6802981C50-C
2. CHAPTER 2 - PRODUCT
OVERVIEW
2.1INTRODUCTION
G24 is a GSM/GPRS/EDGE OEM module. It is similar to a condensed cellular phone core, which can be integrated into a
communication system to enable the transfer of voice or data information over a cellular network. For a detailed description of
the G24 cellular engine refer to reference
This OEM module which once was controlled by an external CPU is now enhanced to be controlled by the customer’s java
MIDlet applications running on G24's CPU. This new module name is OEM KJAVA.
The main Java differences between a mobile handset and G24 KJAVA engines are shown in Table 1:
HandsetG24
[1].
Table 1: G24 Java Compared to a Handset
Java is not the main feature.Java controls all activities.
Activation via Menu by the user.Activated automatically upon power-up.
MIDlet is for entertainment (Games, Calculators, …).MIDlet is a stand alone controller.
G24 KJAVA allows the customer MIDlet to control the following major features:
• Circuit Switched calls (data and voice)
• IP Network connections
• SMS/MMS
• GSM/GPRS Network status
• Serial connectivity
• SIM card
• NVM Data base (Phone book, File System, Record management)
• HW interfaces: A2D and GPIO
• Power (Low power mode, Airplane mode, Real Time Clock)
• MIDlet upgrade
6802981C50-C5
CHAPTER 2 - PRODUCT OVERVIEW
Note
Figure 1 and Figure 2 present the differences between basic module architecture and the KJAVA one:.
Figure 1. G24 - Basic Module Architecture
Figure 2. G24 - KJAVA Architecture
Two G24 hardware configurations are available:
• OEM - display and keypad are disabled
• HMI - display and keypad are enabled
These two configurations look identical and can be identified by the model name printed on the units.
In order to facilitate G24’s integration with external systems, an evaluation board (EVB) should be u sed. The EVB consist of
the following features:
• 70 pin connector for G24 placement
• SIM card interface
• Antenna
• DC power supply
• USB and RS232 interfaces
• Digital and analog audio interfaces
• Switches, jumpers and LEDs for miscellaneous controls and indications
For a detailed description of the EVB, see “EVALUATION BOARD” and reference [2].
A handset, display and keypad can be attached to the EVB. Such an EVB configuration requires the use of an HMI G24 unit.
6 6802981C50-C
CHAPTER 2 - PRODUCT OVERVIEW
2.2PRODUCT ADVANTAGES
1.Cheaper & Simpler - No External CPU (the traditional controller).
• Java MIDlet controls G24 functionality by running on its own CPU ("On target"), instead of using external control ler
CPU executing AT commands.
• Smaller PCB.
2.Friendly & Flexible - Java Language has rich verity of standard cellular APIs.
3.Easy maintenance - Over The Air (OTA) customer MIDlet application upgrade.
4.Provides full Java solution New Motorola proprietary API - dedicated for the M2M market segment.
5.Partial mode - AT command mode running si mu ltaneously with Java mode.
Example: Developers can use the G24 as a GPRS/EDGE module to connect to the internet via external TCP/IP stack (i.e.
connect it to a standard computer dialer), on the other hand, in parallel, a Java MIDlet can be run.
2.3TYPICAL USE CASE
A typical M2M use case can be described as follows:
G24 integrated within a vending machine, when the machine is out of products it toggles a G24 I/O pin which notifies the MIDlet
(via G24 proprietary API). The MIDlet uses a standard SMS protocol (JSR 120) to notify a control center about this event.
6802981C50-C 7
CHAPTER 2 - PRODUCT OVERVIEW
8 6802981C50-C
3. CHAPTER 3 - GENERAL SETUP
3.1EVALUATION BOARD
Figure 3 shows a G24 unit, display and SIM card mounted on the evaluation board (EVB) and other major EVB components.
Table 2 gives a description of the components.
Figure 3. Evaluation Board - Major Components
Table 2: Evaluation Board Description
No.
1.J210Wall adapter supply connector
2.S200Main power supply switch
3.D200Main power supply indication LED
6802981C50-C9
Reference
Designator
Description
CHAPTER 3 - GENERAL SETUP
Note
Table 2: Evaluation Board Description (Continued)
No.
4.J380USB Mini-B Connector
5.J300RS232-1 Connector
6.J330RS232-2 Connector
7.J350RS232-3 Data Logger Connector
8.J430Speaker Connector
9.J460Microphone Connector
10.J440Headset Connector
11.J480Alert speaker Connector
12.-Keypad and Display
13.-G24
14.J100SIM card Tray
15.S170General switches for testing
16.S160General switches for A2D
17.S110, D701G24 On/Off push-button and indication LED
Reference
Designator
Description
18.M1Antenna
19.-Antenna Cable
20.P2On board antenna connector
21.J122CLI Display
3.1.1Antenna Installation
The numbers in parenthesis refer to the numbers shown in Figure 3.
1.Connect the supplied antenna stub to the EVB antenna base (18).
2.Connect the supplied antenna cable to the EVB SMA antenna connector (20).
3.1.2Power Supply Installation
1.The supplied wall adapter includes a North-American type electrical plug, with optional adapter for European wall sockets. Connect the supplied wall adapter (1), or connect the power supply via the DC supply jacks.
10 6802981C50-C
CHAPTER 3 - GENERAL SETUP
Note
Note
• When using a DC supply, set its voltage level to 3.6V-4.2V, and its current limiting to 2.5A.
• Use the power supply source selection jumper (P204 and P2 03) to activate either of the power supply sources.
• Verify that P200, P201 jumpers are placed.
3.1.3G24 EVB Placement
1.Position the G24 unit over its connector and align with the supporting spacers.
2.Use the supplied screws to fasten the G24 to the board spacers.
3.Connect the antenna cable to the G24 MMCX connector.
3.1.4Start Operation
1.Turn-on the main power switch S200 (2), and verify that indication led D200 (3) is on. Led D701 (10) will turn-on briefly.
2.Turn on G24 by pressing the On/Off push-button switch (17) for a period of 1-2 seconds. Led D701 (17) will turn on permanently.
3.G24 is now ready.
Turning on the ignition switch (IGN1 - S100) causes the unit to turn on automatically whenever the main power
switch S200 (2) is turned on, skipping the On/Off push-button switch (17) press.
3.2SOFTWARE CONFIGURATION
G24 KJAVA has several GSM models available:
• Dual Band Europe
• Dual Band USA
• Quad Band
• Quad Edge
3.2.1Software Version
User should use the following versions and up:
G24: G24_G_0C.11.B2R.
DM: DM_20_11_07.hs - version 2.2.3
3.2.2Available Memory
Flash: 10 MB - Jar file and all data saved by MIDlet (RMS, File System).
RAM: 1.8 MB - Heap size.
Baud rate 19200bps, 8 data bits, 1 stop bit, no parity bit, Flow Control = HW (Auto CTS/RTS)
3.2.5Query System Information
There are two ways to query for system information. The first one is by using DM default outputs upon its startup. Some of its
outputs are:
• Software version
• Flex version
• DM version
The second way is by using OSC AP I via user own MIDlet. This can be done by using: OSC.getProperty method.
3.2.6MIDlet Downloading
3.2.6.1Serial (UART2)
Downloading a MIDlet via serial communications can be done using two different applications.
The first is a multipurpose tool developed alongside the G24, called "Jadpur".
The second is a Motorola Java loader application tool called "MIDway".
Both tools are available in MOTODEV website [4].
Jadpur Setup Stages:
Jadpur requires MS .NET framework installed on your PC.
1.Connect G24 UART2 to PC COM via RS232 cable.
2.Switch the KMgr pin to JTool mode.
3.Run Jadpur, use the Ports button to select the desired COM port, and from "File"->Settings -> Communication menu option
to configure the COM port baudrate to 19200 bps.In the Settings menu, check-mark the "One Click Download" option.
4.Use "File">"Open JAD" menu item to select the JAD file for download. JAD file properties will be displayed in the upper
right corner window frame.
5.Click the Download button, located in the bottom toolbar, to send the oemdownload command and send JAD file.
6.MIDlet download and installation process reports are sent to terminal window, ending with "MIDlet installation
completed".
MIDway Setup Stages:
1.Connect G24 UART2 to PC COM via RS232 cable.
2.Run MIDway and from "File"->Settings menu-> "Communication Settings" configure to 19200 bps. In the "AT command"
box enter "OEMdownload" and click OK.
12 6802981C50-C
CHAPTER 3 - GENERAL SETUP
Note
3.Switch the KMgr pin to JTool mode.
4.Select "File"->"Send AT command" menu item to send the download command to the device.
5.Select "File">"Open JAD" menu item to select JAD file.
6.Select "File">"Send JAD" menu item to send the JAD file (JAR file will be sent automatically).
Using "AT command" box and “Debug Log” Tab in MIDway imitates the traditional terminal use. It is possible to work
separately - sending JTool commands through external terminal and limiting the MIDway to handle the down load
process only.
3.2.6.2Over the Air
Provides the ability to download and install content over a wireless network.
MIDlets stored on a web server can be downloaded to the unit in two ways:
1.Using the OT ADownload API from a UM.
2.Triggering an OTA download from the DM.
3.2.6.3Common Errors
1.Attributes common to JAR manifest and JAD are not identical.
2.The MIDlet-JAR-Size attribute field does not contain the correct JAR size in bytes.
3.Wrong JAD attributes:
MIDlet-Name must be "UserMIDlet" (case sensitive).
MicroEdition-Configuration should be CLDC-1.1.
MicroEdition-Profile must be MIDP-2.0.
4.Untrusted MIDlet trying to replace trusted MIDlet (resolution: trusted MIDlet must be deleted first).
Refer to "Motorola MIDway User's Guide" in the SDK documentation for additional information.
3.2.7Reflashing G24 Software
G24 enables its own software upgrade. Upgrades can be done via:
1.USB with RSD tool.
2.UART1 with PCLoader tool ("OEMreflash" command must be issued via UART2 before using PCLoader).
For the above tools installation and user guides, contact customer care:
M2MCare@motorola.com
3.2.8G24-J HMI
See reference document [5], G24-J HMI Display Integration Guide.
6802981C50-C 13
CHAPTER 3 - GENERAL SETUP
14 6802981C50-C
4. CHAPTER 4 - KJAVA
Note
ARCHITECTURE
4.1GENERAL
The G24 KJAVA product runs one of the following two types of MIDlets:
User MIDlet (UM)
The UM is the customer's MIDlet which controls the G24 to its needs. The UM is the core concept within the G24 Java module.
It lets the customers to run their own code on the G24's CPU. UM is expected to run "forever".
MIDlet-Name attribute (in JAD file) must be "UserMIDlet" (case sensitive) and is verified during MIDlet installation
(Any other name will cause the MIDlet to be rejected).
Default MIDlet (DM)
The DM is a MIDlet provided by the manufacturer. It is a backup MIDlet which enables basic control in case UM has failed or
is absent (e.g. out of the factory). It also enables the customers to broadcast a command for a fresh UM download to all of their
newly scattered units
“APPENDIX B - DEFAULT MIDlet FEATURES” describes all the DM's supported features.
6802981C50-C15
CHAPTER 4 - KJAVA ARCHITECTURE
Note
G24 start
procedure
MIDlet
Manager
JTOOL
Manager
K
J
A
V
A
M
a
n
a
g
e
r
G
P
I
O
p
i
n
=
O
n
K
J
A
V
A
M
a
n
a
g
e
r
G
P
I
O
p
i
n
=
O
ff
KJAVA Manager
GPIO pin = On/Off
MIDlet OTA
Manager
T
r
i
g
g
e
r
f
o
r
M
I
D
l
e
t
u
p
d
a
t
e
M
I
D
l
e
t
d
o
w
n
l
o
a
d
c
o
m
p
l
e
t
e
/
f
a
i
l
e
d
In charge of the G24
MIDlet (G24 MIDlet
controls the G24
functionality)
Supported Tools
1. SW upgrade
2. KDWP enable or
disable
3. Module configuration
(debug logs, set baud
rate, …)
4. MIDlet update
(download)
OTA update triggred
by the MIDlet
4.2FUNCTIONAL DESCRIPTION
G24 KJAVA module has three entities:
• MIDlet Manager - Manages and executes the MIDlet.
• JTool Manager - Manages G24 maintenance
•JAL
• G24 SW reflash
• KDWP activation
• Module configuration
• OTA download Manager - Over The Air MIDlet download procedure
The handshake between these three entities, controlling the G24, is shown in Figure 4. These three entities are mutually exclusive, i.e. upon starting one of these entities the already running one will be stopped.
A GPIO pin ("KMgr pin") selects between MIDlet Manager and JTool Manager entities.
Pin status and selection is defined as follows:
• OFF (low HW signal) - JTool Manager.
• ON (high HW signal) - MIDlet Manager.
16 6802981C50-C
Figure 4. G24 KJAVA Architecture
Line must be pulled to ON if not connected through a switch.
Loading...
+ 50 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.