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

Debug: 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-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-3301

Modularity: Unexpected "Not evaluated item"

The log file may report that the midp.conf file may contain an unexpected evaluation error.

MERT-3358

User should not launch two instances of JMEE runtime

See Usage Notes above.

MERT-3401

Cannot attach NetBeans to kdp unless it is run with "-v 9"

It may be necessary to append "-v 9" to the kdp command line when a connection to NetBeans is required.

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 users2) Missing ClassObject req support; Eclipse breaks on it when showing static variables

MERT-3543

Cannot start runtime under regular user once it was started under root

Once the JMEE runtime is started with super user priviledges (using sudo), it's no longer possible to start it without sudo, until attributes or owner of jwc_properties.ini file are fixed.

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-3588

PeripheralNotAvailableException isn't thrown when opening an MMIO peripheral device that's already opened

Occasionally, opening an MMIO peripheral device that has already been opened will fail to throw a PeripheralNotAvailableException. MMIO has no native resources to be guarded, hence the opening of another instance of the peripheral device does not pose any security concerns.

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-3663

Can't set bit shifting ordering in SPI

A bug at the driver level prevents the programmer from setting the bit shifting in SPI peripherals to Peripheral.LITTLE_ENDIAN.

MERT-3676

Infinite log output when REPORT_LEVEL = 0

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

MERT-3677

MMIO: different exceptions when opening by config in different platforms

An attempt to create MMIO device outside the allowed range (in restricted area) on Keil/Raspberry throws a PeripheralConfigInvalidException. However, on the Windows platform, it throws an IOException. This happens because the Windows configuration doesn't have a restricted address table, but the implementation does an additional check of configuration and throws an IOException because the emulator returns an error for those particular memory regions.

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

Device Access API Spec: Description on ADCChannel.startAcquisition(...) if the count is zero

The DAAPI Spec 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.

MERT-3800

Device Access API Spec: Description on DACChannel.startGeneration(...) if the count is zero

The DAAPI Spec 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.

MERT-3806

AcquisitionEvent and Monitoring constructors do not throw any exceptions

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-3827

Using GPIO pins before performing any operation on UART, I2C, or SPI makes them unavailable.

It's possible to use the same physical pin for different roles (GPIO/I2C, GPIO/SPI, GPIO/UART). A kernel driver bug allows an implementation to choose this role only once without a driver restart. As a result, the device/pin can be opened in another role without any problems, but it does not work correctly. To avoid this, a PeripheralNotAvailable exception is thrown. After that, it's necessary to restart the board to have I2C, SPI, or UART peripherals available again.

MERT-3932

Incorrect exception thrown when incorrectly opening a UART port for a second time.

On the second attempt to open a UART port by a config which contains an unsupported databits value, the implementation will throw a PeripheralNotAvailableException instead of the correct exception, a PeripheralConfigInvalidException, which is what is thrown the first time.