Hello, I'm seeing in the documentation and in the code that ov64b sensors are supported by SDK 1.4. I've confirmed that the bins exist in chi-cdk.
However, I'm not seeing any information/documentation on camera configs nor any default camera-server configs in the source code for this sensor.
How do I go about using it with voxl-camera-server.conf?
@Alex-Kushleyev Thanks, everything looks alright now that I've removed the other cameras from the config file
@modaltb yup, a single IMX412 on M0173 J5.
I've removed all the other com.qti.sensormodule*.bin files. These are the outputs I get when I run voxl-camera-server -l and voxl-camera-server with and without tracking_front enabled in the config file.
As you can see, I'm still getting the same strange behaviour.
Default C28:
voxl2:/$ voxl-camera-server -l
existing instance of voxl-camera-server found, attempting to stop it
DEBUG: Attempting to open the hal module
DEBUG: SUCCESS: Camera module opened on attempt 0
DEBUG: ----------- Number of cameras: 1
DEBUG: Cam idx: 0, Cam slot: 2, Slave Address: 0x0034, Sensor Id: 0x0577
DEBUG: Note: This list comes from the HAL module and may not be indicative
DEBUG: of configurations that have full pipelines
DEBUG: Number of cameras: 1
====================================
Stats for camera: 0
ANDROID_SCALER_AVAILABLE_RAW_SIZES:
These are likely supported by the sensor
4056 x 3040
3840 x 2160
1920 x 1080
1920 x 1080
1920 x 1080
1280 x 720
1280 x 720
ANDROID_SCALER_AVAILABLE_STREAM_CONFIGURATIONS:
These are NOT necessarily supported by the sensor
4056 x 3040 HAL_PIXEL_FORMAT_YCbCr_420_888
4056 x 3040 HAL_PIXEL_FORMAT_BLOB
4000 x 3000 HAL_PIXEL_FORMAT_YCbCr_420_888
4000 x 3000 HAL_PIXEL_FORMAT_BLOB
3840 x 2160 HAL_PIXEL_FORMAT_YCbCr_420_888
3840 x 2160 HAL_PIXEL_FORMAT_BLOB
3264 x 2448 HAL_PIXEL_FORMAT_YCbCr_420_888
3264 x 2448 HAL_PIXEL_FORMAT_BLOB
3200 x 2400 HAL_PIXEL_FORMAT_YCbCr_420_888
3200 x 2400 HAL_PIXEL_FORMAT_BLOB
2976 x 2976 HAL_PIXEL_FORMAT_YCbCr_420_888
2976 x 2976 HAL_PIXEL_FORMAT_BLOB
2688 x 1512 HAL_PIXEL_FORMAT_YCbCr_420_888
2688 x 1512 HAL_PIXEL_FORMAT_BLOB
2592 x 1944 HAL_PIXEL_FORMAT_YCbCr_420_888
2592 x 1944 HAL_PIXEL_FORMAT_BLOB
2048 x 1536 HAL_PIXEL_FORMAT_YCbCr_420_888
2048 x 1536 HAL_PIXEL_FORMAT_BLOB
1920 x 1440 HAL_PIXEL_FORMAT_YCbCr_420_888
1920 x 1440 HAL_PIXEL_FORMAT_BLOB
1928 x 1208 HAL_PIXEL_FORMAT_YCbCr_420_888
1928 x 1208 HAL_PIXEL_FORMAT_BLOB
1920 x 1080 HAL_PIXEL_FORMAT_YCbCr_420_888
1920 x 1080 HAL_PIXEL_FORMAT_BLOB
1600 x 1200 HAL_PIXEL_FORMAT_YCbCr_420_888
1600 x 1200 HAL_PIXEL_FORMAT_BLOB
1440 x 1080 HAL_PIXEL_FORMAT_YCbCr_420_888
1440 x 1080 HAL_PIXEL_FORMAT_BLOB
1280 x 960 HAL_PIXEL_FORMAT_YCbCr_420_888
1280 x 960 HAL_PIXEL_FORMAT_BLOB
1280 x 800 HAL_PIXEL_FORMAT_YCbCr_420_888
1280 x 800 HAL_PIXEL_FORMAT_BLOB
1280 x 768 HAL_PIXEL_FORMAT_YCbCr_420_888
1280 x 768 HAL_PIXEL_FORMAT_BLOB
1280 x 720 HAL_PIXEL_FORMAT_YCbCr_420_888
1280 x 720 HAL_PIXEL_FORMAT_BLOB
1080 x 1080 HAL_PIXEL_FORMAT_YCbCr_420_888
1080 x 1080 HAL_PIXEL_FORMAT_BLOB
1024 x 738 HAL_PIXEL_FORMAT_YCbCr_420_888
1024 x 738 HAL_PIXEL_FORMAT_BLOB
1024 x 768 HAL_PIXEL_FORMAT_YCbCr_420_888
1024 x 768 HAL_PIXEL_FORMAT_BLOB
864 x 480 HAL_PIXEL_FORMAT_YCbCr_420_888
864 x 480 HAL_PIXEL_FORMAT_BLOB
800 x 600 HAL_PIXEL_FORMAT_YCbCr_420_888
800 x 600 HAL_PIXEL_FORMAT_BLOB
800 x 480 HAL_PIXEL_FORMAT_YCbCr_420_888
800 x 480 HAL_PIXEL_FORMAT_BLOB
720 x 1280 HAL_PIXEL_FORMAT_YCbCr_420_888
720 x 1280 HAL_PIXEL_FORMAT_BLOB
720 x 480 HAL_PIXEL_FORMAT_YCbCr_420_888
720 x 480 HAL_PIXEL_FORMAT_BLOB
640 x 512 HAL_PIXEL_FORMAT_YCbCr_420_888
640 x 512 HAL_PIXEL_FORMAT_BLOB
640 x 480 HAL_PIXEL_FORMAT_YCbCr_420_888
640 x 480 HAL_PIXEL_FORMAT_BLOB
640 x 400 HAL_PIXEL_FORMAT_YCbCr_420_888
640 x 400 HAL_PIXEL_FORMAT_BLOB
640 x 360 HAL_PIXEL_FORMAT_YCbCr_420_888
640 x 360 HAL_PIXEL_FORMAT_BLOB
352 x 288 HAL_PIXEL_FORMAT_YCbCr_420_888
352 x 288 HAL_PIXEL_FORMAT_BLOB
320 x 240 HAL_PIXEL_FORMAT_YCbCr_420_888
320 x 240 HAL_PIXEL_FORMAT_BLOB
240 x 320 HAL_PIXEL_FORMAT_YCbCr_420_888
240 x 320 HAL_PIXEL_FORMAT_BLOB
176 x 144 HAL_PIXEL_FORMAT_YCbCr_420_888
176 x 144 HAL_PIXEL_FORMAT_BLOB
4056 x 3040 HAL_PIXEL_FORMAT_RAW10
4056 x 3040 HAL_PIXEL_FORMAT_RAW12
4056 x 3040 HAL_PIXEL_FORMAT_RAW16
4056 x 3040 HAL_PIXEL_FORMAT_RAW_OPAQUE
ANDROID_SENSOR_INFO_SENSITIVITY_RANGE
min = 100
max = 35200
ANDROID_SENSOR_MAX_ANALOG_SENSITIVITY
2200
ANDROID_SENSOR_INFO_EXPOSURE_TIME_RANGE
min = 0ns
max = 243753000ns
====================================
Number of cameras detected: 1
====================================
voxl2:/$ voxl-camera-server
detected system image 1.7.10
using new imx412 defaults
detected system image 1.7.10
using new imx412 defaults
=================================================================
configuration for 4 cameras:
cam #0
name: tracking_front
sensor type: ar0144
isEnabled: 1
camId: 0
camId2: -1
fps: 30
en_rotate: 1
en_rotate2: 0
en_preview: 1
pre_width: 1280
pre_height: 800
en_raw_preview: 1
en_small_video: 0
small_video_width: -1
small_video_height: -1
en_large_video: 0
large_video_width: -1
large_video_height: -1
en_snapshot: 0
snap_width: -1
snap_height: -1
exif_focal_length: 0.000000
exif_focal_len_35mm_format:0
exif_fnumber: 0.000000
ae_mode: lme_msv
msv_exposure_min_us: 20
msv_exposure_max_us: 33000
standby_enabled: 0
decimator: 1
independent_exposure:0
cam #1
name: hires_front
sensor type: imx412
isEnabled: 1
camId: 1
camId2: -1
fps: 30
en_rotate: 0
en_rotate2: 0
en_preview: 0
pre_width: 640
pre_height: 480
en_raw_preview: 0
en_small_video: 1
small_video_width: 640
small_video_height: 480
en_large_video: 0
large_video_width: 4056
large_video_height: 3040
en_snapshot: 0
snap_width: 4056
snap_height: 3040
exif_focal_length: 3.100000
exif_focal_len_35mm_format:17
exif_fnumber: 1.240000
ae_mode: isp
msv_exposure_min_us: 20
msv_exposure_max_us: 33000
standby_enabled: 0
decimator: 1
independent_exposure:0
cam #2
name: hires_down
sensor type: imx412
isEnabled: 1
camId: 2
camId2: -1
fps: 30
en_rotate: 0
en_rotate2: 0
en_preview: 0
pre_width: 640
pre_height: 480
en_raw_preview: 0
en_small_video: 1
small_video_width: 640
small_video_height: 480
en_large_video: 1
large_video_width: 4056
large_video_height: 3040
en_snapshot: 1
snap_width: 4056
snap_height: 3040
exif_focal_length: 3.100000
exif_focal_len_35mm_format:17
exif_fnumber: 1.240000
ae_mode: isp
msv_exposure_min_us: 20
msv_exposure_max_us: 33000
standby_enabled: 0
decimator: 1
independent_exposure:0
cam #3
name: tracking_down
sensor type: ar0144
isEnabled: 1
camId: 3
camId2: -1
fps: 30
en_rotate: 0
en_rotate2: 0
en_preview: 1
pre_width: 1280
pre_height: 800
en_raw_preview: 1
en_small_video: 0
small_video_width: -1
small_video_height: -1
en_large_video: 0
large_video_width: -1
large_video_height: -1
en_snapshot: 0
snap_width: -1
snap_height: -1
exif_focal_length: 0.000000
exif_focal_len_35mm_format:0
exif_fnumber: 0.000000
ae_mode: lme_msv
msv_exposure_min_us: 20
msv_exposure_max_us: 33000
standby_enabled: 0
decimator: 1
independent_exposure:0
fsync_en: 1
fsync_gpio: 109
=================================================================
Starting Camera: tracking_front (id #0)
Connected to cpu-monitor
ERROR: Camera 0 failed to find supported preview config: 1280x800
WARNING: Failed to start cam tracking_front due to invalid resolution
WARNING: assuming cam is missing and trying to compensate
Starting Camera: hires_front (originally id #1) with id offset: 1
gbm_create_device(156): Info: backend name is: msm_drm
Starting Camera: hires_down (originally id #2) with id offset: 1
WARNING: cam hires_down (id 1) does not seem to be alive
Starting Camera: tracking_down (originally id #3) with id offset: 1
WARNING: cam tracking_down (id 2) does not seem to be alive
------ voxl-camera-server: Started 1 of 4 cameras
------ voxl-camera-server: Camera server is now running
C28 with tracking_front disabled:
voxl2:/$ voxl-camera-server -l
DEBUG: Attempting to open the hal module
DEBUG: SUCCESS: Camera module opened on attempt 0
DEBUG: ----------- Number of cameras: 1
DEBUG: Cam idx: 0, Cam slot: 2, Slave Address: 0x0034, Sensor Id: 0x0577
DEBUG: Note: This list comes from the HAL module and may not be indicative
DEBUG: of configurations that have full pipelines
DEBUG: Number of cameras: 1
====================================
Stats for camera: 0
ANDROID_SCALER_AVAILABLE_RAW_SIZES:
These are likely supported by the sensor
4056 x 3040
3840 x 2160
1920 x 1080
1920 x 1080
1920 x 1080
1280 x 720
1280 x 720
ANDROID_SCALER_AVAILABLE_STREAM_CONFIGURATIONS:
These are NOT necessarily supported by the sensor
4056 x 3040 HAL_PIXEL_FORMAT_YCbCr_420_888
4056 x 3040 HAL_PIXEL_FORMAT_BLOB
4000 x 3000 HAL_PIXEL_FORMAT_YCbCr_420_888
4000 x 3000 HAL_PIXEL_FORMAT_BLOB
3840 x 2160 HAL_PIXEL_FORMAT_YCbCr_420_888
3840 x 2160 HAL_PIXEL_FORMAT_BLOB
3264 x 2448 HAL_PIXEL_FORMAT_YCbCr_420_888
3264 x 2448 HAL_PIXEL_FORMAT_BLOB
3200 x 2400 HAL_PIXEL_FORMAT_YCbCr_420_888
3200 x 2400 HAL_PIXEL_FORMAT_BLOB
2976 x 2976 HAL_PIXEL_FORMAT_YCbCr_420_888
2976 x 2976 HAL_PIXEL_FORMAT_BLOB
2688 x 1512 HAL_PIXEL_FORMAT_YCbCr_420_888
2688 x 1512 HAL_PIXEL_FORMAT_BLOB
2592 x 1944 HAL_PIXEL_FORMAT_YCbCr_420_888
2592 x 1944 HAL_PIXEL_FORMAT_BLOB
2048 x 1536 HAL_PIXEL_FORMAT_YCbCr_420_888
2048 x 1536 HAL_PIXEL_FORMAT_BLOB
1920 x 1440 HAL_PIXEL_FORMAT_YCbCr_420_888
1920 x 1440 HAL_PIXEL_FORMAT_BLOB
1928 x 1208 HAL_PIXEL_FORMAT_YCbCr_420_888
1928 x 1208 HAL_PIXEL_FORMAT_BLOB
1920 x 1080 HAL_PIXEL_FORMAT_YCbCr_420_888
1920 x 1080 HAL_PIXEL_FORMAT_BLOB
1600 x 1200 HAL_PIXEL_FORMAT_YCbCr_420_888
1600 x 1200 HAL_PIXEL_FORMAT_BLOB
1440 x 1080 HAL_PIXEL_FORMAT_YCbCr_420_888
1440 x 1080 HAL_PIXEL_FORMAT_BLOB
1280 x 960 HAL_PIXEL_FORMAT_YCbCr_420_888
1280 x 960 HAL_PIXEL_FORMAT_BLOB
1280 x 800 HAL_PIXEL_FORMAT_YCbCr_420_888
1280 x 800 HAL_PIXEL_FORMAT_BLOB
1280 x 768 HAL_PIXEL_FORMAT_YCbCr_420_888
1280 x 768 HAL_PIXEL_FORMAT_BLOB
1280 x 720 HAL_PIXEL_FORMAT_YCbCr_420_888
1280 x 720 HAL_PIXEL_FORMAT_BLOB
1080 x 1080 HAL_PIXEL_FORMAT_YCbCr_420_888
1080 x 1080 HAL_PIXEL_FORMAT_BLOB
1024 x 738 HAL_PIXEL_FORMAT_YCbCr_420_888
1024 x 738 HAL_PIXEL_FORMAT_BLOB
1024 x 768 HAL_PIXEL_FORMAT_YCbCr_420_888
1024 x 768 HAL_PIXEL_FORMAT_BLOB
864 x 480 HAL_PIXEL_FORMAT_YCbCr_420_888
864 x 480 HAL_PIXEL_FORMAT_BLOB
800 x 600 HAL_PIXEL_FORMAT_YCbCr_420_888
800 x 600 HAL_PIXEL_FORMAT_BLOB
800 x 480 HAL_PIXEL_FORMAT_YCbCr_420_888
800 x 480 HAL_PIXEL_FORMAT_BLOB
720 x 1280 HAL_PIXEL_FORMAT_YCbCr_420_888
720 x 1280 HAL_PIXEL_FORMAT_BLOB
720 x 480 HAL_PIXEL_FORMAT_YCbCr_420_888
720 x 480 HAL_PIXEL_FORMAT_BLOB
640 x 512 HAL_PIXEL_FORMAT_YCbCr_420_888
640 x 512 HAL_PIXEL_FORMAT_BLOB
640 x 480 HAL_PIXEL_FORMAT_YCbCr_420_888
640 x 480 HAL_PIXEL_FORMAT_BLOB
640 x 400 HAL_PIXEL_FORMAT_YCbCr_420_888
640 x 400 HAL_PIXEL_FORMAT_BLOB
640 x 360 HAL_PIXEL_FORMAT_YCbCr_420_888
640 x 360 HAL_PIXEL_FORMAT_BLOB
352 x 288 HAL_PIXEL_FORMAT_YCbCr_420_888
352 x 288 HAL_PIXEL_FORMAT_BLOB
320 x 240 HAL_PIXEL_FORMAT_YCbCr_420_888
320 x 240 HAL_PIXEL_FORMAT_BLOB
240 x 320 HAL_PIXEL_FORMAT_YCbCr_420_888
240 x 320 HAL_PIXEL_FORMAT_BLOB
176 x 144 HAL_PIXEL_FORMAT_YCbCr_420_888
176 x 144 HAL_PIXEL_FORMAT_BLOB
4056 x 3040 HAL_PIXEL_FORMAT_RAW10
4056 x 3040 HAL_PIXEL_FORMAT_RAW12
4056 x 3040 HAL_PIXEL_FORMAT_RAW16
4056 x 3040 HAL_PIXEL_FORMAT_RAW_OPAQUE
ANDROID_SENSOR_INFO_SENSITIVITY_RANGE
min = 100
max = 35200
ANDROID_SENSOR_MAX_ANALOG_SENSITIVITY
2200
ANDROID_SENSOR_INFO_EXPOSURE_TIME_RANGE
min = 0ns
max = 243753000ns
====================================
Number of cameras detected: 1
====================================
voxl2:/$ voxl-camera-server
detected system image 1.7.10
using new imx412 defaults
detected system image 1.7.10
using new imx412 defaults
=================================================================
configuration for 4 cameras:
cam #0
name: tracking_front
sensor type: ar0144
isEnabled: 0
camId: 0
camId2: -1
fps: 30
en_rotate: 1
en_rotate2: 0
en_preview: 1
pre_width: 1280
pre_height: 800
en_raw_preview: 1
en_small_video: 0
small_video_width: -1
small_video_height: -1
en_large_video: 0
large_video_width: -1
large_video_height: -1
en_snapshot: 0
snap_width: -1
snap_height: -1
exif_focal_length: 0.000000
exif_focal_len_35mm_format:0
exif_fnumber: 0.000000
ae_mode: lme_msv
msv_exposure_min_us: 20
msv_exposure_max_us: 33000
standby_enabled: 0
decimator: 1
independent_exposure:0
cam #1
name: hires_front
sensor type: imx412
isEnabled: 1
camId: 1
camId2: -1
fps: 30
en_rotate: 0
en_rotate2: 0
en_preview: 0
pre_width: 640
pre_height: 480
en_raw_preview: 0
en_small_video: 1
small_video_width: 640
small_video_height: 480
en_large_video: 0
large_video_width: 4056
large_video_height: 3040
en_snapshot: 0
snap_width: 4056
snap_height: 3040
exif_focal_length: 3.100000
exif_focal_len_35mm_format:17
exif_fnumber: 1.240000
ae_mode: isp
msv_exposure_min_us: 20
msv_exposure_max_us: 33000
standby_enabled: 0
decimator: 1
independent_exposure:0
cam #2
name: hires_down
sensor type: imx412
isEnabled: 1
camId: 2
camId2: -1
fps: 30
en_rotate: 0
en_rotate2: 0
en_preview: 0
pre_width: 640
pre_height: 480
en_raw_preview: 0
en_small_video: 1
small_video_width: 640
small_video_height: 480
en_large_video: 1
large_video_width: 4056
large_video_height: 3040
en_snapshot: 1
snap_width: 4056
snap_height: 3040
exif_focal_length: 3.100000
exif_focal_len_35mm_format:17
exif_fnumber: 1.240000
ae_mode: isp
msv_exposure_min_us: 20
msv_exposure_max_us: 33000
standby_enabled: 0
decimator: 1
independent_exposure:0
cam #3
name: tracking_down
sensor type: ar0144
isEnabled: 1
camId: 3
camId2: -1
fps: 30
en_rotate: 0
en_rotate2: 0
en_preview: 1
pre_width: 1280
pre_height: 800
en_raw_preview: 1
en_small_video: 0
small_video_width: -1
small_video_height: -1
en_large_video: 0
large_video_width: -1
large_video_height: -1
en_snapshot: 0
snap_width: -1
snap_height: -1
exif_focal_length: 0.000000
exif_focal_len_35mm_format:0
exif_fnumber: 0.000000
ae_mode: lme_msv
msv_exposure_min_us: 20
msv_exposure_max_us: 33000
standby_enabled: 0
decimator: 1
independent_exposure:0
fsync_en: 1
fsync_gpio: 109
=================================================================
Skipping Camera: tracking_front, configuration marked disabled
Starting Camera: hires_front (id #1)
WARNING: cam hires_front (id 1) does not seem to be alive
Starting Camera: hires_down (id #2)
WARNING: cam hires_down (id 2) does not seem to be alive
Starting Camera: tracking_down (id #3)
WARNING: cam tracking_down (id 3) does not seem to be alive
ERROR: failed to initialize any cameras
------ voxl-camera-server: Started 0 of 4 cameras
------ voxl-camera-server: Camera server is now running
------ voxl-camera-server: Camera server is now stopping
Connected to cpu-monitor
------ voxl-camera-server: Camera server exited gracefully, returning -1
@jcai said in VOXL2 Camera Configuration not found:
@tom I just flashed 1.3.5 and was able to configure C28. However, there still seems to be an issue.
My camera is connected to J5 on the breakout, which should be hires_down. Using
voxl-inspect-cam, the camera shows up as hires_front.Furthermore, if I disable just tracking_front in the camera server config file, the server will fail to initialize hires_front. Since I only have one camera physically connected, the camera server will not find any cameras and fail to start.
Thanks Travis, I was able to get a build with the correct configuration options as well as my own changes. However, the issues I described above are still present. Could this be a hardware fault?
Also, I have a custom kernel build (that wasn't being used during my issues in my last comment) created by following this guide: https://docs.modalai.com/voxl2-kernel-build-guide/
The only change I made in this kernel was to enable CONFIG_MACVLAN=y by editing kona-perf_defconfig in
apps_proc/poky/meta-voxl2-bsp/recipes-kernel/linux-msm/files/configs/m0054
However, as you said, this kernel version doesn't support the M0173 breakout board. How do I build a version that does while also adding my macvlan config?
@tom I just flashed 1.3.5 and was able to configure C28. However, there still seems to be an issue.
My camera is connected to J5 on the breakout, which should be hires_down. Using voxl-inspect-cam, the camera shows up as hires_front.
Furthermore, if I disable just tracking_front in the camera server config file, the server will fail to initialize hires_front. Since I only have one camera physically connected, the camera server will not find any cameras and fail to start.
Hello,
I'm using a VOXL2 (board only), a micro-coax camera adapter (M0173), and an IMX412 (M0161).
I'm following the documentation here. When configuring SKU, I can set 20 for VOXL2-board-only but camera configurations 26-30 don't appear. The same is true if I run voxl-configure-camera.
Any ideas as to the cause? All components are connected to the VOXL already.
VOXL currently thinks it is in the following hardware:
family code: MCCA-M0054 (voxl2-board-only)
compute board: 4 (voxl2)
hw version: 1
cam config: 0
modem config: ()
tx config: ()
extras config: ()
SKU: MCCA-M0054-C0-M0-X0
If this is what you want, select 1 (accept and continue) to
leave it as-is. Otherwise, select the desired product family:
1) accept and continue 12) voxlcam
2) starling-2 13) seeker
3) starling-2-max 14) rb5-flight
4) starling 15) flight-deck
5) px4-autonomy-dev-kit 16) voxl-deck
6) sentinel 17) voxl2-flight-deck
7) fpv 18) voxl2-test-fixture
8) D0010 19) voxl2-mini-test-fixture
9) stinger 20) voxl2-board-only
10) D0015 21) voxl2-mini-board-only
11) m500 22) quit
#? 20
selected voxl2-board-only
------------------------------------------------------------------
If you would like to select a special camera config that differs
from the default for your product family, please select an option.
Simply hit ENTER to use the default
01 - ov7251 tracking ov7251 stereo
02 - ov7251 tracking
03 - ov7251 tracking ov7251 stereo imx214 hires
04 - ov7251 tracking imx214 hires
05 - pmd-tof ov7251 tracking
06 - D0005 Starling pmd-tof imx214 hires ov7251 tracking
08 - imx214
09 - pmd-tof
10 - ov7251 stereo
11 - D0006 Sentinel
12 - ov9782 stereo
13 - ov9782 stereo imx214 hires
14 - ov9782 stereo pmd-tof ov7251 tracking (copy)
15 - D0008 dual 9782 tracking
16 - pmd-tof ov7251 dual tracking imx214 hires
17 - D0010 pmd-tof imx412 hires ov7251 tracking ov9782 stereo
18 - D0008 triple ov9782
19 - D0005 without tof imx214 hires ov7251 tracking
20 - D0011 imx412 hires ar0144 tracking
21 - old C6
22 - D0013 voxl2 mini dual ar0144
23 - D0010 without stereo
24 - pmd-tof LIOW2 (new TOF)
25 - dual ar0144
31 - D0013 COAX dual ar0144 tracking
32 - D0008 triple ov9782 rotated
C - use user-defined custom camera config in
(/data/modalai/custom_camera_config.txt)
q - Quit The Wizard
Simply hit ENTER to use the default
selection: ^C
Thanks,
Josh
@Alex-Kushleyev Yup, editing kona-perf_defconfig looks to have worked, thanks!
@Alex-Kushleyev I think this is just an issue with Windows drivers. I ended up switching over to OSX to use adb and fastboot, no issues there. I'm just using a USB drive to get the .img file from the VM to the Mac. Boot tests look good.
One more thing, I'm looking at the kernel build guide and there's a section that says I can enable in tree drivers by editing:
apps_proc/poky/meta-voxl2-bsp/recipes-kernel/linux-msm/files/m005x.cfg
I don't have this file in my system. the closest I found is ../linux-msm/files/configs/m0054. In this directory, there's kona_defconfig and kona-perf_defconfig. What's the difference between these two files? Are these the correct files to be editing to enable, for example, CONFIG_MACVLAN?
@Alex-Kushleyev I've managed to get the build working, thanks! I think the problems started because my initial docker image was built with sudo. Removing the workspace folder and starting from scratch got everything set up as user.
I'm now attempting to test the build using:
adb reboot bootloader
fastboot boot your_new_kernel.img
Are there specific drivers I need to download? Once I put the voxl into bootloader, VirtualBox can't detect the device anymore. The same is true on my Windows host. As a result, running fastboot boot new_kernel.img gives me a constant <waiting for any device> message. As reference, here's my device manager during normal and bootloader modes. The "Android" device also comes and goes. It usually exists for a couple seconds before disappearing.
On the host:
jcai@jcai-VirtualBox:~/qrb5165-kernel-build-docker/workspace/lu.um.1.2.1/apps_proc$ ls -lah
total 48K
drwxr-xr-x 8 root root 4.0K Oct 9 15:42 .
drwxr-xr-x 3 root root 4.0K Oct 8 13:03 ..
drwxrwxr-x 2 1001 1001 20K Aug 23 2022 deb_premirror_packages
drwxr-xr-x 5 root root 4.0K Oct 8 17:27 disregard
drwxr-xr-x 2 root root 4.0K Oct 9 09:49 downloads
drwxr-xr-x 34 root root 4.0K Oct 9 15:25 poky
drwxr-xr-x 7 root root 4.0K Oct 9 15:23 .repo
lrwxrwxrwx 1 root root 27 Oct 8 17:33 setup-environment -> poky/qti-conf/set_bb_env.sh
drwxr-xr-x 25 root root 4.0K Oct 8 17:31 src
In Docker:
user@8de0065c2813:~/build_mount/lu.um.1.2.1/apps_proc$ ls -lah
total 48K
drwxr-xr-x 8 root root 4.0K Oct 9 19:42 .
drwxr-xr-x 3 root root 4.0K Oct 8 17:03 ..
drwxrwxr-x 2 1001 1001 20K Aug 23 2022 deb_premirror_packages
drwxr-xr-x 5 root root 4.0K Oct 8 21:27 disregard
drwxr-xr-x 2 root root 4.0K Oct 9 13:49 downloads
drwxr-xr-x 34 root root 4.0K Oct 9 19:25 poky
drwxr-xr-x 7 root root 4.0K Oct 9 19:23 .repo
lrwxrwxrwx 1 root root 27 Oct 8 21:33 setup-environment -> poky/qti-conf/set_bb_env.sh
drwxr-xr-x 25 root root 4.0K Oct 8 21:31 src
Yeah, ownership looks like an issue here
@Alex-Kushleyev I was only able to follow the guide exactly until I got into the container. From there , all the scripts inside were run with sudo. Otherwise, I would get permission issues like below.
@Alex-Kushleyev I'm having some issues with building the kernel. I'm running the latest Ubuntu in VirtualBox (on Windows) for this. In the container, the sync and patch scripts run without issue but when building as root, I get the following error:
If I run build without sudo, I get access permission issues:
@Zachary-Lowell-0 I'm on Docker 24.0.2
So I was reading through the kernel build guide, and I saw an example that enabled smsc95xx by modifying the m005x.cfg file (CONFIG_USB_NET_SMSC95XX=y).
From what I can tell by reading through the IPVLAN docs, it's much the same steps to enable it (CONFIG_IPVLAN=y or CONFIG_IPVLAN=m). So it looks like it should be safe? Is this still something you would advise against? Also, would there be any issues with running all of the build stuff on MacOS?
Hello,
I'm trying to set up a Docker network with an ipvlan driver. The network starts without issue, but when creating the container, I'm getting the following error:
Error response from daemon: failed to create the ipvlan port: operation not supported
Unfortunately, I haven't been able to find much about this error, so currently the only lead I have has to do with the Linux kernel version. The Docker docs says:
Kernel requirements:
IPvlan Linux kernel v4.2+ (support for earlier kernels exists but is buggy). To check your current kernel version, use uname -r
I see that my current version is 4.19.125. Is there a way to upgrade? I'm fairly new to Linux so reading through the VOXL2 Kernel Build Guide hasn't been very helpful to me.
Thanks!
Update: running
voxl2:/$ ip link add link eth0 name ipvlan-test type ipvlan
RTNETLINK answers: Operation not supported
It looks like I might be missing a module? Not sure there
@Eric-Katzfey There might be something about networking that I'm not understanding here.
voxl-streamer by default streams RTSP to <IP>:8900, so for me I can see the stream by going to rtsp://192.168.1.222:8900/live
Just changing the port to 9976 doesn't equate to udp @ 127.0.0.1:9976, does it?
@Moderator Am I able to specify the IP and port that the stream from voxl-streamer is sent to? Since the third-party software encodes and writes to UDP:127.0.0.1:9976, I'm wondering if it's possible to direct voxl-streamer straight there instead
Hello, I'm somewhat new to video streaming, networking, and Linux development. I'm working on a VOXL2 running voxl-suite 1.3.4~beta3. In addition, I have an M0173 breakout connected with two M0166 tracking and two M0161 Hires cameras. My current project will only use one of the Hires cameras. I've been able to successfully stream the Hires cam over RTSP using voxl-streamer as a sanity check.
However, my project involves third-party (whom I'm able to contact) software onboard that uses ffmpeg to encode and compress video from /dev/video0 and write it to UDP:127.0.0.1:9976. Is it possible for me to direct the Hires camera to video0 for the software to use? From what I've read, the camera can't be accessed directly via video0 (hence the use of voxl-camera-server). Are there any workarounds here?