libftdi Archives

Subject: Re: windows 7 Python modules

From: Joachim Schambach <jschamba@xxxxxxxxxxxxxxxxxx>
To: <libftdi@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 25 Oct 2014 11:45:27 -0500
I have invented my own protocol to communicate with an FPGA based board
we designed that uses an FTDI chip to provide USB  access. This protocol
includes functions like readRegister, writeRegister, readMemory,
writeMemory, etc.
I have a C++ library that provides these functions to the command line,
or to a (C++) application program.
At some point, we decided it would be nice to have scripting capability
for these functions and decided on Python to provide this. It was easy
to convert the library into a Python "extension" module under Linux and
compile it.
Now one of our users wants to do the scripting in Windows, so I am
trying to simply compile the same module under Windows.
>From the libftdi web the claim is that it works under Windows, so I
thought it would be easy to port this module, which I am now finding is
a little more work than I thought. I didn't want to have to re-write the
whole protocol in Python again (having to try to figure out how to do
that), but rather just provide the final "user" function in Python, thus
the idea to compile the protocol as a module...
cheers,
Jo

On 10/24/2014 7:17 PM, Xiaofan Chen wrote:
> On Sat, Oct 25, 2014 at 8:11 AM, Xiaofan Chen <xiaofanc@xxxxxxxxx> wrote:
>> BTW, why do you need to build your own Python bindings?
>>
> I ask because there are already a few Python bindings for FTDI, other
> than libftdi's Python binding, there are also a few others.
>
> Eg:
> https://pypi.python.org/pypi/pyftdi/0.9.6
> https://pypi.python.org/pypi/pylibftdi/0.14.2
>

-- 
Dr Joachim Schambach
The University of Texas at Austin
Department of Physics
1 University Station #C1600
Austin, Texas 78712-0264, USA
(512) 471-1303, FAX: (781) 998-5513
email: jschamba@xxxxxxxxxxxxxxxxxx


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread