ModalAI Forum

@Eric-Katzfey
FYI, I just moved /lib and /usr/lib to /data.
This allowed to have enough space for my work.

Thank you.

@Eric-Katzfey
I am moving files to /data folder.
I have

voxl:/usr$ ls
aarch64-oe-linux             bin   etc    include  lib64    local  share  tests
arm-oemllib32-linux-gnueabi  data  games  lib      libexec  sbin   src

I would like to move lib64 and lib folders to /data/usr and do sudo ln -s /data/usr/lib /usr/lib and 'sudo ln -s /data/usr/lib64 /usr/lib64.
But I see the error -bash: /bin/resize: No such file or directory when I used some ubuntu commands.

Could you please advise me to move these folders into /data?

@Adrian-Hidalgo Thank you.
But the target directory is /dev/root for libraries... so I need to increase the size of this.

@Adrian-Hidalgo
As I mentioned, selecting C3 configuration in my Seeker make voxl-camera-server work correctly.
I confirmed voxl-inspect-qvio displayed correct pose data.

Thanks, though.

By the way, I am wondering if I can increase the storage size of /dev/root on the VOXL. Do you have any idea?

@Adrian-Hidalgo Thanks for your suggestions that I have already tried.
Cables and connections are fine.

What I found just before is cameras were shown up when I did not choose 7: TOF + Stereo + Tracking with voxl-configure-cameras.

Just before, I chose 3: Hires + Stereo + Tracking and 2) yes_rotate.
Then voxl-inspect-qvio outputted correct x,y, and z data (in QGC).

Do you think this is the issue only for my Seeker?

For your information,

voxl:~$ voxl-version 
cat: /etc/modalai/voxl-software-bundle-version.txt: No such file or directory
--------------------------------------------------------------------------------
system-image:    ModalAI 3.3.0 BUILDER: ekatzfey BUILD_TIME: 2021-06-06_19:28
kernel:          #1 SMP PREEMPT Sun Jun 6 19:41:01 UTC 2021 3.18.71-perf
factory-bundle:  1.0.1 (Yocto installation)
--------------------------------------------------------------------------------
architecture:    aarch64
processor:       apq8096
os:              GNU/Linux
--------------------------------------------------------------------------------
voxl-suite:
Package: voxl-suite
Version: 0.5.0
Depends: libjpeg_turbo (>= 9.0.4), libmodal_exposure (>= 0.0.2), libmodal_json (>= 0.3.6), libmodal_pipe (>= 2.1.1), librc_math (>= 1.1.5), libvoxl_cutils (>= 0.0.2), libvoxl_io (>= 0.5.4), mavlink-camera-manager (>= 0.0.2), mongoose (>= 7.3.0), opencv (>= 4.5.2-2), openmp (>= 10.0.2), voxl-camera-calibration (>= 0.1.1), voxl-camera-server (>= 0.8.1), voxl-cpu-monitor (>= 0.2.0), voxl-dfs-server (>= 0.2.2), voxl-docker-support (>= 1.1.3), voxl-gphoto2 (>= 0.0.5), voxl-imu-server (>= 0.9.1), voxl-mavlink (>= 0.0.2), voxl-modem (>= 0.12.0), voxl-mpa-tools (>= 0.3.6), voxl-nodes (>= 0.2.0), voxl-portal (>= 0.1.2), voxl-qvio-server (>= 0.3.4), voxl-streamer (>= 0.2.6), voxl-tag-detector (>= 0.0.2), voxl-tflite (>= 2.2.3), voxl-tflite-server (>= 0.1.5), voxl-utils (>= 0.8.4), voxl-vision-px4 (>= 0.9.5), voxl-vpn (>= 0.0.3)
Status: install user installed
Architecture: all
Installed-Time: 5549

Thank you for your reply, @Adrian-Hidalgo .

Please refer to https://forum.modalai.com/topic/547/voxl-camera-server/7?_=1656346172322

This is the problem.

Output of voxl-camera-server -d 0 is

.
.
.

------ voxl-camera-server INFO: Camera server is now stopping
		There is a chance that it may segfault here, this is a mmqcamera bug, ignore it

------ voxl-camera-server INFO: Stopping tracking camera
------ Result thread on camera: tracking recieved stop command, exiting
------ voxl-camera-server INFO: tracking camera stopped successfully

------ voxl-camera-server INFO: Stopping tof camera
Fault address: 0x68
Address not mapped.
Segmentation fault

@Alex-Gardner

Hi Alex,

I have the same issue, but I have output of journalctl -u voxl-camera-server as shown below

Jan 01 00:57:14 apq8096 bash[1968]: There is a chance that it may segfault here, this is a mmqcamera bug, ignore it
Jan 01 00:57:14 apq8096 bash[1968]: ------ voxl-camera-server INFO: Stopping tracking camera
Jan 01 00:57:14 apq8096 bash[1968]: ------ voxl-camera-server INFO: tracking camera stopped successfully
Jan 01 00:57:14 apq8096 bash[1968]: ------ voxl-camera-server INFO: Stopping tof camera
Jan 01 00:57:14 apq8096 bash[1968]: Fault address: 0x68
Jan 01 00:57:14 apq8096 bash[1968]: Address not mapped.
Jan 01 00:57:14 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Main process exited, code=killed, status=11/SEGV[[0m
Jan 01 00:57:14 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Unit entered failed state.[[0m
Jan 01 00:57:14 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Failed with result 'signal'.[[0m
Jan 01 01:01:56 apq8096 systemd[1]: Stopped voxl-camera-server.
Jan 01 01:01:56 apq8096 systemd[1]: Started voxl-camera-server.
Jan 01 01:01:57 apq8096 bash[3385]: ------ voxl-camera-server INFO: Camera server is now stopping
Jan 01 01:01:57 apq8096 bash[3385]: There is a chance that it may segfault here, this is a mmqcamera bug, ignore it
Jan 01 01:01:57 apq8096 bash[3385]: ------ voxl-camera-server INFO: Stopping tracking camera
Jan 01 01:01:57 apq8096 bash[3385]: ------ voxl-camera-server INFO: tracking camera stopped successfully
Jan 01 01:01:57 apq8096 bash[3385]: ------ voxl-camera-server INFO: Stopping tof camera
Jan 01 01:01:57 apq8096 bash[3385]: Fault address: 0x68
Jan 01 01:01:57 apq8096 bash[3385]: Address not mapped.
Jan 01 01:01:57 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Main process exited, code=killed, status=11/SEGV[[0m
Jan 01 01:01:57 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Unit entered failed state.[[0m
Jan 01 01:01:57 apq8096 systemd[1]: [[1;39mvoxl-camera-server.service: Failed with result 'signal'.[[0m

any advice?

Is there any instruction for the factory reset on Seeker?