Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

  1. ModalAI Support Forum
  2. VOXL 2 and VOXL 2 Mini
  3. VOXL 2 (M0054-1) secure boot: signing inputs, OEM ID and signed firehose

VOXL 2 (M0054-1) secure boot: signing inputs, OEM ID and signed firehose

Scheduled Pinned Locked Moved Unsolved VOXL 2 and VOXL 2 Mini
2 Posts 2 Posters 48 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Ilan GanorI Offline
    Ilan GanorI Offline
    Ilan Ganor
    wrote last edited by
    #1

    We are enabling Qualcomm secure boot on VOXL 2 (QRB5165, M0054-1) with our own signing key, then closing debug with QFPROM fuses, and adding encrypted storage. We will sign with SecTools v2 from the QRB5165 SDK. To do that we need a few things from the VOXL 2 side:

    1. Unsigned boot images for the current VOXL 2 system image (XBL, TZ, devcfg, AOP, DSP and modem firmware, ABL), or a build path that produces them.
    2. The OEM ID and Model ID used on VOXL 2, and any sec.dat or fuse settings you use or recommend.
    3. A firehose programmer we can sign with our key, so fused units can still be flashed over EDL. Does the VOXL 2 flash flow (QDL, fastboot) work with a signed firehose?
    4. Are any QFPROM fuses blown on shipped units?
    5. Does the current system image use ICE inline encryption (FBE) for /data? If yes, where are the keys held (TEE, RPMB)?
    6. Does ABL support verified boot (AVB) for the kernel and root filesystem?
    7. Any known issues or guidance for secure boot on VOXL 2.

    If any of this needs an NDA or a support contract, please tell us how to set it up.

    Thanks,
    Ilan

    1 Reply Last reply
    0
    • Hector NevarezH Offline
      Hector NevarezH Offline
      Hector Nevarez
      ModalAI Team
      wrote last edited by
      #2

      Hi Ilan,

      Secure boot isn't something we've validated on VOXL 2 ourselves. To answer your questions, we did a one-off test: we re-signed the images from our flatbuild with a throwaway test key and checked that SecTools could sign and validate them. We haven't flashed re-signed images, booted them, or fused a board. Please treat the below as what we believe the path is, not a tested procedure.

      One caution before you blow any fuses: QFPROM fuses are one-time and can't be undone. A wrong key hash, OEM ID or Model ID, or any image in the boot chain signed with the wrong key, could permanently brick the board. We'd recommend flashing your signed images on an unfused board first and making sure everything boots and runs, then fusing a board for real.

      1. Unsigned boot images for the current VOXL 2 system image (XBL, TZ, devcfg, AOP, DSP and modem firmware, ABL), or a build path that produces them.

      You'll need to go to downloads.modalai.com to get the flatbuild for M0054-1. It's under downloads/Flat Builds/M0054(154)-1.zip. It has the boot images (XBL, TZ, devcfg, AOP, ABL), the DSP firmware (inside NON-HLOS.bin), and the firehose programmer.

      These images aren't unsigned. They're signed with Qualcomm's default SecTools test key, with OEM ID and Model ID set to 0x0000. We believe you can re-sign them with your own key rather than starting from unsigned images. In our test, SecTools replaced only the signature and the code stayed the same. A few images (TZ, QUP firmware, and part of XBL) also carry a Qualcomm production signature, and SecTools kept it when we re-signed.

      1. The OEM ID and Model ID used on VOXL 2, and any sec.dat or fuse settings you use or recommend.

      We don't sign the images with our own key. The flatbuild carries Qualcomm's default test signature with OEM ID and Model ID at 0x0000. We don't ship a sec.dat and don't blow any secure boot fuses, so we don't believe there's anything from our side you'd need to match. Whatever OEM ID and Model ID you choose should match between your fuse settings and the images you sign.

      1. A firehose programmer we can sign with our key, so fused units can still be flashed over EDL. Does the VOXL 2 flash flow (QDL, fastboot) work with a signed firehose?

      The firehose programmer is in the flatbuild as ufs/prog_firehose_ddr.elf, and we were able to re-sign it the same way as the other images. We haven't tested our flash flow on a fused board, so we can't say yet whether QDL or fastboot work there. Make sure you have a working signed firehose before you fuse, since that's likely your only way to recover a board over EDL.

      1. Are any QFPROM fuses blown on shipped units?

      No, we don't blow QFPROM fuses on shipped units.

      1. Does the current system image use ICE inline encryption (FBE) for /data? If yes, where are the keys held (TEE, RPMB)?

      No. /data isn't encrypted; it's a plain ext4 partition. The kernel has inline encryption support built in, but our image doesn't set it up, so there's no key storage to describe on our side.

      1. Does ABL support verified boot (AVB) for the kernel and root filesystem?

      Not at the moment. ABL has support for verified boot and dm-verity, but both are turned off in our build. The boot image has no AVB footer and the vbmeta partitions are empty, so ABL boots the kernel without checking it.

      Turning it on would mean rebuilding ABL with verified boot enabled and signing the boot image with your key. dm-verity also needs a read-only root filesystem, and VOXL 2's rootfs is read-write today, so that part would be a bigger change.

      1. Any known issues or guidance for secure boot on VOXL 2.

      The main one we expect is that PX4 on the DSP will likely stop working. VOXL 2 generates a per-device test signature at first boot so PX4 and our sensor code can run on the sensors DSP (SLPI). We don't expect test signatures to be accepted on a fused board, so those DSP libraries would need production signing before PX4 will load. Depending on the method, that may need a rebuilt SLPI firmware from our side, so please let us know before you fuse if you need PX4 running.

      Let me know if you have additional questions thanks!

      1 Reply Last reply
      0

      Reading along? Create a free ModalAI Forum account to join in.

      With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.

      Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      ModalAI
      Categories Recent Tags ModalAI.com Docs
      © 2026 ModalAI® · Accelerating autonomy for smaller, smarter, safer drones · Powered by NodeBB
      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups