Asked
Resolved Resolved by ptp!

Arcpi / Ezbpi On Raspberry Pi 3 Errors

Hello,

I am trying to run ARCPi and EZBPi on a Raspberry Pi 3. I have tried installing them on two different versions of Raspbian, the latest release and the 11/13/18 (stretch) version, which was released closer to "DJ's 9th Live Hack" (I have been following that YouTube tutorial). When I execute ARCPi, I get the following error before ARC launches:


pi@raspberrypi:~/EZ-BuilderPi $ mono ARC.exe
Unknown heap type: #GUlD

Unknown heap type: #Blop

Unknown heap type: #GUlD

Unknown heap type: #Blop

The help viewer could not load. Maybe you don't have chmsee installed or haven't set MONO_HELP_VIEWER. The specific error message was: ApplicationName='chmsee', CommandLine='"https://synthiam.com/Software";', CurrentDirectory='', Native error= Cannot find the specified file
X11 Error encountered: 
  Error: BadMatch (invalid parameter attributes)
  Request:     12 (0)
  Resource ID: 0x1C013B8
  Serial:      48245
  Hwnd:        Hwnd, Mapped:True ClientWindow:0x1C013B9, WholeWindow:0x1C013B8, Zombie=False, Parent:[Hwnd, Mapped:True ClientWindow:0x1C013B7, WholeWindow:0x1C013B6, Zombie=False, Parent:[]]
  Control:     System.Windows.Forms.Panel, BorderStyle: None  at System.Environment.get_StackTrace () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0 
  at System.Windows.Forms.XplatUIX11.HandleError (System.IntPtr display, System.Windows.Forms.XErrorEvent& error_event) [0x00000] in :0 
  at System.Drawing.GDIPlus.GdipCreateFromXDrawable_linux (System.IntPtr , System.IntPtr , System.IntPtr& ) [0x00000] in <1917aa1c39d94b1a91807b8cd9f03350>:0 
  at System.Drawing.Graphics.FromXDrawable (System.IntPtr drawable, System.IntPtr display) [0x00000] in <1917aa1c39d94b1a91807b8cd9f03350>:0 
  at System.Drawing.Graphics.FromHwnd (System.IntPtr hwnd) [0x00000] in <1917aa1c39d94b1a91807b8cd9f03350>:0 
  at System.Windows.Forms.Control.CreateGraphics () [0x00000] in :0 
  at System.Windows.Forms.TextBoxBase.CreateGraphicsInternal () [0x00000] in :0 
  at System.Windows.Forms.Document.owner_VisibleChanged (System.Object sender, System.EventArgs e) [0x00000] in :0 
  at System.Windows.Forms.Control.OnVisibleChanged (System.EventArgs e) [0x00000] in :0 
  at System.Windows.Forms.Control.OnParentVisibleChanged (System.EventArgs e) [0x00000] in :0 

Once ARC launches, if I try to open a previously saved project, a window pops up with a similar message:

Version: 2019.05.08.00

