Pololu Robotics & Electronics
Menu
My account Comments or questions? About Pololu Contact Ordering information Distributors

Installing MaestroControlCenter on Raspi2


#1

I have followed the directions in the readme file for linux installation “Maestro Servo Controller Linux Software (release 150116)”. Upon attempting to run the Controller software from the command line:

sudo /home/pi/Desktop/maestro-linux/MaestroControlCenter

… the MaestroControlCenter software fails to load. I’d like a workaround or to know what I’ve done wrong. Details: In the terminal the OS’s objections are:

(cli:2757): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-can-change-accels after class was initialised

(cli:2757): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-popup-delay after class was initialised

(cli:2757): GLib-GObject-WARNING **: Attempt to add property GtkSettings::gtk-menu-popdown-delay after class was initialised
* Assertion at mini-codegen.c:807, condition `i == sel' not met

Stacktrace:

  at <unknown> <0xffffffff>
  at System.Windows.Forms.TextBoxBase.Draw (System.Drawing.Graphics,System.Drawing.Rectangle) <0x000af>
  at System.Windows.Forms.TextBoxBase.OnPaintInternal (System.Windows.Forms.PaintEventArgs) <0x00063>
  at System.Windows.Forms.Control.WmPaint (System.Windows.Forms.Message&) <0x0017f>
  at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message&) <0x00223>
  at System.Windows.Forms.TextBoxBase.WndProc (System.Windows.Forms.Message&) <0x0031f>
  at System.Windows.Forms.TextBox.WndProc (System.Windows.Forms.Message&) <0x001db>
  at System.Windows.Forms.Control/ControlWindowTarget.OnMessage (System.Windows.Forms.Message&) <0x0002b>
  at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) <0x0003b>
  at System.Windows.Forms.NativeWindow.WndProc (intptr,System.Windows.Forms.Msg,intptr,intptr) <0x002a3>
  at System.Windows.Forms.XplatUIX11.DispatchMessage (System.Windows.Forms.MSG&) <0x00023>
  at System.Windows.Forms.XplatUI.DispatchMessage (System.Windows.Forms.MSG&) <0x0002f>
  at System.Windows.Forms.Application.RunLoop (bool,System.Windows.Forms.ApplicationContext) <0x00b5f>
  at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext) <0x00063>
  at System.Windows.Forms.Application.Run (System.Windows.Forms.Form) <0x00033>
  at Pololu.MaestroControlCenter.Program.Main () <0x0003f>
  at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:


Debug info from gdb:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0x731ff430 (LWP 2761)]
[New Thread 0x732ff430 (LWP 2760)]
[New Thread 0x75b7b430 (LWP 2759)]
0x76e95aac in waitpid () from /lib/arm-linux-gnueabihf/libpthread.so.0
  Id   Target Id         Frame 
  4    Thread 0x75b7b430 (LWP 2759) "cli" 0x76e93770 in sem_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
  3    Thread 0x732ff430 (LWP 2760) "cli" 0x76e91504 in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
  2    Thread 0x731ff430 (LWP 2761) "cli" 0x76e91504 in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
* 1    Thread 0x76f69000 (LWP 2757) "cli" 0x76e95aac in waitpid () from /lib/arm-linux-gnueabihf/libpthread.so.0

Thread 4 (Thread 0x75b7b430 (LWP 2759)):
#0  0x76e93770 in sem_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1  0x001fff10 in mono_sem_wait (sem=0x2f523c, alertable=1) at mono-semaphore.c:119
#2  0x0017db28 in finalizer_thread (unused=<optimized out>) at gc.c:1073
#3  0x001625b4 in start_wrapper_internal (data=0x878248) at threads.c:643
#4  start_wrapper (data=0x878248) at threads.c:688
#5  0x001f5c30 in thread_start_routine (args=0x833748) at wthreads.c:294
#6  0x00204268 in inner_start_thread (arg=0x83373c) at mono-threads-posix.c:49
#7  0x76e8cc00 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#8  0x76df9728 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
#9  0x76df9728 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0x732ff430 (LWP 2760)):
#0  0x76e91504 in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1  0x001dfa3c in _wapi_handle_timedwait_signal_handle (handle=0x415, timeout=0x0, alertable=1, poll=<optimized out>) at handles.c:1588
#2  0x001f2b5c in WaitForSingleObjectEx (handle=0x1f2b5c, timeout=3076096, alertable=1045) at wait.c:196
#3  0x00160344 in mono_wait_uninterrupted (thread=0x734dec10, multiple=3128840, numhandles=1, handles=0x732fea0c, waitall=0, ms=-1, alertable=1) at threads.c:1455
#4  0x00161ed4 in ves_icall_System_Threading_WaitHandle_WaitOne_internal (this=<optimized out>, handle=0x83cc14, ms=-1, exitContext=<optimized out>) at threads.c:1587
#5  0x73c0ff98 in ?? ()
#6  0x73c0ff98 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0x731ff430 (LWP 2761)):
#0  0x76e91504 in pthread_cond_wait@@GLIBC_2.4 () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1  0x001dfa3c in _wapi_handle_timedwait_signal_handle (handle=0x414, timeout=0x0, alertable=1, poll=<optimized out>) at handles.c:1588
#2  0x001f2b5c in WaitForSingleObjectEx (handle=0x1f2b5c, timeout=3076096, alertable=1044) at wait.c:196
#3  0x00160344 in mono_wait_uninterrupted (thread=0x734decc0, multiple=3128840, numhandles=1, handles=0x731fea0c, waitall=0, ms=-1, alertable=1) at threads.c:1455
#4  0x00161ed4 in ves_icall_System_Threading_WaitHandle_WaitOne_internal (this=<optimized out>, handle=0x83cc14, ms=-1, exitContext=<optimized out>) at threads.c:1587
#5  0x73c0ff98 in ?? ()
#6  0x73c0ff98 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x76f69000 (LWP 2757)):
#0  0x76e95aac in waitpid () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1  0x000b2148 in mono_handle_native_sigsegv (signal=<optimized out>, ctx=<optimized out>) at mini-exceptions.c:2299
#2  <signal handler called>
#3  0x76d5a8dc in raise () from /lib/arm-linux-gnueabihf/libc.so.6
#4  0x76d5e65c in abort () from /lib/arm-linux-gnueabihf/libc.so.6
#5  0x000136fc in ?? ()
Cannot access memory at address 0x0
#6  0x000136fc in ?? ()
Cannot access memory at address 0x0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

#2

Hello.

I added code tags ([ code ] [ /code ] without spaces) to your post to make it easier to read; please use this method to post code in the future.

Unfortunately, we do not support running the Maestro software on the Raspberry Pi. Please read the “Supported Operating Systems” section in the Maestro User’s Guide for more information about why ARM-based Linux machines are not supported.

Instead, you could use UscCmd (the command line utility that comes with the Maestro Control Center) to control your Maestro from your Raspberry Pi. To see a description of the commands for UscCmd, type usccmd with nothing else at the command line. To get a better understanding of how UscCmd works, you can see its C# source code in the Pololu USB Software Development Kit.

Alternatively, you could write your own code or use an example code from the “Related Resources” section of the user’s guide to control your Maestro from your Raspberry Pi.

- Amanda


Maestro Control Center gives error on Raspberry PI 2