<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[VOXL2 didn&#x27;t detect IMX412 Camera]]></title><description><![CDATA[<ol>
<li>Hardware Configuration</li>
</ol>
<ul>
<li>VOXL2 QRB5165M ( * 2)</li>
<li>IMX412 camera module (M0107) ( * 2)</li>
<li>Tested both with and without the extension cable (M0036) ( * 2)</li>
<li>Using official connectors, ports, and cables</li>
</ul>
<p dir="auto"><img src="/assets/uploads/files/1748420062114-dc6cad0f-4721-4aff-8ce3-7a315fe84a31-image.png" alt="dc6cad0f-4721-4aff-8ce3-7a315fe84a31-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto"><img src="/assets/uploads/files/1748420094905-6d7d0586-3184-44b9-8af6-6c914434adc7-image.png" alt="6d7d0586-3184-44b9-8af6-6c914434adc7-image.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Questions</p>
<ol>
<li>
<p dir="auto">With a direct connection (without an extension cable), given that voxl-camera-server -l detects one camera, but dmesg shows sensor ID read failures, could my hardware setup (connectors, pinout, cable integrity, extension cable) still be the root cause, despite the initial detection?</p>
</li>
<li>
<p dir="auto">Do the repeated I2C errors (read id: 0x0 expected id 0x356) strongly indicate a faulty IMX412 sensor, or is it more likely a persistent cable/connection issue that dmesg is reflecting?</p>
</li>
<li>
<p dir="auto">Are there any further diagnostic steps or voxl- tools I can use to specifically debug I2C communication with the camera sensor on the VOXL2, especially given the ERROR: object missing misp_channels message from voxl-camera-server?</p>
</li>
<li>
<p dir="auto">Are there any known compatibility issues or specific driver/firmware quirks with the IMX412 (M0107) on VOXL2, particularly with the configuration I'm using or when using the M0036 extension cable? I suspected a hardware issue, so I tried swapping out the board, cable, and camera with a spare set I have, but the problem persists.</p>
</li>
</ol>
<p dir="auto"><img src="/assets/uploads/files/1748420205055-3ee9f85d-3c7c-4d93-9ca8-fe433780cd74-image.png" alt="3ee9f85d-3c7c-4d93-9ca8-fe433780cd74-image.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.modalai.com/topic/4461/voxl2-didn-t-detect-imx412-camera</link><generator>RSS for Node</generator><lastBuildDate>Sun, 07 Jun 2026 08:37:17 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/topic/4461.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 28 May 2025 08:16:49 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to VOXL2 didn&#x27;t detect IMX412 Camera on Wed, 11 Jun 2025 23:25:50 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.modalai.com/uid/7">@Alex-Kushleyev</a></p>
<p dir="auto">The issue has been resolved. Thank you for your help.</p>
]]></description><link>https://forum.modalai.com/post/22575</link><guid isPermaLink="true">https://forum.modalai.com/post/22575</guid><dc:creator><![CDATA[ysc]]></dc:creator><pubDate>Wed, 11 Jun 2025 23:25:50 GMT</pubDate></item><item><title><![CDATA[Reply to VOXL2 didn&#x27;t detect IMX412 Camera on Thu, 05 Jun 2025 03:08:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.modalai.com/uid/3077">@ysc</a> ,</p>
<p dir="auto">I am sorry, the camera ID vs slot ID may be a bit confusing when you first start playing with camera configurations.</p>
<p dir="auto">In your case you only have one camera plugged into Camera Hardware Slot 2, (so you use the sensormodule with index 2), but once the cameras are detected by the system, they are assigned with <code>camera id</code>s which start with 0. So in your configuration file, you need to set <code>camera_id</code> to <code>0</code> and it should be called <code>camera_id</code>, not <code>camId</code>.  -- you actually have both of those, so please remove <code>camId</code> and <code>camId2</code> entries, and just set <code>camera_id</code> to 0.</p>
<p dir="auto">You also have some duplicate (incorrectly named) parameters such as <code>pre_width</code> and <code>pre_height</code> -- the correct ones are <code>preview_width</code> and <code>preview_height</code>, which are also there. I think you probably got those from the information that camera server prints out when it starts, which actually does not use correct parameter names, such as <code>camId</code> and <code>pre_width</code>, etc... We should fix that..</p>
<p dir="auto">Alex</p>
]]></description><link>https://forum.modalai.com/post/22465</link><guid isPermaLink="true">https://forum.modalai.com/post/22465</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 05 Jun 2025 03:08:44 GMT</pubDate></item><item><title><![CDATA[Reply to VOXL2 didn&#x27;t detect IMX412 Camera on Wed, 04 Jun 2025 05:19:35 GMT]]></title><description><![CDATA[<p dir="auto">Hello, <a class="plugin-mentions-user plugin-mentions-a" href="https://forum.modalai.com/uid/7">@Alex-Kushleyev</a></p>
<p dir="auto">I'm having an issue where the IMX412 camera connected to J7L (camera slot 2) is detected but the camera server fails to start.</p>
<ul>
<li>
<p dir="auto">Solutions Already Attempted:<br />
a) Sensor Module File Modification:<br />
- Copied /usr/share/modalai/chi-cdk/imx412-fpv/com.qti.sensormodule.imx412_fpv_2.bin to<br />
- /usr/lib/camera/ directory</p>
<p dir="auto">b) Configuration File Modification:<br />
- In /etc/modalai/voxl-camera-server.conf<br />
- Set camId and camera_id to 2<br />
- Disabled MISP-related settings (en_misp: false, misp_venc_enable: false)</p>
</li>
<li>
<p dir="auto">Current Status:</p>
<p dir="auto">a) Camera Sensor Detection Status:<br />
- Successfully detected (sensor_id:0x577)<br />
- CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:2,slave_addr:0x34,sensor_id:0x577</p>
<p dir="auto">b) Camera Server Status:<br />
● voxl-camera-server.service - voxl-camera-server<br />
Loaded: loaded (/usr/bin/voxl-camera-server; enabled; vendor preset: enabled)<br />
Active: failed (Result: exit-code) since Wed 2025-06-04 05:05:08 UTC; 9min ago<br />
Process: 7181 ExecStart=/usr/bin/voxl-camera-server (code=exited, status=255)<br />
Main PID: 7181 (code=exited, status=255)</p>
<p dir="auto">c) Camera Server Logs:<br />
- ERROR: object missing misp_channels (I understand this error is not fatal)<br />
- Userspace process termination warning:<br />
CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died</p>
<p dir="auto">d) Sensor Module Files Status:<br />
total 5364<br />
-rwxr-xr-x 1 root root   9912 Nov 11  2024 com.qti.eeprom.cmk_imx577.so<br />
-rwxr-xr-x 1 root root   9912 Nov 11  2024 com.qti.sensor.imx412_fpv.so<br />
-rw-r--r-- 1 root root  97304 Jun  4 04:50 com.qti.sensormodule.imx412_fpv_2.bin<br />
-rw-r--r-- 1 root root 957344 Nov 11  2024 com.qti.tuned.cmk_imx577.bin<br />
-rw-r--r-- 1 root root 835464 Nov 11  2024 com.qti.tuned.cmk_ov9282.bin<br />
-rw-r--r-- 1 root root 931864 Nov 11  2024 com.qti.tuned.default.bin<br />
-rw-r--r-- 1 root root 957344 Nov 11  2024 com.qti.tuned.imx412_fpv.bin<br />
-rw-r--r-- 1 root root 793816 Nov 11  2024 com.qti.tuned.ov9782.bin<br />
-rw-r--r-- 1 root root 882376 Nov 11  2024 com.qti.tuned.sony_imx335.bin<br />
drwxr-xr-x 2 root root   4096 Nov 11  2024 components</p>
<p dir="auto">e) Current Configuration File Content:<br />
{<br />
"cameras": [<br />
{<br />
"name": "hires",<br />
"type": "imx412",<br />
"enabled": true,<br />
"camId": 2,<br />
"camId2": -1,<br />
"fps": 30,<br />
"en_rotate": 0,<br />
"en_rotate2": 0,<br />
"en_preview": false,<br />
"pre_width": 640,<br />
"pre_height": 480,<br />
"en_raw_preview": false,<br />
"en_small_video": true,<br />
"small_video_width": 640,<br />
"small_video_height": 480,<br />
"en_large_video": false,<br />
"large_video_width": 4056,<br />
"large_video_height": 3040,<br />
"en_misp": false,<br />
"misp_width": 4056,<br />
"misp_height": 3040,<br />
"en_snapshot": false,<br />
"snap_width": 4056,<br />
"snap_height": 3040,<br />
"exif_focal_length": 3.1,<br />
"exif_focal_len_35mm_format": 17,<br />
"exif_fnumber": 1.24,<br />
"ae_mode": "isp",<br />
"msv_exposure_min_us": 20,<br />
"msv_exposure_max_us": 33000,<br />
"gain_min": 54,<br />
"gain_max": 8000,<br />
"standby_enabled": false,<br />
"decimator": 1,<br />
"independent_exposure": false,<br />
"camera_id": 2,<br />
"preview_width": 640,<br />
"preview_height": 480,<br />
"small_venc_mode": "h264",<br />
"small_venc_br_ctrl": "cqp",<br />
"small_venc_Qfixed": 30,<br />
"small_venc_Qmin": 15,<br />
"small_venc_Qmax": 40,<br />
"small_venc_nPframes": 9,<br />
"small_venc_mbps": 2,<br />
"small_venc_osd": false,<br />
"large_venc_mode": "h264",<br />
"large_venc_br_ctrl": "cqp",<br />
"large_venc_Qfixed": 40,<br />
"large_venc_Qmin": 15,<br />
"large_venc_Qmax": 50,<br />
"large_venc_nPframes": 29,<br />
"large_venc_mbps": 40,<br />
"large_venc_osd": false,<br />
"en_snapshot_width": 4056,<br />
"en_snapshot_height": 3040,<br />
"exif_focal_length_in_35mm_format": 17,<br />
"snapshot_jpeg_quality": 75,<br />
"misp_venc_enable": false,<br />
"misp_venc_mode": "none",<br />
"misp_venc_br_ctrl": "cqp",<br />
"misp_venc_Qfixed": 38,<br />
"misp_venc_Qmin": 15,<br />
"misp_venc_Qmax": 50,<br />
"misp_venc_nPframes": 29,<br />
"misp_venc_mbps": 30,<br />
"misp_venc_osd": false,<br />
"misp_awb": "auto",<br />
"misp_gamma": 1.6<br />
}<br />
],<br />
"fsync_en": false,<br />
"fsync_gpio": 109<br />
}</p>
</li>
<li>
<p dir="auto">Problem Summary:</p>
<ul>
<li>Camera sensor is successfully detected (sensor_id:0x577)</li>
<li>Correct sensor module file (imx412_fpv_2.bin) is installed</li>
<li>Configuration file has camId and camera_id both set to 2</li>
<li>MISP-related settings are all disabled</li>
<li>However, camera server fails to start and userspace process terminates</li>
</ul>
</li>
<li>
<p dir="auto">Additional Attempts Made:</p>
<ul>
<li>Restarted camera server (systemctl restart voxl-camera-server)</li>
<li>Ran in debug mode (voxl-camera-server -d)</li>
<li>Checked system logs (dmesg | grep -i cam)</li>
<li>Disabled MISP-related settings</li>
</ul>
</li>
</ul>
<p dir="auto">Are there any additional suggestions or things I should check to resolve this issue?</p>
]]></description><link>https://forum.modalai.com/post/22449</link><guid isPermaLink="true">https://forum.modalai.com/post/22449</guid><dc:creator><![CDATA[ysc]]></dc:creator><pubDate>Wed, 04 Jun 2025 05:19:35 GMT</pubDate></item><item><title><![CDATA[Reply to VOXL2 didn&#x27;t detect IMX412 Camera on Fri, 30 May 2025 16:20:55 GMT]]></title><description><![CDATA[<p dir="auto">Since your camera is plugged into J7 using M0076 , that would mean it is using J7L (lower) camera port, which is lot id 2, however the sensormodule you have in <code>/usr/lib/camera</code> is <code>com.qti.sensormodule.imx412_fpv_1.bin</code>, which means it is for slot id 1 (number at the end corresponds to the slot id). you replace that with <code>com.qti.sensormodule.imx412_fpv_2.bin</code> , which you can find inside <code>/usr/share/modalai/chi-cdk/imx412-fpv</code> -- the <code>chi-cdk</code> location is used to store all possible supported camera drivers (sensormodules).</p>
<p dir="auto">Do not worry about the following print statement, it is not fatal : <code>ERROR: object missing misp_channels</code></p>
<p dir="auto">Alex</p>
]]></description><link>https://forum.modalai.com/post/22398</link><guid isPermaLink="true">https://forum.modalai.com/post/22398</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Fri, 30 May 2025 16:20:55 GMT</pubDate></item><item><title><![CDATA[Reply to VOXL2 didn&#x27;t detect IMX412 Camera on Fri, 30 May 2025 05:19:17 GMT]]></title><description><![CDATA[<p dir="auto">Thank you, <a class="plugin-mentions-user plugin-mentions-a" href="https://forum.modalai.com/uid/7">@Alex-Kushleyev</a> I'm attaching additional test results and logs.</p>
<p dir="auto">In /usr/lib/camera/, only IMX412-related sensormodule files were kept; others were deleted.<br />
/etc/modalai/voxl-camera-server.conf was configured for a single IMX412 (hires) camera.<br />
voxl-camera-server was run in both foreground and debug modes.</p>
<p dir="auto">I'm wondering if there are any additional areas I should check, or if there are any known issues related to the IMX412 (M0107) module, slot, or firmware. Also, if anyone has resolved similar symptoms, please share your experience.</p>
<p dir="auto">voxl2:/$ dmesg | grep -i cam<br />
[    0.000000] OF: reserved mem: initialized node pil_camera_region@86200000, compatible id removed-dma-pool<br />
[    1.744872] msm-bus-type slv-qhs-camera-cfg: Linked as a consumer to regulator.34<br />
[    1.747294] cam_cc-kona ad00000.qcom,camcc: Linked as a consumer to regulator.1<br />
[    1.747302] cam_cc-kona ad00000.qcom,camcc: Linked as a consumer to regulator.34<br />
[    1.747355] register_client_adhoc:Client handle 25 clk_camcc_debugfs<br />
[    1.752561] cam_cc-kona ad00000.qcom,camcc: Registered CAM CC clocks<br />
[    1.923626] synx: registered bind ops for cam_sync<br />
[    1.923813] msm_cam_smmu soc:qcom,cam_smmu:msm_cam_smmu_ife: Linked as a consumer to 15000000.apps-smmu<br />
[    1.923944] iommu: Adding device soc:qcom,cam_smmu:msm_cam_smmu_ife to group 27<br />
[    1.924130] msm_cam_smmu soc:qcom,cam_smmu:msm_cam_smmu_jpeg: Linked as a consumer to 15000000.apps-smmu<br />
[    1.924236] iommu: Adding device soc:qcom,cam_smmu:msm_cam_smmu_jpeg to group 28<br />
[    1.924316] platform soc:qcom,cam_smmu:msm_cam_icp_fw: assigned reserved memory node pil_camera_region@86200000<br />
[    1.924446] msm_cam_smmu soc:qcom,cam_smmu:msm_cam_smmu_icp: Linked as a consumer to 15000000.apps-smmu<br />
[    1.924595] iommu: Adding device soc:qcom,cam_smmu:msm_cam_smmu_icp to group 29<br />
[    1.924667] CAM_INFO: CAM-SMMU: cam_smmu_get_memory_regions_info: 3730 [icp] : Discard region specified [0xdff00000 0xe0200000] in [0x10c00000 0xfef00000]<br />
[    1.924754] msm_cam_smmu soc:qcom,cam_smmu:msm_cam_smmu_cpas_cdm: Linked as a consumer to 15000000.apps-smmu<br />
[    1.924858] iommu: Adding device soc:qcom,cam_smmu:msm_cam_smmu_cpas_cdm to group 30<br />
[    1.925051] msm_cam_smmu soc:qcom,cam_smmu:msm_cam_smmu_fd: Linked as a consumer to 15000000.apps-smmu<br />
[    1.925153] iommu: Adding device soc:qcom,cam_smmu:msm_cam_smmu_fd to group 31<br />
[    1.925464] cam-cpas ac40000.qcom,cam-cpas: Linked as a consumer to regulator.79<br />
[    1.926382] register_client_adhoc:Client handle 57 cam_ahb<br />
[    1.926493] register_client_adhoc:Client handle 58 cam_hf_0_mnoc<br />
[    1.926608] register_client_adhoc:Client handle 59 cam_sf_0_mnoc<br />
[    1.926711] register_client_adhoc:Client handle 60 cam_sf_icp_mnoc<br />
[    1.927795] msm_cam_cdm ac4d000.qcom,cpas-cdm0: Linked as a consumer to regulator.79<br />
[    1.929515] cam_vfe acb4000.qcom,ife0: Linked as a consumer to regulator.79<br />
[    1.929526] cam_vfe acb4000.qcom,ife0: Linked as a consumer to regulator.75<br />
[    1.930316] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input<br />
[    1.930322] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top<br />
[    1.930801] cam_vfe acc3000.qcom,ife1: Linked as a consumer to regulator.79<br />
[    1.930812] cam_vfe acc3000.qcom,ife1: Linked as a consumer to regulator.76<br />
[    1.931564] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input<br />
[    1.931569] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top<br />
[    1.932027] CAM_INFO: CAM-UTIL: cam_soc_util_get_option_clk_by_name: 559 No clk data for ife_dsp_clk<br />
[    1.932030] CAM_WARN: CAM-ISP: cam_vfe_init_soc_resources: 154 Option clk get failed with rc -22<br />
[    1.932044] cam_vfe acd9000.qcom,ife-lite0: Linked as a consumer to regulator.79<br />
[    1.932560] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input<br />
[    1.932564] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top<br />
[    1.932942] CAM_INFO: CAM-UTIL: cam_soc_util_get_option_clk_by_name: 559 No clk data for ife_dsp_clk<br />
[    1.932945] CAM_WARN: CAM-ISP: cam_vfe_init_soc_resources: 154 Option clk get failed with rc -22<br />
[    1.932959] cam_vfe acdb200.qcom,ife-lite1: Linked as a consumer to regulator.79<br />
[    1.933444] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input<br />
[    1.933448] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top<br />
[    1.933869] CAM_INFO: CAM-UTIL: cam_soc_util_get_option_clk_by_name: 559 No clk data for ife_dsp_clk<br />
[    1.933872] CAM_WARN: CAM-ISP: cam_vfe_init_soc_resources: 154 Option clk get failed with rc -22<br />
[    1.933885] cam_vfe acdd400.qcom,ife-lite2: Linked as a consumer to regulator.79<br />
[    1.934365] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input<br />
[    1.934370] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top<br />
[    1.934746] CAM_INFO: CAM-UTIL: cam_soc_util_get_option_clk_by_name: 559 No clk data for ife_dsp_clk<br />
[    1.934749] CAM_WARN: CAM-ISP: cam_vfe_init_soc_resources: 154 Option clk get failed with rc -22<br />
[    1.934763] cam_vfe acdf600.qcom,ife-lite3: Linked as a consumer to regulator.79<br />
[    1.935243] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input<br />
[    1.935248] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top<br />
[    1.935624] CAM_INFO: CAM-UTIL: cam_soc_util_get_option_clk_by_name: 559 No clk data for ife_dsp_clk<br />
[    1.935627] CAM_WARN: CAM-ISP: cam_vfe_init_soc_resources: 154 Option clk get failed with rc -22<br />
[    1.935642] cam_vfe ace1800.qcom,ife-lite4: Linked as a consumer to regulator.79<br />
[    1.936135] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input<br />
[    1.936140] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top<br />
[    1.936616] CAM_ERR: CAM-ISP: cam_ife_hw_mgr_init: 8806 Offline IFE thresholds max 720000000 nom 560000000  min360000000<br />
[    1.936619] CAM_ERR: CAM-ISP: cam_ife_hw_mgr_init: 8806 Offline IFE thresholds max 720000000 nom 560000000  min360000000<br />
[    1.936707] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936720] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936733] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936746] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936758] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936771] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936783] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936795] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936808] CAM_ERR: CAM-ISP: cam_isp_context_debug_register: 5406 failed to create dentry<br />
[    1.936811] CAM_INFO: CAM-ISP: cam_isp_dev_probe: 163 Camera ISP probe complete<br />
[    1.937013] CAM_INFO: CAM: cam_res_mgr_probe: 685 Enable shared gpio support.<br />
[    1.937173] cam-cci-driver ac4f000.qcom,cci: Linked as a consumer to regulator.79<br />
[    1.937669] CAM_INFO: CAM-CCI: cam_cci_platform_probe: 454 Device Type :0<br />
[    1.937751] cam-cci-driver ac50000.qcom,cci: Linked as a consumer to regulator.79<br />
[    1.938064] CAM_INFO: CAM-CCI: cam_cci_platform_probe: 454 Device Type :1<br />
[    1.938203] cam-csiphy-driver ac6a000.qcom,csiphy: Linked as a consumer to regulator.79<br />
[    1.938217] cam-csiphy-driver ac6a000.qcom,csiphy: Linked as a consumer to regulator.61<br />
[    1.938257] cam-csiphy-driver ac6c000.qcom,csiphy: Linked as a consumer to regulator.79<br />
[    1.938267] cam-csiphy-driver ac6c000.qcom,csiphy: Linked as a consumer to regulator.61<br />
[    1.938305] cam-csiphy-driver ac6e000.qcom,csiphy: Linked as a consumer to regulator.79<br />
[    1.938320] cam-csiphy-driver ac6e000.qcom,csiphy: Linked as a consumer to regulator.61<br />
[    1.938361] cam-csiphy-driver ac70000.qcom,csiphy: Linked as a consumer to regulator.79<br />
[    1.938371] cam-csiphy-driver ac70000.qcom,csiphy: Linked as a consumer to regulator.61<br />
[    1.938406] cam-csiphy-driver ac72000.qcom,csiphy: Linked as a consumer to regulator.79<br />
[    1.938416] cam-csiphy-driver ac72000.qcom,csiphy: Linked as a consumer to regulator.61<br />
[    1.938456] cam-csiphy-driver ac74000.qcom,csiphy: Linked as a consumer to regulator.79<br />
[    1.938466] cam-csiphy-driver ac74000.qcom,csiphy: Linked as a consumer to regulator.61<br />
[    1.939318] CAM_WARN: CAM-ICP: cam_a5_get_dt_properties: 46 QoS need not be set<br />
[    1.939336] cam-a5 ac00000.qcom,a5: Linked as a consumer to regulator.79<br />
[    1.939460] cam-ipe ac9a000.qcom,ipe0: Linked as a consumer to regulator.77<br />
[    1.939580] cam-bps ac7a000.qcom,bps: Linked as a consumer to regulator.74<br />
[    1.940484] cam-jpeg-enc ac53000.qcom,jpegenc: Linked as a consumer to regulator.79<br />
[    1.940605] cam-jpeg-dma ac57000.qcom,jpegdma: Linked as a consumer to regulator.79<br />
[    1.941031] CAM_INFO: CAM-JPEG: cam_jpeg_dev_probe: 162 Camera JPEG probe complete<br />
[    1.941167] cam_fd_hw ac5f000.qcom,fd: Linked as a consumer to regulator.79<br />
[    2.045399] CAM_ERR: CAM-CCI: cam_cci_assign_fops: 528 Invalid dev node:00000000bc36af2d offset: 0<br />
[    2.046187] cam_cc_sleep_clk_src: CXO configuration failed<br />
[    6.693838] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]<br />
[    6.703981] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079,OEM_IMAGE_VERSION_STRING=CRM,BUILD_TIME: Oct 17 2019 05:49:19,CACHE_ENABLED at icphostinterface.c:636 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[    6.703985] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :ELF variant: CACHE-ENABLED:T480:API_V2:USE_CDM_1_1: , API version: 0x2000049 at icphostinterface.c:637 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[    6.704146] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully<br />
[    6.808437] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58<br />
[    6.808543] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60<br />
[    6.808588] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.56<br />
[    6.808688] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79<br />
[    6.823354] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000<br />
[    6.823383] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:<br />
[    6.823389] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22<br />
[    6.823393] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22<br />
[    6.823398] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:<br />
[    6.823470] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79<br />
[    6.825555] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.56<br />
[    6.825589] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60<br />
[    6.825643] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58<br />
[    6.866711] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died<br />
[   10.251798] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry<br />
[   10.276464] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]<br />
[   10.286710] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079,OEM_IMAGE_VERSION_STRING=CRM,BUILD_TIME: Oct 17 2019 05:49:19,CACHE_ENABLED at icphostinterface.c:636 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[   10.286717] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully<br />
[   10.286726] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :ELF variant: CACHE-ENABLED:T480:API_V2:USE_CDM_1_1: , API version: 0x2000049 at icphostinterface.c:637 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[   10.349388] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58<br />
[   10.349501] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60<br />
[   10.349554] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.56<br />
[   10.349658] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79<br />
[   10.364493] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000<br />
[   10.364593] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:<br />
[   10.364601] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22<br />
[   10.364606] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22<br />
[   10.364612] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:<br />
[   10.364710] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79<br />
[   10.366854] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.56<br />
[   10.366904] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60<br />
[   10.366972] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58<br />
[   10.402561] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died<br />
[   11.788843] RTW: set pairwise key camid:0, addr:82:93:76:ba:1a:d1, kid:0, type:AES<br />
[   11.793321] RTW: set group key camid:1, addr:82:93:76:ba:1a:d1, kid:1, type:AES<br />
[   13.625836] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry<br />
[   13.638044] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]<br />
[   13.648196] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully<br />
[   13.648203] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079,OEM_IMAGE_VERSION_STRING=CRM,BUILD_TIME: Oct 17 2019 05:49:19,CACHE_ENABLED at icphostinterface.c:636 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[   13.648206] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :ELF variant: CACHE-ENABLED:T480:API_V2:USE_CDM_1_1: , API version: 0x2000049 at icphostinterface.c:637 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[   13.666107] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58<br />
[   13.666296] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60<br />
[   13.666342] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.56<br />
[   13.666432] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79<br />
[   13.681010] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000<br />
[   13.681042] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:<br />
[   13.681047] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22<br />
[   13.681050] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22<br />
[   13.681054] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:<br />
[   13.681134] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79<br />
[   13.683225] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.56<br />
[   13.683262] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60<br />
[   13.683311] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58<br />
[   13.718822] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died<br />
[  135.786669] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry<br />
[  135.805905] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]<br />
[  135.816165] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully<br />
[  135.816181] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079,OEM_IMAGE_VERSION_STRING=CRM,BUILD_TIME: Oct 17 2019 05:49:19,CACHE_ENABLED at icphostinterface.c:636 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[  135.816192] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :ELF variant: CACHE-ENABLED:T480:API_V2:USE_CDM_1_1: , API version: 0x2000049 at icphostinterface.c:637 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[  135.842587] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58<br />
[  135.842690] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60<br />
[  135.842712] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.56<br />
[  135.842818] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79<br />
[  135.862220] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000<br />
[  135.862278] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:<br />
[  135.862288] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22<br />
[  135.862294] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22<br />
[  135.862302] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:<br />
[  135.862455] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79<br />
[  135.864362] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.56<br />
[  135.864450] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60<br />
[  135.864546] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58<br />
[  135.913924] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died<br />
[  612.461063] RTW: set pairwise key camid:0, addr:22:2a:fd:f6:b1:d3, kid:0, type:AES<br />
[  612.470069] RTW: set group key camid:1, addr:22:2a:fd:f6:b1:d3, kid:1, type:AES<br />
[  755.451248] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry<br />
[  755.473531] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]<br />
[  755.483615] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully<br />
[  755.483622] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079,OEM_IMAGE_VERSION_STRING=CRM,BUILD_TIME: Oct 17 2019 05:49:19,CACHE_ENABLED at icphostinterface.c:636 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[  755.483626] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :ELF variant: CACHE-ENABLED:T480:API_V2:USE_CDM_1_1: , API version: 0x2000049 at icphostinterface.c:637 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM<br />
[  755.542979] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58<br />
[  755.543103] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60<br />
[  755.543157] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.56<br />
[  755.543269] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79<br />
[  755.558053] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000<br />
[  755.558127] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:<br />
[  755.558134] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22<br />
[  755.558138] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22<br />
[  755.558143] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:<br />
[  755.558243] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79<br />
[  755.560357] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.56<br />
[  755.560402] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60<br />
[  755.560452] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58<br />
[  755.606789] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died<br />
voxl2:/$<br />
voxl2:/$ voxl-camera-server -d<br />
voxl2:/$ cat /etc/modalai/voxl-camera-server.conf<br />
{<br />
"cameras": [<br />
{<br />
"name": "hires",<br />
"type": "imx412",<br />
"enabled": true,<br />
"camId": 2,<br />
"camId2": -2,<br />
"fps": 30,<br />
"en_rotate": 0,<br />
"en_rotate2": 0,<br />
"en_preview": true,<br />
"pre_width": 640,<br />
"pre_height": 480,<br />
"en_raw_preview": false,<br />
"en_small_video": true,<br />
"small_video_width": 1024,<br />
"small_video_height": 768,<br />
"en_large_video": true,<br />
"large_video_width": 4056,<br />
"large_video_height": 3040,<br />
"en_misp": false,<br />
"misp_width": -1,<br />
"misp_height": -1,<br />
"en_snapshot": false,<br />
"snap_width": 4056,<br />
"snap_height": 3040,<br />
"exif_focal_length": 3.1,<br />
"exif_focal_len_35mm_format": 17,<br />
"exif_fnumber": 1.24,<br />
"ae_mode": "isp",<br />
"msv_exposure_min_us": 20,<br />
"msv_exposure_max_us": 33000,<br />
"gain_min": 54,<br />
"gain_max": 8000,<br />
"standby_enabled": false,<br />
"decimator": 1,<br />
"independent_exposure": false,<br />
"camera_id": -1,<br />
"preview_width": 640,<br />
"preview_height": 480,<br />
"small_venc_mode": "h264",<br />
"small_venc_br_ctrl": "cqp",<br />
"small_venc_Qfixed": 30,<br />
"small_venc_Qmin": 15,<br />
"small_venc_Qmax": 40,<br />
"small_venc_nPframes": 9,<br />
"small_venc_mbps": 2,<br />
"small_venc_osd": false,<br />
"large_venc_mode": "h264",<br />
"large_venc_br_ctrl": "cqp",<br />
"large_venc_Qfixed": 40,<br />
"large_venc_Qmin": 15,<br />
"large_venc_Qmax": 50,<br />
"large_venc_nPframes": 29,<br />
"large_venc_mbps": 40,<br />
"large_venc_osd": false,<br />
"en_snapshot_width": 4056,<br />
"en_snapshot_height": 3040,<br />
"exif_focal_length_in_35mm_format": 17,<br />
"snapshot_jpeg_quality": 75,<br />
"misp_venc_enable": true,<br />
"misp_venc_mode": "h265",<br />
"misp_venc_br_ctrl": "cqp",<br />
"misp_venc_Qfixed": 38,<br />
"misp_venc_Qmin": 15,<br />
"misp_venc_Qmax": 50,<br />
"misp_venc_nPframes": 29,<br />
"misp_venc_mbps": 30,<br />
"misp_venc_osd": false,<br />
"misp_awb": "auto",<br />
"misp_gamma": 1.6<br />
}<br />
],<br />
"fsync_en": false,<br />
"fsync_gpio": 109<br />
}<br />
voxl2:/$</p>
<p dir="auto">voxl2:/$ ls /usr/lib/camera/<br />
com.qti.eeprom.cmk_imx577.so<br />
com.qti.sensor.imx412_fpv.so<br />
com.qti.sensormodule.imx412_fpv_1.bin<br />
com.qti.tuned.cmk_imx577.bin<br />
com.qti.tuned.cmk_ov9282.bin<br />
com.qti.tuned.default.bin<br />
com.qti.tuned.imx412_fpv.bin<br />
com.qti.tuned.ov9782.bin<br />
com.qti.tuned.sony_imx335.bin<br />
components<br />
voxl2:/$</p>
<h1>voxl2:/$ voxl-camera-server<br />
using new imx412 defaults<br />
ERROR: object missing misp_channels</h1>
<p dir="auto">configuration for 1 cameras:</p>
<p dir="auto">cam #0<br />
name:                hires<br />
sensor type:         imx412<br />
isEnabled:           1<br />
camId:               -1<br />
camId2:              -1<br />
fps:                 30<br />
en_rotate:           0<br />
en_rotate2:          0</p>
<pre><code>en_preview:          1
pre_width:           640
pre_height:          480
en_raw_preview:      0

