Beta Draft: 2016-04-19
Reference Platform Release Notes (STM 32F746GDISCOVERY)
Release 8.3 Developer Preview
It contains the following sections:
The Oracle Java ME Embedded release 8.3 software for the STM 32F746GDISCOVERY platform is a ready-to-run binary for use with an ST Micro 32F746GDISCOVERY 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 following features are included in the Oracle Java ME Embedded 8.3 software:
ARM RTX OS (CMSIS-RTOS)
CLDC 8 (JSR-360) (full CLDC) including SVM support
Generic Connection Framework (GCF) 8
TCP/IP client socket (
TCP/IP server socket (
Secure client socket (
Java ME Embedded Profile (MEEP) 8:
Minimal Profile Set
Device I/O API 1.1, which provide enhanced device controls and improved input/output (I/O) for small embedded devices:
General-purpose input/output (GPIO)
Analog-to-digital converter (ADC)
Inter-Integrated Circuit (I2C)
Serial Peripheral Interface (SPI)
Universal Asynchronous Receiver/Transmitter (UART)
System Configuration API
Output/logging through USB/serial
Flash file system on an SD Card
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 (32F746GDISCOVERY) 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 STM 32F746GDISCOVERY board:
JIT compilation is not supported.
No root certificates are included by default.
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: "
socket://" (client and server), "
ssl://" (client only), "
https://". The socket timeout option is not supported because of platform limitations.
This platform implementation supports HTTPS and TLSv1.0 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.0 protocol supports the following cipher suites:
ModemConnection, any multicasting, and IPv6 addressing is not supported.
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
The file system (FS) must be based on FAT32 and supports only short (8.3 format) filenames.
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.
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.
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.
The security-related functionality of a final developed application for release into the field is supported by the available components of the Oracle Java ME Embedded software stack incorporated by the developer into the application. The security precautions required by applications in the field are beyond the scope of these recommendations, but must be observed by the application developer.
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.
If the operating environment is open to network access, you must observe the following precautions to protect valuable resources from malicious intrusion:
Locate the development environment behind a secure firewall that strictly limits unauthorized network access to its file system and services. Limit access privileges to those that are required for development while allowing all the bidirectional local network communications that are necessary for the application's functionality. The firewall configuration must support these requirements to run the software while also addressing them from a security standpoint.
Follow the principle of least privilege by assigning the minimum set of system access permissions required for installation and execution of the software.
Do not store any sensitive information on the same file system that hosts the installation.
Ensure that the operating system patches are up-to-date on host machines in the development environment.
The Oracle Java ME Embedded software distribution bundle contains security certificates that are needed for testing during development of products for final release to customers. Some of these certificates are self-signed security certificates generated by Oracle that are mapped to privileged security domains. IMlets or MIDlets signed by these certificates get high privileges to access restricted APIs; these certificates present a security vulnerability if they are released to end users on a customer's device. Other certificates issued by universally recognized certificate authorities (CAs) are used only for signature verification and they do not present a vulnerability.
After final testing of the product is completed and the product is being prepared for release to end users, you must remove self-signed security certificates that present a security vulnerability.
The CLI is incorporated in the Developer Agent, which communicates with a device through an unsecured protocol. The Developer Agent is a Java SE application that can be reverse engineered to tamper with or to get information about the communication protocol, which might be used by an untrusted entity to manipulate the device. If you decide to implement the Developer Agent in a product deployment, it is your responsibility to incorporate adequate security measures around the Developer Agent communication channel. This channel uses TCP port 2201 on the Raspberry Pi device for the communication.
For generic bugs in this release of the Oracle Java ME SDK that might affect the STM 32F746GDISCOVERYplatform, see Oracle Java ME Software Development Kit Release Notes.
The following are known bugs in this release of the Oracle Java ME Embedded software:
The Java ME Embedded runtime doesn’t throw the
UnsupportedOperationException from the following calls:
This issue affects the following DIO VTS 1.1 tests:
An attempt to open an SPI device with an unsupported clock frequency does not throw the
DeviceManager.open(SPIDeviceConfig cfg), where
cfg.getClockFrequency() is not supported, tries to set an “adjusted” clock frequency in the range of MIN-MAX values.
The following documentation is included with this release of the Oracle Java ME Embedded software. See
All (this document)
Reference Platform Release Notes (STM 32F746GDISCOVERY)
Demonstrates how to install, run, and troubleshoot the Oracle Java ME Embedded software on the Raspberry Pi platform.
Getting Started Guide for the Reference Platform (STM 32F746GDISCOVERY)
Oracle® Java ME Embedded Reference Platform Release Notes (STM 32F746GDISCOVERY), Release 8.3 Developer Preview
Copyright © 2016, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.