Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Error run listMidlets.sh

[email protected] ~ $ sudo sh javame8.2/bin/listMidlets.sh
Java is starting. Press Ctrl-C to exit
Frame buffer device detected: BCM2708
Frame buffer '/dev/fb0' detected: 592x448, depth=16
Failed to open /dev/input/by-id
[ERROR] [LCD] iso=-1:javacall_init_frame_buffer: failed to init keyboards
[CRITICAL] [PROXY] iso=-1:Can't create server
can not connect to device manager
[ERROR] [AMS] iso=0:The MIDlet suite could not be run.
How fix?
Answers
-
I have the same problem. This is undocumented :-(
You have to kill the runMidlet process that is running at startup. But wait! A better solution is to connect via AMS. The AMS client is already running on the board.
Connect to the board via the proxy with
> java -jar Proxy.jar -socket <ip of board>
on the PC (host). Then connect with putty to the proxy using localhost and port 65002. Now you are connected to the AMS of the board. Then type
>>> ams-list
If you can't connect via the proxy then the board is probably connected via Device Connections Manager. Disconnect the device from the Device Connections Manager. See the task bar icon in at the right corner. Try again.