<?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[Getting to OTA DFU]]></title><description><![CDATA[<p dir="auto">We're trying to get to the point where we can update a FiPy's firmware over-the-air.</p>
<p dir="auto">When would someone what to follow the instructions here:<br />
<a href="https://github.com/pycom/pycom-micropython-sigfox#steps-for-using-secure-boot-and-flash-encryption" target="_blank" rel="noopener noreferrer nofollow">https://github.com/pycom/pycom-micropython-sigfox#steps-for-using-secure-boot-and-flash-encryption</a><br />
Specifically, am I correct in thinking the FiPy comes delivered with the bootloader already installed, and so the above is only necessary for newly manufactured hardware that has no bootloader on it?  Or is the bootloader that ships with the FiPy not using Secure Boot/encryption and this process must be used to add these to protect the code from unintended eyes?</p>
<p dir="auto">Going through the instructions linked to above, our pyTrack board shows up as ttyACM0 instead of ttyUSB0 (we tried both Ubuntu and Debian).  Executing:</p>
<pre><code>python $IDF_PATH/components/esptool_py/esptool/espefuse.py --port /dev/ttyACM0 burn_key flash_encryption flash_encryption_key.bin
</code></pre>
<p dir="auto">we get</p>
<pre><code>A fatal error occurred: Failed to connect to ESP32: Invalid head of packet ('\x08')
</code></pre>
<p dir="auto">Thanks for any guidance you can offer!</p>
]]></description><link>https://forum.pycom.io/topic/4403/getting-to-ota-dfu</link><generator>RSS for Node</generator><lastBuildDate>Fri, 17 Apr 2026 21:10:40 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/topic/4403.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 18 Feb 2019 15:36:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Getting to OTA DFU on Mon, 18 Feb 2019 15:36:25 GMT]]></title><description><![CDATA[<p dir="auto">We're trying to get to the point where we can update a FiPy's firmware over-the-air.</p>
<p dir="auto">When would someone what to follow the instructions here:<br />
<a href="https://github.com/pycom/pycom-micropython-sigfox#steps-for-using-secure-boot-and-flash-encryption" target="_blank" rel="noopener noreferrer nofollow">https://github.com/pycom/pycom-micropython-sigfox#steps-for-using-secure-boot-and-flash-encryption</a><br />
Specifically, am I correct in thinking the FiPy comes delivered with the bootloader already installed, and so the above is only necessary for newly manufactured hardware that has no bootloader on it?  Or is the bootloader that ships with the FiPy not using Secure Boot/encryption and this process must be used to add these to protect the code from unintended eyes?</p>
<p dir="auto">Going through the instructions linked to above, our pyTrack board shows up as ttyACM0 instead of ttyUSB0 (we tried both Ubuntu and Debian).  Executing:</p>
<pre><code>python $IDF_PATH/components/esptool_py/esptool/espefuse.py --port /dev/ttyACM0 burn_key flash_encryption flash_encryption_key.bin
</code></pre>
<p dir="auto">we get</p>
<pre><code>A fatal error occurred: Failed to connect to ESP32: Invalid head of packet ('\x08')
</code></pre>
<p dir="auto">Thanks for any guidance you can offer!</p>
]]></description><link>https://forum.pycom.io/post/25984</link><guid isPermaLink="true">https://forum.pycom.io/post/25984</guid><dc:creator><![CDATA[criegel]]></dc:creator><pubDate>Mon, 18 Feb 2019 15:36:25 GMT</pubDate></item><item><title><![CDATA[Reply to Getting to OTA DFU on Mon, 18 Feb 2019 20:36:02 GMT]]></title><description><![CDATA[<p dir="auto">You have to go through all steps, the bootloader is not encrypted from the beginning.</p>
<p dir="auto">I am not sure about the error. Did you boot into bootloader mode, if not, that might be your problem.</p>
]]></description><link>https://forum.pycom.io/post/25991</link><guid isPermaLink="true">https://forum.pycom.io/post/25991</guid><dc:creator><![CDATA[johand]]></dc:creator><pubDate>Mon, 18 Feb 2019 20:36:02 GMT</pubDate></item></channel></rss>