Subcategories

• VOXL 2 Mini

  VOXL 2 Support Forum

  55
  Topics
  312
  Posts

  J

  Hello

  We are experiencing issues when connecting via wifi. We setup the voxl-wifi on 5ghz and it will work great for a while. Eventually, after a few days with minimal changes it will stop working. We can ifconfig wlan0 down and up again to get some signal, but it is very weak.

  The things we have changed is all on the px4 side and the camera configs, so nothing with softap specifically other then setting it up.

  We keep getting to the point where we factory reset the drone and then it works again for a few days. Any advice or assistance would be beneficial.

  Thank you

• VOXL 2

  VOXL 2 Support Forum

  559
  Topics
  3114
  Posts

  L

  Hi all,

  I'm attempting to recover the last flight logs from a VOXL 2 that suffered a crash. The VOXL 2 appears to power on normally (LEDs light up, board shows no visible damage), but it will not allow me to connect via ADB, SSH, or fastboot.

  When connected to a PC, the device shows up as: Qualcomm HS-USB QDLoader 9008, so EDL.

  My goal:
  I'm trying to recover flight logs from the onboard UFS storage before re-flashing the system image.

  What I've tried:

  Installed Qualcomm USB drivers to recognize Qualcomm HS-USB QDLoader 9008 as COM5 Installed QPST/QFIL 2.7.460 (digitally signed Qualcomm build) Tried accessing partitions via QFIL's Partition Manager using various prog_firehose_ddr.elf files
  Every attempt so far results in: ERROR: function: sahara_rx_data: Unable to read packet header. Only read 0 bytes. ERROR: function: sahara_main: Sahara protocol error ERROR: function: main: Uploading Image using Sahara protocol failed Download Fail: Sahara Fail: QsaharaServer Fail: Process fail

  Hardware Information:

  Model: VOXL 2 (M0154) Software was likely VOXL2 SDK 1.40? I've accessed VOXL2 QDL Image 14.1a_1.7.8, VOXL2 QDL Image 14.1a_1.1.2, and M0054-2 Starling QDL Image 1.7.4, for their prog_firehose_ddr.elf files and none have worked.

  Questions:
  Before proceeding with ModalAI's QDL web-based flashing tool (which I understand will wipe the UFS storage), I'm trying to confirm:

  Is there a VOXL 2 M0154 specific QDL image that includes the correct prog_firehose_ddr.elf for data recovery? Can the modal-qdl CLI or GUI tools be used in a non-destructive way to read partitions, similar to QFIL's "Read Data" function? If not, is there any safe way to extract the partitions regarding flight logs before flashing the board back to factory state?

  System Setup:

  Host: Windows 11 + Ubuntu (WSL2) Device Manager shows: Qualcomm HS-USB QDLoader 9008 (COM 5) When attaching the Bus ID from Windows to WSL, lsusb shows: Bus 001 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

  Any help or access to the proper prog_firehose_ddr.elf for M0154 would be greatly appreciated.
  My main priority is preserving those flight logs to narrow down what went wrong during a simple arm test.

  Images:
  (This VOXL 2 was from a legacy flight deck)
  20251108_111842.jpg
  (QFIL Tool attempts for data recovery)
  Screenshot 2025-11-08 112441.png

• VOXL Flight
  77
  Topics
  300
  Posts

  L

  @LucasW to answer my own question, VOXL supports 5 GHz. This can be verified by running iw list and looking at the supported channels.

  The /data/misc/wifi/wpa_supplicant.conf file does not seem to take effect when trying to specify frequencies, for instance (for 5 GHz channels 36, 40, 44, and 48:

  country=ch ctrl_interface=/var/run/wpa_supplicant network={ ssid="my-ssid" bssid=00:00:00:00:00:00 freq_list=5180 5200 5220 5240 scan_freq=5180 5200 5220 5240 proto=RSN key_mgmt=WPA-PSK pairwise=CCMP TKIP group=CCMP TKIP psk="my-pwd" }

  The only way I found to connect to 5 GHz is to disable the 2.4 GHz radio entirely on the router. Otherwise, the connection defaults to 2.4 GHz.
  On the router, it is also better to set a fixed channel (e.g., 36) rather than letting it be automatic. In auto mode, the robots could not connect systematically to the network.

  Note also that my question was wrong in the sense that the hostapd.conf files are used to generate the access point, not to connect in station mode.

  These are maybe considerations that could be added to the technical doc @Chad-Sweet ?

• VOXL
  119
  Topics
  560
  Posts

  A

  @qqa , we have document how to achieve folder-level encryption on VOXL2 here : https://docs.modalai.com/enabling-file-encryption/ . Please let us know if you have any other questions.

• Flight Core v2
  41
  Topics
  232
  Posts

  E

  @adiprin1 Can you please start a new forum topic for this? And please include information about the device that you are looking to attach? Thanks!

• Flight Core
  36
  Topics
  135
  Posts

  T

  Unbricked! Here's some context/advice for anyone trying to do the same. If you purchased a cheapo STLINK V2 from Amazon as I did. Picture below...

  alt text

  $0 Fix:
  What may very well happen to ya, is the RESET pin doesn't work. In this case you will need a friend. With said friend, you must dilligently connect to the board using Under Reset Mode and Hardware Reset. The second your homie clicks the connect button, you, the bricker of the board must move your jumper cable from the RESET pin which is 3.3V to an open Ground, leave it for exactly 1 second, then move it back to RESET. This should work like a charm, but may require one or two tries to get the right timing. See instructions below.

  alt text

  $10 Fix:
  Program a Pico/Arduino to do your 1 second ground for you.

  $78 Fix:
  Buy the real STLINK V2.

• VOXL 2 IO

  VOXL 2 I/O (M0065) Support

  24
  Topics
  173
  Posts

  J

  @Alex-Kushleyev ,

  Thank you for the clarification!

  We will change the service and see if it meets our needs.

  Regards,
  Jacob

• Flight Core - ArduPilot
  3
  Topics
  12
  Posts

  P

  ok I found the problem...
  the Cube Serial inteface are driven by TXS0108E Level Shifter powered both side with 3.3 volt making it marginal for the Voxl Primary Serial interface. Switching to secondary interface on the Voxl made it work correctly.

  I sent a request for a change in the WIKI to reflect that configuration

  40f28124-b098-4482-a038-25c450b9df6c-image.png