# Voxl 2 -- Not receiving any data from hi-res camera

Source: https://forum.modalai.com/topic/4231/voxl-2-not-receiving-any-data-from-hi-res-camera
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2025-03-05 06:18:38 UTC by Maanav Iyengar
Replies: 5 · Views: 741

## Maanav Iyengar · 2025-03-05 06:18:38 UTC

Hi Support Team,

We've been running into an issue with our [hi-res camera](https://www.modalai.com/collections/image-sensors/products/msu-m0107?variant=45747768590640). As of yesterday, it was working perfectly fine, but today, while the [Voxl 2](https://www.modalai.com/collections/all/products/voxl-2?variant=39914779869235) detects the camera, it's not giving us any data. The hi-res camera is connected to Hardware ID 2 (J7) Lower. We've tried other configurations with our [dual image sensor expander](https://www.modalai.com/products/mdk-m0135?variant=44751905816880) but we know that J7 Lower works because we've had no issues with our [tracking camera](https://www.modalai.com/products/msu-m0149-1?variant=46680053907760) in that same port. You can find an image of our setup [here](https://drive.google.com/file/d/1NvWcEdNclFr1bnxipfkB3IG90ThgzdaO/view?usp=sharing).

**When running "voxl-camera-server", we get the output below:**

```
voxl2:/$ voxl-camera-server
detected system image 1.7.8
using new imx412 defaults
=================================================================
configuration for 1 cameras:

cam #0
    name:                hires
    sensor type:         imx412
    isEnabled:           1
    camId:               0
    camId2:              -1
    fps:                 30
    en_rotate:           0
    en_rotate2:          0

    en_preview:          1
    pre_width:           640
    pre_height:          480
    en_raw_preview:      0

    en_small_video:      0
    small_video_width:   1024
    small_video_height:  768

    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:             lme_msv
    msv_exposure_min_us: 20
    msv_exposure_max_us: 33000
    standby_enabled:     0
    decimator:           1
    independent_exposure:0

fsync_en:            0
fsync_gpio:          109
=================================================================
Starting Camera: hires (id #0)
Connected to cpu-monitor
gbm_create_device(156): Info: backend name is: msm_drm

------ voxl-camera-server: Started 1 of 1 cameras

------ voxl-camera-server: Camera server is now running
```

**After running "voxl-inspect-cam -a", we get the output below:**

```
|   Pipe Name |  bytes  | wide |  hgt |exp(ms)| gain | frame id |latency(ms)|  fps |  mbps  | format
| hires_color | Server DisconnectedMost likely the server stopped without cleaning up
Client is cleaning up pipes for the servern pipe_client_open opening request pipe: No such device or address
ERROR in pipe_client_open opening request pipe: No such device or address
Most likely the server stopped without cleaning up
Client is cleaning up pipes for the server
closing and exiting
```

**And the output from "voxl-camera-server" now says "Aborted".**

**When running "dmesg", we get the output below:**

```
[ 1923.059388] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry
[ 1923.086696] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
[ 1923.096914] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully
[ 1923.096923] 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
[ 1923.096928] 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
[ 1923.206469] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
[ 1923.207319] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
[ 1923.207350] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
[ 1923.207453] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
[ 1923.227457] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:3,slave_addr:0x34,sensor_id:0x577
[ 1923.227537] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
[ 1923.229601] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
[ 1923.229617] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
[ 1923.229638] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
[ 1923.269802] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
[ 1923.270141] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
[ 1923.270210] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
[ 1923.270585] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
[ 1923.283777] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 997 CAM_ACQUIRE_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34
[ 1923.290980] CAM_INFO: CAM-HFI: cam_hfi_resume: 679 Resume IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
[ 1926.305226] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
[ 1926.307375] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
[ 1926.307436] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
[ 1926.307509] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
[ 1926.308032] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1047 CAM_RELEASE_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34
[ 1926.331828] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died
[ 1926.414785] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry
[ 1926.425556] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
[ 1926.435903] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully
[ 1926.435922] 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
[ 1926.435933] 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
[ 1926.482917] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
[ 1926.483009] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
[ 1926.483026] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
[ 1926.483118] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
[ 1926.497706] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:3,slave_addr:0x34,sensor_id:0x577
[ 1926.497754] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
[ 1926.499791] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
[ 1926.499803] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
[ 1926.499818] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
[ 1926.520755] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
[ 1926.520925] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
[ 1926.520989] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
[ 1926.521143] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
[ 1926.534451] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 997 CAM_ACQUIRE_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34
[ 1926.541285] CAM_INFO: CAM-HFI: cam_hfi_resume: 679 Resume IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
[ 1975.970540] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:6 IPP resource not available
[ 1975.970556] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:5 IPP resource not available
[ 1975.970566] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:4 IPP resource not available
[ 1975.970576] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:3 IPP resource not available
[ 1975.970585] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:2 IPP resource not available
[ 1975.970714] CAM_ERR: CAM-ISP: cam_ife_hw_mgr_print_acquire_info: 710 Successfully acquire single IFE[1 -1] with [11 pix] [0 pd] [0 rdi] ports for ctx:2
[ 1975.988176] CAM_INFO: CAM-CSIPHY: cam_csiphy_core_cfg: 1137 START_DEV: CSIPHY_IDX: 3, Device_slot: 0, Datarate: 996000000, Settletime: 2200000000
[ 1975.998381] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input
[ 1975.998387] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top
[ 1975.998809] CAM_ERR: CAM-ISP: cam_ife_mgr_start_hw: 4510 ->Config HW, 00000000eab2628f
[ 1975.999724] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1089 CAM_START_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34
[ 1976.007991] CAM_ERR: CAM-ISP: cam_ife_csid_irq: 4848 CSID:1 lane 0 over flow
[ 1976.007996] CAM_INFO: CAM-ISP: cam_ife_csid_halt_csi2: 1931 CSID: 1 cnt: 1 Halt csi2 rx
[ 1976.008007] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 0 CSIPHY index: 3
[ 1976.008011] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 1 CSIPHY index: 3
[ 1976.008015] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 2 CSIPHY index: 3
[ 1976.008019] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 3 CSIPHY index: 3
[ 1976.008025] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 103 PHY base addr=        pK-error offset=0x8b0 size=11
[ 1976.008031] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR0 = 0x4
[ 1976.008036] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR1 = 0x1
[ 1976.008041] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR2 = 0x80
[ 1976.008045] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR3 = 0x20
[ 1976.008050] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR4 = 0x0
[ 1976.008055] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR5 = 0x10
[ 1976.008059] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR6 = 0x4
[ 1976.008064] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR7 = 0x0
[ 1976.008069] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR8 = 0x2
[ 1976.008073] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR9 = 0x40
[ 1976.008078] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR10 = 0x4
[ 1976.008085] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 4 CSIPHY index: 3
[ 1976.008090] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 5 CSIPHY index: 3
[ 1976.008146] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4616 idx 1 err 5 phy 3  lane type:0 ln num:4 ln cfg:0x3210 cnt 1
[ 1976.008149] cam_csid_evt_bottom_half_handler: 1 callbacks suppressed
[ 1976.008155] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RDI0: 0
[ 1976.008157] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RDI1: 0
[ 1976.008166] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RDI2: 0
[ 1976.008171] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RDI3: 0
[ 1976.008176] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status TOP: 0
[ 1976.008181] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RX: 38000
[ 1976.008186] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status IPP: 0
[ 1976.008191] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status PPP: 0
[ 1976.008195] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status UDI0: 0
[ 1976.008200] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status UDI1: 0
[ 1980.746360] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
[ 1980.748491] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
[ 1980.748550] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
[ 1980.748623] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
[ 1980.757772] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 5
[ 1980.757776] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 5
[ 1980.757780] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 5
[ 1980.757784] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
[ 1980.757787] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
[ 1980.757791] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
[ 1980.757794] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
[ 1980.757797] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
[ 1980.757800] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
[ 1980.757804] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
[ 1980.757807] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 7
[ 1980.757811] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 9
[ 1980.757814] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 9
[ 1980.757817] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 9
[ 1980.757820] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
[ 1980.757824] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
[ 1980.757827] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
[ 1980.757830] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
[ 1980.757834] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
[ 1980.757837] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
[ 1980.757840] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
[ 1980.757843] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 11
[ 1980.757847] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 1
[ 1980.757851] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 1
[ 1980.757854] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 1
[ 1980.757858] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
[ 1980.757861] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
[ 1980.757864] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
[ 1980.757867] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
[ 1980.757870] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
[ 1980.757873] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
[ 1980.757876] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
[ 1980.757880] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 3
[ 1980.757885] CAM_ERR: CAM-ISP: __cam_isp_ctx_release_dev_in_top_state: 3789 releasing hw
[ 1980.757922] CAM_INFO: CAM-ISP: cam_ife_mgr_release_hw: 4755 Release HW success ctx id: 2
[ 1980.757975] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died
[ 1980.758980] CAM-REQ-MGR_UTIL cam_req_mgr_util_free_hdls:99 CAM_WARN: CAM-CRM: cam_req_mgr_util_free_hdls: 99 Dev handle = 8b0102 session_handle = 790200
[ 1980.758987] CAM-REQ-MGR_UTIL cam_req_mgr_util_free_hdls:99 CAM_WARN: CAM-CRM: cam_req_mgr_util_free_hdls: 99 Dev handle = 100104 session_handle = 790200
[ 1980.776158] ion_buffer_destroy: 6 callbacks suppressed
[ 1980.776161] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.776953] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.777065] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.785014] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.785031] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.785046] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.785094] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.785411] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.785512] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
[ 1980.785986] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
```

We've got a tight deadline coming up and would greatly appreciate any help here. Thanks.

## Reply by Alex Kushleyev (ModalAI staff) · 2025-03-05 14:43:41 UTC

@Maanav-Iyengar ,

Thank you for providing lots of details about your case. Please see my comments below:
- from the image, it looks like your camera is actually connected to J7U, not J7L (because I see JU marking next to the flex cable connection on M0135). Please double check this. Either way, it should be ok because the imx412 camera is actually supported on both J7L and J7U.
- from the `dmesg` log i can see that there is some kind of error in the high speed MIPI transmission. Sometimes this happens if the extension flex (M0036) is not good.

My recommendation:
- if you have another M0036 flex cable, please try it with the same setup
- test the same setup by connecting the IMX412 camera in *the other* slot of the J7 connector: if you were testing in J7U, then test using J7L and vice versa
- you will need to configure your camera drivers to detect imx412 in slot 2 (J7L) or slot 3 (J7U). 
  - check which imx412 sensormodule you have in `/usr/lib/camera/` (index at the end will tell you the slot number, such as 2 or 3). (Please tell me which sensormodule is present). 
- Then copy the needed sensormodule from `/usr/share/modalai/chi-cdk/imx412/` for the appropriate slot to `/usr/lib/camera/`
- try your test again

Alex

## Reply by Maanav Iyengar · 2025-03-06 05:13:39 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev Hi Alex, thanks for getting back to me so quickly. 

Good catch. I mistakenly mentioned J7L. I tried swapping between J7L and J7U and configuring the camera drivers, but the result remained the same.

Unfortunately, I don’t have an extra M0036 flex cable.

Do you have any suggestions on what I should try next?

## Reply by Alex Kushleyev (ModalAI staff) · 2025-03-06 15:44:43 UTC (in reply to Maanav Iyengar)

@Maanav-Iyengar , in the original post you mentioned that the camera (connected to voxl2 in the exact same way?) was working just fine? can you confirm this? 

Has anything at all changed between the working and non-working state?

Does the same error happen every time right after you start the camera server and attempt to view the stream, or are you able to get some frames before the issue occurs?

Alex

## Reply by Maanav Iyengar · 2025-03-07 07:09:26 UTC (in reply to Alex Kushleyev)

@Alex-Kushleyev Hi Alex, the camera was working just fine about a day before I made my first post; however, it still does not work. Unfortunately, we are not able to get any frames before the issue occurs.

## Reply by Alex Kushleyev (ModalAI staff) · 2025-03-07 16:55:45 UTC (in reply to Maanav Iyengar)

@Maanav-Iyengar , you can try to move the camera to J6L and use sensormodule with ID 0. 

If that does not work, then the issue is most likely not in VOXL2, but somewhere upstream (M0135 or farther up)

If you have another camera, you can try plugging it in instead of IMX412, so this would test the M0135 + M0036 path. Any camera would do, but you would just need to set up the correct sensormodule .

If you use any other camera for testing, which already has a flex on it (unlike M0107 IMX412), then you can skip the M0036 extension flex (you can test with and without it). If you use tracking camera, keep an eye on pin1 orientation, as it is backwards compared to hires cameras.

Alex