If OpenOCD goes sniffing around at memory locations that can mess up e.g. debugging before memory controllers are set up and such.
I could be convinced to have it enabled by default, if we had an option to turn it off. From a marketing point of view, having it enabled by default if it almost always works is great! I don't know how this feature works though... What does the user have to do? How does OpenOCD know whether the user is running FreeRTOS, ThreadX or eCos? -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/ _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
