---------- Forwarded message ---------- From: Akos Vandra <[email protected]> Date: 26 September 2011 23:36 Subject: Re: [Openocd-development] ft2232_transfer why bit-by-bit? To: Laurent Gauch <[email protected]>
Hi! Sorry, it seems like I wanted to do too much too fast. Turns out I don't have an SWD compatible programmer yet. I am going to make a programmer compatible with kt_link_swd. I found its pinout over the internet, and I am currently making up the schematic. Does anyone by chance have designs for such a programmer, that I could build myself? I find 50E too much for the kt_link. If not, I might release the gerber files to the public. Regards, Ákos On 26 September 2011 15:08, Laurent Gauch <[email protected]> wrote: >> Hi! >> >> Is there a good reason why ft2232_transfer uses bit-by-bit mpsse transfer? >> If not, I would be happy to rewrite it to use bytewise transfer, if >> the number of bits to be transferred is divisable by 8. >> Might make things a *little* bit faster... >> >> Regards, >> Ákos > > This will be great, Akos. > > Also, the high level JTAG API will allow you to implement byte wise - bit > wise instead bit wise only without changing the API interface. > > Have fun. > > Regards, > Laurent > http://www.amontec.com Amontec JTAGkey-2P High-Speed USB JTAG SPI Emulator > Cable with Power supply 3.3V @ 500mA on pin 19. > > > > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
