To All Ye Linaro Toolchain Folk, (and OpenOCD developers too)
After a week of reading specifications and code, I am ready to start
doing some serious hacking on OpenOCD. The following outlines my present
plans and expectations, with the caveat that time can change everything.
Last week, I
Sounds great!
The only question that comes to mind at this point is what unrelated
refactoring work you think should be in place before this
work starts?
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
On 09/27/2010 12:13 AM, Øyvind Harboe wrote:
Sounds great!
The only question that comes to mind at this point is what unrelated
refactoring work you think should be in place before this work
starts?
I am looking at the commonality of ARMv7a between A8 and A9
specifically. For example, I
On Mon, Sep 27, 2010 at 9:33 AM, Zach Welch zwe...@codesourcery.com wrote:
On 09/27/2010 12:13 AM, Øyvind Harboe wrote:
Sounds great!
The only question that comes to mind at this point is what unrelated
refactoring work you think should be in place before this work
starts?
I am looking at
Hi all,
are there some instructions how to quickly add new architecture to
OpenOCD sources ?
I plan adding Lattice Mico32 target.
Where to start, which of existing targets to copy and start changing ?
Best regards,
Drasko
___
Openocd-development
Unless I hear objections, I plan to push this support in the
not too distant future.
The current support for pipes does not support named pipes,
and it is also gdb specific.
I've got it coded up and ready for testing. I broken apart
this support in as many small commits as possible,
each of
ep93xx and at91rm9200 are conditionally built only on arm and were not
updated to reflect changes in command registration handler.
This patch makes them properly compile again, fixing a build failure
experienced on Debian armel.
Signed-off-by: Luca Bruno lu...@debian.org
---
memory leaks and missing check on memory allocation.
Signed-off-by: Øyvind Harboe oyvind.har...@zylin.com
---
src/flash/nor/core.c | 13 +++--
1 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/src/flash/nor/core.c b/src/flash/nor/core.c
index d200d8c..2c1d9de 100644
---
On 09/27/2010 06:50 AM, Øyvind Harboe wrote:
[snip]
- I have purposely kept the somewhat misleading port names because
it makes the code more rebasable. Once this series is pushed, I
intend to go back and do a bit of renaming of variables and fix up
the documentation.
I think you need to have
On Mon, Sep 27, 2010 at 5:09 PM, Zach Welch zwe...@codesourcery.com wrote:
On 09/27/2010 06:50 AM, Øyvind Harboe wrote:
[snip]
- I have purposely kept the somewhat misleading port names because
it makes the code more rebasable. Once this series is pushed, I
intend to go back and do a bit of
On 09/27/2010 07:12 AM, John Rigby wrote:
On Mon, Sep 27, 2010 at 1:05 AM, Zach Welch zwe...@codesourcery.com wrote:
...
Last week, I started testing my BeagleBoard with OpenOCD, so I have
begun trying to validate and improve the Cortex-A8 support. Indeed, I
have already committed a minor
On 09/27/2010 08:15 AM, Øyvind Harboe wrote:
The only breakage that I can think of is that the -p option is gone.
I was thinking about adding it back, but print a warning and
translate it to -c log_output openocd.log; gdb_port pipe
I think this is a better option than removing it. Print a loud
I'm using OpenOCD and a Flyswatter to debug some new code that is
based on the u-boot-next tree. The board is a Beagle C4. The problem
that I am seeing is that I can not access memory from the telnet
sesson to OpenOCD or from an attached gdb session. I believe the
problem is that in the -next
Sorry, first time I've used git-send-email. Didn't realize the
commit message was so sparse.
While the Seralyzer is currently an internal-only tool in our
Company, I don't think adding it to upstream will have any effect
on the maintainability of the ft2232 driver.
-Original Message-
On Mon, Sep 27, 2010 at 6:19 PM, Zach Welch zwe...@codesourcery.com wrote:
On 09/27/2010 08:15 AM, Øyvind Harboe wrote:
The only breakage that I can think of is that the -p option is gone.
I was thinking about adding it back, but print a warning and
translate it to -c log_output openocd.log;
I think it was operator error. I can't reproduce the problem.
On Mon, Sep 27, 2010 at 2:06 PM, John Rigby jcri...@gmail.com wrote:
I'm using OpenOCD and a Flyswatter to debug some new code that is
based on the u-boot-next tree. The board is a Beagle C4. The problem
that I am seeing is that
16 matches
Mail list logo