System.IO.DirectoryNotFoundException: Directory 'EZ-Builder/Examples' not found.
  at System.IO.Directory.ValidateDirectoryListing (System.String path, System.String searchPattern, System.Boolean& stop) [0x00091] in <8f2c484307284b51944a1a13a14c0266>:0 
  at System.IO.Directory.GetFileSystemEntries (System.String path, System.String searchPattern, System.IO.FileAttributes mask, System.IO.FileAttributes attrs) [0x00023] in <8f2c484307284b51944a1a13a14c0266>:0 
  at System.IO.Directory.GetDirectories (System.String path, System.String searchPattern) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0 
  at System.IO.Directory.GetDirectories (System.String path) [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0 
  at EZ_Builder.FormOpenEZB.XtZsj07xQ5 () [0x0000b] in <8a9b654daa5e46dc9cae530155c2d0ff>:0 
  at EZ_Builder.FormOpenEZB..ctor (System.String folder) [0x0002d] in <8a9b654daa5e46dc9cae530155c2d0ff>:0 
  at (wrapper remoting-invoke-with-check) EZ_Builder.FormOpenEZB:.ctor (string)
  at EZ_Builder.FormMain.MenuClick_Open (System.Object sender, System.EventArgs e) [0x00027] in <8a9b654daa5e46dc9cae530155c2d0ff>:0 
  at (wrapper delegate-invoke) :invoke_void_object_EventArgs (object,System.EventArgs)
  at System.Windows.Forms.RibbonItem.OnClick (System.EventArgs e) [0x00042] in <8137470ea8f14440974ce9168ccc636e>:0 
  at System.Windows.Forms.RibbonButton.OnClick (System.EventArgs e) [0x0003f] in <8137470ea8f14440974ce9168ccc636e>:0 
  at System.Windows.Forms.RibbonMouseSensor.Control_MouseClick (System.Object sender, System.Windows.Forms.MouseEventArgs e) [0x00041] in <8137470ea8f14440974ce9168ccc636e>:0 
  at System.Windows.Forms.Control.OnMouseClick (System.Windows.Forms.MouseEventArgs e) [0x0001c] in :0 
  at System.Windows.Forms.Control.HandleClick (System.Int32 clicks, System.Windows.Forms.MouseEventArgs me) [0x0005d] in :0 
  at System.Windows.Forms.Control.WmLButtonUp (System.Windows.Forms.Message& m) [0x00071] in :0 
  at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) [0x0016f] in :0 
  at System.Windows.Forms.Ribbon.WndProc (System.Windows.Forms.Message& m) [0x00191] in <8137470ea8f14440974ce9168ccc636e>:0 
  at System.Windows.Forms.Control+ControlWindowTarget.OnMessage (System.Windows.Forms.Message& m) [0x00000] in :0 
  at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x0000b] in :0 
  at System.Windows.Forms.NativeWindow.WndProc (System.IntPtr hWnd, System.Windows.Forms.Msg msg, System.IntPtr wParam, System.IntPtr lParam) [0x0008e] in :0 

I searched Synthiam Community for a similar thread, so forgive me if this issue has been addressed in a previous post and I missed it. I am happy to answer any questions. Does anyone know what I could have done wrong during the installation?

Thanks Tim


Related Hardware Raspberry Pi

ARC Pro

Upgrade to ARC Pro

Experience the transformation – subscribe to Synthiam ARC Pro and watch your robot evolve into a marvel of innovation and intelligence.

#25   — Edited

Regarding servo choices, I can totally understand your point... If you would like to have your build in the limelight, it is always good to have a strong brand connected to it! Also your concern of the LewanSoul servos being inconsistent or even diminishing at some point is a very valid argument.

Things that made me choose them anyways is of course the price, with my robot having 14DOF now, which is 196 Euros using LewanSoul servos, vs 700 Euros using Dynamixel AX-12A servos...

But also I can run the LewanSoul on 5v (recommended specs for full torque are 7.4V, but I did not run into any issues using them on 5V). So I can use a single 20Amps power supply to power the servos and all peripherals...

And last of all, I had trouble to drive the Dynamixel with the hardware they supplied! You will always have to use a shield or microcontroller board to get them to work, while using the LewanSoul servos, you can use their simple BusLinker to drive the servos with python directly from your Raspian or Windows OS without having to code another peripheral!

Good to hear you are using the AIY Voice kit v1, the later version is build on to of a Pi Zero, which is not having enough horsepower to drive custom hotword detection... And very good to hear that AIY Voice will be available in ARC soon!!!

I love your website...hope you will be able to sort out installing issues so we can go on and build some awesome robots!!

#26  

I forgot to mention, but I guess you already figured it out yourself... ARC fully supports Dynamixel and LewanSoul LX16A servos!!:)

#27  

That's a great point, having the option to operate the servos at 5v would make powering the robot simpler. The AX-12's worked with little trouble, but we have had issues with the XL430's and XL-320's. I found that the Expansion board was necessary to ID/setup the XL430's even with the OpenCM9. They are great servos, but definitely a bit finicky (and expensive).