en_small_video:      1
small_video_width:   1024
small_video_height:  768

en_large_video:      1
large_video_width:   4056
large_video_height:  3040

en_misp:             0
misp_width:          -1
misp_height:         -1

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
gain_min           : 54
gain_max           : 8000
standby_enabled:     0
decimator:           1
independent_exposure:0
</code></pre>
<h1>fsync_en:            0<br />
fsync_gpio:          109</h1>
<p dir="auto">voxl2:/$</p>
]]></description><link>https://forum.modalai.com/post/22395</link><guid isPermaLink="true">https://forum.modalai.com/post/22395</guid><dc:creator><![CDATA[ysc]]></dc:creator><pubDate>Fri, 30 May 2025 05:19:17 GMT</pubDate></item><item><title><![CDATA[Reply to VOXL2 didn&#x27;t detect IMX412 Camera on Thu, 29 May 2025 02:51:13 GMT]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-user plugin-mentions-a" href="https://forum.modalai.com/uid/3077">@ysc</a> , please see the following documentation pages:</p>
<p dir="auto"><a href="https://docs.modalai.com/debugging-camera-issues/" rel="nofollow ugc">https://docs.modalai.com/debugging-camera-issues/</a><br />
<a href="https://docs.modalai.com/configure-cameras/#connect-a-new-camera" rel="nofollow ugc">https://docs.modalai.com/configure-cameras/#connect-a-new-camera</a></p>
<p dir="auto">Your VOXL2 SW is likely set up for different camera configuration and you have a non-standard single camera setup (your IMX412 is connected to J7L, which is camera slot 2).</p>
<p dir="auto">Considering that <code>voxl-camera-server -l</code> is already detecting your camera, you can confirm that it is IMX412 based on the sensor ID (also in docs above). The i2c read errors are coming from trying to detect cameras which are not physically connected (0x356 is the WHOAMI register value of AR0144 camera, which you do not have connected to your voxl2).</p>
<p dir="auto">If you look in your <code>/usr/lib/camera/</code>, you should only have an imx412 sensormodule with slot 2 (com.qti.sensormodule.imx412*_2.bin) and if you don't want to see the i2c probe errors, you can remove other sensormodules from that directory (however they should not hurt, since you are already detecting your IMX412 camera, it seems).</p>
<p dir="auto">You also need to take a look at your <code>/etc/modalai/voxl-camera-server.conf</code> and confirm it is correctly set up for a single hires imx412 camera. Then run <code>voxl-camera-server</code> in foreground to see any error messages.</p>
<p dir="auto">Alex</p>
]]></description><link>https://forum.modalai.com/post/22381</link><guid isPermaLink="true">https://forum.modalai.com/post/22381</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Thu, 29 May 2025 02:51:13 GMT</pubDate></item></channel></rss>