1. Support
  2. OpenICE
  3. Bugs
0

Beaglebone Element14 error message when starting OpenICE 0.6.2

Alistair MacDonald 10 years ago in OpenICE • updated by Jeff Peterson 10 years ago • 4
Hello. I've been trying to follow the directions for the device-adaptor but running into some glitches.
#1) I'm using the Beaglebone Element14 Black revision C - following the flashing directions for disk image C, it installs version 0.6.2. I noticed that the serial RS232 port is ttyO2 instead of ttyO1, but before I even get to that point, I try to start the software and get this message: (note, the adaptor setup directions say to type OpenICE-0.6.3/bin/OpenICE but the only directory is OpenICE 0.6.2). Here's the copied error message - is there something I'm missing? Sorry, I'm not a developer.

debian@beaglebone:~$ OpenICE-0.6.2/bin/OpenICE

Graphics Device initialization failed for : es2, sw

Error initializing QuantumRenderer: no suitable pipeline found

java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found

at com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:280)

at com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:227)

at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:173)

at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:209)

at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675)

at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:695)

at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$152(LauncherImpl.java:182)

at com.sun.javafx.application.LauncherImpl$$Lambda$2/4940284.run(Unknown Source)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found

at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:94)

at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:124)

... 1 more

Exception in thread "main" java.lang.RuntimeException: No toolkit found

at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:185)

at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:209)

at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675)

at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:695)

at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$152(LauncherImpl.java:182)

at com.sun.javafx.application.LauncherImpl$$Lambda$2/4940284.run(Unknown Source)

at java.lang.Thread.run(Thread.java:745)

debian@beaglebone:~$

Under review
Jeff Peterson 10 years ago
Hi Alistair,

Unfortunately, Oracle removed support for JavaFX on ARM devices. This means that the OpenICE Supervisor will not build or run on the Beaglebone platform anymore. Due to resource constraints (and to the fact we JUST rebuilt the GUI with JavaFX), we have chosen to say that the Supervisor is not compatible with ARM anymore. Although it is foreseeable that someone may want to run both a Device-Adapter and Supervisor on one beaglebone device, we envision a future where the Supervisor apps are doing complex computations that exceed the capabilities of an ARM beaglebone.

If you would like to run the device-adapter and supervisor on one board, I would suggest investigating a small x86 system like the Intel NUC. If running the Supervisor in a centralized location is not a problem, run the Device-Adapter on an ARM device and the Supervisor on a laptop/desktop/server.

Here is a nice link that about sums up the situation: https://www.linkedin.com/pulse/oracle-just-removed-javafx-support-arm-jan-snelders

Thanks,
Jeff
Alistair MacDonald 10 years ago
Hi Jeff-

Thanks for the reply. I'm actually only trying to run the Device-Adapter, not the Supervisor program. Following the Device-Adapter Beaglebone Setup instructions on OpenICE, at the bottom of the first page it says:

Your new device-adapter is ready to use. You can start the software with OpenICE-0.6.3/bin/OpenICE from the home directory. Check out the next page for more instructions.

This was where I ran into the big error message. Does the device-adaptor work without this command? The supervisor program on my computer recognizes the Beaglebone on the local network - initially with clock and exclamation point which disappear once the modem is on an active network/NTP. But I'm not able to get any vital sign data at all from the RJ45 port (outgoing) of a Philips Intellivue MP70 (version K) because I get stuck at a "Negotiating - requesting association connection." I'll paste a screenshot so you can see. I've stopped and started the service with the terminal sudo commands, but can't seem to get beyond this point. I've tried different machines - including MX800s and different ports (LAN) to no avail. Any help would be greatly appreciated!!








Alistair MacDonald 10 years ago
I think I just realized where the problem is - I've been using the Cisco RJ45 to DB9 cable and not the modular adapter. Just ordered the adapter from Amazon. Hoping this will get me past my 'negotiating - requesting association' spot.
Jeff Peterson 10 years ago
Hi Alistair,

Hopefully the pinout was the problem and the new adapter fixes it.

Check out this topic for clarification on the pinout:
http://community.openice.info/topic/730165-philips-rj45-port-wiring/http://community.openice.info/topic/730165-philips-rj45-port-wiring/

Other community members have had issues with Philips pinout before. If for some reason the standard pinout doesn't work, people have had success with the MP5 pinout:
For the MP70/MX800, you need (DB9 -> RJ45):
2 ->5
3 ->7
5-> 4

For the MP5, you need (DB9 -> RJ45):
2 ->7
3 ->5
5-> 4

Let me know if you fix your issue. Thanks,
Jeff

Customer support service by UserEcho