Thank you, I looking forward to helping anyone interested in building a MAKI or "Monkey" robot.:D

Yeah, I have installed the Dynamixel plugin, but have not tested it yet. I wanted to make sure that I could install ARC without errors first.

#28  

Hello everyone,

I have not been able to run:

sudo mono ARC.exe

without errors:

Unknown heap type: #GUlD

Unknown heap type: #Blop

Unknown heap type: #GUlD

Unknown heap type: #Blop

so I have decided to just run the EZBPi server on the Raspberry Pi and run ARC on my Windows Laptop until I can figure out what I am doing wrong. I am able to connect to the Pi and the camera is streaming great; however, when I "stop" the camera, EZBPi Server also disconnects and aborts on the Raspberry Pi:

pi@raspberrypi:~/EZBPi $ sudo mono EZBPi.exe
Raspberry EZBPi Version: 2019.8.27.1
Verbose logging is: False
Serial port is: /dev/serial0
EZB: TCP Started on port 23
EZ-B Server started on TCP Port: 23
Camera: TCP Started on port 24
Camera Server started on TCP Port: 24
Press ESC to quit
Camera: TCP Connection from: 10.0.0.5

=================================================================
   Native Crash Reporting
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================
/proc/self/maps:
00010000-00412000 r-xp 00000000 b3:02 262718     /usr/bin/mono-sgen
00422000-00426000 r--p 00402000 b3:02 262718     /usr/bin/mono-sgen
00426000-0042b000 rw-p 00406000 b3:02 262718     /usr/bin/mono-sgen
0042b000-00439000 rw-p 00000000 00:00 0 
00a97000-01170000 rw-p 00000000 00:00 0          [heap]
6b000000-6b0ff000 rw-p 00000000 00:00 0 
6b0ff000-6b100000 ---p 00000000 00:00 0 
6b100000-6b194000 rw-p 00000000 00:00 0 
6b194000-6b200000 ---p 00000000 00:00 0 
6b200000-6b2ff000 rw-p 00000000 00:00 0 
6b2ff000-6b300000 ---p 00000000 00:00 0 
6b300000-6b3ff000 rw-p 00000000 00:00 0 
6b3ff000-6b400000 ---p 00000000 00:00 0 
6b400000-6b4ff000 rw-p 00000000 00:00 0 
6b4ff000-6b500000 ---p 00000000 00:00 0 
6b500000-6b5ff000 rw-p 00000000 00:00 0 
6b5ff000-6b600000 ---p 00000000 00:00 0 
6b600000-6b6ff000 rw-p 00000000 00:00 0 
6b6ff000-6b700000 ---p 00000000 00:00 0 
6b700000-6b7ff000 rw-p 00000000 00:00 0 
6b7ff000-6b800000 ---p 00000000 00:00 0 
6b800000-6b900000 rw-p 00000000 00:00 0 
6ba00000-6baff000 rw-p 00000000 00:00 0 
6baff000-6bb00000 ---p 00000000 00:00 0 
6bb00000-6bbff000 rw-p 00000000 00:00 0 

=================================================================
   Native stacktrace:
=================================================================
    (No frames) 


=================================================================
   Telemetry Dumper:
=================================================================
Pkilling 0x76fc1b00 from 0x70fff430
Pkilling 0x730ff430 from 0x70fff430
Pkilling 0x739ff430 from 0x70fff430
Pkilling 0x72dff430 from 0x70fff430
Pkilling 0x736ff430 from 0x70fff430
Pkilling 0x76667430 from 0x70fff430
Pkilling 0x6cff8430 from 0x70fff430
Pkilling 0x72aff430 from 0x70fff430
Pkilling 0x733ff430 from 0x70fff430
Pkilling 0x70ba2430 from 0x70fff430
Entering thread summarizer pause from 0x70fff430
Finished thread summarizer pause from 0x70fff430.
domain required for stack walk
Waiting for dumping threads to resume

=================================================================
   External Debugger Dump:
