3 Troubleshooting

The flash.bat script fails and the firmware is not installed on the board.

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:

1. Open the file flash/jmee.uvproj from the Oracle Java ME Embedded distribution with the Keil µVision IDE.

2. Select the menu Flash > Configure Flash Tools.

3. Choose your debugger from the list under Use Target Driver for Flash Programming and click OK.

4. Select the menu Flash > Download.

The firmware installs on the board.

An output file specified in the flash.bat is not generated.

There is a bug in version 4.6 of the MDK-ARM toolkit.

Use MDK-ARM 4.54 or 4.7

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 rtc_upd.cfg file.

Oracle Java ME Embedded fails to initialize the network on the board.

The network configuration is incorrect.

Edit the file platform.cfg in the SD card and edit the network configuration parameters. Insert the SD card on the board and press the Reset button.

Oracle Java ME Embedded fails to reset the clock on the board.

The rtc_upd.cfg configuration file was not renamed prior to board initialization.

Rename the rtc_upd.cfg file on the SD card to rtc.cfg and reset the board.

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 java/jwc_prop.ini and set the property odt_run_on_start to true. Insert the SD card on the board and press the Reset button.

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 platform.cfg. See the section Setting Up the MicroSD Card in Chapter 1. Insert the SD card on the board and press the Reset button.

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 thunderbird.exe during the debugging session.