Hello,
On 07.02.2011 03:57, Aaron Carroll wrote:
On 04/02/11 17:00, Øyvind Harboe wrote:
Maybe DAPs should exist independently of JTAG and
targets and targets should refer to the DAP relevant
to that target?
Agreed, but then how does one discover the DAP relevant to a TAP.
Suppose core0 is on
> Agreed, but then how does one discover the DAP relevant to a TAP.
> Suppose core0 is online and you're bringing up core1... all you have is
> a fresh target and a TAP pointer.
Create a list of DAPs and scan it. If there is no DAP there add one,
if there is, use it?
--
Øyvind Harboe
Can Zylin
On 4 February 2011 17:00, Øyvind Harboe wrote:
> Maybe DAPs should exist independently of JTAG and
> targets and targets should refer to the DAP relevant
> to that target?
Also a good idea to be transport independent (SWD comes to mind).
But I don't understand oocd internals enough to see a nice
On 04/02/11 17:00, Øyvind Harboe wrote:
Maybe DAPs should exist independently of JTAG and
targets and targets should refer to the DAP relevant
to that target?
Agreed, but then how does one discover the DAP relevant to a TAP.
Suppose core0 is online and you're bringing up core1... all you have i
Maybe DAPs should exist independently of JTAG and
targets and targets should refer to the DAP relevant
to that target?
--
Ø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/zy1000.html
ARM7 ARM9 ARM11 XSca
Hi,
I'm about to start hacking on support for multiple targets per TAP.
Specifically this is for Cortex-A9, where a single TAP (ADIv5 DAP)
exposes several cores. The problem is that each core is a separate
target, but they need to share DAP data (struct adiv5_dap).
Currently, "struct adiv5_dap" i
