On 04/06/2010 10:35, Xiaochen Zhou wrote:
It seems some issues in openocd-0.4.0 with MIPS 4KEc core, I did some
experiments below:
For info the MIPS has been mainly tested on a m4k (aka PIC32).
This also means that testing has been on a little endian system, so
bugs
could be present.
Issue
If the DCC working area is about to be overwritten, report
explicit error.
Perhaps this will put the user on the right track of
his problems?
Signed-off-by: Øyvind Harboe oyvind.har...@zylin.com
---
src/target/arm7_9_common.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
GDB and OpenOCD has two different error number
spaces and no mapping exists between them.
If a specific error number is to be reported
to GDB then this has to be done at the calling
site, rather than as a generic routine that
tries to map retval to GDB error number speak.
Signed-off-by: Øyvind
If the DCC working area is about to be overwritten, report
explicit error.
Perhaps this will put the user on the right track of
his problems?
Signed-off-by: Øyvind Harboe oyvind.har...@zylin.com
---
src/target/arm7_9_common.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
Hi Frederic,
just a warning about daily build. Don't spend too much time
on it yet...
I've identified another DCC regression since 1.66 (there
has been some performance optimisations that need
to be backed out, I think).
Looking into it now...
--
Øyvind Harboe
US toll free 1-866-980-3434 /
I figured out, that the SIGINT signal was caused by an string function.
There is a memset in the tskTCB *prvAllocateTCBAndStack(...) function in task.c
and if I comment it the problem is solved..
till the next SIGINT is caused by strncpy in void
prvInitialiseTCBVariables(...) also in task.c
On Mon, Jun 7, 2010 at 5:21 PM, Kenan Özdemir gla...@hotmail.de wrote:
I figured out, that the SIGINT signal was caused by an string function.
There is a memset in the tskTCB *prvAllocateTCBAndStack(...) function in
task.c and if I comment it the problem is solved..
till the next SIGINT is