=================================================================
[New LWP 4192]
[New LWP 4193]
[New LWP 4194]
[New LWP 4195]
[New LWP 4196]
[New LWP 4210]
[New LWP 4211]
[New LWP 6661]
[New LWP 6842]
[New LWP 6843]
[New LWP 6844]
[New LWP 6845]
[New LWP 6846]
[New LWP 6847]
[New LWP 6848]
[New LWP 6861]
[New LWP 6862]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
__libc_read (nbytes=1024, buf=0x7607af20, fd=0) at ../sysdeps/unix/sysv/linux/read.c:26
26   ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
  Id   Target Id                                      Frame 
* 1    Thread 0x76fc1b00 (LWP 4191) "mono"            __libc_read (nbytes=1024, buf=0x7607af20, fd=0) at ../sysdeps/unix/sysv/linux/read.c:26
  2    Thread 0x75fff430 (LWP 4192) "SGen worker"     futex_wait_cancelable (private=0, expected=0, futex_word=0x437b28) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
  3    Thread 0x76667430 (LWP 4193) "Finalizer"       0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x42fe08) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  4    Thread 0x739ff430 (LWP 4194) "TCP Server for " 0x76efb3d0 in __libc_accept (fd=5, addr=..., len=0x0) at ../sysdeps/unix/sysv/linux/accept.c:26
  5    Thread 0x736ff430 (LWP 4195) "TCP Server for " 0x76efb3d0 in __libc_accept (fd=7, addr=..., len=0x0) at ../sysdeps/unix/sysv/linux/accept.c:26
  6    Thread 0x733ff430 (LWP 4196) "Timer-Scheduler" futex_reltimed_wait_cancelable (private=0, reltime=0x733fe258, expected=0, futex_word=0xa9cc38) at ../sysdeps/unix/sysv/linux/futex-internal.h:142
  7    Thread 0x72dff430 (LWP 4210) "Thread Pool Wor" futex_abstimed_wait_cancelable (private=0, abstime=0x72dfed7c, expected=1, futex_word=0x430348) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  8    Thread 0x72aff430 (LWP 4211) "Thread Pool Wor" futex_abstimed_wait_cancelable (private=0, abstime=0x72afed7c, expected=1, futex_word=0x430348) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  9    Thread 0x730ff430 (LWP 6661) "Timer-Scheduler" futex_reltimed_wait_cancelable (private=0, reltime=0x730fec50, expected=0, futex_word=0x438158) at ../sysdeps/unix/sysv/linux/futex-internal.h:142
  10   Thread 0x70fff430 (LWP 6842) "TCP Server for " __waitpid (options=0, stat_loc=0x70ffdc40, pid=6890) at ../sysdeps/unix/sysv/linux/waitpid.c:30
  11   Thread 0x707ff430 (LWP 6843) "VCHIQ completio" 0x76c7551c in ioctl () at ../sysdeps/unix/syscall-template.S:78
  12   Thread 0x6fffe430 (LWP 6844) "HDispmanx Notif" 0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x7383d480 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  13   Thread 0x6f7fd430 (LWP 6845) "HTV Notify"      0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x7383c5f4 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  14   Thread 0x6effc430 (LWP 6846) "HCEC Notify"     0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x7383d384 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  15   Thread 0x6e7fb430 (LWP 6847) "vc.ril.camera"   0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0xed63d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  16   Thread 0x6dffa430 (LWP 6848) "vc.camera_info"  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0xed6208) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  17   Thread 0x6d7f9430 (LWP 6861) "vc.ril.video_sp" 0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x1038578) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  18   Thread 0x6cff8430 (LWP 6862) "vc.ril.image_en" 0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x1091768) at ../sysdeps/unix/sysv/linux/futex-internal.h:205

