OpenCPN Runs on Embedded ARM

[verkerkbr]

Now I have started with a clean sheet. I have set every item in the config.txt to off.

If I now start the system the monitor is not switched off. But again showing the colored square on the screen.

But simply moving the cursor then the correct desktop appears. This can be repeated.

No movement no desktop. Movement of the cursur desktop again. Tried this on an HDMI touchscreen.

Touch on the screen is the desktop for a short time.

Removing the USB GPS etc does not help.

Any idea what is going on here ? Using VNC then I don't have this problem.

It is not dependent on the type of monitor. The behaviour is the same.

Regards,


Bram

[Alisdair]

Originally Posted by verkerkbr

Now I have started with a clean sheet. I have set every item in the config.txt to off.

If I now start the system the monitor is not switched off. But again showing the colored square on the screen.

But simply moving the cursor then the correct desktop appears. This can be repeated.

No movement no desktop. Movement of the cursur desktop again. Tried this on an HDMI touchscreen.

Touch on the screen is the desktop for a short time.

Removing the USB GPS etc does not help.

Any idea what is going on here ? Using VNC then I don't have this problem.

It is not dependent on the type of monitor. The behaviour is the same.

Regards,


Bram

That's a different problem to the one you described earlier, and is the Raspberry Pi's way of telling you that it's not getting enough power.

[conachair]

Originally Posted by verkerkbr

Now I have started with a clean sheet. I have set every item in the config.txt to off.

If I now start the system the monitor is not switched off. But again showing the colored square on the screen.

But simply moving the cursor then the correct desktop appears. This can be repeated.

No movement no desktop. Movement of the cursur desktop again. Tried this on an HDMI touchscreen.

Touch on the screen is the desktop for a short time.

Removing the USB GPS etc does not help.

Any idea what is going on here ? Using VNC then I don't have this problem.

It is not dependent on the type of monitor. The behaviour is the same.

Regards,


Bram

That was exactly the same symptoms i had, rainbow screen , move the mouse & the desktop appears.

Apologies for the shakey one handed video work...
The multimeter is connected to the ground & 5v pins on the pi GPIO pins...

https://www.youtube.com/watch?v=MWbO...ature=youtu.be

[petter5]

Originally Posted by conachair

That was exactly the same symptoms i had, rainbow screen , move the mouse & the desktop appears.

Apologies for the shakey one handed video work...
The multimeter is connected to the ground & 5v pins on the pi GPIO pins...

The rainbow sign is a system alert built into newer versions of Raspberry to warn about insufficient power supply to the system witch can result in system instability and odd behaviour. Before doing any other measures, please use a sufficient power supply for the system. If using mains, the official Raspberry power supply is cheap, strong enough and of excellent quality:| +5V dc, 1 Output, Micro USB, 2A, 10W, Australia/China, European Plug, UK, US/Japan Official Raspberry Pi Power Supply |

I had similar problems with rainbow displayed on the display, after changing power supply to the above mentioned, the rainbow and problems was gone.

As can be seen from your multimeter, the voltage on your system is not sufficient. The reason for things working through VNC is that a VNC connection uses less power for GPU opereations and thereby stress your power requirements less.

[conachair]

Originally Posted by petter5

The rainbow sign is a system alert built into newer versions of Raspberry to warn about insufficient power supply to the system witch can result in system instability and odd behaviour. Before doing any other measures, please use a sufficient power supply for the system.

I know

Also, if the Pi is starting to struggle for power there will be a small rainbow square top right of the screen.
Not sure if this gets displayed with the new opengl driver enabled.

[verkerkbr]

I did not saw the difference between with or without OpenGL driver. And also removing the USB things like GPS mouse etc did not solve the problem.

Now I have used another loader and a very short usb cable.

And Alas ! It works without the rainbow screen appearing.

The conclusion seems to be that the working of the GPU chip needs more power for OpenGL then without.

Thanks for your help. You don't expect a problem by changing to another software driver.

Regards,


Bram

[petter5]

Originally Posted by conachair

I know

Also, if the Pi is starting to struggle for power there will be a small rainbow square top right of the screen.
Not sure if this gets displayed with the new opengl driver enabled.

