On Sun, Jul 20, 2008 at 8:24 PM, Dominic Rath <[EMAIL PROTECTED]> wrote: > On Sunday 20 July 2008 20:15:38 you wrote: >> On Sun, Jul 20, 2008 at 7:51 PM, Dominic Rath <[EMAIL PROTECTED]> wrote: >> > Hi list, >> > >> > while working with the OpenOCD's telnet interface for a bit I got several >> > of these messages: >> > >> > keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet >> > not sent! (1258) >> > >> > I had the jtag_speed set to a very high value (1400), because the target >> > is an ARM926EJ-S core running at the 32kHz slow clock. >> > >> > Would it be possible to limit that warning to GDB connections? >> >> The problem is that we need to catch & fix these problems. > > I fully agree with you here - take it as a bug report: even the most simple > JTAG operation (halt in my case) could possibly take several seconds if the > target is running from a very slow clock. > >> Even if it works for you in a telnet session, it will break when >> doing the same from GDB. >> >> Perhaps it should be prefixed with "BUG:" ? > > I think so. To me, the warning suggested there was something wrong with my > setup. BUG makes it clear that this is something in the OpenOCD that needs to > be fixed. In that case it's of course fine to keep the message enabled on the > telnet interface, too.
Committed. I've found that these sort of timeout problems *really* confuse users. They think there is something wrong with the connection to the GDB server and are looking in all the wrong places for a solution. > > Regards, > > Dominic > -- Ø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
