Oracle® Java ME Embedded Getting Started Guide for the Reference Platform (Keil) Release 3.3.1 E38140-02 |
|
Previous |
Next |
This chapter contains a list of common problems that you may encounter while installing and running the Oracle Java ME Embedded software on the Keil MCBSTM32F200 board. This chapter provides information on the causes of these problems and possible solutions for them.
The common problems in this chapter are grouped in four categories:
Table 3-1 contains information about problems and solutions when installing the firmware on the board.
Table 3-1 Problems and Solutions - Installing the Firmware on the Board
Problem | Cause | Solution |
---|---|---|
The |
The debugger is not connected. |
Connect the debug cable to the board and to the computer. Both the power cable and the debug cable must be connected to install the firmware on the board. |
(continued) |
Your debugger is not the ULINK ME debugger. |
Follow these steps:
The firmware installs on the board. |
An output file specified in the |
There is a bug in version 4.6 of the MDK-ARM toolkit. |
Use MDK-ARM 4.54 or 4.7 |
Table 3-2 contains information about problems and solutions when starting the runtime on the board.
Table 3-2 Problems and Solutions - Starting Oracle Java ME Embedded on the Board
Problem | Cause | Solution |
---|---|---|
Oracle Java ME Embedded fails to start on the board, even after the firmware is installed correctly. |
The SD card is not inserted correctly. |
Eject the SD card from the board, insert it again and press the Reset button. |
(continued) |
The SD card is not formatted correctly using FAT32. |
Format the SD card using the Windows format tool and copy the files from the Oracle Java ME Embedded distribution. See the section Setting Up the MicroSD Card in Chapter 1. Insert the SD card on the board and press the Reset button. |
(continued) |
Some files in the SD card are marked as read only. |
Change the attributes of all files in the SD card and assign them write permissions. Insert the SD card on the board and press the Reset button. |
(continued) |
In rare cases, the file system of the SD card may be corrupted. |
Re-format and re-install the contents of the SD card. See the section Setting Up the MicroSD Card in Chapter 1. Insert the SD card on the board and press the Reset button. |
An authorization failure is given when an IMlet attempts to access any Device Access API. |
The IMlet is not signed. |
Sign the IMlet using a keystore with a trusted certificate authority (CA). |
(continued) |
The date on the board may invalidate the certificate used to authenticate the digital signature. |
See the section Setting Up the MicroSD Card in Chapter 1 for the procedure on how to reset the date on the board by modifying the |
Oracle Java ME Embedded fails to initialize the network on the board. |
The network configuration is incorrect. |
Edit the file |
Oracle Java ME Embedded fails to reset the clock on the board. |
The |
Rename the |
Table 3-3 contains information about problems and solutions when using the board with the Oracle Java ME SDK and the NetBeans IDE.
Table 3-3 Problems and Solutions - Oracle Java ME SDK and the NetBeans IDE
Problem | Cause | Solution |
---|---|---|
The Java ME menu does not appear; unable to find the Device Selector. |
The Oracle Java ME SDK plugin for the IDE is not installed. |
Install the Oracle Java ME SDK plugin that is specifically for your development IDE, as described in Chapter 2. |
The board is not detected when adding a new device to the Device Selector. |
On-device debugging is not enabled. |
Edit the file |
The runtime on the board has problems accessing files or it is unstable. |
The SD card is not supported or it is not formatted correctly. |
Ensure that you are using a supported SD card and that you format it using the Windows formatting tool. See the section Setting Up the MicroSD Card in Chapter 1. Insert the SD card on the board and press the Reset button. |
The board resets itself, especially when installing large IMlets or debugging applications. |
In some cases the watchdog may trigger while the board communicates with the Oracle Java ME SDK and the NetBeans IDE. |
Disable the watchdog on the file |
The debugging session freezes, disconnects unexpectedly, or shows error messages. |
The firewall on the computer is blocking some debugging traffic. |
Open TCP port 2808 on your firewall configuration settings. The exact procedure to open a port differs depending on your version of Windows or your firewall software. |
(continued) |
Thunderbird is using a port that is needed for communication with the board. |
Close |
The TCP log of the Oracle Java ME Embedded software can help you diagnose problems that arise when running IMlets on the board. The TCP log is covered in the section Connecting to the CLI and Logging Ports in Chapter 1.
If you cannot view the TCP log, the system log of the Keil MCBSTM32F200 board can provide you with the same information. Follow these steps to view the system log:
Connect a serial cable from the computer to the board. Use the upper DB9 connector.
Ensure that the log.method
property from the jwc_prop.ini
file contains the value UART
in its list.
Open a terminal emulator on the computer, such as PuTTY.
Choose a serial connection and set the following options:
Speed: 115200
Data bits: 8
Stop bits: 1
Parity: None
Flow control: XON/XOFF
In PuTTY these options are in the category Connection > Serial.
Open the connection. The system log appears on the terminal.