The rainbow is implemented at hardware level and is completely independent of witch os loaded.

[Alisdair]

Originally Posted by verkerkbr

Now I have started with a clean sheet. I have set every item in the config.txt to off.

If I now start the system the monitor is not switched off. But again showing the colored square on the screen.

But simply moving the cursor then the correct desktop appears. This can be repeated.

No movement no desktop. Movement of the cursur desktop again. Tried this on an HDMI touchscreen.

Touch on the screen is the desktop for a short time.

Removing the USB GPS etc does not help.

Any idea what is going on here ? Using VNC then I don't have this problem.

It is not dependent on the type of monitor. The behaviour is the same.

Regards,


Bram

Originally Posted by verkerkbr

I did not saw the difference between with or without OpenGL driver. And also removing the USB things like GPS mouse etc did not solve the problem.

Now I have used another loader and a very short usb cable.

And Alas ! It works without the rainbow screen appearing.

The conclusion seems to be that the working of the GPU chip needs more power for OpenGL then without.

Thanks for your help. You don't expect a problem by changing to another software driver.

Regards,


Bram

Making the computer work harder has probably been enough to trip it.
You'd almost certainly experience the same without OpenGL if you overclocked it, or tried to run several applications concurrently.

Of course, maybe you just had a lossy USB cable and everything would be fine with your shorter cable.

[verkerkbr]

With a GPU setting of 180 it works without Problems. If I take a much higher value, then I have again the voltage problem back. Good to know for others with this voltage drop effect.

[deltasig]

Greetings,
I got an orange pi PC to just find out what one can do with that much "compute power"; I was very pleasantly surprised when I saw the results compared to the Rpi's B+ and 2B that I have. I installed a Lubuntu 15.04 with all the trappings from browsers to Kodi and of course, OpenCPN from the PPA. I had all the hardware acceleration set up and the video playing but the big O did not want to use the accelerated graphics! Other than that and the spooky sounding ship bells, everything worked fine and at a workable speed, from loading vector charts, creating and editing routes to tracking AIS and GPS.
I searched long and far to figure out what to do but I did not come up with anything useful to make it use the accelerated graphics.
I wonder if it is necessary to compile OpenCPN in my machine but then again I was not sure what libraries to use etc.
I hope I do not abuse the storage provided by showing some of the graphics performance figures of the OPi PC and what I get when I run O from the command line, which, oddly enough, is the same I get when I enter glxinfo. Please, contribute any thoughts; I'll be glad to answer questions. BTW the system was running some pretty demanding programs with graphics (stock market and portofolio tracking) and searching with pcmanFM (File Manager) when the benchmarks were run; impressive for $15 + 3.83 shipped

orangepi@OrangePI:~$ glmark2-es2
================================================== =====
glmark2 2011.09
================================================== =====
OpenGL Information
GL_VENDOR: ARM
GL_RENDERER: Mali-400 MP
GL_VERSION: OpenGL ES 2.0
================================================== =====
[build] use-vbo=false: FPS: 71
[build] use-vbo=true: FPS: 86
[texture] texture-filter=nearest: FPS: 91
[texture] texture-filter=linear: FPS: 85
[texture] texture-filter=mipmap: FPS: 111
[shading] shading=gouraud: FPS: 120
[shading] shading=blinn-phong-inf: FPS: 185
[shading] shading=phong: FPS: 135
[bump] bump-render=high-poly: FPS: 102
[bump] bump-render=normals: FPS: 272
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 124
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 67
[pulsar] light=false:quads=5:texture=false: FPS: 280
[desktop] blur-radius=5:effect=blurasses=1:separable=true:windo ws=4: FPS: 53
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 283
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 174
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 265
[function] fragment-complexity=low:fragment-steps=5: FPS: 208
[function] fragment-complexity=medium:fragment-steps=5: FPS: 137
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 142
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 79
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 79
================================================== =====
glmark2 Score: 143
================================================== =====

