search

jflemer-ndp / libmpsse

Automatically exported from code.google.com/p/libmpsse
0 stars 0 forks source link

No ability to bulk set pins, or set pin direction. #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. There really aren't any steps here, it appears there isn't any way to set 
pin direction for bitbang mode or to set all pins at the same time.

Please provide any additional information below.

I was looking for a way to "bulk" set the pins of a particular interface in 
bitbang mode.  It appears that I can read and write them using PinHigh/PinLow 
individually.  This is certainly useful, but I wanted to be able to "set them 
all at once" for an application I am doing.  In this case, I have a sort of 
"JTAG finder" that can scan pins and "hunt" for JTAG.  In order for that to 
work though, I have to be able to change the pin direction as well as be able 
to set pins "all at once".  So I created a SetDirection and a WritePins 
function.

I don't know if you will find them generally useful or not, but I thought they 
could be.  Even without the WritePins functionality, I figured the SetDirection 
might be needed in BitBang mode.

It is a patch against the latest release, *NOT* the latest SVN.  Hope that 
doesn't create any issues.  At any rate, it does seem to work and my JTAG 
finder appears to do the job.

libmpsse really is one of the neatest libraries out there.  I guess that is 
because it is connected with some of the coolest/cheapest hardware I've seen in 
a while.  It can REALLY get your PC/laptop connected to a lot of hobby stuff.

Original issue reported on code.google.com by robokni...@gmail.com on 28 Dec 2012 at 6:12

Attachments:

GoogleCodeExporter commented 9 years ago 
I forgot to set the priority on this to "low".  So unless you think it is a 
"medium" issue, it really was more of a feature request anyway.

Original comment by robokni...@gmail.com on 28 Dec 2012 at 6:17

GoogleCodeExporter commented 9 years ago 
Always seem to forget things... I also changed the "#include <ftdi.h>" because 
it appears that the newest libftdi library puts things in "<libftdi/ftdi.h>" 
... I don't really think that is an issue, probably something to be fixed with 
configure or something like that, but I thought I would note it.

Original comment by robokni...@gmail.com on 28 Dec 2012 at 6:26

GoogleCodeExporter commented 9 years ago 
Patches applied, thanks!

I'm opening a separate issue for supporting the new location of ftdi.h.

Original comment by heffne...@gmail.com on 28 Jan 2013 at 6:37