On Mon, Jan 28, 2013 at 4:52 PM, Laurent Gauch <[email protected]> wrote: > But the new AMONTEC JTAGKEY-3 ft2232 dongle will not need to have RnW > signal for remoting the SWD. We just need to set one time, at JTAGkey > init, a signal called JTAGnSWD ! So how the end-user will know about > what to do with RnW coming with your swd implementation !
You name it "JTAGnSWD" and hardcode into the driver srouce code. I name it "RnW" and make is accessible via TCL, it also needs to be set one time, this is very similar behavior :-) However you think of your one interface, while I think of various different interfaces as well :-) My solution allow creating scrtipts at TCL level, while your needs to have things hardcoded. This is the main difference I guess.. If is also possible to create interface for your interface's signals to drive them from TCL. But this is exactly what I did, wiht the difference that you can (re)define signals at TCL level with my solution :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ------------------------------------------------------------------------------ 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