orangepi@OrangePI:~$ es2gears
EGL_VERSION = 1.4 Linux-r4p0-00rel0
vertex shader info:
fragment shader info:
info:
842 frames in 5.0 seconds = 168.299 FPS
768 frames in 5.0 seconds = 153.447 FPS
693 frames in 5.0 seconds = 138.462 FPS
869 frames in 5.0 seconds = 173.626 FPS
1018 frames in 5.0 seconds = 203.519 FPS
741 frames in 5.0 seconds = 148.022 FPS
1024 frames in 5.0 seconds = 204.636 FPS
739 frames in 5.0 seconds = 147.711 FPS
1086 frames in 5.0 seconds = 217.200 FPS
1075 frames in 5.0 seconds = 214.957 FPS
1097 frames in 5.0 seconds = 219.356 FPS
948 frames in 5.0 seconds = 189.297 FPS
888 frames in 5.0 seconds = 177.600 FPS
1053 frames in 5.0 seconds = 210.432 FPS
1098 frames in 5.0 seconds = 219.512 FPS
1015 frames in 5.0 seconds = 202.878 FPS
976 frames in 5.0 seconds = 195.044 FPS
1035 frames in 5.0 seconds = 206.876 FPS
1032 frames in 5.0 seconds = 206.194 FPS
892 frames in 5.0 seconds = 178.364 FPS
1012 frames in 5.0 seconds = 202.319 FPS
1034 frames in 5.0 seconds = 206.635 FPS
1023 frames in 5.0 seconds = 204.600 FPS
1071 frames in 5.0 seconds = 214.157 FPS
967 frames in 5.0 seconds = 193.400 FPS
996 frames in 5.0 seconds = 199.120 FPS

orangepi@OrangePI:~$ glxinfo
name of display: :0.0
MESA-LOADER: malformed or no PCI ID
libGL error: unable to load driver: mali_drm_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: mali_drm
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4

orangepi@OrangePI:~$ es2_info
EGL_VERSION: 1.4 Linux-r4p0-00rel0
EGL_VENDOR: ARM
EGL_EXTENSIONS:
EGL_KHR_image, EGL_KHR_image_base, EGL_KHR_image_pixmap,
EGL_KHR_gl_texture_2D_image, EGL_KHR_gl_texture_cubemap_image,
EGL_KHR_gl_renderbuffer_image, EGL_KHR_reusable_sync, EGL_KHR_fence_sync,
EGL_EXT_swap_buffers_with_damage, EGL_KHR_lock_surface,
EGL_KHR_lock_surface2, EGL_EXT_create_context_robustness,
EGL_ANDROID_blob_cache
EGL_CLIENT_APIS: OpenGL_ES
GL_VERSION: OpenGL ES 2.0
GL_RENDERER: Mali-400 MP
GL_EXTENSIONS:
GL_OES_texture_npot, GL_OES_compressed_ETC1_RGB8_texture,
GL_OES_standard_derivatives, GL_OES_EGL_image, GL_OES_depth24,
GL_ARM_rgba8, GL_ARM_mali_shader_binary, GL_OES_depth_texture,
GL_OES_packed_depth_stencil, GL_EXT_texture_format_BGRA8888,
GL_OES_vertex_half_float, GL_EXT_blend_minmax, GL_OES_EGL_image_external,
GL_OES_EGL_sync, GL_OES_rgb8_rgba8, GL_EXT_multisampled_render_to_texture,
GL_EXT_discard_framebuffer, GL_OES_get_program_binary,
GL_ARM_mali_program_binary, GL_EXT_shader_texture_lod, GL_EXT_robustness,
GL_OES_depth_texture_cube_map, GL_KHR_debug
[xcb] Unknown request in queue while appending request
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
Segmentation fault

orangepi@OrangePI:~$ opencpn
/usr/share/themes/Lubuntu-default/gtk-2.0/apps/thunar.rc:55: error: invalid string constant "thunar-statusbar", expected valid string constant
MESA-LOADER: malformed or no PCI ID
libGL error: unable to load driver: mali_drm_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: mali_drm
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.front
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround40
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround41
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround50
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround51
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started

[NahanniV]

Originally Posted by deltasig

