Posts made by Matthew Wellner

@Alex-Kushleyev Thanks again for the help. Unfortunately as it turns out, even though I have a Boson 640+ FLIR told me that the version I have is right before they started providing the MIPI output. I can still use the UVC interface, but it doesn't look like the Boson+ that I have can use the MIPI adapter after all. I don't know that many others will have my problem, but you guys might want to note that only the newest version of the Boson camera will support the MIPI adapter kit (https://flir.custhelp.com/app/answers/detail/a_id/6245/~/flir-oem---boson-software-versions).

Matt

@Alex-Kushleyev - I took a look at the Hadron documentation you linked about and I might have missed it, but I'm not sure which socket I am supposed to plug the Boson into given the labeling - Should the Boson be plugged into the HR port or the 5L port?

The board plugged into the Boson is the M0201.

Thanks!
Matt

@Alex-Kushleyev

Here is the output from dmesg -w when I run voxl-camera-server -l:

[  431.574827] perf: interrupt took too long (3149 > 3133), lowering kernel.perf_event_max_sample_rate to 63500
[  433.269948] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry
[  433.300805] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
[  433.311075] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully
[  433.311129] 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
[  433.311142] 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
[  433.464626] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59
[  433.466717] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.55
[  433.468818] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60
[  433.468851] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79
[  433.496472] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 731 [Applying Alternative Address] : Sensor Index   : 3613024436
[  433.496477] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address  : 0xE2
[  433.496480] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x7750
[  433.496482] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x71
[  433.496666] CAM_ERR: CAM-CCI: cam_cci_irq: 232 Base:        pK-error, M0_Q0 NACK ERROR: 0x8000000
[  433.496723] CAM_ERR: CAM-CCI: cam_cci_wait: 270 failed rc -22
[  433.496727] CAM_ERR: CAM-CCI: cam_cci_transfer_end: 345 failed rc -22
[  433.496730] CAM_ERR: CAM-CCI: cam_cci_data_queue: 870 Slave: 0xe0 failed rc -22
[  433.496732] CAM_ERR: CAM-CCI: cam_cci_i2c_write: 1450 failed rc: -22
[  433.496736] CAM_ERR: CAM-SENSOR: cam_cci_i2c_write_table_cmd: 123 Failed rc = -22
[  433.496737] CAM_ERR: CAM-SENSOR: cam_sensor_set_alt_id: 768 [Applying Alternative Address] : Probe : camera_io_dev_write failed: rc=-22
[  433.496835] CAM_ERR: CAM-CCI: cam_cci_read: 1340 read_words = 0, exp words = 1
[  433.496839] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.496840] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.496843] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x7750:
[  433.496880] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
[  433.496986] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79
[  433.501213] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.60
[  433.501260] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.55
[  433.501292] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.59
[  433.526323] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
[  433.526429] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
[  433.526523] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
[  433.526560] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
[  433.544735] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  433.544818] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x20:
[  433.544832] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.544839] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.544848] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x214:
[  433.545095] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
[  433.548685] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
[  433.548839] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
[  433.548966] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
[  433.579656] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59
[  433.581907] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.55
[  433.584401] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60
[  433.584540] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79
[  433.609848] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
[  433.609954] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xd4:
[  433.609968] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.609975] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.609984] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0xff:
[  433.610164] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79
[  433.613619] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.60
[  433.613750] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.55
[  433.613862] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.59
[  433.640381] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.59
[  433.640593] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.60
[  433.640685] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.55
[  433.640902] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.79
[  433.656073] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  433.656156] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
[  433.656163] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.656167] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.656172] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
[  433.656256] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
[  433.658387] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.55
[  433.658438] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
[  433.658505] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.59
[  433.687773] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.59
[  433.691592] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.55
[  433.694141] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.60
[  433.694264] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.79
[  433.718658] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 731 [Applying Alternative Address] : Sensor Index   : 3613028532
[  433.718705] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 732 [Applying Alternative Address] : Slave Address  : 0xE2
[  433.718712] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 733 [Applying Alternative Address] : Slave sensor id: 0x7750
[  433.718718] CAM_INFO: CAM-SENSOR: cam_sensor_set_alt_id: 734 [Applying Alternative Address] : cci_client sid : 0x71
[  433.718885] CAM_ERR: CAM-CCI: cam_cci_irq: 258 Base:        pK-error, M1_Q0 NACK ERROR: 0x20000000
[  433.718943] CAM_ERR: CAM-CCI: cam_cci_wait: 270 failed rc -22
[  433.718951] CAM_ERR: CAM-CCI: cam_cci_transfer_end: 345 failed rc -22
[  433.718958] CAM_ERR: CAM-CCI: cam_cci_data_queue: 870 Slave: 0xe0 failed rc -22
[  433.718964] CAM_ERR: CAM-CCI: cam_cci_i2c_write: 1450 failed rc: -22
[  433.719002] CAM_ERR: CAM-SENSOR: cam_cci_i2c_write_table_cmd: 123 Failed rc = -22
[  433.719010] CAM_ERR: CAM-SENSOR: cam_sensor_set_alt_id: 768 [Applying Alternative Address] : Probe : camera_io_dev_write failed: rc=-22
[  433.719219] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  433.719311] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xe0:
[  433.719318] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.719322] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.719328] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x7750:
[  433.719416] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
[  433.723247] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
[  433.723323] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.55
[  433.723388] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.59
[  433.748263] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59
[  433.748550] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60
[  433.748635] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.55
[  433.748846] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79
[  433.764442] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
[  433.764550] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
[  433.764561] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.764568] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.764576] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
[  433.764690] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79
[  433.766882] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.55
[  433.766957] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.60
[  433.767266] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.59
[  433.794883] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.58
[  433.797233] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.55
[  433.799580] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.60
[  433.799719] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.79
[  433.824690] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
[  433.824892] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xd4:
[  433.824903] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.825047] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.825056] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0xff:
[  433.825210] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.79
[  433.829028] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.60
[  433.829145] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.55
[  433.829248] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.58
[  433.856662] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.58
[  433.856947] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.60
[  433.857052] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.55
[  433.857316] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.79
[  433.873707] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:0,slave_addr:0x34,sensor_id:0x577
[  433.873856] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.79
[  433.876113] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.55
[  433.876193] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.60
[  433.876297] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.58
[  433.906802] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58
[  433.909084] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.55
[  433.911458] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60
[  433.911541] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79
[  433.934593] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  433.934753] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xd4:
[  433.934764] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.934770] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.934779] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0xff:
[  433.934902] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79
[  433.939356] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60
[  433.939491] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.55
[  433.939610] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58
[  433.966788] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
[  433.969160] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
[  433.971485] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
[  433.971623] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
[  433.996414] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  433.996614] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xd4:
[  433.996626] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  433.996633] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  433.996642] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0xff:
[  433.996843] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
[  434.000928] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
[  434.001059] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
[  434.001168] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
[  434.030683] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.59
[  434.033001] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.55
[  434.035566] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.60
[  434.035687] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.79
[  434.060425] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  434.060517] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xd4:
[  434.060566] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  434.060573] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  434.060581] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0xff:
[  434.060726] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
[  434.063418] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
[  434.063527] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.55
[  434.063634] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.59
[  434.090281] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.59
[  434.092434] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.55
[  434.094363] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.60
[  434.094474] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.79
[  434.117561] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  434.117639] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0xd4:
[  434.117651] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  434.117658] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  434.117666] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0xff:
[  434.117782] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.79
[  434.120568] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.60
[  434.120684] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.55
[  434.120784] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.59
[  434.144431] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58
[  434.144691] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60
[  434.144790] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.55
[  434.145044] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79
[  434.160015] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  434.160185] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
[  434.160196] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  434.160204] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  434.160212] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
[  434.160375] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79
[  434.162589] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.55
[  434.162661] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60
[  434.162759] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58
[  434.188783] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59
[  434.189340] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60
[  434.189451] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.55
[  434.189720] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79
[  434.205777] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
[  434.205898] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
[  434.205909] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  434.205917] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  434.205926] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
[  434.206047] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79
[  434.208273] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.55
[  434.208352] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.60
[  434.208456] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.59
[  434.231916] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
[  434.232050] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
[  434.232095] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
[  434.232224] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
[  434.246838] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  434.247005] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
[  434.247021] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  434.247027] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  434.247035] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
[  434.247256] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
[  434.249430] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
[  434.249496] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
[  434.249584] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
[  434.276816] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.59
[  434.277144] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.60
[  434.277240] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.55
[  434.277540] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.79
[  434.292566] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
[  434.292688] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
[  434.292694] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
[  434.292699] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
[  434.292704] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
[  434.292783] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
[  434.295325] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.55
[  434.295373] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
[  434.295437] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.59
[  434.349070] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died

