] Automatic RTOS Detection
Why change the target scripts?
Perhaps a config option like:
openocd -c rtos auto
--
Ø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
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
Message-
From: Øyvind Harboe [mailto:oyvind.har...@zylin.com]
Sent: Tuesday, 23 August 2011 5:35 PM
To: Evan Hunter
Cc: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development] Automatic RTOS Detection
If OpenOCD goes sniffing around at memory locations that can mess
up e.g. debugging
On Tue, Aug 23, 2011 at 9:47 AM, Evan Hunter ehun...@broadcom.com wrote:
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
-
From: Øyvind Harboe [mailto:oyvind.har...@zylin.com]
Sent: Tuesday, 23 August 2011 5:35 PM
To: Evan Hunter
Cc: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development] Automatic RTOS Detection
If OpenOCD goes sniffing around at memory locations that can mess
up e.g. debugging
Then perhaps we only need to clearly state in the manual the the GDB command
to turn off threads?
--
Ø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/
___
On 08/23/2011 09:47 AM, Evan Hunter wrote:
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
What if I have a system with an RTOS and want to debug the startup code
using GDB? In that case, memory is *not* yet initialized, yet the symbol
table would enable RTOS support.
Disable threads using gdb command to do so before connecting?
--
Øyvind Harboe - Can Zylin Consulting help on
On 08/23/2011 12:24 PM, Øyvind Harboe wrote:
What if I have a system with an RTOS and want to debug the startup code
using GDB? In that case, memory is *not* yet initialized, yet the symbol
table would enable RTOS support.
Disable threads using gdb command to do so before connecting?
If there is such a command, that is OK with me.
I got the impression it had yet to be implemented.
That's what I though too :-) I don't know what that gdb command
is though...
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87
...@discworld.dascon.de]
Sent: 23 August 2011 19:59
To: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development] Automatic RTOS Detection
On 08/23/2011 09:47 AM, Evan Hunter wrote:
The way it has been designed means that no memory locations are touched
until symbol locations are provided by GDB
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
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.
That's necessary but not sufficient.
There needs to be a way that the user can easily discover
...@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
Le 23/08/2011 03:47, Evan Hunter a écrit :
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
The code will not affect those who are not using a supported operating
system. I have used the automatic thread awareness code with no
problems in the following cases:
* No RTOS - STM32
* FreeRTOS - STM32
* ThreadX - STM32
I agree the memory state issue is still a potential problem which
Hi All,
I would like propose that the TCL scripts for Cortex-M3 systems be updated to
turn on automatic RTOS detection.
What does everyone think? The effects should be benign if no known RTOS is
detected...
It would simply involve adding -rtos auto to the end of the target configure
Why change the target scripts?
Perhaps a config option like:
openocd -c rtos auto
--
Ø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/
___
18 matches
Mail list logo