Thread 18 (Thread 0x6cff8430 (LWP 6862)):
#0  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x1091768) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x1091768, abstime=0x0) at sem_waitcommon.c:115
#2  0x76efa1f4 in __new_sem_wait_slow (sem=0x1091768, abstime=0x0) at sem_waitcommon.c:282
#3  0x72c98968 in mmal_component_action_thread_func () from /opt/vc/lib/libmmal_core.so
#4  0x73517cb0 in vcos_thread_entry (arg=0x1091680) at /home/dom/projects/staging/userland/interface/vcos/pthreads/vcos_pthreads.c:144
#5  0x76ef0494 in start_thread (arg=0x6cff8430) at pthread_create.c:486
#6  0x76c7d578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 17 (Thread 0x6d7f9430 (LWP 6861)):
#0  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x1038578) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x1038578, abstime=0x0) at sem_waitcommon.c:115
#2  0x76efa1f4 in __new_sem_wait_slow (sem=0x1038578, abstime=0x0) at sem_waitcommon.c:282
#3  0x72c98968 in mmal_component_action_thread_func () from /opt/vc/lib/libmmal_core.so
#4  0x73517cb0 in vcos_thread_entry (arg=0x1038490) at /home/dom/projects/staging/userland/interface/vcos/pthreads/vcos_pthreads.c:144
#5  0x76ef0494 in start_thread (arg=0x6d7f9430) at pthread_create.c:486
#6  0x76c7d578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 16 (Thread 0x6dffa430 (LWP 6848)):
#0  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0xed6208) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0xed6208, abstime=0x0) at sem_waitcommon.c:115
#2  0x76efa1f4 in __new_sem_wait_slow (sem=0xed6208, abstime=0x0) at sem_waitcommon.c:282
#3  0x72c98968 in mmal_component_action_thread_func () from /opt/vc/lib/libmmal_core.so
#4  0x73517cb0 in vcos_thread_entry (arg=0xed6120) at /home/dom/projects/staging/userland/interface/vcos/pthreads/vcos_pthreads.c:144
#5  0x76ef0494 in start_thread (arg=0x6dffa430) at pthread_create.c:486
#6  0x76c7d578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 15 (Thread 0x6e7fb430 (LWP 6847)):
#0  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0xed63d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0xed63d8, abstime=0x0) at sem_waitcommon.c:115
#2  0x76efa1f4 in __new_sem_wait_slow (sem=0xed63d8, abstime=0x0) at sem_waitcommon.c:282
#3  0x72c98968 in mmal_component_action_thread_func () from /opt/vc/lib/libmmal_core.so
#4  0x73517cb0 in vcos_thread_entry (arg=0xed62f0) at /home/dom/projects/staging/userland/interface/vcos/pthreads/vcos_pthreads.c:144
#5  0x76ef0494 in start_thread (arg=0x6e7fb430) at pthread_create.c:486
#6  0x76c7d578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 14 (Thread 0x6effc430 (LWP 6846)):
#0  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x7383d384 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x7383d384 , abstime=0x0) at sem_waitcommon.c:115
#2  0x76efa1f4 in __new_sem_wait_slow (sem=0x7383d384 , abstime=0x0) at sem_waitcommon.c:282
#3  0x73823720 in cecservice_notify_func () from /opt/vc/lib/libbcm_host.so
#4  0x73517cb0 in vcos_thread_entry (arg=0x7383d398 ) at /home/dom/projects/staging/userland/interface/vcos/pthreads/vcos_pthreads.c:144
#5  0x76ef0494 in start_thread (arg=0x6effc430) at pthread_create.c:486
Backtrace stopped: Cannot access memory at address 0x65006a

Thread 13 (Thread 0x6f7fd430 (LWP 6845)):
#0  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x7383c5f4 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x7383c5f4 , abstime=0x0) at sem_waitcommon.c:115
#2  0x76efa1f4 in __new_sem_wait_slow (sem=0x7383c5f4 , abstime=0x0) at sem_waitcommon.c:282
#3  0x738223b0 in tvservice_notify_func () from /opt/vc/lib/libbcm_host.so
#4  0x73517cb0 in vcos_thread_entry (arg=0x7383c608 ) at /home/dom/projects/staging/userland/interface/vcos/pthreads/vcos_pthreads.c:144
#5  0x76ef0494 in start_thread (arg=0x6f7fd430) at pthread_create.c:486
Backtrace stopped: Cannot access memory at address 0x65006a