Greetings,
I got an orange pi PC to just find out what one can do with that much "compute power"; I was very pleasantly surprised when I saw the results compared to the Rpi's B+ and 2B that I have. I installed a Lubuntu 15.04 with all the trappings from browsers to Kodi and of course, OpenCPN from the PPA. I had all the hardware acceleration set up and the video playing but the big O did not want to use the accelerated graphics! Other than that and the spooky sounding ship bells, everything worked fine and at a workable speed, from loading vector charts, creating and editing routes to tracking AIS and GPS.
I searched long and far to figure out what to do but I did not come up with anything useful to make it use the accelerated graphics.
I wonder if it is necessary to compile OpenCPN in my machine but then again I was not sure what libraries to use etc.
....

Not sure what the problem is, but I would try building from the latest source.

Follow these directions:
Compiling - Linux | Official OpenCPN Homepage

When you get to the cmake step: Check the log messages to be sure that OpenGLes is found.

I have a CubieTruck with the same GPU and it works with OpenGLes.
I do get a garbled screen on startup, but clicking on the chart clears that.

Let me know how it works for you.

Cheers,
JM.

[deltasig]

Thank you, JM

I include a section of the cmake output. How do I know if the "right" GL is going to be used?

-- *** Build Architecture is armhf
-- *** Staging to build opencpn 4.2.0 ***
-- *** Package will NOT include documentation ***
-- *** Package will NOT include GSHHS data ***
-- *** Package will NOT include tide and current data ***
-- Found OpenGL: /usr/lib/arm-linux-gnueabihf/libGL.so
-- Found OpenGL....
-- GL Lib: /usr/lib/arm-linux-gnueabihf/libGLU.so/usr/lib/arm-linux-gnueabihf/libGL.so
-- GL Include: /usr/include
-- Adding local GLU
-- Revised GL Lib: GLU_static/usr/lib/arm-linux-gnueabihf/libGL.so
-- Found wxWidgets: TRUE
-- Found wxWidgets...
-- wxWidgets Libraries: -L/usr/lib/arm-linux-gnueabihf;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_baseu_net-3.0;-lwx_baseu_xml-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu-3.0
-- Revised wxWidgets Libraries: -L/usr/lib/arm-linux-gnueabihf;-pthread;-lwx_gtk2u_gl-3.0;-lwx_baseu_net-3.0;-lwx_baseu_xml-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu-3.0
--
-- *** Staging to build opencpn ***
-- Build type: Release
-- *** Will install to /usr/local ***


Any idea about the audio related messages in my previous post?
I took care of the "thunar-statusbar" message; it appears only when one runs the lubuntu-default theme.
What do you use for display for your CubieTruck? I'm thinking to just use a "remote" tablet over x2go. Have you tried anything like that? Thank you.

[NahanniV]

Originally Posted by deltasig

Thank you, JM

I include a section of the cmake output. How do I know if the "right" GL is going to be used?

-- *** Build Architecture is armhf
-- *** Staging to build opencpn 4.2.0 ***
-- *** Package will NOT include documentation ***
-- *** Package will NOT include GSHHS data ***
-- *** Package will NOT include tide and current data ***
-- Found OpenGL: /usr/lib/arm-linux-gnueabihf/libGL.so
-- Found OpenGL....
-- GL Lib: /usr/lib/arm-linux-gnueabihf/libGLU.so/usr/lib/arm-linux-gnueabihf/libGL.so
-- GL Include: /usr/include
-- Adding local GLU
-- Revised GL Lib: GLU_static/usr/lib/arm-linux-gnueabihf/libGL.so
-- Found wxWidgets: TRUE
-- Found wxWidgets...
-- wxWidgets Libraries: -L/usr/lib/arm-linux-gnueabihf;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_baseu_net-3.0;-lwx_baseu_xml-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu-3.0
-- Revised wxWidgets Libraries: -L/usr/lib/arm-linux-gnueabihf;-pthread;-lwx_gtk2u_gl-3.0;-lwx_baseu_net-3.0;-lwx_baseu_xml-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu-3.0
--
-- *** Staging to build opencpn ***
-- Build type: Release
-- *** Will install to /usr/local ***


Any idea about the audio related messages in my previous post?
I took care of the "thunar-statusbar" message; it appears only when one runs the lubuntu-default theme.
What do you use for display for your CubieTruck? I'm thinking to just use a "remote" tablet over x2go. Have you tried anything like that? Thank you.

