Re: [Openocd-development] [PATCH] cortex_a9: implement read/write memory through APB-AP

2011-02-10 Thread Øyvind Harboe
On Thu, Feb 10, 2011 at 8:57 AM, luca ellero lro...@gmail.com wrote: Sorry for the double posting. I made some mess :-( Please discard 1st posting, 2nd is the right one. Apologies for any inconvenience This is the right one?

Re: [Openocd-development] [PATCH] cortex_a9: implement read/write memory through APB-AP

2011-02-10 Thread luca ellero
2011/2/10 Øyvind Harboe oyvind.har...@zylin.com On Thu, Feb 10, 2011 at 8:57 AM, luca ellero lro...@gmail.com wrote: Sorry for the double posting. I made some mess :-( Please discard 1st posting, 2nd is the right one. Apologies for any inconvenience This is the right one?

Re: [Openocd-development] [PATCH] cortex_a9: fix dap_ap_select() usage

2011-02-10 Thread luca ellero
On 09/02/2011 10.57, Øyvind Harboe wrote: Hi Aaron, On Wed, Feb 9, 2011 at 10:54 AM, Aaron Carrollaar...@cse.unsw.edu.au wrote: Hi all, I think the consensus on this issue is that AP handling could be improved. Until someone has the motivation to fix it properly, can this patch be applied?

Re: [Openocd-development] [PATCH] cortex_a9: fix dap_ap_select() usage

2011-02-10 Thread Øyvind Harboe
Merged. Thanks! -- Ø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 XScale Cortex JTAG debugger and flash programmer ___

Re: [Openocd-development] [PATCH] cortex_a9: implement read/write memory through APB-AP

2011-02-10 Thread Øyvind Harboe
Merged. Thanks! -- Ø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 XScale Cortex JTAG debugger and flash programmer ___

[Openocd-development] Problems with commit messages

2011-02-10 Thread Øyvind Harboe
I think perhaps there is a problem with commit messages these days on sourceforge. Anyone? Counting objects: 9, done. Delta compression using up to 4 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 1.37 KiB, done. Total 5 (delta 4), reused 0 (delta 0)

Re: [Openocd-development] [PATCH] cortex_a9: implement read/write memory through APB-AP

2011-02-10 Thread Aaron Carroll
Hi Luca, On 10 February 2011 06:19, Luca Ellero lro...@gmail.com wrote: This patch adds read/write capability to memory addresses not accessible through AHB-AP (for example boot ROM code). To select between AHB and APB, a dap apsel command must be issued: dap apsel 0 - following memory

Re: [Openocd-development] Problems with commit messages

2011-02-10 Thread Spencer Oliver
On 10/02/2011 09:09, Øyvind Harboe wrote: I think perhaps there is a problem with commit messages these days on sourceforge. Anyone? I just did a small commit and received no email, so looks like something has broken. I was sent an email yesterday about changes:

[Openocd-development] current and maximum jtag queue size for jtag hardware ?

2011-02-10 Thread Mathias K.
Hello, is there any way to determine the current and maximum queue size before a jtag_execute_queue() has to be executed ? Regards, Mathias ___ Openocd-development mailing list Openocd-development@lists.berlios.de

Re: [Openocd-development] current and maximum jtag queue size for jtag hardware ?

2011-02-10 Thread Øyvind Harboe
On Thu, Feb 10, 2011 at 8:05 PM, Mathias K. kes...@freenet.de wrote: Hello, is there any way to determine the current and maximum queue size before a jtag_execute_queue() has to be executed ? no and no. There is no maximum queue size and the api doesn't and should expose the queue size. Also

Re: [Openocd-development] current and maximum jtag queue size for jtag hardware ?

2011-02-10 Thread Øyvind Harboe
no and no. There is no maximum queue size and the api doesn't and should expose the queue size. 'should not' -- Ø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 XScale

Re: [Openocd-development] Correct definition of JTAG_INSTR_CLAMP in dsp563xx_once.c

2011-02-10 Thread Mathias K.
Hello, in app. note AN1839 (dsp563xx) its 3 ;-). In DSP56300FM and AN2074 they use the correct number 5. Regards, Mathias Am 10.02.2011 20:25, schrieb Phil Fong: Hi, I've been working on Rodrigo on adding support to flash Freescale dsp56800e devices and have been looking at the

[Openocd-development] [PATCH] dsp563xx mem rw changes

2011-02-10 Thread Mathias K.
Changes: - delay jtag queue excecution to decrease memory read/write times - fix an early queue excecution in once interface diff --git a/src/target/dsp563xx.c b/src/target/dsp563xx.c index 4371d0a..9bfb9a1 100644 --- a/src/target/dsp563xx.c +++ b/src/target/dsp563xx.c @@ -29,8 +29,6 @@ #include

Re: [Openocd-development] [PATCH] cortex_a9: implement read/write memory through APB-AP

2011-02-10 Thread Aaron Carroll
Hi Luca, On 11 February 2011 02:00, du...@dummy.com du...@dummy.com wrote: On 10/02/2011 11.10, Aaron Carroll wrote: On 10 February 2011 06:19, Luca Ellerolro...@gmail.com  wrote: This patch adds read/write capability to memory addresses not accessible through AHB-AP (for example boot ROM

[Openocd-development] JTAG_STABLECLOCKS for jlink

2011-02-10 Thread Phil Fong
After some experimenting with building the right cable and generating an appropriate SVF file, I was able to program a Lattice XP2 using OpenOCD and a Signalyzer-H2. Since I also have a jlink, I figured why not give that a shot. It seems that the jlink does not have the JTAG_STABLECLOCKS jtag

[Openocd-development] [PATCH] interface decrease calling overhead

2011-02-10 Thread Mathias K.
Changes: - declare tap_set_state_impl, tap_get_state, tap_set_end_state, tap_get_end_state as static inline, this will decrease the calling overhead for this status getter and setter functions diff --git a/src/jtag/interface.c b/src/jtag/interface.c index 1ed4512..8d5d514 100644 ---

Re: [Openocd-development] [PATCH] interface decrease calling overhead

2011-02-10 Thread Øyvind Harboe
I don't have any objections to this particular patch, but if we have to start doing tweaks at this level, then where does it end? Is there any profiling data that backs up this particular optimization as particularly effective? It is very surprising that this would make an impact, but that's