@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.