The way it has been designed means that no memory locations are touched until symbol locations are provided by GDB. The symbols names which are available tell the system which RTOS is in use.
On most platforms OpenOCD would have initialised the memory system by the time GDB attaches. However, you are correct, on some platforms the memory controller may have to be enabled in the software. Hence, I would suggest only enabling the feature for Cortex-M3 devices or just STM32 devices to start with, since it has only been implemented/tested for these so far... Evan -----Original Message----- From: Øyvind Harboe [mailto:[email protected]] Sent: Tuesday, 23 August 2011 5:35 PM To: Evan Hunter Cc: [email protected] Subject: Re: [Openocd-development] Automatic RTOS Detection 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 [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
