> Current ft2232 driver use Layouts. Layout initialization routines are > hardcoded into sources and configuration files. Initialization of > interface in JTAG mode and SWD mode is different, which requires > separate initialization routine in the sources and layout name change > - configuration change is unavoidable in this case. This is why I have > created separate interface ft2232_swd to leave existing solution > untouched and be able to work with new interfaces... Does your ft2232 swd not depending on how the SWD buffers are controlled ... so depending on the layout used ... (the K T LINK is certainly not the best efficient layout to use for SWD, since you have to control the SWDIO OE N by an GPIO access ! ). We have a better solution in our labs, but for now we have to decide if the JTAGkey-3 (with SWD CJTAG down-to 0.7V VREF !) will keep the same VID as the JTAGkey-1 and JTAGkey-2. Then we will come with JTAGkey-3 in production. If we keep the same VID we have the possibility to detect the SWD capability by a specific gpio acces on the ft2232 GPIOH. But does you code could be able to do some specific GPIO sequences (before asserting the JTAG_OE_N ) to detect if the layout JTAGkey-X has the SWD capability ?
Regards, Laurent http://www.amontec.com ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
