@claw When finished, the terminal will display "partition 1 is now bootable" which signifies that the flat build was successfully flashed

I added some changes to output the data in the log, if you were to do a "git pull", you'll be able to see log data for Provision/CDT/Flat Build. There is a timeout implemented to avoid any issues that can cause the the process to hang indefinitely. Through testing we've noticed a significant difference in using a high speed USB-C cable which cuts the flat build flash roughly in half. If you do not have that available, you can run the following command inside /modal-qdl/qdl/qfil_app/modalai/2024-06-17-1.7.4-M0054-1/ufs to flash the flat build manually (no timeout):

sudo qdl --debug --storage ufs --include . prog_firehose_ddr.elf rawprogram_unsparse0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml

@claw I see, when you open the flat build folder, are the following contents displayed as such:

I've seen some occurrences after downloading the zip where the flat build folder gets extracted inside another folder. If that is the case, move the actual flat build folder to look like the image above.

If not, inside the ufs folder of the flat build image, you can run this command manually for a more detailed output:

sudo qdl --debug --storage ufs --include . prog_firehose_ddr.elf rawprogram_unsparse0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml

@claw After downloading the flat build zip file from our downloads page here, extract them into the following directory:

/modal-qdl/qdl/qfil_app/modalai

When running the QDL application, the downloaded flat build will populate in the drop down menu where you'll select the flat build, click "Select Build", and then click "Flash Flat Build". Let me know if you have any other issues.

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