Re: [OpenOCD-devel] DAP handling for Cortex-A

On Friday 20 November 2015 13:25:04 Andreas Fritiofson wrote: > On Fri, Nov 20, 2015 at 11:20 AM, Matthias Welwarsky > > How would gdb utilize the ahb-ap for uploading binaries? > > First of all, should it? As (I think) we have established, the main (only?) > type of memory access associated with

Re: [OpenOCD-devel] DAP handling for Cortex-A

> > Speaking of confusing nomenclature, what is a "DAP target" even? Also you > keep on using the term "dap port" which doesn't exist in ADIv5. I think you > mean AP. On an platform with more then 1 DAP you have Dap(X).AccessPort(Y) when I refer to a “Dap Port” - I generally mean an access por

Re: [OpenOCD-devel] DAP handling for Cortex-A

On Fri, Nov 20, 2015 at 10:51 PM, Duane Ellis wrote: > > > > You got it wrong, this is a Tcl variable, you can call it whatever you > like. For this example, it's an excellent name. > > I’m quite familiar with it being a TCL Variable, I was the original author > of this feature in OpenOCD. > > So

Re: [OpenOCD-devel] DAP handling for Cortex-A

> > You got it wrong, this is a Tcl variable, you can call it whatever you like. > For this example, it's an excellent name. I’m quite familiar with it being a TCL Variable, I was the original author of this feature in OpenOCD. perhaps I should say it differently, inside of openocd - the code

Re: [OpenOCD-devel] DAP handling for Cortex-A

On Fri, Nov 20, 2015 at 9:21 PM, Duane Ellis wrote: > > > > Maybe you could explain how you envision the user to interact with > the dap > > > > object and with 'mww' and 'mdw’. > > > > $soc.ahb mdb 0xdeadbeef <- using mem_ap_read() on ap 0 > > > First off: > Stop with the names like:

Re: [OpenOCD-devel] DAP handling for Cortex-A

> > > Maybe you could explain how you envision the user to interact with the dap > > > object and with 'mww' and 'mdw’. > > $soc.ahb mdb 0xdeadbeef <- using mem_ap_read() on ap 0 First off: Stop with the names like: “$soc.ahb” - that is not a very good name Reason - There can

Re: [OpenOCD-devel] DAP handling for Cortex-A

On Fri, Nov 20, 2015 at 11:20 AM, Matthias Welwarsky wrote: > On Tuesday 10 November 2015 21:19:46 Andreas Fritiofson wrote: > > > Maybe you could explain how you envision the user to interact with the > dap > > > object and with 'mww' and 'mdw'. > > > Memory access would work like this: > > > >

Re: [OpenOCD-devel] DAP handling for Cortex-A

On Tuesday 10 November 2015 21:19:46 Andreas Fritiofson wrote: > > Maybe you could explain how you envision the user to interact with the dap > > object and with 'mww' and 'mdw'. > Memory access would work like this: > > soc.cortex_a mdb 0xdeadbeef <- using target_read_memory(), in turn > using

Re: [OpenOCD-devel] DAP handling for Cortex-A

On Tue, Nov 10, 2015 at 11:12 PM, Duane Ellis wrote: > As I described earlier about the DAP… > > >> > http://sourceforge.net/p/openocd/mailman/openocd-devel/thread/20150428234557.8376.qm...@stuge.se/ > I should have replied to that too but I didn't have time. > > There are many problems with t

Re: [OpenOCD-devel] DAP handling for Cortex-A

As I described earlier about the DAP… >> http://sourceforge.net/p/openocd/mailman/openocd-devel/thread/20150428234557.8376.qm...@stuge.se/ >> >> There are many problems with the DAP, and the gene

Re: [OpenOCD-devel] DAP handling for Cortex-A

On Tue, Nov 10, 2015 at 5:49 PM, Matthias Welwarsky wrote: > On Monday 09 November 2015 01:05:25 Andreas Fritiofson wrote: > > > One of the main flaws with the current architecture is that the target is > > the main object the user interacts with. The target being something that > > GDB would be

Re: [OpenOCD-devel] DAP handling for Cortex-A

On Monday 09 November 2015 01:05:25 Andreas Fritiofson wrote: > Hi! > > Replying on top to provide background for the inline answers. > > I believe the structure of the ARMv7 support was designed at a time when > its debug architecture was not fully understood, at least not the relation > between

Re: [OpenOCD-devel] DAP handling for Cortex-A

Hi! Replying on top to provide background for the inline answers. I believe the structure of the ARMv7 support was designed at a time when its debug architecture was not fully understood, at least not the relation between the different components. Also, as with almost all additions to OpenOCD, it

[OpenOCD-devel] DAP handling for Cortex-A

Hi, I'm contemplating what to do with the handling of APs for Cortex-A DAPs. What is the background of the "dap apsel" command? The way it is implemented in cortex_a doesn't really make sense. For example, they are not "debug_ap" and "memory_ap". Both AHB and APB are MEM-APs, i.e. you can do me