Starvis IMX412 doesn't work with VOXL
-
I tested these sensors with VOXL Flight.
hires: Starvis IMX412
tracking: OV7251 167° Tracking Sensor Module
ToFThe error occured after I typed
voxl-configure-cameras 6and check hires view in voxl-portal.-- Logs begin at Thu 1970-01-01 00:00:04 UTC, end at Thu 1970-01-01 00:01:06 UTC. -- Jan 01 00:00:07 apq8096 systemd[1]: Started voxl-camera-server. Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: Camera server is now stopping Jan 01 00:00:10 apq8096 bash[2030]: There is a chance that it may segfault here, this is a mmqcamera bug, ignore it Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: Stopping tracking camera Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: tracking camera stopped successfully Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: Stopping hires camera Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: hires camera stopped successfully Jan 01 00:00:10 apq8096 bash[2030]: ------ voxl-camera-server INFO: Stopping stereo camera Jan 01 00:00:10 apq8096 bash[2030]: Segmentation fault: Jan 01 00:00:10 apq8096 bash[2030]: Fault thread: voxl-camera-ser(tid: 2030) Jan 01 00:00:10 apq8096 bash[2030]: Fault address: 0x68 Jan 01 00:00:10 apq8096 bash[2030]: Address not mapped. Jan 01 00:00:10 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Main process exited, code=killed, status=11/SEGV[[0m Jan 01 00:00:10 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Unit entered failed state.[[0m Jan 01 00:00:10 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Failed with result 'signal'.[[0msystem image: 3.8.0 / voxl-suite: 0.7
And I also tested it with System Image 4.0, but the error also occured.
-- Logs begin at Thu 1970-01-01 00:10:17 UTC, end at Thu 1970-01-01 00:13:17 UTC. -- Jan 01 00:12:42 apq8096 systemd[1]: Stopped voxl-camera-server. Jan 01 00:12:42 apq8096 systemd[1]: Started voxl-camera-server. Jan 01 00:12:43 apq8096 bash[3645]: ERROR: Camera 1 failed to find supported preview config: 640x480 Jan 01 00:12:43 apq8096 bash[3645]: ERROR: Failed to start camera: tracking, exiting Jan 01 00:12:43 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Main process exited, code=exited, status=255/n/a[[0m Jan 01 00:12:43 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Unit entered failed state.[[0m Jan 01 00:12:43 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Failed with result 'exit-code'.[[0m Jan 01 00:12:53 apq8096 systemd[1]: Stopped voxl-camera-server. Jan 01 00:12:53 apq8096 systemd[1]: Started voxl-camera-server. Jan 01 00:12:53 apq8096 bash[3976]: WARNING: Recieved RAW10 frame, will be converting to RAW8 on cpu Jan 01 00:12:59 apq8096 bash[3976]: ERROR: Recieved Fatal error from camera:hires Jan 01 00:12:59 apq8096 bash[3976]: ERROR: Sending request 3, ErrorCode: -ENODEV Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: hires request thread recieved ESTOP Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: tracking result thread recieved ESTOP Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: hires result thread recieved ESTOP Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: tof result thread recieved ESTOP Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: tracking request thread recieved ESTOP Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Thread: tof request thread recieved ESTOP Jan 01 00:12:59 apq8096 bash[3976]: ------ voxl-camera-server INFO: Camera server is now stopping Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Deleting buffers: 3 of 16 still in use Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Deleting buffers: 3 of 16 still in use Jan 01 00:12:59 apq8096 bash[3976]: WARNING: Deleting buffers: 3 of 16 still in use Jan 01 00:13:00 apq8096 bash[3976]: ------ voxl-camera-server INFO: Camera server exited gracefullyI found "ERROR: Recieved Fatal error from camera:hires" from the message.
so I disabled hires with voxl-camera-server.conf.
And ToF and Tracking work.
Would this require replacing the Starvis camera?
Or do I need to set up something else? -
this usually means one of the following:
- camera configuration does not match what is installed. the configuration needs to match what is installed, not what you want to use
- a connector is not properly seated
- a connector is backwards
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login