I too get a hang up after issuing any command after ‘reset halt’.
Honestly? I have no idea what is going on with your system, I haven’t managed to solve my problem yet.
Here is what I would do.
Install a newer version of openOCD, maybe 0.3.1, 0.2.0. Freddie’s windows installation packages all seem fine to me. The only restriction I can see is using the open source ‘libusb-win32’ driver as opposed to FTDI’s original. This is a hassle but it works.
Strip your config file down to the bare minimum. Giving only commands for setting up your interface (make it run slow) and your target. But not issuing any actual commands. As the ‘target’ config file usually provides a ‘reset-init’ routine which can be run when issuing a reset, I would make a copy of that config file but remove the routine. That way when you issue a reset, it literally just resets the device, without doing anything else automatically. If you need an example I can try and knock up a basic test config file, which will do nothing but test the communication between openOCD and your chip - negating hardware issues.
Then using telnet, try halt and resume. Perhaps even ‘reset’. Keep a close eye on both the telnet window and the openOCD window for errors…sometimes telnet doesn’t say anything but openOCD goes ape, or visa versa.
I think the reason ‘every call of a script causes silent hangup’ is because those scripts themselves are issuing commands which either your chip isn’t ready for, or cannot accept. Example: my setup works until I issue a ‘reset’ command which runs the routine in the target config. This routine contains many ‘mww’ instructions to write to config registers on the chip. This results in the chip essentially dying on its arse, meaning and subsequent commands (halt, resume, reset, poll) causes the windows to freeze. Leaving me unhappy.
I will post back if I find a solution. But as there can be many causes (hardware, chip config, config files, openocd version differences) its gonna be a sod to find.
Good luck, and I know this post is quite old, but this was jsut incase you’re still having problems.