<?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[VOXL2 Flashing upstream kernel v5 or v6 using ModalAI Device Tree]]></title><description><![CDATA[<p dir="auto">Does the VOXL2 come with Secure Boot enabled? I.e. can I take an upstream kernel from <a href="http://kernel.org" rel="nofollow ugc">kernel.org</a> and simply append the Device Tree Blob from the ModalAI SDK GitHub to generate a bootable image loaded via fastboot? Do I need either a special unlock of the device or proprietary software components to boot the device if I do not need the user-space flight/camera features? I am comparing to the Linaro open-source option for a Thundercomm RB5, where I can load a custom ABL and kernel without signing images. Is there a similar option for the  VOXL2, as it has piqued our interest for its SWAP advantages?</p>
<p dir="auto">Thank you</p>
]]></description><link>https://forum.modalai.com/topic/2860/voxl2-flashing-upstream-kernel-v5-or-v6-using-modalai-device-tree</link><generator>RSS for Node</generator><lastBuildDate>Fri, 11 Sep 2026 10:26:30 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/topic/2860.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 14 Nov 2023 18:40:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to VOXL2 Flashing upstream kernel v5 or v6 using ModalAI Device Tree on Thu, 16 Nov 2023 00:01:21 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/dsupplee" aria-label="Profile: dsupplee">@<bdi>dsupplee</bdi></a> yes, the images on VOXL 2 are unsigned. please see the VOXL 2 kernel build guide here: : <a href="https://docs.modalai.com/voxl2-kernel-build-guide/" rel="nofollow ugc">https://docs.modalai.com/voxl2-kernel-build-guide/</a></p>
]]></description><link>https://forum.modalai.com/post/13248</link><guid isPermaLink="true">https://forum.modalai.com/post/13248</guid><dc:creator><![CDATA[Moderator]]></dc:creator><pubDate>Thu, 16 Nov 2023 00:01:21 GMT</pubDate></item><item><title><![CDATA[Reply to VOXL2 Flashing upstream kernel v5 or v6 using ModalAI Device Tree on Wed, 15 Nov 2023 18:13:42 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/moderator" aria-label="Profile: Moderator">@<bdi>Moderator</bdi></a> Thank you for your timely response</p>
<p dir="auto">I understand that the SDK uses that method to preserve proprietary features, but if one does not need those features, does the VOXL 2 bootloader allow for loading custom images into the "boot" partition? The device shouldn't care how the image is built, and so I mainly ask about the feasibility of flashing unsigned images (regardless of how they were built) to the "boot", "rootfs", and "user" partitions with something like fastboot.</p>
]]></description><link>https://forum.modalai.com/post/13238</link><guid isPermaLink="true">https://forum.modalai.com/post/13238</guid><dc:creator><![CDATA[dsupplee]]></dc:creator><pubDate>Wed, 15 Nov 2023 18:13:42 GMT</pubDate></item><item><title><![CDATA[Reply to VOXL2 Flashing upstream kernel v5 or v6 using ModalAI Device Tree on Wed, 15 Nov 2023 17:37:35 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/dsupplee" aria-label="Profile: dsupplee">@<bdi>dsupplee</bdi></a> you can find details of how to build the kernel for VOXL 2 here: <a href="https://docs.modalai.com/voxl2-kernel-build-guide/" rel="nofollow ugc">https://docs.modalai.com/voxl2-kernel-build-guide/</a></p>
<p dir="auto">VOXL 2 uses the "Qualcomm method" for builds and we rely on many of Qualcomm's proprietary features which does not lend itself well to full open source.</p>
]]></description><link>https://forum.modalai.com/post/13235</link><guid isPermaLink="true">https://forum.modalai.com/post/13235</guid><dc:creator><![CDATA[Moderator]]></dc:creator><pubDate>Wed, 15 Nov 2023 17:37:35 GMT</pubDate></item></channel></rss>