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:
- 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.
- The OEM ID and Model ID used on VOXL 2, and any sec.dat or fuse settings you use or recommend.
- 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?
- Are any QFPROM fuses blown on shipped units?
- Does the current system image use ICE inline encryption (FBE) for /data? If yes, where are the keys held (TEE, RPMB)?
- Does ABL support verified boot (AVB) for the kernel and root filesystem?
- 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