• Introduction

• What’s Supported in This Release

• Usage Notes

• Installation and Runtime Security Guidelines

• Known Bugs

• Product Documentation

The Oracle Java ME Embedded release 8.3 software for the STM32429I-EVAL platform is a ready-to-run binary for use with STM32F4 MCU family, not only an ST Micro STM32429I-EVAL board. See the Usage Notes for more details.

The Oracle Java ME Embedded software uses an optimized platform stack for small embedded devices, which includes the Connected Limited Device Configuration (CLDC) HotSpot Implementation (Java Virtual Machine) version 8, the Micro Edition Embedded Profile (MEEP) application environment, the Generic Connection Framework (GCF) API, and enhanced support for various Java Specification Requests (JSRs).

The Oracle Java ME Embedded software for the reference board platform includes an CLDC implementation with a high-performance Java Virtual Machine that can run IMlets and access input/output ports. This runtime is optimized for the reference board platform.

Getting Started Guide for the Reference Platform (STM32429I-EVAL) describes how to install the Oracle Java ME Embedded distribution on the SD card, how to connect to the board from the development host computer, and how to install, run, and debug IMlets on the board.

Note the following important information before running the Oracle Java ME Embedded software on the STM32429I-EVAL board:

• Network interfaces and access points are only minimally supported. There is only one network interface (type: "WIRED"; name: "Ethernet_Interface"), and there is no way to create, modify, or delete access points. Doing so will throw an IOException. Also, there is only one system access point (network interface type: "WIRED"; name: "System_ethernet"), which is connected automatically. Any attempt to explicitly connect or disconnect to this access point will throw an IOException.

• The following GCF protocols are supported on the platform: datagram, TCP/IP client socket, TCP/IP server socket, and HTTP. The following protocol schemes can be used: "datagram://", "socket://" (client and server), "ssl://" (client only), "http://", "https://". The socket timeout option is not supported because of platform limitations.

• This platform implementation supports HTTPS and TLSv1.2 client cryptographic connections only. The connection options "Protocol" and "CipherSuite" are supported. However, "Certificate" is not supported, as there is no client authentication. The TLSv1.2 protocol supports the following cipher suites:

  • TLS_RSA_EXPORT_WITH_RC4_40_MD5

  • TLS_RSA_WITH_RC4_128_MD5

  • TLS_RSA_WITH_RC4_128_SHA

• Instances of CommConnection, ModemConnection, any multicasting, and IPv6 addressing is not supported.

• Only the PowerStateEvent.POWER_STATE_OFF and PowerStateEvent.POWER_STATE_FULL_POWER states are supported in this implementation. Using the PowerManager.setPowerState() method with any other value will throw an ILLEGAL_STATE_TRANSITION_REQUEST exception.

• The only root directory visible to the IMlet user is /root, which is mapped to the SD card as /java/appdb/root. Therefore, the user's accessible directories are /root/user and /root/tmp.

• The file system (FS) must be based on FAT (FAT12, FAT16, FAT32).

• The correct path separator for the file system is the forward slash (/).

• The maximum number of open files is four (4).

• Timestamps are constrained by the DOS epoch (Jan 1, 1980 - Dec 31, 2107). In addition, only creation and modification of timestamps are supported.

• The javax.microedition.cellular package, javax.microedition.key package, and the javax.microedition.media package are not supported.

• To connect the board to the SDK, additional files for the proxy are needed. These files are available via the SDK Update Center.

• Math/crypto hardware acceleration is not supported.

The Oracle Java ME Embedded release 8.3 software installation requires an execution model that ensures certain networked resources available. These required resources might include, but are not limited to, a variety of communication capabilities between the product's installed components.

It is important to note that the product's installation and runtime system is fundamentally a developer system that is not specifically designed to guard against malicious attacks from outside intruders. Given this, the product's architecture can present an insecure operating environment to the installation file system and its runtime environment, during execution. For this reason, it is critically important to observe the precautions outlined in the following security guidelines when installing and running the software.

To maintain optimum network security, the software package can be installed and run in a closed network operating environment; the software system that is not connected directly to the Internet or to a company intranet environment that could introduce unwanted exposure to malicious intrusion. This is the ideal secure operating environment whenever the application under development does not require an Internet connection.

When the application under development requires an Internet connection, you must conform to the guidelines highlighted in Protecting Operating Environment From Malicious Intrusion.