Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

  1. ModalAI Support Forum
  2. VOXL Accessories
  3. Image Sensors
  4. Camera not recognised

Camera not recognised

Scheduled Pinned Locked Moved Image Sensors
2 Posts 2 Posters 408 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    TomP
    Contributor
    wrote on last edited by
    #1

    Hello everyone,

    We use this camera:
    Image Sensor 4k High-resolution, Low-light Sensor for VOXL® (Starvis IMX412 w/ M12-style Lens) (MSU-M0107)

    Unfortunately, it is not recognised by the VOXL2 (see picture).
    VOXL2_Bug.jpg

    The module also says (voxl-camera-server):

    ERROR:   Found zero cameras connected, need at least one. 
    

    We used "voxl-configure-cameras 17" before.

    Here is another interesting dmesg output that could mean something:

    [  161.278305] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address  : 0xE2
    [  161.278307] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x9281
    [  161.278309] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x71
    [  161.278452] CAM_ERR: CAM-CCI: cam_cci_irq: 258 Base:        pK-error, M1_Q0 NACK ERROR: 0x20000000
    [  161.278478] CAM_ERR: CAM-CCI: cam_cci_wait: 270 failed rc -22
    [  161.278480] CAM_ERR: CAM-CCI: cam_cci_transfer_end: 345 failed rc -22
    [  161.278483] CAM_ERR: CAM-CCI: cam_cci_data_queue: 870 Slave: 0xe0 failed rc -22
    [  161.278485] CAM_ERR: CAM-CCI: cam_cci_i2c_write: 1450 failed rc: -22
    [  161.278487] CAM_ERR: CAM-SENSOR: cam_cci_i2c_write_table_cmd: 123 Failed rc = -22
    [  161.278489] CAM_ERR: CAM-SENSOR: cam_sensor_set_alt_id: 768 [Applying Alternative Address] : Probe : camera_io_dev_write failed: rc=-22
    [  161.278618] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
    [  161.278642] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xe0:
    [  161.278644] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
    [  161.278646] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
    [  161.278649] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x9281:
    [  161.278703] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
    [  161.282198] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
    [  161.312366] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.60
    [  161.312412] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.79
    [  161.325847] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 731 [Applying Alternative Address] : Sensor Index   : 391409844
    [  161.325850] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address  : 0xE4
    [  161.325853] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x9281
    [  161.325855] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x72
    [  161.325999] CAM_ERR: CAM-CCI: cam_cci_irq: 258 Base:        pK-error, M1_Q0 NACK ERROR: 0x20000000
    [  161.326018] CAM_ERR: CAM-CCI: cam_cci_wait: 270 failed rc -22
    [  161.326021] CAM_ERR: CAM-CCI: cam_cci_transfer_end: 345 failed rc -22
    [  161.326024] CAM_ERR: CAM-CCI: cam_cci_data_queue: 870 Slave: 0xe0 failed rc -22
    [  161.326026] CAM_ERR: CAM-CCI: cam_cci_i2c_write: 1450 failed rc: -22
    [  161.326029] CAM_ERR: CAM-SENSOR: cam_cci_i2c_write_table_cmd: 123 Failed rc = -22
    [  161.326031] CAM_ERR: CAM-SENSOR: cam_sensor_set_alt_id: 768 [Applying Alternative Address] : Probe : camera_io_dev_write failed: rc=-22
    [  161.326082] CAM_ERR: CAM-CCI: cam_cci_read: 1340 read_words = 0, exp words = 1
    [  161.326090] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
    [  161.326092] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
    [  161.326095] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x9281:
    [  161.326151] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.79
    [  161.326161] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
    [  161.330027] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.60
    [  161.368230] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died
    voxl2:/$
    

    By the way, we have also tried other cameras (e.g. Image Sensor 4k High-resolution for VOXL® (8x8x5.8mm) (MSU-M0025) ). Always the same problem.

    I would be very happy to receive any tips.

    Best regards
    Tom

    Alex KushleyevA 1 Reply Last reply
    0
    • T TomP

      Hello everyone,

      We use this camera:
      Image Sensor 4k High-resolution, Low-light Sensor for VOXL® (Starvis IMX412 w/ M12-style Lens) (MSU-M0107)

      Unfortunately, it is not recognised by the VOXL2 (see picture).
      VOXL2_Bug.jpg

      The module also says (voxl-camera-server):

      ERROR:   Found zero cameras connected, need at least one. 
      

      We used "voxl-configure-cameras 17" before.

      Here is another interesting dmesg output that could mean something:

      [  161.278305] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address  : 0xE2
      [  161.278307] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x9281
      [  161.278309] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x71
      [  161.278452] CAM_ERR: CAM-CCI: cam_cci_irq: 258 Base:        pK-error, M1_Q0 NACK ERROR: 0x20000000
      [  161.278478] CAM_ERR: CAM-CCI: cam_cci_wait: 270 failed rc -22
      [  161.278480] CAM_ERR: CAM-CCI: cam_cci_transfer_end: 345 failed rc -22
      [  161.278483] CAM_ERR: CAM-CCI: cam_cci_data_queue: 870 Slave: 0xe0 failed rc -22
      [  161.278485] CAM_ERR: CAM-CCI: cam_cci_i2c_write: 1450 failed rc: -22
      [  161.278487] CAM_ERR: CAM-SENSOR: cam_cci_i2c_write_table_cmd: 123 Failed rc = -22
      [  161.278489] CAM_ERR: CAM-SENSOR: cam_sensor_set_alt_id: 768 [Applying Alternative Address] : Probe : camera_io_dev_write failed: rc=-22
      [  161.278618] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
      [  161.278642] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xe0:
      [  161.278644] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
      [  161.278646] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
      [  161.278649] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x9281:
      [  161.278703] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
      [  161.282198] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
      [  161.312366] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.60
      [  161.312412] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.79
      [  161.325847] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 731 [Applying Alternative Address] : Sensor Index   : 391409844
      [  161.325850] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address  : 0xE4
      [  161.325853] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x9281
      [  161.325855] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x72
      [  161.325999] CAM_ERR: CAM-CCI: cam_cci_irq: 258 Base:        pK-error, M1_Q0 NACK ERROR: 0x20000000
      [  161.326018] CAM_ERR: CAM-CCI: cam_cci_wait: 270 failed rc -22
      [  161.326021] CAM_ERR: CAM-CCI: cam_cci_transfer_end: 345 failed rc -22
      [  161.326024] CAM_ERR: CAM-CCI: cam_cci_data_queue: 870 Slave: 0xe0 failed rc -22
      [  161.326026] CAM_ERR: CAM-CCI: cam_cci_i2c_write: 1450 failed rc: -22
      [  161.326029] CAM_ERR: CAM-SENSOR: cam_cci_i2c_write_table_cmd: 123 Failed rc = -22
      [  161.326031] CAM_ERR: CAM-SENSOR: cam_sensor_set_alt_id: 768 [Applying Alternative Address] : Probe : camera_io_dev_write failed: rc=-22
      [  161.326082] CAM_ERR: CAM-CCI: cam_cci_read: 1340 read_words = 0, exp words = 1
      [  161.326090] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
      [  161.326092] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
      [  161.326095] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x9281:
      [  161.326151] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.79
      [  161.326161] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
      [  161.330027] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.60
      [  161.368230] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died
      voxl2:/$
      

      By the way, we have also tried other cameras (e.g. Image Sensor 4k High-resolution for VOXL® (8x8x5.8mm) (MSU-M0025) ). Always the same problem.

      I would be very happy to receive any tips.

      Best regards
      Tom

      Alex KushleyevA Offline
      Alex KushleyevA Offline
      Alex Kushleyev
      ModalAI Team
      wrote on last edited by
      #2

      @TomP , if you look at C19 configuration (https://docs.modalai.com/voxl2-camera-configs/#c-17-tof-tracking-stereo0v9782-and-hiresimx412) , the IMX412 camera is connected to the other camera port on the dual camera flex. You have it connected to the connector that goes straight out (7JU), C19 shows IMX412 connected to the port going off to the side (7JL).

      If you want to keep IMX412 connected as shown in your picture, please copy the following file, which will tell the camera pipeline to try to detect the IMX412 camera on 7JU:

      cp /usr/share/modalai/chi-cdk/imx412/com.qti.sensormodule.imx412_3.bin /usr/lib/camera/
      

      Please double check this 🙂

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      ModalAI
      Categories Recent Tags ModalAI.com Docs
      © 2026 ModalAI® · Accelerating autonomy for smaller, smarter, safer drones · Powered by NodeBB
      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups