a
push fails using HTTP -
(http://code.google.com/p/gerrit/issues/detail?id=1051)
Regards,
Evan
On Thu, 24 Nov 2011 23:35:53 -0600, Austin, Alex wrote:
git commit --amend --sign-off
Or something like that. It's complaining that there's no Signed Off
By line in the commit message.
Mick Davis
to be no
longer valid, giving the following error:
Making maintainer-clean in jimtcl
make[1]: *** No rule to make target `maintainer-clean'. Stop.
Regards,
Evan Hunter
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https
Hi Andreas,
You are right - Looking at it again, the qP code looks like I got halfway
through implementing it, then found that I should be using qThreadExtraInfo
instead.
Please feel free to remove it. The only reason I haven't already is that I've
not had time.
Regards,
Evan
From: andr
.
I just have a OpenOCD script which is used when connecting GDB, and put the
memory clear operation in that, but you may be able to put it in the reset
handler.
Evan
-Original Message-
From: Jonathan Dumaresq [mailto:jdumar...@cimeq.qc.ca]
Sent: 14 October 2011 23:42
To: e...@ozhiker.com
does not detect threads left
in memory from previous run
mww 0x2000 0x 0x4000
Regards,
Evan Hunter
On Thu, 13 Oct 2011 09:34:52 -0400, Jonathan Dumaresq wrote:
Hi,
I have seem on the ml that FreeRTOS is now supported in openocd. I
wonder if
there is some documentation
Hi all,
My last patch for FreeRTOS was not quite correct - it had an off-by-one error.
Attached patch fixes it.
Regards,
Evan Hunter
0001-Fix-off-by-one-bug-in-FreeRTOS.PATCH
Description: 0001-Fix-off-by-one-bug-in-FreeRTOS.PATCH
___
Openocd
,
Evan Hunter
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
I used int64_t for threadid because in the implementations I wrote for
FreeRTOS and ThreadX, the threadid is actually the address of the
thread control block. Hence if it is running on a 64 bit processor
(currently unlikely) it would need a 64 bit address.
Regards,
Evan
Quoting Jie
compatibility too.
Regards,
Evan
Quoting Jie Zhang jzhang...@gmail.com:
Hi Evan,
GDB manual says about qP:
Don't use this packet; use the `qThreadExtraInfo' query instead
(see below).
Since qThreadExtraInfo is already supported in rtos.c, why qP is
still needed?
Regards,
Jie
of any cases where it would be a bad thing to be able to see
thread states...
Evan
-Original Message-
From: Øyvind Harboe [mailto:oyvind.har...@zylin.com]
Sent: Tuesday, 23 August 2011 3:05 PM
To: Evan Hunter
Cc: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development
, 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
visibility of
threads, stacks and locals for each thread, in the same way that native
debugging does. If you use eclipse, or similar GUI front end, then the commands
for retrieving threads and stacks are all automated, requiring only the -rtos
auto config command.
Evan
-Original Message
behaves as expected with a single thread
of execution showing in the boot-up code, then multiple threads once the
system has started.
Perhaps there's a better way of doing this, but I haven't yet thought of
one.
Evan
-Original Message-
From: Michael Schwingen [mailto:rincew
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
would need resolving
Evan
Quoting Michel Catudal michelcatu...@gmail.com:
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
command in each case.
Regards,
Evan Hunter
Broadcom
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Hi All,
Attached are two patches that fix bugs that I've found in FreeRTOS thread
awareness.
Regards,
Evan Hunter
Broadcom
0001-Fix-FreeRTOS-thread-list-parsing.patch
Description: 0001-Fix-FreeRTOS-thread-list-parsing.patch
0002-Add-suspended-task-list-to-FreeRTOS-support.patch
CHANNEL_A is
tried. There may be a better way of doing this - my patch may not catch errors
as well as the previous code.
Regards,
Evan Hunter
0001-Add-verify_image_checksum-command.patch
Description: 0001-Add-verify_image_checksum-command.patch
0003-try-other-ft2232-channels.patch
the GDB bug described in
http://sourceware.org/bugzilla/show_bug.cgi?id=12648
* Generally you will want to make your OpenOCD script blank the device
memory so that the RTOS awareness does not read old, invalid thread information
Regards,
Evan Hunter
Date: Tue, 24 May 2011
should control the startup out of
reset, and ensure that the bit in the DBGMCU_CR register gets set before the
program starts running.
Any thoughts on how this can be achieved?
Regards,
Evan Hunter
___
Openocd-development mailing list
Openocd
Thanks Michel,
I hadn’t had time to investigate it.
Evan
-Original Message-
From: Michel JAOUEN [mailto:michel.jao...@stericsson.com]
Sent: Tuesday, 19 April 2011 5:59 PM
To: Evan Hunter; Øyvind Harboe
Cc: openocd-development@lists.berlios.de
Subject: RE: [Openocd-development] RTOS
Hi Øyvind,
The scanf format %llx does not work in MinGW. Perhaps some system specific
macros are needed such as in the attached
Evan
-Original Message-
From: Øyvind Harboe [mailto:oyvind.har...@zylin.com]
Sent: Monday, 11 April 2011 11:03 PM
To: Evan Hunter
Cc: openocd-development
I'm not sure what you mean - when there is no -rtos parameter, the only
modified code in target.c that will be run is the initialization of the rtos
variables:
target-rtos = NULL;
target-rtos_auto_detect = false;
Evan
-Original Message-
From: Øyvind Harboe
Ah - those are in gdb_server.c
Yes, you could have checks of target-rtos in the gdb_server file wherever an
rtos function is called, however I think you'll find that already happens
within the rtos functions themselves. I have no preference as to where the
check occurs.
Evan
-Original
thread.
Regards,
Evan Hunter
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
25 matches
Mail list logo
