<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[VOXL 2 (M0054-1) secure boot: signing inputs, OEM ID and signed firehose]]></title><description><![CDATA[<p dir="auto">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:</p>
<ol>
<li>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.</li>
<li>The OEM ID and Model ID used on VOXL 2, and any sec.dat or fuse settings you use or recommend.</li>
<li>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?</li>
<li>Are any QFPROM fuses blown on shipped units?</li>
<li>Does the current system image use ICE inline encryption (FBE) for /data? If yes, where are the keys held (TEE, RPMB)?</li>
<li>Does ABL support verified boot (AVB) for the kernel and root filesystem?</li>
<li>Any known issues or guidance for secure boot on VOXL 2.</li>
</ol>
<p dir="auto">If any of this needs an NDA or a support contract, please tell us how to set it up.</p>
<p dir="auto">Thanks,<br />
Ilan</p>
]]></description><link>https://forum.modalai.com/topic/5551/voxl-2-m0054-1-secure-boot-signing-inputs-oem-id-and-signed-firehose</link><generator>RSS for Node</generator><lastBuildDate>Tue, 17 Nov 2026 18:52:13 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/topic/5551.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 17 Nov 2026 08:45:13 GMT</pubDate><ttl>60</ttl></channel></rss>