> Can you do a 'shutdown' command over telnet ?
Yes, I can. However, after doing so, I am in the 'hung' state
again, just as if I had terminated openocd by typing ^C.
The shutdown command works even in this state, see below:

tkoel...@gerd0022 ~
$ openocd
Open On-Chip Debugger 0.4.0 (2010-04-13-19:21)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
RCLK - adaptive
fast memory access is enabled
dcc downloads are enabled
trst_only separate trst_push_pull
CS0 NAND
Info : device: 6 "2232H"
Info : deviceID: 67358712
Info : SerialNumber: 53SZGA1LA
Info : Description: Amontec JTAGkey-2 A
Info : max TCK change to: 30000 kHz
Info : RCLK (adaptive clock speed)
Info : JTAG tap: dm365.jrc tap/device found: 0x8b83e02f (mfg: 0x017, part: 
0xb83e, ver: 0x8)
Info : JTAG tap: dm365.etb enabled
Info : JTAG tap: dm365.arm enabled
Info : Embedded ICE version 6
Info : dm365.arm: hardware has 2 breakpoint/watchpoint units
Info : ETM v1.3
Info : accepting 'telnet' connection from 0
shutdown command invoked

tkoel...@gerd0022 ~
$ openocd
Open On-Chip Debugger 0.4.0 (2010-04-13-19:21)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.berlios.de/doc/doxygen/bugs.html
RCLK - adaptive
fast memory access is enabled
dcc downloads are enabled
trst_only separate trst_push_pull
CS0 NAND
Info : device: 6 "2232H"
Info : deviceID: 67358712
Info : SerialNumber: 53SZGA1LA
Info : Description: Amontec JTAGkey-2 A
Info : max TCK change to: 30000 kHz
Info : RCLK (adaptive clock speed)
Error: couldn't read enough bytes from FT2232 device (0 < 81)
Error: couldn't read from FT2232
Error: couldn't read enough bytes from FT2232 device (0 < 81)
Error: couldn't read from FT2232
Command handler execution failed
Warn : jtag initialization failed; try 'jtag init' again.
Info : accepting 'telnet' connection from 0
shutdown command invoked

tkoel...@gerd0022 ~
$

thanks,
Thomas
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to