I think that this is highlighting a more general problem in OpenOCD: If GDB requests memory access, OpenOCD cannot tell if that memory access is allowable.
I have run into this on Cortex-M3 devices, where the call stack always ends with a value 0xfffffffX which causes GDB to request memory read at this location, which does not exist. It is handled gracefully due to the ARM debug memory access port, but should really not happen in the first place... Evan -----Original Message----- Message: 6 Date: Tue, 23 Aug 2011 14:33:55 +0200 From: Michael Schwingen <rincew...@discworld.dascon.de> To: openocd-development@lists.berlios.de Subject: Re: [Openocd-development] Automatic RTOS Detection Message-ID: <4e539e33.3080...@discworld.dascon.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 08/23/2011 02:10 PM, Evan Hunter wrote: > The way I do this on the STM32 is to use TCL script JTAG to zero the memory > before allowing GDB to attach. > > This is necessary since a previous run of the system can leave valid > contents in the RTOS variables, which are indistinguishable from real RTOS > data. > > With the memory zeroed, the system behaves as expected with a single thread > of execution showing in the boot-up code, then multiple threads once the > system has started. > However, if there *is* no memory at those locations after reset, this scheme will not work when debugging the memory initialization code, so there needs to be some way to disable the RTOS support. cu Michael _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
