On Wed, Mar 14, 2012 at 2:21 PM, simonqian.openocd <simonqian.open...@gmail.com> wrote: > (...) > I didn't change the name of jtag_reset_config, jtag_set_error, > jtag_execute_queue, and even jtag_add_sleep. > Despite the jtag_ prefix, I can make things working. > Should I add a set of same functions with swd_ prefix?
I would rather rename all functions like this into "target_reset" or better "board_reset", please see my last mail to know the details :-) The reset signal is a part of an interface device and board itself. There is no sRST signal in JTAG and SWD, but they also can reset target using proper DAP communication. This is why I would rather put it together with the interface and/or dedicated board layer containing "hard reset" for upper layers, even target/dap. Reset in SWD or JTAG or other Transport/Target would mean that this is a "soft reset"... Please take a look at src/interface in my fork - there is a framework already created do define signals at runtime (or from configuration files) and operate on them at will with "bitbang" command. I had to create this in order for sRST to work, but also and more important drive the buffer logic part of the interface (mainly the RnW signal). Additional outcome from this is that we can now write TCL scripts that implement any desired function with no hardcoding (i.e. SPI programmer as TCL module) :-) Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
