<?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[Topics tagged with ftdi]]></title><description><![CDATA[A list of topics that have been tagged with ftdi]]></description><link>https://forum.pycom.io/tags/ftdi</link><generator>RSS for Node</generator><lastBuildDate>Tue, 10 Mar 2026 16:14:33 GMT</lastBuildDate><atom:link href="https://forum.pycom.io/tags/ftdi.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 21 Jan 2019 06:43:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Minimal Hardware to program Lopy4 with USB]]></title><description><![CDATA[@protonx I made myself a base board too for the Pycom modules. A Kicad sketch is here: https://github.com/robert-hh/Pycom-baseboard
It uses pre-built modules for USB/Serial and SD card. I did not want to deal with SMD parts, and space did not matter. It also has the espressif logic for activating the bootloader, and jumpers for the connection to Reset, Tx, Rx and P2.
Not that this costs less than an Pycom expansion board, but it makes fewer troubles when using (no PIC, standard drivers, ..)
]]></description><link>https://forum.pycom.io/topic/4248/minimal-hardware-to-program-lopy4-with-usb</link><guid isPermaLink="true">https://forum.pycom.io/topic/4248/minimal-hardware-to-program-lopy4-with-usb</guid><dc:creator><![CDATA[robert-hh]]></dc:creator><pubDate>Mon, 21 Jan 2019 06:43:26 GMT</pubDate></item><item><title><![CDATA[TX&#x2F;RX only console upgrade (Pymark) does not work with V1.9 firmware?]]></title><description><![CDATA[This issue is discussed on GitHub here
]]></description><link>https://forum.pycom.io/topic/3665/tx-rx-only-console-upgrade-pymark-does-not-work-with-v1-9-firmware</link><guid isPermaLink="true">https://forum.pycom.io/topic/3665/tx-rx-only-console-upgrade-pymark-does-not-work-with-v1-9-firmware</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Thu, 30 Aug 2018 10:27:23 GMT</pubDate></item><item><title><![CDATA[Exp Board 2.0 serial communication problem]]></title><description><![CDATA[@szyba91 What do you mean with: does not work? The copying or the script?
For copying Filezilla also support a upload option with the right cick on the file. SImple Double-Click also copies. Did you set the number of transfers to 1 in the settings? The ftp server in the xxPy devices is pretty limited.
I had never problems using ftp for file transfer, but I'm using FireFTP, which is a Firefox plugin. That is convenient because I have firefox open anyhow almost all the time.
]]></description><link>https://forum.pycom.io/topic/3603/exp-board-2-0-serial-communication-problem</link><guid isPermaLink="true">https://forum.pycom.io/topic/3603/exp-board-2-0-serial-communication-problem</guid><dc:creator><![CDATA[robert-hh]]></dc:creator><pubDate>Fri, 17 Aug 2018 05:45:42 GMT</pubDate></item><item><title><![CDATA[FTDI drivers with FiPy+PyTrack in Win 7]]></title><description><![CDATA[@sandipg
The voltage and capacity are OK but it's the wrong connector, you want a JST PH-2 (also check the polarity as there is no standard)
For Germany perhaps check out these two from HobbyKing: (the higher capacity 2000mAh is cheaper as it's on sale, but see dimensions etc)
https://hobbyking.com/de_de/turnigy-2000mah-1s-1c-lipoly-w-2-pin-jst-ph-connector.html
https://hobbyking.com/de_de/turnigy-1200mah-1s-1c-lipoly-w-2-pin-jst-ph-connector.html
]]></description><link>https://forum.pycom.io/topic/2345/ftdi-drivers-with-fipy-pytrack-in-win-7</link><guid isPermaLink="true">https://forum.pycom.io/topic/2345/ftdi-drivers-with-fipy-pytrack-in-win-7</guid><dc:creator><![CDATA[jmarcelino]]></dc:creator><pubDate>Fri, 29 Dec 2017 22:53:29 GMT</pubDate></item><item><title><![CDATA[OSX Pymakr Atom plugin, not seeing lopy]]></title><description><![CDATA[@soren Sorry for the late reply. Atom currently always copies the top option in the list. If there is an actual Pycom serial detected, it will place that one at the top. Anyway, this is just a result of your issue, not the cause.
So just to be sure, after rebooting your mac, you are able to connect to your device? Then when switching out to a different lopy, the comport disappears from the list of serials, even when closing the connection during the swap? Do you switch expansionboards, or just the lopy? You could even hot-swap your lopy while keeping the expansion board connected, see if that helps.
]]></description><link>https://forum.pycom.io/topic/2209/osx-pymakr-atom-plugin-not-seeing-lopy</link><guid isPermaLink="true">https://forum.pycom.io/topic/2209/osx-pymakr-atom-plugin-not-seeing-lopy</guid><dc:creator><![CDATA[Ralph]]></dc:creator><pubDate>Wed, 24 Jan 2018 13:11:11 GMT</pubDate></item><item><title><![CDATA[No serial-over-USB connection to expansion board]]></title><description><![CDATA[got similar error, my expansion board doesnt show as recognized
]]></description><link>https://forum.pycom.io/topic/682/no-serial-over-usb-connection-to-expansion-board</link><guid isPermaLink="true">https://forum.pycom.io/topic/682/no-serial-over-usb-connection-to-expansion-board</guid><dc:creator><![CDATA[shariq]]></dc:creator><pubDate>Thu, 06 Sep 2018 12:54:23 GMT</pubDate></item></channel></rss>