(Michael and I discussed something offline).

GDB timeout fix commited.

OpenOCD needs to keep the GDB connection alive.

The solution is *NOT* "set remotetimeout XXX". Users can't
be expected to figure out this from the cryptic error message.

The solution is to invoke the function below more often than
every 2 seconds(see target/target.c for example).

LOG_USER_N("%s", "")


Index: C:/workspace/openocd/src/helper/command.c
===================================================================
--- C:/workspace/openocd/src/helper/command.c   (revision 708)
+++ C:/workspace/openocd/src/helper/command.c   (working copy)
@@ -411,6 +411,8 @@
        char *words[128] = {0};
        int retval;
        int i;
+
+       LOG_USER_N("%s", ""); /* Keep GDB connection alive*/
        
        if ((!context) || (!line))
                return ERROR_INVALID_ARGUMENTS;


-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to