2 Installing and Running Applications on the STM32429I-EVAL Board

Installing the Oracle Java ME SDK 8.1

Before developing for the ST Micro STM32429I-EVAL board, a modified version of the Oracle Java ME SDK 8.1 must be installed in two steps.

1. Install the Oracle Java ME SDK 8.1 distribution.

2. Install the Oracle Java ME STM Update Package version 8.1 using the Update Manager application of the Oracle Java ME SDK 8.1. You must install this update or the Java ME SDK tools will not be able to communicate with the ST Micro STM32429I-EVAL board using either a TCP/IP or serial connection.

Connecting to the ST Micro STM32429I-EVAL Embedded Board

There are two different ways to connect to the STM32429I-EVAL board.

1. Run NetBeans IDE 8.0.2, which will use the Oracle Java ME SDK. If you wish to use the NetBeans IDE, skip to the Using NetBeans with the STM32429I-EVAL Board below.

2. Manually start a Developer Agent program on the desktop host and run commands using the Application Management System (AMS) CLI.

The Developer Agent program is a JAR file inside the util directory of the Oracle Java ME Embedded distribution, and is named proxy.jar. You can start the Developer Agent program on the desktop host computer either in a server or a client mode. After the Developer Agent program starts, you can use the AMS CLI to communicate with the board.

Running IMlets on STM32429I-EVAL Using the AMS CLI

The next step is to make a raw connection to the AMS CLI. Note, however, you must first run the Developer Agent program on the desktop host and the Java runtime on the board as described above, unless the Developer Agent was started automatically by Java ME SDK Device Manager.

At this point, you can start a PuTTY executable file on your desktop computer. Use this to create Raw socket connections to the IP address of the host running the Developer Agent (typically localhost), and port 65002. For example, a connection to localhost and the port 65002 is shown in Figure 2-1. Be sure that the socket connection type is set to Raw and not SSH.

Figure 2-1 Using PuTTY to Connect to the Command-Line Interface

Description of "Figure 2-1 Using PuTTY to Connect to the Command-Line Interface"

The window from port 65002 provides a CLI as shown in Figure 2-2.

Figure 2-2 Command-Line Interface to STM32429I-EVAL

Description of "Figure 2-2 Command-Line Interface to STM32429I-EVAL"

You can use the command-line interface to run the AMS commands shown in Table 2-1. For a complete list of CLI commands, see the Oracle Java ME Embedded Developer's Guide at https://docs.oracle.com/javame/8.1/me-dev-guide/agentconsole.htm#sthref26

Here is a typical example of using the AMS to install, list, run, and remove an Oracle Java ME Embedded application on the board:

192.168.1.12:2201>> ams-install file:///C:/some/directory/hello.jar hostdownload
<<ams-install,start install,file:///C:/some/directory/hello.jar
<<ams-install,install status: stage DONE, 0%
<<ams-install,install status: stage DONE, 100%
<<ams-install,OK,Install success

192.168.1.12:2201>> ams-install http://www.example.com/netdemo.jar hostdownload
<<ams-install,start install,http://www.example.com/netdemo.jar
<<ams-install,install status: stage DONE, 0%
<<ams-install,install status: stage DONE, 100%
<<ams-install,OK,Install success

192.168.1.12:2201>> ams-install http://www.example.com/notthere.jar hostdownload
<<ams-install,start install,http://www.example.com/notthere.jar
<<ams-install,install status: stage DONE, 100%
<<ams-install,FAIL,errorCode=JAR_NOT_FOUND, Invalid JAD Exception, reason: 20 (JAR_NOT_FOUND), message: Reason = 20, extra data: http://www.example.com/notthere.jar

Note that the final installation example failed with an error code and matching description.

Similarly, install an additional IMlet: rs232dem. After an IMlet is installed, verify it using the ams-list command. Each IMlet has been assigned a number by the AMS for convenience.

192.168.1.12:2201>> ams-list
<<ams-list,0.hello|Oracle,STOPPED
<<ams-list,1.netdemo|Oracle,STOPPED
<<ams-list,2.rs232dem|Oracle,RUNNING
<<ams-list,OK,3 suites are installed

You can use the ams-remove command to remove any installed IMlet.

192.168.1.12:2201>> ams-remove 0
<<ams-remove,OK,removed

The results can again be verified with the ams-list command.

192.168.1.12:2201>> ams-list
<<ams-list,1.netdemo|Oracle,STOPPED
<<ams-list,2.rs232dem|Oracle,RUNNING
<<ams-list,OK,2 suites are installed

Finally, start the IMlet using the ams-run command. The application can be terminated with the ams-stop command.

192.168.1.12:2201>> ams-run 1
<<ams-run,OK,started

192.168.1.12:2201>> ams-list
<<ams-list,1.netdemo|Oracle,RUNNING
<<ams-list,2.rs232dem|Oracle,RUNNING
<<ams-list,OK,2 suites are installed