@Alex-Kushleyev - Also, I noticed that the VOXL side adapter that was included with the Boson+ kit that I ordered includes spots for 2 coax cable connections. The one on the website looks like it only has one connection. Is the board I have newer, or did I receive the wrong board (it's labeled M0181)?

@Alex-Kushleyev - I have an extra USB 2 to 4 pin JST-GH connector and a 6 pin JST-GH connector. Can I use the pinout from the MCBL-00104 cable to configure the Boson+? I don't have a JST-SH connector on the version of the board I received.

@Alex-Kushleyev Sorry for the delay getting back to you - I was able to communicate over USB to the boson and run through that configuration. The only thing that was different was that I tried running the latest version of FLIR configuration tool (off of their website) and it forced me to use Boson 3.0.0 App that didn't have a specific setting to send video over MIPI (like the other configuration tool has). I don't have the specific JST-GH to USB cable that there is a header for on the m0153 board, so I was using the FLIR USB-C board that I previously used with the Boson. Could that be part of my issue with the camera?

Thanks again!
Matt

@tom Should I have kernel version 1.0.1 installed instead of 1.0.0? I don't have a M0173 board. I was connecting the boson cable directly according to the directions here: https://docs.modalai.com/M0153/#boson-software-setup - Do I need the M0173?

@Alex-Kushleyev - I'm not sure if you are the right person to ask, but I was hoping you could help me figure out the issue I am having above?

@bendraper I'm not sure if this is still an issue for you, but you need to get a SIM specifically for data from here: https://fi.google.com/data - After they ship it to you, you can activate it through your Google Fi account using the instructions/activation code that come with the SIM.

Hi,

I followed the guide posted here: https://docs.modalai.com/M0153/#boson-software-setup but I'm having trouble getting the boson camera detected by voxl-camera-server (voxl-camera-server -l detects my tracking and hires cameras already just not the boson). I also noticed that voxl-configure-cameras options 36 and 37 don't exist in the version I am running (SDK 1.5.0 / voxl-camera-server 2.2.4)

I have the board side of the M0153 physically connected to the J8 socket and I copied the boson bin files from the /usr/share/modalai/chi-cdk/ into /usr/lib/camera

Thanks in advance for the help!

I grabbed the /usr/bin/quectel-CM from another VOXL2 on an older SDK (1.4.1) and swapped out the one that came with 1.5.0 and everything is working again...

Hi!

I just updated to the newest VOXL SDK (1.5.0) to get support for the Hadron and Boson cameras and after the flash my Quectel 5G modem will no longer get an IP address from the cellular network. I ran through voxl-configure-modem again and I also ran the voxel-modem-start command manually. When I run voxel-modem-start manually, I get this error:

qrb5165 based hardware detected...
\Setting mode preference to LTE / 5G
AT+QNWPREFCFG="mode_pref",LTE:NR5G
OK

Initalizing cellular connection...
/usr/bin/voxl-modem-start: line 84: /usr/bin/quectel-CM: cannot execute binary file: Exec format error
/usr/bin/voxl-modem-start: line 84: /usr/bin/quectel-CM: cannot execute binary file: Exec format error
/usr/bin/voxl-modem-start: line 84: /usr/bin/quectel-CM: cannot execute binary file: Exec format error

If I run "file /usr/bin/quectel-CM", I get this:

/usr/bin/quectel-CM: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=22bb006a724be58f44e4eb6b7ed46f859144f314, for GNU/Linux 3.2.0, stripped

Isn't this supposed to be "ARM aarch64"? I'm going to try copying the quectel-CM from a previous release to see if that fixes my issue, but let me know.

@Alex-Kushleyev - It looks like everything is working. Thanks again!

@Alex-Kushleyev

So... I replaced the dual camera adapter with the single flex cable connected to the interposer and the camera on J7U. I reflashed the SDK and now I am able to keep the voxl-camera-server up with 30fps. I'll go through the tutorial again and hopefully I'll be good to go.

I also ordered another camera that can use the coax cable instead so that I don't have any cable related issues. I'll post back with how following through the tutorial goes, but thanks again for your help!

@Alex-Kushleyev - I replaced the dual camera adapter with a flex extension and a M0076 interposer to directly connect the camera to J7U and I am getting this output when I run voxl-camera-server:

Apr 28 14:02:13 m0054 kernel: [  308.863682] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry
Apr 28 14:02:13 m0054 kernel: [  308.892491] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
Apr 28 14:02:13 m0054 kernel: [  308.902754] 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
Apr 28 14:02:13 m0054 kernel: [  308.902765] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully
Apr 28 14:02:13 m0054 kernel: [  308.902776] 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
Apr 28 14:02:14 m0054 kernel: [  309.026191] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
Apr 28 14:02:14 m0054 kernel: [  309.026286] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
Apr 28 14:02:14 m0054 kernel: [  309.026383] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
Apr 28 14:02:14 m0054 kernel: [  309.026414] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
Apr 28 14:02:14 m0054 kernel: [  309.049655] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 28 14:02:14 m0054 kernel: [  309.049816] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 28 14:02:14 m0054 kernel: [  309.049822] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x214:
Apr 28 14:02:14 m0054 kernel: [  309.049927] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 28 14:02:14 m0054 kernel: [  309.054006] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
Apr 28 14:02:14 m0054 kernel: [  309.054050] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 28 14:02:14 m0054 kernel: [  309.054081] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
Apr 28 14:02:14 m0054 kernel: [  309.078537] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
Apr 28 14:02:14 m0054 kernel: [  309.078695] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
Apr 28 14:02:14 m0054 kernel: [  309.078727] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
Apr 28 14:02:14 m0054 kernel: [  309.078858] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
Apr 28 14:02:14 m0054 kernel: [  309.098545] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 28 14:02:14 m0054 kernel: [  309.099453] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 28 14:02:14 m0054 kernel: [  309.099460] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 28 14:02:14 m0054 kernel: [  309.099464] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 28 14:02:14 m0054 kernel: [  309.099469] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 28 14:02:14 m0054 kernel: [  309.099549] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 28 14:02:14 m0054 kernel: [  309.101115] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 28 14:02:14 m0054 kernel: [  309.101149] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
Apr 28 14:02:14 m0054 kernel: [  309.101183] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
Apr 28 14:02:14 m0054 kernel: [  309.154760] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died

@Alex-Kushleyev - Sorry for the delay. I have a M0084 that sits between the camera and the VOXL2 on the J7U port. I'm guessing that the dual adapter can cause issues in this application?

@Alex-Kushleyev

The camera is connected to a smaller flex cable (camera extension flex?) that is connected to the flex cable that plugs into the VOXL2 J7U port. I don't think I have another camera here - I may, but it's definitely not the same camera.

I planned to buy a micro coax cable and adapter board to use on this project, but I planned to validate the low latency setup worked before doing so

I have a second VOXL2 - I might try moving the camera from this setup to the other setup and I'll go through the procedures again to verify I didn't mess up the drivers.

@Alex-Kushleyev

Here is what I am running:

• M0107 (purchased 12/2023 just in case there were any issues with older versions)
• I am using a flex cable connected to J7U directly to the camera (I haven't moved any hardware around except for adding a wifi USB adapter for some testing that I am doing)
• Yes
• Yes

I followed the procedure to swap out the drivers and I am still seeing the voxl-camera-server die... Did I need to remove the .so file in /usr/lib/camera as well?

Apr 25 15:57:00 m0054 kernel: [161821.673062] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
Apr 25 15:57:00 m0054 kernel: [161821.683296] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully
Apr 25 15:57:00 m0054 kernel: [161821.683304] 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
Apr 25 15:57:00 m0054 kernel: [161821.683308] 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
Apr 25 15:57:00 m0054 kernel: [161821.724105] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
Apr 25 15:57:00 m0054 kernel: [161821.724169] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
Apr 25 15:57:00 m0054 kernel: [161821.724234] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
Apr 25 15:57:00 m0054 kernel: [161821.724261] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
Apr 25 15:57:00 m0054 kernel: [161821.748891] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 25 15:57:00 m0054 kernel: [161821.751009] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x20:
Apr 25 15:57:00 m0054 kernel: [161821.751011] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 25 15:57:00 m0054 kernel: [161821.751013] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 25 15:57:00 m0054 kernel: [161821.751016] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x214:
Apr 25 15:57:00 m0054 kernel: [161821.751091] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 25 15:57:00 m0054 kernel: [161821.805664] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:3,slave_addr:0x34,sensor_id:0x577
Apr 25 15:57:00 m0054 kernel: [161821.805730] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 25 15:57:00 m0054 kernel: [161821.807790] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 25 15:57:00 m0054 kernel: [161821.807800] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
Apr 25 15:57:00 m0054 kernel: [161821.807820] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
Apr 25 15:57:00 m0054 kernel: [161821.825950] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
Apr 25 15:57:00 m0054 kernel: [161821.826027] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
Apr 25 15:57:00 m0054 kernel: [161821.826043] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
Apr 25 15:57:00 m0054 kernel: [161821.826121] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
Apr 25 15:57:00 m0054 kernel: [161821.840661] CAM_INFO: CAM-HFI: cam_hfi_resume: 679 Resume IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
Apr 25 15:57:00 m0054 kernel: [161821.840851] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 997 CAM_ACQUIRE_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34
Apr 25 15:57:00 m0054 kernel: [161821.870871] msm_vidc:   high: 00000001: ....e: Opening video instance: ffffffd8fc0d2000, 0
Apr 25 15:57:00 m0054 voxl-cpu-monitor[1757]: client "voxl-camera-server74194795" with id 0 has disconnected from channel 0
Apr 25 15:57:00 m0054 voxl-cpu-monitor[1757]: client "voxl-camera-server94269699" connected to channel 0  with client id 0
Apr 25 15:57:00 m0054 kernel: [161822.302893] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:6 IPP resource not available
Apr 25 15:57:00 m0054 kernel: [161822.302896] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:5 IPP resource not available
Apr 25 15:57:00 m0054 kernel: [161822.302898] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:4 IPP resource not available
Apr 25 15:57:00 m0054 kernel: [161822.302899] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:3 IPP resource not available
Apr 25 15:57:00 m0054 kernel: [161822.302901] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:2 IPP resource not available
Apr 25 15:57:00 m0054 kernel: [161822.302926] 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:1
Apr 25 15:57:00 m0054 kernel: [161822.325127] CAM_ERR: CAM-ISP: cam_ife_csid_irq: 4855 CSID:1 lane 1 over flow
Apr 25 15:57:00 m0054 kernel: [161822.325132] CAM_INFO: CAM-ISP: cam_ife_csid_halt_csi2: 1931 CSID: 1 cnt: 1 Halt csi2 rx
Apr 25 15:57:00 m0054 kernel: [161822.325141] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 0 CSIPHY index: 3
Apr 25 15:57:00 m0054 kernel: [161822.325144] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 1 CSIPHY index: 3
Apr 25 15:57:00 m0054 kernel: [161822.325146] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 2 CSIPHY index: 3
Apr 25 15:57:00 m0054 kernel: [161822.325149] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 3 CSIPHY index: 3
Apr 25 15:57:00 m0054 kernel: [161822.325154] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 103 PHY base addr=        pK-error offset=0x8b0 size=11
Apr 25 15:57:00 m0054 kernel: [161822.325160] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR0 = 0x14
Apr 25 15:57:00 m0054 kernel: [161822.325164] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR1 = 0x0
Apr 25 15:57:00 m0054 kernel: [161822.325169] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR2 = 0x80
Apr 25 15:57:00 m0054 kernel: [161822.325173] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR3 = 0x22
Apr 25 15:57:00 m0054 kernel: [161822.325178] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR4 = 0x0
Apr 25 15:57:00 m0054 kernel: [161822.325183] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR5 = 0x50
Apr 25 15:57:00 m0054 kernel: [161822.325187] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR6 = 0x0
Apr 25 15:57:00 m0054 kernel: [161822.325192] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR7 = 0x0
Apr 25 15:57:00 m0054 kernel: [161822.325197] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR8 = 0xa
Apr 25 15:57:00 m0054 kernel: [161822.325201] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR9 = 0x40
Apr 25 15:57:00 m0054 kernel: [161822.325206] CAM_INFO: CAM-CSIPHY: cam_csiphy_status_dmp: 117 CSIPHY3_IRQ_STATUS_ADDR10 = 0x4
Apr 25 15:57:00 m0054 kernel: [161822.325209] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 4 CSIPHY index: 3
Apr 25 15:57:00 m0054 kernel: [161822.325211] CAM_INFO: CAM-CSIPHY: cam_csiphy_subdev_handle_message: 22 subdev index : 5 CSIPHY index: 3
Apr 25 15:57:00 m0054 kernel: [161822.325265] 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
Apr 25 15:57:00 m0054 kernel: [161822.325271] cam_csid_evt_bottom_half_handler: 1 callbacks suppressed
Apr 25 15:57:00 m0054 kernel: [161822.325280] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RDI0: 0
Apr 25 15:57:00 m0054 kernel: [161822.325285] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RDI1: 0
Apr 25 15:57:00 m0054 kernel: [161822.325294] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RDI2: 0
Apr 25 15:57:00 m0054 kernel: [161822.325303] CAM_ERR: CAM-ISP: cam_csid_evt_bottom_half_handler: 4621 status RDI3: 0
Apr 25 15:57:01 m0054 kernel: [161823.383488] msm_vidc:   err : ffffffff: .....: DBLP Set: status 0
Apr 25 15:57:05 m0054 kernel: [161827.032884] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  0 fd 96 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032888] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  1 fd 98 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032890] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  2 fd 100 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032891] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  3 fd 102 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032893] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  4 fd 104 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032894] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  5 fd 106 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032895] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  6 fd 108 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032897] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  7 fd 110 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032898] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  8 fd 112 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032899] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  9 fd 114 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032901] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 10 fd 116 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032902] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 11 fd 118 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032903] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 12 fd 120 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032905] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 13 fd 122 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032906] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 14 fd 124 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032907] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 15 fd 126 off 0 size 884736 filled 0
Apr 25 15:57:05 m0054 kernel: [161827.032910] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  0 fd 96 off 0 daddr dfb00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032921] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  1 fd 98 off 0 daddr dfa00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032925] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  2 fd 100 off 0 daddr df900000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032929] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  3 fd 102 off 0 daddr df800000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032932] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  4 fd 104 off 0 daddr df700000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032936] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  5 fd 106 off 0 daddr df600000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032939] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  6 fd 108 off 0 daddr df500000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032942] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  7 fd 110 off 0 daddr df400000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032944] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  8 fd 112 off 0 daddr df300000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032947] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  9 fd 114 off 0 daddr df200000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032952] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 10 fd 116 off 0 daddr df100000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032955] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 11 fd 118 off 0 daddr df000000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032958] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 12 fd 120 off 0 daddr def00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032960] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 13 fd 122 off 0 daddr dee00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032963] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 14 fd 124 off 0 daddr ded00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 kernel: [161827.032965] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 15 fd 126 off 0 daddr dec00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 25 15:57:05 m0054 voxl-portal[1760]: ERROR in pipe_client_open opening request pipe: No such device or address
Apr 25 15:57:05 m0054 kernel: [161827.035402] msm_vidc:   err : 00000001: h265e: State not recognized
Apr 25 15:57:05 m0054 kernel: [161827.035404] msm_vidc:   err : 00000001: h265e: Failed to move from state: 16 to 13
Apr 25 15:57:05 m0054 kernel: [161827.035408] msm_vidc:   err : 00000001: h265e: msm_comm_kill_session: no session to kill for inst ffffffd8fc0d2000
Apr 25 15:57:05 m0054 kernel: [161827.035409] msm_vidc:   err : 00000001: h265e: Failed to move inst: ffffffd8fc0d2000 to state 13
Apr 25 15:57:05 m0054 kernel: [161827.035412] msm_vidc:   err : 00000001: h265e: Failed STOP Streaming inst = ffffffd8fc0d2000 on cap = 9
Apr 25 15:57:05 m0054 kernel: [161827.035457] msm_vidc:   high: 00000001: h265e: Closed video instance: ffffffd8fc0d2000
Apr 25 15:57:05 m0054 voxl-portal[1760]: Most likely the server stopped without cleaning up
Apr 25 15:57:05 m0054 voxl-portal[1760]: Client is cleaning up pipes for the server
Apr 25 15:57:05 m0054 kernel: [161827.044477] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 25 15:57:05 m0054 kernel: [161827.045822] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 25 15:57:05 m0054 kernel: [161827.045834] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
Apr 25 15:57:05 m0054 kernel: [161827.045850] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
Apr 25 15:57:05 m0054 kernel: [161827.053512] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 5
Apr 25 15:57:05 m0054 kernel: [161827.053514] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 5
Apr 25 15:57:05 m0054 kernel: [161827.053515] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
Apr 25 15:57:05 m0054 kernel: [161827.053515] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
Apr 25 15:57:05 m0054 kernel: [161827.053516] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
Apr 25 15:57:05 m0054 kernel: [161827.053517] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
Apr 25 15:57:05 m0054 kernel: [161827.053517] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
Apr 25 15:57:05 m0054 kernel: [161827.053518] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
Apr 25 15:57:05 m0054 kernel: [161827.053518] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 6
Apr 25 15:57:05 m0054 kernel: [161827.053519] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 7
Apr 25 15:57:05 m0054 kernel: [161827.053520] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 9
Apr 25 15:57:05 m0054 kernel: [161827.053521] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 9
Apr 25 15:57:05 m0054 kernel: [161827.053521] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 9
Apr 25 15:57:05 m0054 kernel: [161827.053523] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
Apr 25 15:57:05 m0054 kernel: [161827.053524] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
Apr 25 15:57:05 m0054 kernel: [161827.053525] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 10
Apr 25 15:57:05 m0054 kernel: [161827.053526] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 11
Apr 25 15:57:05 m0054 kernel: [161827.053528] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 1
Apr 25 15:57:05 m0054 kernel: [161827.053529] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
Apr 25 15:57:05 m0054 kernel: [161827.053531] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
Apr 25 15:57:05 m0054 kernel: [161827.053532] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
Apr 25 15:57:05 m0054 kernel: [161827.053533] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
Apr 25 15:57:05 m0054 kernel: [161827.053534] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 3
Apr 25 15:57:05 m0054 kernel: [161827.053536] CAM_ERR: CAM-ISP: __cam_isp_ctx_release_dev_in_top_state: 3789 releasing hw
Apr 25 15:57:05 m0054 kernel: [161827.053549] CAM_INFO: CAM-ISP: cam_ife_mgr_release_hw: 4755 Release HW success ctx id: 1
Apr 25 15:57:05 m0054 kernel: [161827.053564] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died
Apr 25 15:57:05 m0054 kernel: [161827.053591] CAM-REQ-MGR_UTIL cam_req_mgr_util_free_hdls:99 CAM_WARN: CAM-CRM: cam_req_mgr_util_free_hdls: 99 Dev handle = 1e0102 session_handle = e50200
Apr 25 15:57:05 m0054 kernel: [161827.053592] CAM-REQ-MGR_UTIL cam_req_mgr_util_free_hdls:99 CAM_WARN: CAM-CRM: cam_req_mgr_util_free_hdls: 99 Dev handle = 30103 session_handle = e50200
Apr 25 15:57:05 m0054 kernel: [161827.063758] ion_buffer_destroy: 6 callbacks suppressed
Apr 25 15:57:05 m0054 kernel: [161827.063760] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 25 15:57:05 m0054 kernel: [161827.063802] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 25 15:57:05 m0054 kernel: [161827.063906] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 25 15:57:05 m0054 kernel: [161827.063914] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 25 15:57:05 m0054 kernel: [161827.064018] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 25 15:57:05 m0054 kernel: [161827.064412] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 25 15:57:05 m0054 kernel: [161827.064430] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap

