>> This patch tries to optimize TMS clocks by compacting multiple clocks >> into one FT2232 command. This gives us 6% flash program time reduction. >> And it gives us more performance improvement for gdbproxy when loading >> program via our gnICE and gnICE+ cables. I think this will help other >> JTAG cables based on FT2232(H).
Haven't had a chance to look at the code yet. What is the mechanism behind compacting clocks? With the current code, URJ_TAP_CABLE_CLOCK would stuff (compact?) n requested clocks into a sequence of FT2232 commands, each one clocking 7 times. In which spot did you find further optimization potential? >> But there is one problem I don't know the resolution. What is >> post_signals in ft2232.c for? How should I set it for >> URJ_TAP_CABLE_CLOCK_COMPACT? >> > post_signals was added in this change: > > Revision 1419 - (view) (download) (annotate) - [select for diffs] > Modified Mon Jan 19 12:06:06 2009 UTC (12 months, 2 weeks ago) by kawk > > [2187351] Direct JTAG signal access, get/set_trst extension integrated > from getset_pod branch My understanding is that post_signals acts as a "notepad" to track the status of the pod signals for the queued actions. This allows to predict the status of pod signals without having the need to read them from the FT2232. Arnim ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
