I'm starting to read the documents Rick gave in
https://lists.berlios.de/pipermail/openocd-development/2009-April/005273.html
:)
Duane Ellis wrote:
> So - I guess the next step with OMAP - aka: CortexA8 is to figure out
> how the DAP interface works.
> The existing dap code - well - It's a bit
duane> [thinking about a DAP command]
rick> Yes, a dap command would be useful. You will find that there
isn't a whole lot in the dap layer before you are dealing with the AHB
and APB bus ports.
Yea, that's the sticky or confusing part for me. How do I address port
X, vrs Port Y, per the diag
On Mar 23, 2009, at 7:57 PM, Duane Ellis wrote:
So - I guess the next step with OMAP - aka: CortexA8 is to figure out
how the DAP interface works.
The existing dap code - well - It's a bit confusing to me, and has
such
wonderful documentation.
The dap code provides a layer to handle reque
So - I guess the next step with OMAP - aka: CortexA8 is to figure out
how the DAP interface works.
The existing dap code - well - It's a bit confusing to me, and has such
wonderful documentation.
===
I'm thinking that adding a "dap" command will be helpful - for both
Cortex M3 - and A8. A