cmake is finding desktop OpenGL.
On your board, I think that would be either a software emulation or a translator like GLshim.

The first mention of Opengl in my cmake log is: -- Found OpenGLESv1
(there are also a couple of "Found OpenGL" messages later in the log for plugins)

Did you complete the rest of the steps in the build instructions ?
What happened ?
I think you should be able to configure OpenGL, but it may be slower instead of faster.

Can you post the OpenCPN log file once you have it configured and running: specifically the OpenGL entries.

I don't know anything about the sound problem. Is it still there with the new build ?

Cheers,
JM.

[NahanniV]

Originally Posted by deltasig

....
What do you use for display for your CubieTruck? I'm thinking to just use a "remote" tablet over x2go. Have you tried anything like that? Thank you.

I have a 1920*1080 24" LED LCD at my Nav station.
LG24M45
Works on 12v from batteries.
Draws 20W max, but 6W at minimum brightness, which is bright enough.

I have also used VNC to an IPAD and it worked OK, was usable, but with a little lag.

Cheers,
JM.

[deltasig]

JM, it's great to have you to bounce things off; thank you for your feedback.
I was looking at the CMakeLists.txt:

# Search for opengles, short of running a program to test the speed
# of acceleration, I simply use gles on "native linux" arm systems
IF (ARCH MATCHES "arm*" AND (NOT QT_ANDROID) )
find_path(OPENGLESv1_INCLUDE_DIR GLES/gl.h )
IF (OPENGLESv1_INCLUDE_DIR)
MESSAGE (STATUS "Found OpenGLESv1")
ADD_DEFINITIONS(-DocpnUSE_GLES)
ADD_DEFINITIONS(-DocpnUSE_GL)
ADD_DEFINITIONS(-DUSE_GLU_TESS)

SET(OPENGLES_FOUND "YES")
SET(OPENGL_FOUND "YES")

SET(wxWidgets_USE_LIBS ${wxWidgets_USE_LIBS} gl )
add_subdirectory(src/glshim)

add_subdirectory(src/glu)

SET(OPENGL_LIBRARIES "GL_static" "GLU_static" "EGL" "X11" "drm" "dri2" )
ENDIF()
ENDIF()

I see it is looking for OpenGLESv1 but I have v2 and the only places there is a GLES/gl.h is in
/home/orangepi/OpenCPN/src/glshim/include/GLES/gl.h and
/usr/include/khronos/GLES/gl.h

Here is khronos:
/usr/include/khronos/:
total 12
drwxrwxr-x 2 orangepi orangepi 4096 Dec 27 19:18 EGL
drwxrwxr-x 2 orangepi orangepi 4096 Dec 27 19:18 GLES
drwxrwxr-x 2 orangepi orangepi 4096 Dec 27 19:18 GLES2

/usr/include/khronos/EGL:
total 44
-rw-rw-r-- 1 orangepi orangepi 26187 Aug 5 2015 eglext.h
-rw-rw-r-- 1 orangepi orangepi 12353 Aug 5 2015 egl.h

/usr/include/khronos/GLES:
total 100
-rw-rw-r-- 1 orangepi orangepi 59377 Aug 5 2015 glext.h
-rw-rw-r-- 1 orangepi orangepi 34332 Aug 5 2015 gl.h
-rw-rw-r-- 1 orangepi orangepi 901 Aug 5 2015 glplatform.h

/usr/include/khronos/GLES2:
total 108
-rw-rw-r-- 1 orangepi orangepi 72782 Aug 5 2015 gl2ext.h
-rw-rw-r-- 1 orangepi orangepi 31871 Aug 5 2015 gl2.h
-rw-rw-r-- 1 orangepi orangepi 909 Aug 5 2015 gl2platform.h

Do you think I should change something in the CMakeLists.txt? I'm not very familiar with Cmake scripting but it doesn't look as if it's picking up what it needs, at least in my case.

The compile is at 50% after an hour, so I have a bit more to go before I see results.
BTW, with the ppa version of O, when I set OpenGL I was getting up to 6 FPS; the system was more responsive without it, though.

Nice screen!

Cheers
DS