Posts made by Nathan Raras

@david-moro We can work on adding those drivers in the next system image as well as provide you with a a pre-release binary to support your configuration once it has been fully tested

Hi @david-moro , currently our latest SDK supports ov9782 on J6 (HW ID 0) and imx214 on J6 (HW ID 0) or J7 (HW ID 2 and 3). To setup your current config on a VOXL 2 mini would require the imx214 hires to be connected to the J7 camera port. Refer to our VOXL 2 mini image sensor documentation here

Hey @user887

I attempted to QDL flash a "golden unit" rb5 but wasn't able to replicate the error you're experiencing. I would remove and reattach the SOM ensuring there isn't a loose connection to the rb5 board, remove any cameras or connectors, and trying a different USB cable in the case of a loose connection between the USB cable and rb5.

Hope these tips help!

Hi @Jonathan-Davis,

Our Starling v2 VOXL 2 board requires this flat build image (M0054-2 Starling QDL Image 1.7.4) which is available in our protected downloads as well as in the unbricking documentation here where you can proceed with the same step-by-step instructions. When finished, the qdl command should complete and the terminal should output "partition 1 is now bootable" indicating a successful QDL flash.

Hope this helps!

@LucaVertiq Looking at your voxl-camera-server.conf file, it looks like the configurations are flipped in which tracking should be on camera_id: 0 and hires should be on camera_id: 1. Deleting the camera drivers in /usr/lib/camera and reconfiguring should fix that issue in your voxl-camera-server.conf file

rm com.qti.sensormodule.imx214_3.bin

rm com.qti.sensormodule.ov7251_2.bin 

voxl-configure-cameras 04

@LucaVertiq It seems that we had switched the image sensor binaries for 1.1.1 in which the tracking camera is connected to JL and hires is connected to JU as follows:

After running the C4 configuration, you should be able to see the cameras enumerate when running:

voxl-camera-server -l

To view the pipes for each camera, we can run voxl-camera-server in debug mode using:

voxl-camera-server -d0

and in a seperate terminal, run:

voxl-inspect-cam -a

Hope this helps!

@LucaVertiq I was able to replicate the same setup by following the documentation you provided. Running this command, which is documented at the bottom of the C4 camera configuration, switches the camera ids so that hires is on 0 and tracking is on 1 rather than vice versa. I was able to detect the two cameras but too could not get voxl-camera-server running yet. Hope this helps a bit!