| Oracle® Java Micro Edition Software Development Kit Developer's Guide Release 3.3 for NetBeans on Windows E24265-05 |
|
 Previous |
 Next |
| Oracle® Java Micro Edition Software Development Kit Developer's Guide Release 3.3 for NetBeans on Windows E24265-05 |
|
Previous |
Next |
The Oracle Java ME SDK provides default device skins. A skin is a thin layer on top of the emulator implementation that defines the appearance, screen characteristics, and input controls. This chapter discusses the default emulators provided by Oracle Java ME SDK and describes how you can create and modify a custom device. To make your own device, see "Using the Custom Device Editor."
The Oracle Java ME SDK emulator simulates a CLDC, CDC, or IMP-NG device on your desktop computer. The emulator does not represent a specific device, but it provides correct implementations of its supported APIs.
|
Note: The configuration of all peripherals, except UART, can be inspected in the emulator main window. The configuration of UART is defined by the hardware configuration of the COM ports on your Windows XP or Windows 7 PC. |
The SDK runs applications on an emulator or an external device. Before you can run an application from the SDK, the Device Manager, which manages both emulators and external devices, must be running. When the Oracle Java ME SDK runs, the Device Manager automatically launches and starts detecting devices. The default emulators shipped with the SDK are automatically found and displayed in the Device Selector window (Tools > Java ME > Device Selector).
The SDK uses the device manager to detect devices and displays the available devices in the Device Selector window (Tools > Java ME > Device Selector). The Device Manager is a service and you can see it running in your Windows system tray. In the task manager, the process is labeled device-manager.exe.
You can right-click the icon and select Exit to stop the service.
To restart the device manager, double-click device-manager.exe in your installdir\bin directory. You can also start it from the command line as described in "Run the Device Manager."
In the Windows system tray, click the icon or right-click the icon and select Manage Device Addresses from the menu to open the Device Address Manager. Enter an IP address and select Add to add a device. Select an address and click Remove if you have an address you no longer want to detect. The device is no longer displayed in the Device Selector.
Right-click the icon in the system tray and select Registered Devices to see a list of registered devices and their configuration information such as, screen dimensions, screen depth, security domains, supported APIs, and more.
Typically an emulator is launched when a Java ME SDK project is run from the NetBeans IDE or the command line. The default emulator is determined by the Java ME platform selected for the project, as described in "Managing Java Platforms."
You can open an emulator without running an application from the IDE. From the Windows Start menu, click Programs and select Java(TM) ME Platform SDK 3.3 and select the desired emulator. You can also click the emulator shortcuts installed on your Windows desktop.
To run an application from the emulator, click the Application menu and select Run MIDlet Suite (or Run IMlet Suite). Provide the path to the application and any other information, and click OK.
The CLDC AMS home screen features three utilities:
Install Application. This utility opens a form in which you can specify a URL (or a file path) for a JAD file to install.
Manage Certificate Authorities. This feature displays the certificates authorities for the device. In this interface the white box indicates the certificate is checked (active). You can uncheck certificates that are not needed.
Output Console. The output console displays system output statements from a running application. The application must write to the Java standard output console using, for example:
System.out.println("text");
Start the emulator's Output Console, then start your application. Use F7, Switch running MIDlet, to switch between the application and the Output Console.
Note that the emulator's Output Console is an application that consumes resources. If you get the message "No more concurrent applications allowed," you must close some applications before continuing.
See "Emulator Features" and "Emulator Menus."
You can also access system output information from the emulator by clicking the View menu and selecting Output Console..., which opens an Output Console dialog box. Select a filter from the dropdown list to display specific system output. Click Save to save the output as a .log file.
The device selector can detect a device that has a compatible runtime. Typically this device has network capabilities and is connected to the computer running Java ME SDK.
To detect a physical device, click CTRL-D, or click the device icon at the top of the Device Selector window.
Type an IP address and click Next. Click Finish.
You can also enter an IP address in the Device Manager, as described in "The Device Manager on Windows."
The physical device is listed in the appropriate platform tree. By default, the device has "ExternalDevice" appended to the name.
For example, if an IMP-NG device is detected it is placed in the IMP-NG node and given the name IMPNGExternalDevice1.
For an example of how to configure and work with an external device, see the Oracle Java ME Embedded Getting Started Guide for the Windows Platform. This document is available on the Java ME documentation site under the Oracle Java ME:
http://docs.oracle.com/javame/embedded/embedded.html
Expand the Oracle Java ME Embedded Version node and then the Getting Started and Release Notes node.
The Device Selector window lists all available devices grouped by platform. If this window is not visible, select Tools > Java ME > Device Selector.
If no Java ME platform is registered in NetBeans, the Device Selector displays a node labeled No Device Found. If you see this message at startup, it typically means device discovery is incomplete and you must wait a few seconds.
Each sub node represents a device. Two instances are provided for some CLDC devices, for example, JavaMEPhone1 and JavaMEPhone2. Instances of the same device have the same capabilities but unique names and phone numbers, making it easy for you to test communication between devices of the same type. To make your own device, see "Using the Custom Device Editor."
For Device names, see "Oracle Java ME SDK Directories." The properties for each device are stored in XML files in your user work directory. See Table 8-1.
To view platform properties from the device selector, click on the platform node (for example, CLDC or IMP-NG). The Properties window is, by default, docked in the upper right portion of the user interface. If the Properties window is not visible, click the Windows menu and select Properties.
To view the platform properties in a separate window, right-click the platform node and select Properties. The information in the docked properties window and the separate window is the same.
In the Device Selector window, double-click a device node. The Device Information tab opens in the central Main window. It displays a picture of the device and displays details, supported hardware capabilities, keyboard support, supported media formats, and the supported runtimes.
In the Device Selector window, click a device node (such as JavaMEPhone1) to display the device properties. The Properties window is, by default, docked in the upper right portion of the user interface. If the Properties window is not visible, click the Windows menu and select Properties.
In the Device Selector window, right-click a device and select Properties. Any properties shown in gray font cannot be changed. You can adjust the device properties shown in black. Only CLDC and IMP-NG options can be adjusted. The CDC options cannot be changed.
This section lists general properties that can be changed.
Phone Number. You can set the phone number to any appropriate sequence, considering country codes, area codes, and so forth. If you reset this value, the setting applies to future instances. The number is a base value for the selected device.
Heapsize. The heap is the memory allocated on a device to store your applications's objects. The Heapsize property is the maximum heap size for the emulator. You can choose a new maximum size from the dropdown menu.
Security Domain. Select a security setting from the dropdown menu. See "Specify the Security Domain for an Emulator." Applies to CLDC platforms.
JAM storage size in KB. The amount of space available for applications installed over the air.
Locale. Type in the locale as defined in the MIDP 2.1 specification at:
http://download.oracle.com/otndocs/jcp/midp-2.1-mrel-oth-JSpec
Remove MIDlet Suite in execution mode. If this option is enabled, record stores and other resources created by the MIDlet are removed when you exit the MIDlet (assuming the MIDlet was started in execution mode).
If enabled (checked), the Check boxes for Trace GC (garbage collection), Trace Class Loading, Trace Exceptions, and Trace Method Calls activate tracing for the device the next time the emulator is launched. The trace output is displayed at runtime in the user interface Output window. Trace Method Calls returns many messages, and emulator performance can be affected. See Chapter 11, "Monitoring Memory."
These properties determine the selection of a location provider. Two providers are offered so that your application can test matching the location provider criteria.
If you select a property a short explanation is shown in the description area just below the Properties table. For more information on these values, see the Location API at:
To utilize the Universal Asynchronous Receiver/Transmitter (UART) functionality, you need to create a configuration file (for example UARTConfig.xml). The configuration file defines the device ID and Name, and the Name must point to a real serial port name defined by the operating system. For example,
deviceaccess.uart.dev14.name = COM1
For an already opened UART, you can add it to the peripheral manager by calling PeripheralManager.open with the configuration object.
In application code, you can use Connector.open("comm:COM1") to open a port on the device. On Windows, you can open a serial port such as COM1 or COM2.
The SDK determines which open projects are suitable for a device. Right-click the device and select a project from the context menu.
You can also launch the emulator to ru.n a project from the command line, as explained in "Emulator Command Line Options."
CLDC-based devices are capable of running multiple virtual machines. You can test this behavior in the emulator. Be sure the output window is visible in the SDK (select Window > Output > Output). To test this feature, follow these steps:
Open the sample projects Games and AudioDemo.
In the device selector, choose a CLDC device and run Games. When the emulator launches, run AudioDemo on the same device.
As each MIDlet loads, the AMS automatically installs it.
In AudioDemo, launch the Audio Player, and play the JavaOne theme.
Select AudioPlayer, then from the soft menu, select 1, Launch. Select JavaOne Theme and press the Play soft button.
In the emulator, click the Application menu and select AMS Home, or press F4.
Select Games. From the soft menu, select 1, Open. The music continues to play while you are able to simultaneously launch and play games.
Click the Application menu and select AMS Home, or press F4. Highlight AudioSamples, and from the soft menu, select 2, Bring to foreground. Press the Pause soft key. The music stops playing.
Click the Application menu and select AMS Home, or press F4. Highlight AudioSamples and from the soft menu, select 1, Open. Select Bouncing Ball from the list and press the Launch soft button. Select MIDI background and press the Play soft button.
Click the Application menu and select AMS Home, or press F4. Then click the Application menu and select Switch Running MIDlet. Select Audio Player and press the Switch to soft button. You can press the Play soft button to resume the Audio Player.
Figure 7-5 shows common emulator features available on emulators for the CLDC platform.
Device Name. Shown in the upper window frame. See Table 8-1for a list of default emulator names.
Transmission Indicator. On the upper left of the emulator image, this blue light turns on when a transmission is occurring. Typically you see it when an application is installed over-the-air, or when a message is being sent or received. For example, when you receive a message from the WMA console.
Menus. See "Emulator Menus."
Tool Bar. For the CLDC emulator, the Tool Bar provides shortcuts for the following operations:
Run MIDlet Suite
Install MIDlet Suite
Resume
Suspend
Rotate Clockwise
Rotate Counter Clockwise
External Events Generator
Emulator window always on top
Device ID. Numerical identifier that is unique for each device.
Exit Button. On the upper right of the emulator image, is the termination button. Pushing this button the same effect as clicking Application and selecting Exit.
Emulator Status Bar. Information about the current system state is shown in the status bar at the bottom of the emulator window.
Figure 7-6 shows common emulator features available on emulators for the IMPNG platform.
Device Name. Shown in the upper window frame. See Table 8-1 for a list default emulator names.
Menus. See "Emulator Menus."
Tool Bar. For the IMP-NG Emulator, the Tool Bar provides shortcuts for the following operations:
Run IMlet Suite
Install IMlet Suite
External Events Generator
Emulator window always on top
|
Note: When the Device Manager detects an external IMP-NG device, only the Application, View, and Help menus and the Run IMlet Suite, Install IMlet Suite, and Emulator window always on top icons in the Toolbar are available in the device display. |
Device ID. Numerical identifier that is unique for each device.
Display Panel and Tabs. The display panel displays fields and information dependent on the selected tab:
AMS. The AMS (Application Management System) tab displays the name of the IMlet suite, the IMlet, and the status of the IMlet suite. You can select a suite and perform one of the following operations by clicking the corresponding button to the right of the display:
Install - Specify the location of the IMlet suite path or URL and the security domain and click OK to load the IMlet suite.
Update - Check for any updates to the application and performs the update.
Info - Open a dialog box displaying the application name, vendor name, version, description of the application, class name, and the URL.
Run - Run the selected application. This button is only visible for an installed application that is not running.
Suspend (Resume) - Pause the running IMlet. This button toggles to Resume when execution is paused.
Stop - Stop execution of the application. This button is only visible for a running application.
Remove - Remove the application.
GPIO Pins. The General Purpose Input Ouput (GPIO) Pins tab displays which pins are selected to output and their high or low values.
GPIO Ports. The GPIO Ports tab displays a list of ports, which ports are selected to output, and their maximum and current values.
I2C. The Inter-Integrated Circuit (I2C) tab displays information for the selected slave device and data sent to a master device and data received from a master device.
SPI. In the default SPI implementation, buffered written data can be read from the Slave named SPI. If you have created a custom implementation with the Custom Device Editor, the Slave dropdown list might have additional slaves.
MMIO. The memory-mapped I/O tab displays information for the current device.
DAC. The Digital-to-Analog Converter tab displays the current channel information, converter characteristics, and a graphic display of signal characteristics with the x-axis showing the digital input and the y-axis showing the analog output.
Emulator Status Bar. Information about the current system state is shown in the status bar at the bottom of the emulator window. Also shown is the memory indicator showing used and total memory.
The emulator for the CLDC platform has Application, Device, Edit, Tools, View, and Help menus.
The emulator for the CDC platform has Application, View, and Help menus. The View and Help menus are the same on CDC and CLDC platforms. For CDC, the Device menu is not populated, and Application menu contains only the Exit option.
The Emulator for the IMP-NG platform has Application, Device, Tools, View, and Help menus.
The Application menu is fully populated for the CLDC platform. Table 7-1 describes the Application options:
Table 7-1 Emulator Application Menu
| Option | Accelerator | Description |
|---|---|---|
|
Install MIDlet Suite |
Permanently add a MIDlet suite to the emulator. Enter the path or URL of the MIDlet suite to install on the emulator. Select the desired level of the permissions in the Security Domain field. |
|
|
Install IMlet Suite |
Permanently add a IMlet suite to the emulator. (IMP-NG emulator) Enter the path or URL of the IMlet suite to install on the emulator. Select the desired level of the permissions in the Security Domain field. |
|
|
Run MIDlet Suite |
Emulator interface for launching MIDlets. |
|
|
Run IMlet suite |
Emulator interface for launching IMlets. (IMP-NG platform) |
|
|
AMS Home |
F4 |
Exit the current application and return to the Application Management Software home. (CLDC emulator) |
|
Stop |
F10 |
Stops the currently running MIDlet. (CLDC emulator) |
|
Change Locale |
This option only works with localized MIDlets. (CLDC emulator) Enter a locale identifier. The format is similar to Java SE 6, as follows: 2-letter-lang-code separator 2-letter-country-code For example, en-US, cs-CZ, zh-CN, ja-JP. The separator can be a dash or an underscore. |
|
|
Resume |
F6 |
Resume a suspended application. (CLDC emulator) |
|
Suspend |
F5 |
Pause a running application. (CLDC emulator) Do not use this option if you are running the memory monitor. |
|
Switch Running MIDlet |
F7 |
When you have multiple MIDlets running, toggle between them. You see a list of running MIDlets and you can chose the one you want to switch to. See "Running Projects Simultaneously on a Single Device" (CLDC emulator). |
|
Exit |
Exit button on emulator upper right |
Close the emulator process and stop the build process (or processes). |
This menu is available on CLDC and IMP-NG platforms.
Click the Device menu and select Messages to see what is written in the message area. This is the emulator's Inbox. The Inbox displays WMA messages that are addressed to the device, not an application on the device. Messages are sent to this interface in the following cases:
An MMS message is sent without an AppID in the address
An SMS message is sent without a port in the address (or the port number is 0)
An SMS text message is sent with a port in the address, but there is not a Java ME application listening on the specified port
To test sending messages to the inbox use the WMA Console in NetBeans, or from the command line, use wma-tool.exe to send SMS messages. Note, wma-tool.exe requires an AppID for MMS, so wma-tool cannot be used to send an MMS.
This option is only visible for the CLDC emulator.
Use this feature to test your application's ability to display in portrait and landscape formats. The default is 0 degrees. Change the orientation to 90, 180, or 270 degrees. You can also rotate 90 degrees clockwise (F8) or counterclockwise (F9) from the current position.
Table 7-2 describes the Edit menu, which provides basic editing operations for the CLDC platform.
Table 7-3 describes the utilities accessible from the Tools menu.
Table 7-3 Emulator Tools Menu
| Option | Description |
|---|---|
|
Manage Landmarks |
Opens the Landmark Store utility. In this interface, you can view and edit a landmark store installed as part of an application. You can also create a new landmark store, define landmarks, define landmark categories, and assign landmarks to categories. |
|
Manage File System |
Opens the File System manager and displays the mounted file system root directories. You can mount or unmount a file system directory, copy a mounted file system directory, remount or remove directories. For a description of managing a file system, click the Tools menu and select Manage File System. Click Help in the dialog box. |
|
External Events Generator |
Opens the External Events Generator. The External Events Generator provides a way to interact with an application by injecting events. The interaction may be through a user interface, or through a script file. For a description of the External Events Generator, see "External Events Generator." |
|
Take Screenshot |
Takes a screenshot of the emulator display screen and saves it to the clipboard. (CLDC emulator) |
The following menu options each have a tab on the External Events Generator. The use of the External Events Generator is addressed in the discussion for each JSR:
ADC. The Analog-to-Digital Conversion tab is only visible for the IMP-NG emulator.
Access Points. This tab displays connection information for the selected access point. This tab is visible only for the IMP-NG emulator.
Contactless Communication. See "Using ContactlessDemo." This feature is available only for CLDC devices.
GPIO. This General Purpose Input Output (GPIO) option is visible only for the IMP-NG emulator.
By default, this tab displays ports and pins for a specific device described in "Running the GPIODemo." You can create a custom device to represent a different device. "General Purpose Input Output (GPIO)."
See the Device Access API (installdir\docs\api\deviceaccess) for a description of the GPIO interface.
MMIO. The memory-mapped I/O (MMIO) option is visible only for the IMP-NG emulator. From the Device dropdown list, choose one of the default devices:
TEST_DEVICE. A Little Endian device that contains all block types: byte, short, int, long, and block. Writes to this device also affect BIG_ENDIAN_DEVICE which shares the address space.
WDOGLOG. A Little Endian device that supports only the block type.
RTC. STM32F2xx RTC device. A Little Endian device that supports only the int type.
BIG_ENDIAN_DEVICE. A Big Endian device that shares the address space with the TEST_DEVICE, therefore it contains the same memory blocks. Writes to this device also affect TEST_DEVICE which shares the address space.
If you are using a custom device created with the Custom Device Editor (see "Using the Custom Device Editor"). The device list might include additional devices.
See the Device Access API (installdir\docs\api\deviceaccess) and the Embedded Support API (installdir\docs\api\embedded-support-api) for descriptions of the MMIO interface.
Mobile. The unique International Mobile Subscriber Identity (IMSI) and the International Mobile Station Equipment identity (IMEI) identifiers of the device. This tab is visible only for the IMP-NG emulator.
Pulse Counter. This tab displays the current pulse counters on the device. The default configurations are:
COUNTER_PA0
COUNTER_PB3
COUNTER_PB10
COUNTER_PA3
You can configure the pulse counters you want and send a signal to the configured pulse counter by clicking Send Pulse.
This tab is visible only for the IMP-NG emulator.
Sensors. "Using a Mobile Sensor Project" and "Creating a Sensor Script File." This tab is only visible for the CLDC emulator.
Table 7-4 describes the View menu, which is available for the CLDC, CDC, and IMP-NG platforms.
Table 7-4 Emulator View Menu
| Option | Description |
|---|---|
|
Always On Top |
Keeps the emulator in the foreground. This option is especially useful when you are running multiple emulator instances and you want to see them all and send messages between devices. |
|
Output Console |
Displays system output statements from a running application in the Output Console window. You can filter the output statements for IMP-NG emulators by selecting All, Standard, or Error from the Show dropdown list. Error messages are highlighted. Filtering of output statements and highlighting of error messages are not available for CLDC emulators or external devices. You can save system output information to a |
|
Device Log |
Displays emulator log messages in the Device Log window. The following filters are available from the Level dropdown list:
You can save system output information to a |
With the Custom Device Editor you can create your own devices. The appearance of the custom devices is generic, but the functionality can be tailored to your own specifications.
Follow these steps to create a custom device.
Select Tools > Java ME > Custom Device Editor.
The custom device tree displays Java ME platforms and custom devices, if any.
Alternatively, you can launch the Custom Device Editor from the your installation's bin directory. For example:
C:\Java_ME_platform_SDK_3.3\bin\device-editor.exe
The custom device tree displays Java ME platforms and custom devices, if any.
Select a platform and click the New... button.
Change the default configuration to match your specifications, and click OK.
Your device is added to the custom device tree and eventually appears in the Device Selector. You can run projects from the IDE or from the command line from the custom device.
The custom device tree affects what appears in the Device Selector. For example, if you do not want a custom device to appear in the device selector, you must remove it from the custom device tree.
The device definition is saved in installdir\toolkit-lib\devices.
Custom devices should always be managed using the Custom Device Editor. Using the tool ensures that your device can be detected and integrated with the Oracle Java ME SDK.
New. Select a platform and click New to add a new device.
Edit. Select a device to change, and click Edit.
Clone. Select a device to copy, and click Clone. To prevent confusion, be sure to provide a unique name.
Remove. Select a device to delete and click Remove. This action completely deletes the device.
Import. Select a node in the custom device tree and click Import. Choose a .zip file created with the Export command.
Export. Select a device to save, and click Export.
When a custom device is created it is saved in installdir\toolkit-lib\devices, therefore you could lose your device if you reinstall.
An exported device is stored in a .zip file and saved in the user's My Documents directory (typically username\My Documents).
When you create a new IMP-NG device you can use the default implementation or create your own custom implementation for the interfaces discussed in this section.
See the following resources for in-depth descriptions of the IMP-NG interfaces or devices:
Device Access API (installdir\docs\api\deviceaccess)
Embedded Support API (installdir\docs\api\embedded-support-api)
For more information about default devices look at an IMP-NG property file:
username\javame-sdk\3.3\work\IMPNGDevice1\device.properties
A GPIO port is a platform-defined grouping of GPIO pins that may be configured for output or input. Output ports are both writable and readable while input ports are only readable. Note that GPIO pins that are part of a GPIO port cannot be retrieved nor controlled individually as GPIO Pin instances.
Click Add Port to add entries to the Ports table. Each item in a Ports table row is editable. Check Output to set the port direction to output.
A GPIO pin may be configured for output or input. Output pins are both writable and readable while input pins are only readable. Note, an input listener can only be assigned to a pin set for input.
Click Add Pin to add a row to the Pins table. The ID and name are editable. Click Output to make a pin both readable and writable. Click in the Initial Value column to toggle the Initial Value from Low to High.
The process for configuring I2C and SPI interfaces is very similar.
On an I2C bus, data is transferred between the I2C master device and an I2C slave device through single or combined messages. On an SPI bus, data is transferred between the SPI master device and an SPI slave device in full duplex. That is, data is transmitted by the SPI master to the SPI slave at the same time data is received from the SPI slave by the SPI master. See the Embedded Support API for more details.
Select Sample Echo to choose the default bus implementation. This default implementation simply reads buffered written data from the slave.
Select Custom to specify your own bus implementation.
Supply your bus implementation JAR file and the name of the Java class that implements the bus.
For I2C, the bus is:
com.oracle.jme.toolkit.deviceaccess.i2c.I2CSlaveBus
For SPI, the bus is:
com.oracle.jme.toolkit.deviceaccess.spi.SPISlaveBus
To add Slaves, click Add and specify an ID and Name. For SPI, specify the Word Length as well.
|
Note: On an SPI bus, data is transferred between the SPI master device and an SPI slave device in full duplex. So every |
The default devices are described in "External Events Generator."
If you want to provide your own MMIO emulation, you must specify a custom handler.
Supply your implementation JAR file and the name of the Java class that implements com.oracle.jme.toolkit.deviceaccess.mmio.MMIOHandler. For comparison, the default JAR file is:
installdir\toolkit-lib\devices\IMPNGDevice\code\emulator_deviceaccess_mmio-sample-handler.jar
To add devices to the custom MMIO implementation, use the Devices and Device Memory tables as follows:
Click Add Device to add a row to the Devices table.
A default ID is assigned but you can double-click in the ID column to edit the value.
A default Name is supplied, but it can also be edited.
In the Byte Ordering column, make a selection from the dropdown list.
Click a row in the Device table to select a Device.
Click Add Memory.
In the Type column, make a selection from the dropdown list. Double-click to edit the Address column entries.
If the type is Block, you can double-click to edit the Size column entries as well as the Address column entries.
Click OK.
|
 Copyright © 2009, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
