Skip to Main Content

Embedded Technologies

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

STM32f4 Discovery - Midlet is not installed

Michael KrollFeb 6 2014

Hello all,

I finally installed all necessary components to run a MIDlet on the StM32f4 Discovery board.

All installation steps were so far successful. I downloaded the latest netbeans version with the ME plugins installed and created the simple MIDlet as described in the documentation:

package me8embeddedapplication1;

import com.oracle.deviceaccess.PeripheralManager;

import com.oracle.deviceaccess.gpio.GPIOPin;

import java.io.IOException;

import java.util.logging.Level;

import java.util.logging.Logger;

import javax.microedition.midlet.MIDlet;

/**

* @author michaelkroll

*/

public class Midlet extends MIDlet {

    @Override

    public void startApp() {

        try {

            GPIOPin pin = (GPIOPin) PeripheralManager.open(1);

            for (int i = 0; i < 10; i++) {

                pin.setValue(true);

                Thread.sleep(1000);

                pin.setValue(false);

                Thread.sleep(1000);

            }

           

            pin.close();

        }

        catch (IOException ioe) {

            Logger.getLogger(Midlet.class.getName()).log(Level.SEVERE, null, ioe);

        } catch (InterruptedException ex) {

            Logger.getLogger(Midlet.class.getName()).log(Level.SEVERE, null, ex);

        }

    }

   

    @Override

    public void pauseApp() {

    }

   

    @Override

    public void destroyApp(boolean unconditional) {

    }

}

When I now try to install and run the MIDlet in the real board, I'm getting the following build failed message:

Copying 1 file to C:\Users\michaelkroll\Documents\NetBeansProjects\ME8EmbeddedApplication1\dist\nbrun4556380608097918760

Copying 1 file to C:\Users\michaelkroll\Documents\NetBeansProjects\ME8EmbeddedApplication1\dist\nbrun4556380608097918760

Jad URL for OTA execution: http://localhost:8082/servlet/org.netbeans.modules.mobility.project.jam.JAMServlet/C%3A/Users/michaelkroll/Documents/NetBeansProjects/ME8EmbeddedApplication1/dist//ME8EmbeddedApplication1.jad

Starting emulator in execution mode

Feb 07, 2014 12:05:40 AM RMIConnector RMIClientCommunicatorAdmin-doStop

WARNING: Failed to call the method close():java.rmi.ConnectException: Connection refused to host: 192.168.125.2; nested exception is:

  java.net.ConnectException: Connection refused: connect

C:\Users\michaelkroll\Documents\NetBeansProjects\ME8EmbeddedApplication1\nbproject\build-impl.xml:791: Execution failed with error code 1.

BUILD FAILED (total time: 1 minute 11 seconds)

I'm running the proxy and established the dial in connection. The TCP logging seems not to work yet, but I can connect to the CLI and can execute ams commands.

When I call ams-list, I'm getting the following message:

ams-list,FAIL, device is not connected.

So it seems there there is one or more pieces in the puzzle not yet working.

Any hint which one ?

When will oracle provide another ea version or even a beta?

Thank you very much in advance for your help,

Michael.

Comments

vladodias

Hi mate,

I'm assuming the value of "http://host:port/tokens" is not in your configuration, i.e. it is purposely edited in the post for information security reasons... otherwise the problem is probably there...

That said, note that OAuth 2.0 is a complete rewrite of OAuth 1.0 from the ground up, sharing only overall goals and general user experience. OAuth 2.0 is not backwards compatible with OAuth 1.0 or 1.1, and should be thought of as a completely new protocol.

Now, OWSM supports single-user OAuth use case, which requires providing partial support of OAuth 1.0 protocol in OWSM to use OAuth1 type of access token and token secret to secure the request to an API. OWSM provides new OAuth1 client policy which allows applications to use Twitter API using the statically generated consumer and access tokens. Retrieval of access token is not done by OWSM policy.

Oracle A-Team blog entry is for OAuth2 and I don't think it will work for your case... You should follow the link below...

10.8.1 About OWSM Integration with Twitter OAuth server

https://docs.oracle.com/middleware/12213/owsm/security/GUID-13F43DB4-C837-42C2-B6C5-6D6E07266415.htm#GUID-04F6A9C8-3EEC-…

Cheers,

Vlad

User_9VIX3

Vlad,

We are on version 12.2.1.0.0 and do not see any OWSM policy supporting OAuth1.0

Is there a patch we need to apply for this policy to be visible

Appreciate your help in advance.

Thank you,

Deepti

vladodias

Hi Deepti,

I can see it on my JDev 12.2.1.3... I'm unaware of any specific patch just to add the policy...

You might have to follow all the steps to upgrade to 12.2.1.3... see note below...

https://docs.oracle.com/en/middleware/lifecycle/12.2.1.3/fupss/upgrading-soa-suite-12c-bam-previous-12c-release.html#GUI…

Note:

If you are upgrading from a previous 12c release (12.1.3.0, 12.2.1.0, or 12.2.1.1), you must complete all of these tasks to upgrade to 12c (12.2.1.3.0) . Do not attempt to update the existing domain by installing the 12.2.1.3.0 distributions into the same Oracle home. Moving the domain to 12.2.1.3.0 is not a patch set installation.

pastedImage_0.png

Cheers,

Vlad

1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Mar 6 2014
Added on Feb 6 2014
0 comments
917 views