You can use the commands summarized in Table 2-2 to modify system properties.

File system commands are summarized in Table 2-3. Note that the system can only access files inside of the /java/appdb directory, and cannot use relative paths that shift the current location outside of this directory (for example, using ".." in the path).

Network commands are shown in Table 2-4.

The CLI supports working with multiple devices. You can use the device commands summarized in Table 2-5.

You can use the keystore commands summarized in Table 2-6.

Using NetBeans with the STM32429I-EVAL Board

Running and debugging IMlet projects on the ST Micro STM32429I-EVAL board using the NetBeans IDE 8.0.2 requires the following software:

• NetBeans IDE 8.0.2

• Oracle Java ME SDK 8.1 with STM32429I-EVAL Update

• Oracle Java ME SDK 8.1 plugins for NetBeans

To install the Java ME SDK 8.1 toolkit in NetBeans 8.0.2, follow these instructions:

1. Select Tools->Plugins, and raise the Plugins dialog. Select the Installed tab, and activate the Java ME plugin.

2. Extract the Java ME NetBeans plugins from the ZIP file, placing them in their own directory.

3. Select the Downloaded tab in the Plugins dialog, and press the Add Plugins... button. Browse to the directory containing the NetBeans Java ME plugins, and select all the files with a .nbm extension, press the Open button to choose them, then press the Install button to install each of the plugins. You can safely ignore any warnings about the updates not being digitally signed. After the plugins are installed, restart the IDE.

Adding the STM32429I-EVAL Board to the Device Connection Manager

Follow these steps to add the STM32429I-EVAL board to the Device Connections Manager in Oracle Java ME SDK 8.1:

1. Ensure that the Developer Agent program is not running on the desktop computer.

2. Start the Oracle Java ME SDK 8.1 Device Connections Manager (located at <SDK Installation Folder>/bin/device-manager.exe) and click its Device Manager icon in the taskbar. A Device Connections Manager window is shown in Figure 2-3.

   Figure 2-3 Device Connections Manager Window

   
   Description of "Figure 2-3 Device Connections Manager Window"
   
   

3. Click the Add button, ensure that the IP Address or Host Name list contains the correct IP address of the ST Micro STM32429I-EVAL board, and click OK. You can verify the current IP address of the board by checking the touchscreen on the STM32429I-EVAL embedded board.

4. After the STM32429I-EVAL board is registered, its IP address is listed on the Device Connections Manager list and its status is Connected as shown in Figure 2-4.

   Figure 2-4 Device Connections Manager Window with STM32429I-EVAL Connected

   
   Description of "Figure 2-4 Device Connections Manager Window with STM32429I-EVAL Connected"
   
   

Assigning the STM32429I-EVAL Board to Your Project

There are two ways to assign the STM32429I-EVAL board to your project:

• Using an existing NetBeans Project with an IMlet you want to run or debug.

• Creating a new NetBeans project.

After you assign the board to your project, clicking Run Project in the NetBeans IDE runs your IMlets on the board instead of on the emulator.

package gpioexample1;
 
import java.io.IOException;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.microedition.midlet.MIDlet;
import jdk.dio.DeviceManager;
import jdk.dio.gpio.GPIOPin;
 
public class GPIOExample1 extends MIDlet {
 
    GPIOPin pin1;
    GPIOPin pin2;
    GPIOPin pin3;
    GPIOPin pin4;
 
    @Override
    public void startApp() {
 
        try {
 
            pin1 = (GPIOPin) DeviceManager.open(1);
            pin2 = (GPIOPin) DeviceManager.open(2);
            pin3 = (GPIOPin) DeviceManager.open(3);
            pin4 = (GPIOPin) DeviceManager.open(4);
 
            for (int i = 0; i < 20; i++) {
                System.out.println("Setting pins to true...");
                pin1.setValue(true);
                pin2.setValue(true);
                pin3.setValue(true);
                pin4.setValue(true);
                Thread.sleep(2000);
                System.out.println("Setting pins to false...");
                pin1.setValue(false);
                pin2.setValue(false);
                pin3.setValue(false);
                pin4.setValue(false);
                Thread.sleep(2000);
            }
        } catch (IOException | InterruptedException ex) {
       Logger.getLogger(GPIOExample1.class.getName()).log(Level.SEVERE, null, ex);
        }
    }
 
    @Override
    public void pauseApp() {
    }
 
    @Override
    public void destroyApp(boolean unconditional) {
    }
}

Accessing Peripherals

Applications such as the previous example that require access to Device I/O APIs must request the appropriate permissions. For more information about the various permissions required to access the Device I/O APIs, see the Device I/O API 1.0 specification at:

http://docs.oracle.com/javame/8.0/api/dio/api/index.html