On 2011-06-10 22:29, Tomek CEDRO wrote:
Michael, in this situation you probably simply don't want to shut down the OpenOCD and leave things as-is with your session active controlling the target. What is the point of leaving target in some specific state when OpenOCD is not running? It sounds crazy! When program quits target should behave as nothing was connected, this is so obvious that I don't really understand the point of this discussion.
Full support here - for me after shutting down OpenOCD I'd like it to restore interface to "initial" state (in most cases - "transparent"). Sometimes - when the interface is placed inside some device it's difficult to physically disconnect it from the board - shutting down OpenOCD is much easier. I also don't understand why would you want interface and target to "freeze" in some specific state at OpenOCD exit - why don't just leave OpenOCD running then? We - who want it to "soft-disconnect" - have no alternative, as it's impossible to force "initial" state of interface with OpenOCD commands.
4\/3!! _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
