3 Troubleshooting

Windows does not recognize the board when connected using USB.

The USB drivers are not loaded.

See Chapter 1, "Installing Oracle Java ME Embedded Software on the Qualcomm IoE Board" for more information about installing the USB drivers for the Qualcomm IoE board.

Windows does not recognize the board when connected using USB.

The board is not powered on.

Press the PWR KEY button on the board.

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

The network configuration is incorrect.

Verify that the network connection on the board is correct. Ensure that the board is using DHCP to obtain an IP address.

(continued)

The network configuration on the WiFi access point is incorrect or unsupported.

Verify that WiFi SSID broadcasting is enabled on the router.

(continued)

The WPA2-PSK authentication algorithm is not working correctly on some routers.

Try to manually set the authentication algorithm to WPA-PSK or disable the security checking.

There are no Java logs in the Brew MP Logger application. However, the device has been recognized successfully by the Logger and Loader applications.

The Oracle Java ME Embedded platform did not start. The java.sig file was not updated or is invalid for Oracle Java ME Embedded 8.

Examine the netsetup logs. See Configuring Wi-Fi Networking in Chapter 2 for additional information. If there is no netlog.txt file or it is incorrect, then ensure that the Oracle Java ME Embedded application has been updated and the java.sig file is valid. The signature file from previous versions of the Oracle Java ME Embedded platform will not work correctly.If the netlog.txt file is present and is correct, then ensure that the Oracle Java ME Embedded application in the /sys/mod/java directory has been updated and the java.sig file is valid. The Java signature file from the previous version must also be updated for version 8.

The board is not detected by the Device Connections Manager when connecting to the board in serial mode.

Varies. See Solution column.

If you have some issues with connecting to the Device Connections Manager and the board, then examine the file <USER_HOME_DIR>/javame-sdk/8.0/log/sos-proxy.log.

1. If the last line in the output looks similar to "Open COM{Number}", then ensure that you have specified the correct COM port. If the port is incorrect, then select the proper one by specifying it in Device Connections Manager and restart the board. Note that is sometimes take a minute or more to boot Java after the board is powered on. This is because of WiFi related settings that are performed during the launch time.

   If you do not use WiFi (3G), then you can disable the network setup with net-related commands. In addition, there is a "system.netsetup.timeout" property that configures the timeout to start Java after the network initialization has been started. If the COM port is correct and more than a minute has passed after the board is powered on, then try to reboot both Device Connections Manager and the board

2. If the last line in the output is not "Open COM{Number}", verify that you specified the correct port numbers to connect to the CLI or the logger, then try to reboot both the Device Connections Manager and the board

The Developer Agent does not start manually and throws a BindException: "Address already in use: JVM_Bind"

The NetBeans IDE or the Device Connection Manager is running on your desktop host computer.

1. Close the NetBeans IDE.

2. Close the Device Connections Manager.

3. Start the Developer Agent program again.

The debugging session freezes, disconnects unexpectedly, or shows error messages.

The firewall on the computer is blocking some debugging traffic.

Thunderbird is using a port that is needed for communication with the board.

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.

Close thunderbird.exe during the debugging session.

The current time and date are invalid.

The time and date on the Qualcomm IoE board are configured automatically only if a valid SIM card is inserted and a carrier provides current time data.

Insert a valid SIM card. If the date and time are still wrong, see Chapter 2, "Setting Up the System Time" to set the system time manually.

A signed IMlet will not install. The AMS gives a return code that the certificate or the authentication is invalid.

The certificate is invalid or it is not added to the keystore.

Check the certificate. Refer to Signing the Application with API Permissions in Chapter 2, "Installing and Running Applications on the Qualcomm IoE Board" for details.

(continued)

The date and time on the board were configured incorrectly.

Insert a valid SIM card. If the date and time are still wrong, see Chapter 2, "Setting Up the System Time", to set the system time manually.