Oracle® Java ME Embedded

MERT-2257

FileConnection.lastModified returns a value that depends on TimeZone setting

FileConnection.lastModified provides a long value representing the time the file was last modified, measured in milliseconds since the epoch (00:00:00 GMT, January 1, 1970), or 0L if an I/O error occurs. However, the value returned depends on TimeZone setting.

MERT-2425

Public AMS API: running a task with the wrong suite name doesn't cause an error.

Running a task using the AMS API with the wrong suite name doesn't throw an exception, nor does it return null for the TaskInfo instance if the task can't start.

Recommendation: Don't rely on an exception or the returned value from actually running the task; instead, use the infomation from the TaskInfo instance received from TaskListener.notifyStatusUpdate() and TaskListener.notifyStatusStopped().

MERT-2935

Debugging: Expressions tab does not show fields.

In Eclipse, using static variables in the Expressions tab in the Debug perspective might cause the debug session to freeze with the following symptoms: Only "pending" values instead of expression results; multiple errors in the device console.

Solution: Avoid the use of static variables in expressions; if necessary, monitor these values in the Variables tab.

MERT-3041

The JMEE VM is not fully compatible with JDWP.

Only a JDWP subset is supported. This subset is enough to work with the current versions of Eclipse/NetBeans.

MERT-3291

PeripheralNotFoundException when opening newly registered UART

The return value of the register() function (the new ID) cannot be used as a parameter to the PeripheralManager.open() function, or a PeripheralNotFoundException will be thrown.

Solution: You can create your own UARTConfig object and pass it into the PeripheralManager.open() function without error.

MERT-3437

There are a small number of unsupported JDWP features.

The most noteworthy missing feaures are:

1) Missing method entry/exit breakpoint support, although it is visible for NetBeans users

2) Missing ClassObject req support; Eclipse breaks on it when showing static variables.

MERT-3577

PeripheralTypeNotSupportedException is thrown during call to PeripheralManager.open(config)

The Oracle Java ME Embedded platform may throw a unexpected exception when using the PeripheralManager.open(config) method with an invalid configuration.

MERT-3638

Device Access API: isOpen() returns different values

Please note that Peripheral instances returned by PeripheralManager.list() are in a closed state, and calling isOpen() for them always returns 'false' even if such Peripheral was already opened by other means.

MERT-3651

SPI: Can open devices using negative addresses

According to the specification, an IllegalArgumentException should be thrown if address is not in the defined range (i.e. not a positive or null integer). However, the implementation now contains workarounds to support additional devices that have negative addresses.

MERT-3676

Infinite log output when JC_SOCKET=0

When the TCP logger is used and the JC_SOCKET parameter is set to 0 in the jwc_properties.ini file, there can be infinite output from the logger.

Workaround: Never set JC_SOCKET to 0. The best solution is manually set JC_SOCKET to 4 in the jwc_properties.ini file.

MERT-3798

Device Access API Spec: Description on unregistering an application-registered peripheral ID while this particular peripheral is still in an open state

The Device Access API Spec does not outline what behavior should occur when unregistering an application-registered peripheral ID while this peripheral is still in the open state. The curent behavior is to close the peripheral.

MERT-3799

ADCChannel.startAcquisition behavior with provided count = 0 is not specified in DA API specification.

The DA API specification does not outline the behavior when the ADCChannel.startAcquisition(values, offset, count, doubleBuffering, listener) method is called and count is zero. Currently, an IllegalArgumentException is thrown.

Workaround: Do not set count = 0 while starting acquisition.

MERT-3800

DACChannel.startGeneration behavior with provided count = 0 is not specified in DA API specification.The DA API specification does not outline the behavior when the DACChannel.startGeneration(values, offset, count, doubleBuffering, listener) method is called and count is zero. Currently, an IllegalArgumentException is thrown.

Workaround: Do not set count = 0 while start generation.

MERT-3806

AcquisitionEvent and Monitoring constructors do not throw any exceptions

The AcquisitionEvent and MonitoringEvent constructors do not throw any exceptions (except NullPointerException) when invalid parameters are supplied.