Thread 12 (Thread 0x6fffe430 (LWP 6844)):
#0  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x7383d480 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x7383d480 , abstime=0x0) at sem_waitcommon.c:115
#2  0x76efa1f4 in __new_sem_wait_slow (sem=0x7383d480 , abstime=0x0) at sem_waitcommon.c:282
#3  0x738264d4 in dispmanx_notify_func () from /opt/vc/lib/libbcm_host.so
#4  0x73517cb0 in vcos_thread_entry (arg=0x7383e1c0 ) at /home/dom/projects/staging/userland/interface/vcos/pthreads/vcos_pthreads.c:144
#5  0x76ef0494 in start_thread (arg=0x6fffe430) at pthread_create.c:486
#6  0x76c7d578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 11 (Thread 0x707ff430 (LWP 6843)):
#0  0x76c7551c in ioctl () at ../sysdeps/unix/syscall-template.S:78
#1  0x73530010 in completion_thread () from /opt/vc/lib/libvchiq_arm.so
#2  0x73517cb0 in vcos_thread_entry (arg=0x73543318 ) at /home/dom/projects/staging/userland/interface/vcos/pthreads/vcos_pthreads.c:144
#3  0x76ef0494 in start_thread (arg=0x707ff430) at pthread_create.c:486
#4  0x76c7d578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 10 (Thread 0x70fff430 (LWP 6842)):
#0  __waitpid (options=0, stat_loc=0x70ffdc40, pid=6890) at ../sysdeps/unix/sysv/linux/waitpid.c:30
#1  __waitpid (pid=6890, stat_loc=0x70ffdc40, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
#2  0x000a24e4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 9 (Thread 0x730ff430 (LWP 6661)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x730fec50, expected=0, futex_word=0x438158) at ../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x730feccc, mutex=0x2, cond=0x438130) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x438130, mutex=0x2, abstime=0x730feccc) at pthread_cond_wait.c:667
#3  0x0032ee34 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 8 (Thread 0x72aff430 (LWP 4211)):
#0  futex_abstimed_wait_cancelable (private=0, abstime=0x72afed7c, expected=1, futex_word=0x430348) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x430348, abstime=abstime@entry=0x72afed7c) at sem_waitcommon.c:115
#2  0x76efa5c4 in __new_sem_wait_slow (sem=0x430348, abstime=0x72afed7c) at sem_waitcommon.c:282
#3  0x002cde6c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 7 (Thread 0x72dff430 (LWP 4210)):
#0  futex_abstimed_wait_cancelable (private=0, abstime=0x72dfed7c, expected=1, futex_word=0x430348) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x430348, abstime=abstime@entry=0x72dfed7c) at sem_waitcommon.c:115
#2  0x76efa5c4 in __new_sem_wait_slow (sem=0x430348, abstime=0x72dfed7c) at sem_waitcommon.c:282
#3  0x002cde6c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 6 (Thread 0x733ff430 (LWP 4196)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x733fe258, expected=0, futex_word=0xa9cc38) at ../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x733fe2d4, mutex=0x2, cond=0xa9cc10) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0xa9cc10, mutex=0x2, abstime=0x733fe2d4) at pthread_cond_wait.c:667
#3  0x0032ee34 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 5 (Thread 0x736ff430 (LWP 4195)):
#0  0x76efb3d0 in __libc_accept (fd=7, addr=..., len=0x0) at ../sysdeps/unix/sysv/linux/accept.c:26
#1  0x002c9c20 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0x739ff430 (LWP 4194)):
#0  0x76efb3d0 in __libc_accept (fd=5, addr=..., len=0x0) at ../sysdeps/unix/sysv/linux/accept.c:26
#1  0x002c9c20 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0x76667430 (LWP 4193)):
#0  0x76efa088 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x42fe08) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
#1  do_futex_wait (sem=sem@entry=0x42fe08, abstime=0x0) at sem_waitcommon.c:115
#2  0x76efa1f4 in __new_sem_wait_slow (sem=0x42fe08, abstime=0x0) at sem_waitcommon.c:282
#3  0x002b53f0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0x75fff430 (LWP 4192)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x437b28) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x0, cond=0x437b00) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x437b00, mutex=0x0) at pthread_cond_wait.c:655
#3  0x0031de68 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x76fc1b00 (LWP 4191)):
#0  __libc_read (nbytes=1024, buf=0x7607af20, fd=0) at ../sysdeps/unix/sysv/linux/read.c:26
#1  __libc_read (fd=0, buf=0x7607af20, nbytes=1024) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x0017e86c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Inferior 1 (process 4191) detached]

