So... finally on to working on performance. Does anyone have any good ideas on how to profile OpenOCD?
For PC hosted OpenOCD the most crucial thing is to reduce the # of roundtrips. Her are my first ideas. - Count number of times the queue is flushed using a global variable. This variable can be "watched" in the debugger and then look at it change as one steps through the code. This should reveal any surprises. Since this is easy to do, I'll do this first. - Use some sort of profiling tool that will give the stack trace of those places where OpenOCD is waiting for the driver to flush a queue. -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
