<?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[Fipy Firmware]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto"><strong>Problem</strong><br />
I have just received my 2 x FiPy and Expansion Board yesterday.<br />
When I perform firmware update according to the pycom doc, only one of them update firmware successfully.  May I know what is the cause? And is there other way to update firmware manually? Thanks.</p>
<p dir="auto"><strong>Wiring</strong></p>
<ol>
<li>Wired G23 to GND pins on Expansion Board.</li>
<li>TX &amp; RX connectors on Expansion Board are secured.</li>
<li>Insert FiPy module in Expansion Board (same Board for both FiPy).</li>
<li>Connect Expansion Board to Windows PC via USB.</li>
<li>Run pycom-fwtool.exe to perform firmware update.</li>
</ol>
<p dir="auto"><strong>Result</strong></p>
<p dir="auto"><strong>1st FiPy (after successful update)</strong></p>
<pre><code>&gt;&gt;&gt; os.uname()
(sysname='FiPy', nodename='FiPy', release='1.15.0.b1', version='v1.8.6-849-baa8c33 on 2018-01-29', machine='FiPy with ESP32', lorawan='1.0.0', sigfox='1.0.1')
</code></pre>
<p dir="auto"><strong>2nd FiPy (unsuccessful update)</strong></p>
<pre><code>&gt;&gt;&gt; os.uname()
(sysname='FiPy', nodename='FiPy', release='1.10.0.b1', version='v1.8.6-834-g5677703c on 2017-11-13', machine='FiPy withESP32', lorawan='1.0.0')
&gt;&gt;&gt; binascii.hexlify(machine.unique_id())
b'30aea42d5b64'
</code></pre>
]]></description><link>https://forum.pycom.io/topic/2614/fipy-firmware</link><generator>RSS for Node</generator><lastBuildDate>Mon, 18 May 2026 06:55:36 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/topic/2614.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 09 Feb 2018 10:54:19 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Fipy Firmware on Fri, 09 Feb 2018 11:51:03 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto"><strong>Problem</strong><br />
I have just received my 2 x FiPy and Expansion Board yesterday.<br />
When I perform firmware update according to the pycom doc, only one of them update firmware successfully.  May I know what is the cause? And is there other way to update firmware manually? Thanks.</p>
<p dir="auto"><strong>Wiring</strong></p>
<ol>
<li>Wired G23 to GND pins on Expansion Board.</li>
<li>TX &amp; RX connectors on Expansion Board are secured.</li>
<li>Insert FiPy module in Expansion Board (same Board for both FiPy).</li>
<li>Connect Expansion Board to Windows PC via USB.</li>
<li>Run pycom-fwtool.exe to perform firmware update.</li>
</ol>
<p dir="auto"><strong>Result</strong></p>
<p dir="auto"><strong>1st FiPy (after successful update)</strong></p>
<pre><code>&gt;&gt;&gt; os.uname()
(sysname='FiPy', nodename='FiPy', release='1.15.0.b1', version='v1.8.6-849-baa8c33 on 2018-01-29', machine='FiPy with ESP32', lorawan='1.0.0', sigfox='1.0.1')
</code></pre>
<p dir="auto"><strong>2nd FiPy (unsuccessful update)</strong></p>
<pre><code>&gt;&gt;&gt; os.uname()
(sysname='FiPy', nodename='FiPy', release='1.10.0.b1', version='v1.8.6-834-g5677703c on 2017-11-13', machine='FiPy withESP32', lorawan='1.0.0')
&gt;&gt;&gt; binascii.hexlify(machine.unique_id())
b'30aea42d5b64'
</code></pre>
]]></description><link>https://forum.pycom.io/post/15605</link><guid isPermaLink="true">https://forum.pycom.io/post/15605</guid><dc:creator><![CDATA[philip_teoph]]></dc:creator><pubDate>Fri, 09 Feb 2018 11:51:03 GMT</pubDate></item><item><title><![CDATA[Reply to Fipy Firmware on Fri, 09 Feb 2018 10:58:08 GMT]]></title><description><![CDATA[<p dir="auto">I have similar problem. FIPY doesn't work.<br />
I tried also building from GIT and enabling logs. Seems that is HW/power issue and the modem is not responding . On GPY same actions have results in modem GSM initialized.</p>
<pre><code>            rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
            configsip: 0, SPIWP:0xee
            clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
            mode:DIO, clock div:1
            load:0x3fff9028,len:8
            load:0x3fff9030,len:1060
            load:0x4009fa00,len:0
            ho 12 tail 0 room 4
            load:0x4009fa00,len:14084
            entry 0x400a05d4

            GPIO direction configured

            uart_set_pin done

            uart_driver_install done
            MicroPython baa8c33-dirty on 2018-02-09; FiPy with ESP32
            Type &quot;help()&quot; for more information.
            &gt;&gt;&gt;
            AT COMMAND: [AT..]
            AT: TIMEOUT
            ONLINE, DISCONNECTING...
            AT COMMAND: [ATH..]
            AT: TIMEOUT
            AT COMMAND: [ATH..]
            AT: TIMEOUT
            AT COMMAND: [ATH..]
            AT: TIMEOUT
            AT COMMAND: [ATH..]
            AT: TIMEOUT
            STILL CONNECTED.
            AT COMMAND: [ATH..]
            AT: TIMEOUT
            AT COMMAND: [ATH..]
            AT: TIMEOUT</code></pre>
]]></description><link>https://forum.pycom.io/post/15606</link><guid isPermaLink="true">https://forum.pycom.io/post/15606</guid><dc:creator><![CDATA[Colateral]]></dc:creator><pubDate>Fri, 09 Feb 2018 10:58:08 GMT</pubDate></item><item><title><![CDATA[Reply to Fipy Firmware on Fri, 09 Feb 2018 11:54:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/2302">@philip_teoph</a></p>
<p dir="auto">Hi,</p>
<p dir="auto">When you tried to update the firmware on the second FiPy, what error did you receive? Are you using the latest updater? (<a href="https://software.pycom.io/findupgrade?product=pycom-firmware-updater&amp;type=all&amp;platform=win32&amp;redirect=true" target="_blank" rel="noopener noreferrer nofollow">https://software.pycom.io/findupgrade?product=pycom-firmware-updater&amp;type=all&amp;platform=win32&amp;redirect=true</a>)</p>
]]></description><link>https://forum.pycom.io/post/15616</link><guid isPermaLink="true">https://forum.pycom.io/post/15616</guid><dc:creator><![CDATA[seb]]></dc:creator><pubDate>Fri, 09 Feb 2018 11:54:44 GMT</pubDate></item><item><title><![CDATA[Reply to Fipy Firmware on Mon, 12 Feb 2018 03:33:48 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/1881">@seb</a> I bought and received both FiPy at the same time and try to update both FiPy modules using same Expansion Board with same pycom firmware update software using same Windows PC.</p>
<p dir="auto">The first FiPy updated successfully.<br />
The second FiPy unsuccessfully in updating.</p>
<p dir="auto">The error is as follows:-<br />
<img src="/assets/uploads/files/1518405180545-fipy-error-message.png" alt="0_1518405183882_Fipy Error Message.png" class="img-responsive img-markdown" /></p>
<p dir="auto"><em>Note: I had try to uninstall and reinstall the pycom firmware update software  with the url link provided by you (i.e. pycom_firware_update_1.1.6.b0.exe), but same error message appears.</em></p>
<p dir="auto">I have also just realize the following:-<br />
<img src="/assets/uploads/files/1518405796716-os_name-resized.png" alt="0_1518405799826_os_name.png" class="img-responsive img-markdown" /></p>
<p dir="auto">Please advice.</p>
<p dir="auto">Thanks.</p>
]]></description><link>https://forum.pycom.io/post/15690</link><guid isPermaLink="true">https://forum.pycom.io/post/15690</guid><dc:creator><![CDATA[philip_teoph]]></dc:creator><pubDate>Mon, 12 Feb 2018 03:33:48 GMT</pubDate></item><item><title><![CDATA[Reply to Fipy Firmware on Mon, 12 Feb 2018 10:03:51 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">In regards to the older firmware not mentioning sigfox, this is due to the firmware thats shipped with the device not supporting sigfox. This was added in a firmware update that was released shortly after the device was released.</p>
<p dir="auto">Could you please connect to the serial port of device thats giving you trouble (either via pymakr or putty), this should show you an interactive prompt you can type code into. If you then connect a wire between <code>Gnd</code> and <code>G23</code> of the expansion board and press the reset button on your fipy, it should reboot into download mode. You should see the following on the serial port, can you confirm?</p>
<pre><code class="language-raw">rst:0x1 (POWERON_RESET),boot:0x2 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_FEO_V2))
waiting for download
</code></pre>
]]></description><link>https://forum.pycom.io/post/15698</link><guid isPermaLink="true">https://forum.pycom.io/post/15698</guid><dc:creator><![CDATA[seb]]></dc:creator><pubDate>Mon, 12 Feb 2018 10:03:51 GMT</pubDate></item><item><title><![CDATA[Reply to Fipy Firmware on Tue, 13 Feb 2018 01:42:01 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/1881">@seb</a> !<img src="/assets/uploads/files/1518486084868-firmware-via-serial-port-resized.png" alt="0_1518486085160_firmware via serial port.png" class="img-responsive img-markdown" /></p>
<p dir="auto">Please note that there is difference in console message displayed:</p>
<p dir="auto">Yours : boot:<strong>0x2</strong> (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_<strong>FEO</strong><em>V2))<br />
Mine  : boot:<strong>0x3</strong> (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI</em>_<strong>REO</strong>_V2))</p>
<p dir="auto">I manage to reboot into download mode as advice.  Whats next please?</p>
<p dir="auto">Thanks.</p>
]]></description><link>https://forum.pycom.io/post/15720</link><guid isPermaLink="true">https://forum.pycom.io/post/15720</guid><dc:creator><![CDATA[philip_teoph]]></dc:creator><pubDate>Tue, 13 Feb 2018 01:42:01 GMT</pubDate></item><item><title><![CDATA[Reply to Fipy Firmware on Tue, 13 Feb 2018 10:08:56 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/2302">@philip_teoph</a> said in <a href="/post/15720">Fipy Firmware</a>:</p>
<blockquote>
<p dir="auto">Yours : boot:0x2 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_FEOV2))<br />
Mine  : boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))</p>
</blockquote>
<p dir="auto">Hi,</p>
<p dir="auto">The difference in the messages does not matter, most devices I have checked display the message the same way yours does (I'm not sure what the differences actually signify). The fact you see the <code>waiting for download</code> message means your FiPy is successfully entering the firmware download mode. Once you see this message can you then close all open connections to the device and try the firmware update tool again. It is important that no other application has the serial port open.</p>
]]></description><link>https://forum.pycom.io/post/15728</link><guid isPermaLink="true">https://forum.pycom.io/post/15728</guid><dc:creator><![CDATA[seb]]></dc:creator><pubDate>Tue, 13 Feb 2018 10:08:56 GMT</pubDate></item><item><title><![CDATA[Reply to Fipy Firmware on Tue, 13 Feb 2018 11:22:10 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="https://forum.pycom.io/uid/1881">@seb</a> It solved!  Thank a lot.</p>
<p dir="auto">Steps : close PuTTY (put to download mode) and start firmware update tool.</p>
<p dir="auto"><img src="/assets/uploads/files/1518520822696-fipy-no-error-message-resized.png" alt="0_1518520822108_Fipy No Error Message.png" class="img-responsive img-markdown" /></p>
]]></description><link>https://forum.pycom.io/post/15733</link><guid isPermaLink="true">https://forum.pycom.io/post/15733</guid><dc:creator><![CDATA[philip_teoph]]></dc:creator><pubDate>Tue, 13 Feb 2018 11:22:10 GMT</pubDate></item></channel></rss>