On Mon, Jan 28, 2013 at 3:53 PM, Laurent Gauch <[email protected]> wrote: > Let the 'HOST PROCESS' calculate bitstream2 while the 'JTAGKEY PROCESS' > resolve and reply bitstream1. > :-)
Uhm, we we are able to get this kind of performance where even some computations introduce delays, that would be nice :-) :-) :-) > Yes, but you come with a RnW signal at TCL level which one is specific > to one layout and one implementation. Or I am wrong. > For me this kind of signal should not have any acces from TCL level, > since it is not a wired signal, but a signal to help emulating the SWD > (and again with the use of a specific layout and implementation). :-) Not exactly. This is a hardwired signal. Signals mask to be precise. Just as any other signal - LED, OE, etc. This can be any port pin of the FT2232 chip. Except there can be hardcoded bitbang_deny in the sources for that layout that we have discussed before to deny usage of some pins from TCL that could damage the interface. This is very useful to bring out that signals out of the hardcode and bring them to the TCL, because this allows to implement operations at TCL level - i.e. quick I2C implementation or some proprietary protocol or additional interface features like voltage redadout or simply target reset. This is why I have invented and introduced interface_signal and interface_bitbang. This is very useful and something new to the OpenOCD. It should be even possible to initialize specific layout from the TCL with the current code. Another thing is that I would prefer Python over TCL :-) :-) "RnW" is a simple name for a signal required by SWD bus, nothing else. Different interfaces will have different values for this mask. This is a bitmask that switch buffers into receive/transmit mode. "nRnW" should be also implemented to complement use of "RnW" as some buffers need that. This got lost somewhere during the experiments, but is trivial to code. This way you can have one interface in the source code and everything else in the TCL configuration file. To add new device is to simply create new TCL file, not rebuild the software. This way configuration can be split into multiple files, that setup different layers, which is at the moment impossible because things are hardcoded and use of configuration file is limited (i.e. you need to have another configuration file for another option of the same interface). Best regards :-) Tomek -- 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