=================================================================
   Basic Fault Address Reporting
=================================================================
Memory around native instruction pointer (0x76c19854):0x76c19844  10 40 2d e9 00 40 a0 e1 08 d0 4d e2 2a 00 00 0a  .@[email protected].*...
0x76c19854  04 20 10 e5 08 10 40 e2 02 00 12 e3 0f 00 00 1a  . ....@.........
0x76c19864  08 31 9f e5 a0 90 fe eb 03 30 9f e7 03 00 80 e0  .1.......0......
0x76c19874  04 30 90 e5 00 00 53 e3 32 00 00 0a 04 00 12 e3  .0....S.2.......

=================================================================
   Managed Stacktrace:
=================================================================
     at  <0xffffffff>
     at MMALSharp.Native.MMALUtil:mmal_port_pool_destroy <0x0003b>
     at MMALSharp.Ports.PortBase:DestroyPortPool <0x0006b>
     at MMALSharp.MMALComponentBase:CleanPortPools <0x00227>
     at MMALSharp.MMALConnectionImpl:Destroy <0x00043>
     at MMALSharp.MMALConnectionImpl:Dispose <0x00037>
     at MMALSharp.Components.MMALDownstreamComponent:ClosePipelineConnections <0x0017f>
     at MMALSharp.Components.MMALDownstreamComponent:Dispose <0x00037>
     at EZBPi.EZBProgram:_CAMServer_OnConnection <0x008cb>
     at EZBPi.TCPServer:handleClientScriptCommand <0x000e7>
     at System.Threading.ThreadHelper:ThreadStart_Context <0x0013f>
     at System.Threading.ExecutionContext:RunInternal <0x0020f>
     at System.Threading.ExecutionContext:Run <0x0002b>
     at System.Threading.ExecutionContext:Run <0x00057>
     at System.Threading.ThreadHelper:ThreadStart <0x0007b>
     at :runtime_invoke_void__this___object <0x000ef>
=================================================================
Aborted

*The main issue that I am trying to work through is getting the Dynamixel XL430-W250-T servos to work. Here is a screenshot of my settings:

User-inserted image

I followed DJ's 9th Live Hack and I have triple checked the connection (I even soldered another connector). I have checked and rechecked the servo ID's (before and after). I have also tried different baud rates. Currently I have it set 57600, but I have also tried 9600 and 1000000. The signal pin of the servo is connected to the TX and RX pins of the Raspberry Pi:

User-inserted image

I have also tested an AX-12 servo (with the baud rate set to 1000000), but I am not able to get either model servo to move. Is there anything else that I can try, or maybe a step that I am missing? Any help is much appreciated!

PRO
Belgium
#29  

in this topic for using AX12A servo's says use baud 115200.

AX12A 

PRO
Synthiam
#30  

Also I believe the correct uart port is 0, not 1

#31   — Edited

Thanks Nomad 6R, I tried 115200, but the AX-12A servo is still not working.

Thanks DJ, I selected UART Port #0, but the XL430 servos are still not responding.

User-inserted image

Do you have any other suggestions? Also, do you have any thoughts about the camera issue?

PRO
Synthiam
#32   — Edited

Verify this checklist...

  • Ensure your servo is TTL.
  • Ensure the RX and TX are connected correctly.
  • Ensure the raspberry pi and servo are both sharing the same ground.
  • Verify the baud rate matches the servo.
  • Ensure the ID selected in the plugin is matching the servo.
  • Ensure the servo is receiving correct required power.

Create a checklist of those items and ensure each one is correct