@Alex-Kushleyev Here is the output from dmesg when I run the voxl-camera-server:

Apr 24 19:31:55 m0054 tailscaled[1610]: netcheck: DetectCaptivePortal(found=false)


Apr 24 19:32:14 m0054 kernel: [88334.080488] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
Apr 24 19:32:24 m0054 kernel: [88344.643537] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry
Apr 24 19:32:25 m0054 kernel: [88344.720291] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
Apr 24 19:32:25 m0054 kernel: [88344.745479] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x20:
Apr 24 19:32:25 m0054 kernel: [88344.745482] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 19:32:25 m0054 kernel: [88344.745488] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 19:32:25 m0054 kernel: [88344.745494] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x214:
Apr 24 19:32:25 m0054 kernel: [88344.745595] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.748968] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.774119] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.58
Apr 24 19:32:25 m0054 kernel: [88344.774208] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.774231] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.774316] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.798756] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
Apr 24 19:32:25 m0054 kernel: [88344.798828] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 19:32:25 m0054 kernel: [88344.798832] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 19:32:25 m0054 kernel: [88344.798838] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 19:32:25 m0054 kernel: [88344.798843] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 19:32:25 m0054 kernel: [88344.798949] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.801095] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.801128] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.801171] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.58
Apr 24 19:32:25 m0054 kernel: [88344.825623] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58
Apr 24 19:32:25 m0054 kernel: [88344.825737] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.825780] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.825906] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.840658] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 24 19:32:25 m0054 kernel: [88344.840730] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 19:32:25 m0054 kernel: [88344.840735] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 19:32:25 m0054 kernel: [88344.840737] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 19:32:25 m0054 kernel: [88344.840740] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 19:32:25 m0054 kernel: [88344.840800] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.842876] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.842906] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.842943] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58
Apr 24 19:32:25 m0054 kernel: [88344.865869] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59
Apr 24 19:32:25 m0054 kernel: [88344.866000] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.866043] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.866171] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.880067] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
Apr 24 19:32:25 m0054 kernel: [88344.880100] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 19:32:25 m0054 kernel: [88344.880104] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 19:32:25 m0054 kernel: [88344.880106] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 19:32:25 m0054 kernel: [88344.880109] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 19:32:25 m0054 kernel: [88344.880163] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.881467] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.881498] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.881538] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.59
Apr 24 19:32:25 m0054 kernel: [88344.905689] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
Apr 24 19:32:25 m0054 kernel: [88344.905829] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.905874] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.906009] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.920664] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:3,slave_addr:0x34,sensor_id:0x577
Apr 24 19:32:25 m0054 kernel: [88344.920718] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.922792] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.922822] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.922861] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
Apr 24 19:32:25 m0054 kernel: [88344.935529] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.59
Apr 24 19:32:25 m0054 kernel: [88344.935651] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.935696] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.936089] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.950853] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 24 19:32:25 m0054 kernel: [88344.950884] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 19:32:25 m0054 kernel: [88344.950890] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 19:32:25 m0054 kernel: [88344.950893] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 19:32:25 m0054 kernel: [88344.950897] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 19:32:25 m0054 kernel: [88344.950969] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.953024] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.953077] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.977985] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.59
Apr 24 19:32:25 m0054 kernel: [88344.978070] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.978115] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.978240] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.992921] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 24 19:32:25 m0054 kernel: [88344.993008] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 19:32:25 m0054 kernel: [88344.993045] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 19:32:25 m0054 kernel: [88344.993048] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 19:32:25 m0054 kernel: [88344.993050] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 19:32:25 m0054 kernel: [88344.993117] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.79
Apr 24 19:32:25 m0054 kernel: [88344.995197] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.55
Apr 24 19:32:25 m0054 kernel: [88344.995226] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.60
Apr 24 19:32:25 m0054 kernel: [88344.995271] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.59
Apr 24 19:32:25 m0054 kernel: [88345.040157] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
Apr 24 19:32:25 m0054 kernel: [88345.040247] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
Apr 24 19:32:25 m0054 kernel: [88345.040267] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
Apr 24 19:32:25 m0054 kernel: [88345.040362] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
Apr 24 19:32:25 m0054 kernel: [88345.054061] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 997 CAM_ACQUIRE_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34
Apr 24 19:32:25 m0054 kernel: [88345.055287] CAM_INFO: CAM-HFI: cam_hfi_resume: 679 Resume IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
Apr 24 19:32:25 m0054 kernel: [88345.085767] msm_vidc:   high: 00000001: ....e: Opening video instance: ffffffd908ed6000, 0
Apr 24 19:32:25 m0054 kernel: [88345.361053] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:6 IPP resource not available
Apr 24 19:32:25 m0054 kernel: [88345.361057] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:5 IPP resource not available
Apr 24 19:32:25 m0054 kernel: [88345.361059] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:4 IPP resource not available
Apr 24 19:32:25 m0054 kernel: [88345.361061] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:3 IPP resource not available
Apr 24 19:32:25 m0054 kernel: [88345.361062] CAM_ERR: CAM-ISP: cam_ife_csid_cid_reserve: 1040 CSID:2 IPP resource not available
Apr 24 19:32:25 m0054 kernel: [88345.361091] CAM_ERR: CAM-ISP: cam_ife_hw_mgr_print_acquire_info: 710 Successfully acquire single IFE[1 -1] with [9 pix] [0 pd] [1 rdi] ports for ctx:9
Apr 24 19:32:25 m0054 kernel: [88345.365802] CAM_INFO: CAM-CSIPHY: cam_csiphy_core_cfg: 1137 START_DEV: CSIPHY_IDX: 3, Device_slot: 0, Datarate: 2500000000, Settletime: 2200000000
Apr 24 19:32:25 m0054 kernel: [88345.374728] CAM_INFO: CAM-ISP: cam_vfe_bus_ver3_init_hw: 3659 Overriding clock gating at bus input
Apr 24 19:32:25 m0054 kernel: [88345.374732] CAM_INFO: CAM-ISP: cam_vfe_top_ver3_init_hw: 246 Disable clock gating at IFE top
Apr 24 19:32:25 m0054 kernel: [88345.374879] CAM_ERR: CAM-ISP: cam_ife_mgr_start_hw: 4510 ->Config HW, 0000000013f5b900
Apr 24 19:32:25 m0054 kernel: [88345.376000] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 1089 CAM_START_DEV Success, sensor_id:0x577,sensor_slave_addr:0x34
Apr 24 19:32:26 m0054 voxl-cpu-monitor[1757]: client "voxl-camera-server51691034" with id 0 has disconnected from channel 0
Apr 24 19:32:26 m0054 voxl-cpu-monitor[1757]: client "voxl-camera-server88398822" connected to channel 0  with client id 0
Apr 24 19:32:30 m0054 kernel: [88350.083476] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  0 fd 130 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083481] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  1 fd 132 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083482] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  2 fd 134 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083484] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  3 fd 136 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083485] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  4 fd 138 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083486] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  5 fd 140 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083487] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  6 fd 142 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083488] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  7 fd 144 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083489] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  8 fd 146 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083490] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx  9 fd 148 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083491] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 10 fd 150 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083492] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 11 fd 152 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083493] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 12 fd 154 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083494] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 13 fd 156 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083495] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 14 fd 158 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083496] msm_vidc:   err : 00000001: h265e: undequeud vb2: CAPTURE: idx 15 fd 160 off 0 size 884736 filled 0
Apr 24 19:32:30 m0054 kernel: [88350.083500] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  0 fd 130 off 0 daddr dfb00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083511] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  1 fd 132 off 0 daddr dfa00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083515] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  2 fd 134 off 0 daddr df900000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083519] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  3 fd 136 off 0 daddr df800000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083522] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  4 fd 138 off 0 daddr df700000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083525] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  5 fd 140 off 0 daddr df600000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083528] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  6 fd 142 off 0 daddr df500000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083532] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  7 fd 144 off 0 daddr df400000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083534] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  8 fd 146 off 0 daddr df300000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083537] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx  9 fd 148 off 0 daddr df200000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083540] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 10 fd 150 off 0 daddr df100000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083543] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 11 fd 152 off 0 daddr df000000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083546] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 12 fd 154 off 0 daddr def00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083549] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 13 fd 156 off 0 daddr dee00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083552] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 14 fd 158 off 0 daddr ded00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 kernel: [88350.083554] msm_vidc:   err : 00000001: h265e: undequeud buf: CAPTURE: idx 15 fd 160 off 0 daddr dec00000 size 884736 filled 0 flags 0x0 ts 0 refcnt 2 mflags 0x1
Apr 24 19:32:30 m0054 voxl-portal[1760]: ERROR in pipe_client_open opening request pipe: No such device or address
Apr 24 19:32:30 m0054 voxl-portal[1760]: Most likely the server stopped without cleaning up
Apr 24 19:32:30 m0054 voxl-portal[1760]: Client is cleaning up pipes for the server
Apr 24 19:32:30 m0054 voxl-portal[1760]: ERROR in pipe_client_open opening request pipe: No such device or address
Apr 24 19:32:30 m0054 voxl-portal[1760]: Most likely the server stopped without cleaning up
Apr 24 19:32:30 m0054 voxl-portal[1760]: Client is cleaning up pipes for the server
Apr 24 19:32:30 m0054 kernel: [88350.096208] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 24 19:32:30 m0054 kernel: [88350.098251] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 24 19:32:30 m0054 kernel: [88350.098263] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
Apr 24 19:32:30 m0054 kernel: [88350.098279] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
Apr 24 19:32:30 m0054 kernel: [88350.106121] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 1
Apr 24 19:32:30 m0054 kernel: [88350.106122] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
Apr 24 19:32:30 m0054 kernel: [88350.106123] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
Apr 24 19:32:30 m0054 kernel: [88350.106124] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 2
Apr 24 19:32:30 m0054 kernel: [88350.106125] CAM_ERR: CAM-SYNC: cam_sync_signal: 203 Error: accessing an uninitialized sync obj = 3
Apr 24 19:32:30 m0054 kernel: [88350.106127] CAM_ERR: CAM-ISP: __cam_isp_ctx_release_dev_in_top_state: 3789 releasing hw
Apr 24 19:32:30 m0054 kernel: [88350.106156] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died
Apr 24 19:32:30 m0054 kernel: [88350.106286] CAM-REQ-MGR_UTIL cam_req_mgr_util_free_hdls:99 CAM_WARN: CAM-CRM: cam_req_mgr_util_free_hdls: 99 Dev handle = 5a0103 session_handle = 7e0200
Apr 24 19:32:30 m0054 kernel: [88350.119201] ion_buffer_destroy: 6 callbacks suppressed
Apr 24 19:32:30 m0054 kernel: [88350.119252] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133256] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133270] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133287] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133294] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133358] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133383] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133392] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133401] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:30 m0054 kernel: [88350.133426] ION client likely missing a call to dma_buf_kunmap or dma_buf_vunmap
Apr 24 19:32:31 m0054 kernel: [88351.602923] msm_vidc:   err : ffffffff: .....: DBLP Set: status 0

