<?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[Comments &amp; Feedback]]></title><description><![CDATA[Let us know how to improve the community experience.]]></description><link>https://forum.sgwireless.com/category/4</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 12:47:56 GMT</lastBuildDate><atom:link href="https://forum.sgwireless.com/category/4.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 02 Apr 2026 16:53:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Bringing Pycom LoPy&#x2F;LoPy4 back to life on upstream MicroPython — collaboration welcome!]]></title><description><![CDATA[<p dir="auto">Hi everyone,</p>
<p dir="auto">I’m Danilo, and I’ve been working on adding official board support for the Pycom LoPy and LoPy4 to the upstream MicroPython project (v1.27.0+, ESP-IDF v5.4/v5.5.1).</p>
<p dir="auto">As many of you know, Pycom’s MicroPython fork was archived in September 2024 (last commit February 2022), leaving LoPy/LoPy4 owners stuck on an ancient codebase based on MicroPython ~v1.20. I wanted to change that.</p>
<p dir="auto"><strong>What’s been done so far:</strong></p>
<ul>
<li>Board definitions for both PYCOM_LOPY (ESP32 + SX1272) and PYCOM_LOPY4 (ESP32 + 8MB flash + 4MB PSRAM + SX1276)</li>
<li>A unified SX1272/SX1276 LoRa driver in Python (the only one in the MicroPython ecosystem that supports both chips)</li>
<li>LoRaWAN 1.0.x MAC layer with OTAA and ABP activation (Class A)</li>
<li>OTA firmware update support (dual app partitions)</li>
<li>Named pin mapping (P0-P23 + LORA_* pins) matching Pycom documentation</li>
<li>Hardware validation test scripts</li>
<li>All four build configurations compile successfully (LoPy, LoPy4, LoPy OTA, LoPy4 OTA)</li>
<li>A MicroPython contributor (robert-hh) has already done a trial build and confirmed WiFi works on actual LoPy4 hardware!</li>
</ul>
<p dir="auto"><strong>Pull Requests currently open:</strong></p>
<ul>
<li>Main PR (board definitions + driver + LoRaWAN + OTA + tests): <a href="https://github.com/micropython/micropython/pull/19026" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/micropython/micropython/pull/19026</a></li>
<li>Board images: <a href="https://github.com/micropython/micropython-media/pull/116" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/micropython/micropython-media/pull/116</a></li>
<li>SX127x driver + LoRaWAN packages for micropython-lib: <a href="https://github.com/micropython/micropython-lib/pull/1102" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/micropython/micropython-lib/pull/1102</a></li>
</ul>
<p dir="auto"><strong>Why this matters:</strong></p>
<p dir="auto">With this port, LoPy/LoPy4 owners get access to 7 years of MicroPython improvements: f-strings, async/await, proper asyncio, TLS 1.3, BLE 5.0, WPA3, and thousands of bug fixes. All while keeping LoRa functionality.</p>
<p dir="auto"><strong>Collaboration welcome!</strong></p>
<p dir="auto">Since SG Wireless now maintains the Pycom legacy, I’d love to collaborate. If anyone from the SG Wireless team or the community would like to help with testing, reviewing, or extending this work (e.g., adding support for FiPy, GPy, or other Pycom boards), please feel free to jump in! The PRs are open and ready for review.</p>
<p dir="auto">If you have a LoPy or LoPy4 board gathering dust, now’s a great time to dust it off!</p>
<p dir="auto">Cheers,<br />
Danilo</p>
]]></description><link>https://forum.sgwireless.com/topic/72/bringing-pycom-lopy-lopy4-back-to-life-on-upstream-micropython-collaboration-welcome</link><guid isPermaLink="true">https://forum.sgwireless.com/topic/72/bringing-pycom-lopy-lopy4-back-to-life-on-upstream-micropython-collaboration-welcome</guid><dc:creator><![CDATA[ddtdanilo]]></dc:creator><pubDate>Thu, 02 Apr 2026 16:53:22 GMT</pubDate></item><item><title><![CDATA[I have a board with Pycom, can I still use it for testing?]]></title><description><![CDATA[<p dir="auto">Hello @Pauleera , yes the board can still be used, the documentation is available here: https://docs.pycom.io/</p>
<p dir="auto">The Pybytes platform however is no longer online, and old Pycom products are not supported on the SG Wireless Cloud platform.</p>
]]></description><link>https://forum.sgwireless.com/topic/69/i-have-a-board-with-pycom-can-i-still-use-it-for-testing</link><guid isPermaLink="true">https://forum.sgwireless.com/topic/69/i-have-a-board-with-pycom-can-i-still-use-it-for-testing</guid><dc:creator><![CDATA[cehlers]]></dc:creator><pubDate>Tue, 24 Jun 2025 16:12:17 GMT</pubDate></item><item><title><![CDATA[Wake up (from Deep sleep) example in documentation]]></title><description><![CDATA[<p dir="auto">Thanks a lot for the feedback, @jandls. This was taken straight from the old Pycom documentation and hasn’t been reviewed/updated yet.</p>
]]></description><link>https://forum.sgwireless.com/topic/65/wake-up-from-deep-sleep-example-in-documentation</link><guid isPermaLink="true">https://forum.sgwireless.com/topic/65/wake-up-from-deep-sleep-example-in-documentation</guid><dc:creator><![CDATA[cehlers]]></dc:creator><pubDate>Sun, 04 May 2025 10:56:05 GMT</pubDate></item><item><title><![CDATA[Wrong link in documentation]]></title><description><![CDATA[<p dir="auto">Thanks for raising this issue, @jandls . The team is looking into it and will apply necessary fixes where necessary.</p>
]]></description><link>https://forum.sgwireless.com/topic/32/wrong-link-in-documentation</link><guid isPermaLink="true">https://forum.sgwireless.com/topic/32/wrong-link-in-documentation</guid><dc:creator><![CDATA[cehlers]]></dc:creator><pubDate>Mon, 21 Apr 2025 20:48:08 GMT</pubDate></item><item><title><![CDATA[Errors in the example script given for LoRaWAN v1.1.x?]]></title><description><![CDATA[<p dir="auto">Thanks again for raising this @jandls , the team is looking into it asap.</p>
]]></description><link>https://forum.sgwireless.com/topic/34/errors-in-the-example-script-given-for-lorawan-v1-1-x</link><guid isPermaLink="true">https://forum.sgwireless.com/topic/34/errors-in-the-example-script-given-for-lorawan-v1-1-x</guid><dc:creator><![CDATA[cehlers]]></dc:creator><pubDate>Sun, 20 Apr 2025 07:53:52 GMT</pubDate></item><item><title><![CDATA[Documentation mentions Sigfox?]]></title><description><![CDATA[<p dir="auto">Sorry, the board does not support Sigfox at this time. We used the old Pycom documentation as a base and it seems there are instances where the team did not remove Sigfox properly. We will review and remove all mentions to Sigfox. We may support Sigfox again in the future but no decision has been made at this point.</p>
]]></description><link>https://forum.sgwireless.com/topic/33/documentation-mentions-sigfox</link><guid isPermaLink="true">https://forum.sgwireless.com/topic/33/documentation-mentions-sigfox</guid><dc:creator><![CDATA[cehlers]]></dc:creator><pubDate>Sun, 20 Apr 2025 07:36:13 GMT</pubDate></item><item><title><![CDATA[What about Pycom products ?]]></title><description><![CDATA[<p dir="auto">Hi</p>
<p dir="auto">I just received an email stating SG Wireless has taken over on assets of Pycom. So how are you going to handle support and warranty for all people that bought Pycom products and never got any firmwares properly working for them neither any support ?<br />
If you took over assets I guess you took also over legal responsabilities of Pycom that never made its job and failed so bad !</p>
<p dir="auto">Thanks</p>
<p dir="auto">Vincèn</p>
]]></description><link>https://forum.sgwireless.com/topic/26/what-about-pycom-products</link><guid isPermaLink="true">https://forum.sgwireless.com/topic/26/what-about-pycom-products</guid><dc:creator><![CDATA[vincen]]></dc:creator><pubDate>Mon, 25 Nov 2024 14:32:13 GMT</pubDate></item></channel></rss>