[Openocd-development] AM3517 Craneboard support

Hi all, I tried to use AM3517evm's config on AM3517 Craneboard. But it seems that no luck to get openOCD work. *sudo openocd -f interface/flyswatter.cfg -f board/am3517evm.cfg Open On-Chip Debugger 0.5.0 (2011-08-31-15:54) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios

[Openocd-development] How to get CPUTAPID for new board

Hi all, I would like to support another cortex A8 machine, s5pc100. In theory, add proper target configs should be enough. Since the support of cortex A8 is almost finished. The first issue comes up is how do I know the CPUTAPID for the new board? I went through the document of openocd, but could

[Openocd-development] [PATCH] omap3530: move assertion of PRM_RSTCTRL from reset-assert-pre to reset-start

If enabling of global software reset is handled in reset-assert-pre stage, target would get into Thumb state occasionally. That's, the target is not indeed reset. Fix this by moving PRM_RSTCTRL in the reset-start stage like previous config. Signed-off-by: Matt Hsu --- tcl/target/omap353

Re: [Openocd-development] [PATCH] Cortex A8 reset handling

> > On my BeagleBoard I can now do "reset halt" and end up somwhere Hi Magnus, Nice work! It seems that all the low-level logic for A8 are ready for debugging. The reset is get gdb hook up with openOCD. Matt > in the X-Loader. > > Best regards, > Magnus > > > ---

Re: [Openocd-development] Cortex-A8, Introduction

Magnus Lundin wrote: > Hello list. > > For those of you who has not yet had the time to read all the TRM's > covering Cortex-A8 and ARM ADIv5, I have started to write up an easy > introduction to the debug components in a Cortex-A8 system. > It's great. The first look on Cortex-A8 debug sy

[Openocd-development] [PATCH][Cortex_A8] Enable-halt-debug-mode-for-cortex_a8.patch

Hi Øyvind, This is a resend patch. It only improves the description as Magnus suggested. Cheers, Matt >From b88fefc9c2d1711b32335a681f0731eae158f756 Mon Sep 17 00:00:00 2001 From: Matt Hsu Date: Fri, 4 Sep 2009 15:43:31 +0800 Subject: [PATCH] [Cortex_A8] Enable-halt-debug-mode-for-cortex

Re: [Openocd-development] [PATCH][Cortex_A8] Fix the hardware single-step logic

>> >> > Hi Matt, > > It makes me very happy to se active work with this code. Hi Magnus, It's all based on you guys great work. :) I'm just standing on the shoulders of giants. (stealing from Holger's blog: http://zecke.blogspot.com/2009/08/standing-on-shoulders-of-giants-fixing.

Re: [Openocd-development] [PATCH][Cortex_A8] Fix the hardware single-step logic

Øyvind Harboe wrote: > 1 and 3 committed. > > Can you let me know when 2 is ready to commit? > Hi Øyvind, I will resend the patch #2 since I think the following code segment should be merged. retval = mem_ap_write_atomic_u32(swjdp, OMAP3530_DEBUG_BASE + CPUDBG_DRC

Re: [Openocd-development] [PATCH][Cortex_A8] Fix the hardware single-step logic

Cheers, Matt > > Re #2: > > On Thursday 03 September 2009, Matt Hsu wrote: > >> --- a/src/target/cortex_a8.c >> +++ b/src/target/cortex_a8.c >> @@ -430,6 +430,13 @@ int cortex_a8_halt(target_t *target) >> retval = mem_ap_write_atomic_u32

Re: [Openocd-development] [PATCH][Cortex_A8] Fix the hardware single-step logic

> > Tested-by: Dirk Behme Hi Dirk, Thanks for your feedback. > > Please apply. > >> Also, the programming breakpoints works as well. > > Could you give some examples how you use this? Giving some logs of how > you are testing would help other to reproduce this ;) The follo

[Openocd-development] [PATCH][Cortex_A8] Fix the hardware single-step logic

Hi all, This series patches fix the hardware single-step logic mainly. With these patches, you can do the step operation on the telnet session. Also, the programming breakpoints works as well. Cheers, Matt >From 8fc6c1839b80447e06c368b0d8948f5feda3e474 Mon Sep 17 00:00:00 2001 From: Matt

Re: [Openocd-development] Cortex-A8 problems

> So in the OMAP initialisation script we have the line > > # set DBGEN signal > > mww 0x5401d030 0x2000 > Hi Magnus, It seems that the debug address space is remapped from 0xD401 to 0x5401. But I could not find out any sections mentioned this remapping.

Re: [Openocd-development] BeagleBoard and Flyswatter

Fred Koehler wrote: > hi, > > I've tested 1 and 2 as Dirk suggested. With both versions I get the > same results. I'm able to connect jtag consistently and from a telnet > session issue the omap3_dbginit command. Lots of improvement from the > last time I tried. Hi all, Thanks Dirk's

Re: [Openocd-development] BeagleBoard and Flyswatter

Øyvind Harboe wrote: > Did you try with the patches I committed today? > Hi Øyvind, Thanks for your reply. Yes. I applied the patch your committed. It definitely works. The jtag session could be established. The problem is I would like to issue commands such as reset halt,

Re: [Openocd-development] BeagleBoard and Flyswatter

Fred Koehler wrote: > hi, > > http://elinux.org/BeagleBoardOpenOCD reports success with using > OpenOCD and the Flyswatter to establish a JTAG connection with the > Beagle board. I've tried to reproduce these steps but am having some > issues. > Hi Fred, No one is an island. I'm trying