MERT-3808

PinEvent and PortEvent constructors do not throw any exceptions

The PinEvent and PortEvent constructors do not throw exceptions when their parameters are out of the defined range.

MERT-3887

An unexpected PeripheralConfigInvalidException is thrown, instead of PeripheralNotFoundException, when opening a peripheral using incorrect configuration parameters.

Instead of a PeripheralNotFoundException, an unexpected PeripheralConfigInvalidException is thrown when calling PeripheralManager.open(java.lang.Class intf, PeripheralConfig config) when the config parameter contains incorrect peripheral hardware addressing.

Workaround: An application should catch both exceptions when opening a peripheral.

MERT-3932

UART port fails to open with a valid or invalid configuration right after it was opened with an unsupported dataBits configuration.

Right after a failed attempt to open UART port with an invalid dataBits value, and a PeripheralConfigInvalidException is thrown, any further attempt to open the same UART port with a valid or invalid configuration will throw a PeripheralNotAvailableException.

Workaround: 1. Use only valid configuration, that is supported by underlying platform (refer to the Getting Started Guide for supported configuration information); 2. If a PeripheralNotAvailableException is thrown, wait some time or reboot the board and open UART port with valid configuration again.

MERT-4306

GPIO output voltage problem.

As was observed on some instances of IoE boards, an output voltage of a GPIO pin may be 1.79 V, not 1.8 V.

MERT-4351

External I2C slave devices with pull-up resistors do not work.

An external I2C slave device that has its own pull-up resistors on both the SDA and SCL lines doesn't work with the board. If the external device does not have pull-up resistors, there are no problems.

Workaround: Remove the R16/R17 (SCL/SDA pulls) resistors from the main IoE board (Gobi) to disable the pull up, or do the same on I2C slave's side.

MERT-4357

Impossible to open one more SPI slave device with a different configuration without rebooting the board.

Only one SPI slave device can be opened at a time. When the first SPI device is closed, any attempt to open the same or another SPI device with a different configuration will fail. A new SPI configuration is applied only after a board reboot.

Workaround: Before working with a new SPI slave device, reboot the board.

MERT-4384

Breakpoint condition "Multiple of" does not work with remote JMEE VM.

Debugging using NetBeans of the code with several threads is unpredictable. This is an issue with NetBeans, and is documented at https://netbeans.org/bugzilla/show_bug.cgi?id=227746.

MERT-4386

An unnecessary pin (pin 36) is mentioned in the jwc_properties.ini file for a pre-configured GPIO port (id=200, name="LEDS")

The port "LEDS" is configured to include three pins; this configuration is described in GSG. However, the list of pins in the jwc_properties.ini file for this port includes four pins. The last pin in the list (pinNumber=36) is ignored by the implementation since the pinCount for the port is 3. The implementation behaves according to the documentation (only three pins are opened when the port is opened; the fourth pin is ignored). The confusing fourth pin may be deleted from the jwc_properties.ini file.

MERT-4569

Garbage appears in the serial channel which leads to channel closing

In rare cases a PC can lost a connection with the board when the tooling over serial is used for running, debugging, or profiling applications. This is caused by "garbage" that appears in the serial communication channel.

Workaround: Reboot the board

MERT-4570

ATDevice.sendCommand method sometimes throws an IOException when a supported command is being sent

In some cases, the ATDevice.sendCommand() function can throw an IOException at the time that a supported AT command is being sent.

Workaround: Try to send the command again if it is in the list of supported commands.

MESDK-1939

Occasionally during the debugging or profiling of an IMlet, the Device Manager looses a connection to the board.

Occasionally during the debugging or profiling of an IMlet, the Device Manager looses a connection to the board. The situation is reproduced only if an IMlet tries to open many network related connections to URLs that are not available/reachable.

Workaround: If tooling's network mode is leveraged then change JC_SOCKET property's value to 4 (DISABLE), it will decrease the number of faults significantly. Otherwise, use tooling's serial mode for debugging/profiling. This mode is more preferable then the network mode. (Refer to the Getting Started Guide in order to figure out what is meant under a tooling mode and how to change system properties.)