@Alex-Kushleyev - Thanks again!

Here is the output from /var/log/syslog when I run "voxl-camera-server -l":

Apr 24 13:55:58 m0054 kernel: [68157.917569] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
Apr 24 13:55:58 m0054 kernel: [68157.917657] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
Apr 24 13:55:58 m0054 kernel: [68157.946997] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 24 13:55:58 m0054 kernel: [68157.947039] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x20:
Apr 24 13:55:58 m0054 kernel: [68157.947042] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 13:55:58 m0054 kernel: [68157.947044] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 13:55:58 m0054 kernel: [68157.947118] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 24 13:55:58 m0054 kernel: [68157.950956] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 24 13:55:58 m0054 kernel: [68157.950973] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
Apr 24 13:55:58 m0054 kernel: [68157.976036] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.58
Apr 24 13:55:58 m0054 kernel: [68157.976121] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.60
Apr 24 13:55:58 m0054 kernel: [68157.976135] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.55
Apr 24 13:55:58 m0054 kernel: [68157.976219] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.79
Apr 24 13:55:58 m0054 kernel: [68158.005077] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
Apr 24 13:55:58 m0054 kernel: [68158.005148] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 13:55:58 m0054 kernel: [68158.005150] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 13:55:58 m0054 kernel: [68158.005151] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 13:55:58 m0054 kernel: [68158.005152] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 13:55:58 m0054 kernel: [68158.006941] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.55
Apr 24 13:55:58 m0054 kernel: [68158.006950] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.60
Apr 24 13:55:58 m0054 kernel: [68158.006982] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.58
Apr 24 13:55:58 m0054 kernel: [68158.032566] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58
Apr 24 13:55:58 m0054 kernel: [68158.032721] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60
Apr 24 13:55:58 m0054 kernel: [68158.032773] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.55
Apr 24 13:55:58 m0054 kernel: [68158.032908] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79
Apr 24 13:55:58 m0054 kernel: [68158.047391] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 24 13:55:58 m0054 kernel: [68158.047453] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 13:55:58 m0054 kernel: [68158.047460] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 13:55:58 m0054 kernel: [68158.047463] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 13:55:58 m0054 kernel: [68158.047466] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 13:55:58 m0054 kernel: [68158.071859] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59
Apr 24 13:55:58 m0054 kernel: [68158.071964] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60
Apr 24 13:55:58 m0054 kernel: [68158.072012] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.55
Apr 24 13:55:58 m0054 kernel: [68158.072156] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79
Apr 24 13:55:58 m0054 kernel: [68158.086849] CAM_ERR: CAM-CCI: cam_cci_irq: 238 Base:        pK-error, M0_Q1 NACK ERROR: 0x10000000
Apr 24 13:55:58 m0054 kernel: [68158.087102] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79
Apr 24 13:55:58 m0054 kernel: [68158.111682] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
Apr 24 13:55:58 m0054 kernel: [68158.111767] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
Apr 24 13:55:58 m0054 kernel: [68158.111807] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
Apr 24 13:55:58 m0054 kernel: [68158.111928] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
Apr 24 13:55:58 m0054 kernel: [68158.126905] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:3,slave_addr:0x34,sensor_id:0x577
Apr 24 13:55:58 m0054 kernel: [68158.126957] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
Apr 24 13:55:58 m0054 kernel: [68158.129028] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
Apr 24 13:55:58 m0054 kernel: [68158.129054] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
Apr 24 13:55:58 m0054 kernel: [68158.129093] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
Apr 24 13:55:58 m0054 kernel: [68158.142057] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.59
Apr 24 13:55:58 m0054 kernel: [68158.142146] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.60
Apr 24 13:55:58 m0054 kernel: [68158.142191] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.55
Apr 24 13:55:58 m0054 kernel: [68158.142399] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Linked as a consumer to regulator.79
Apr 24 13:55:59 m0054 kernel: [68158.157433] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 24 13:55:59 m0054 kernel: [68158.157491] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 13:55:59 m0054 kernel: [68158.157496] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 13:55:59 m0054 kernel: [68158.157498] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 13:55:59 m0054 kernel: [68158.157502] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 13:55:59 m0054 kernel: [68158.157592] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.79
Apr 24 13:55:59 m0054 kernel: [68158.159023] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.55
Apr 24 13:55:59 m0054 kernel: [68158.159056] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor4: Dropping the link to regulator.60
Apr 24 13:55:59 m0054 kernel: [68158.183788] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.59
Apr 24 13:55:59 m0054 kernel: [68158.183871] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.60
Apr 24 13:55:59 m0054 kernel: [68158.183911] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.55
Apr 24 13:55:59 m0054 kernel: [68158.184037] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Linked as a consumer to regulator.79
Apr 24 13:55:59 m0054 kernel: [68158.198670] CAM_ERR: CAM-CCI: cam_cci_irq: 264 Base:        pK-error, M1_Q1 NACK ERROR: 0x40000000
Apr 24 13:55:59 m0054 kernel: [68158.198737] CAM_ERR: CAM-CCI: cam_cci_read: 1329 ERROR with Slave 0x34:
Apr 24 13:55:59 m0054 kernel: [68158.198740] CAM_ERR: CAM-CCI: cam_cci_read_bytes: 1613 failed to read rc:-22
Apr 24 13:55:59 m0054 kernel: [68158.198742] CAM_ERR: CAM-SENSOR: cam_cci_i2c_read: 35 rc = -22
Apr 24 13:55:59 m0054 kernel: [68158.198745] CAM_WARN: CAM-SENSOR: cam_sensor_match_id: 707 read id: 0x0 expected id 0x577:
Apr 24 13:55:59 m0054 kernel: [68158.198801] qcom,camera ac50000.qcom,cci:qcom,cam-sensor5: Dropping the link to regulator.79
Apr 24 13:55:59 m0054 kernel: [68158.239903] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died

I'll wait for your feedback, but I can try reinstalling the drivers from your tutorial and if that doesn't work, I can reflash the SDK as well.