Re: [Openocd-development] Automatic detection of debugbase for cortex A8

2010-12-04 Thread Marek Vasut
On Tuesday 30 November 2010 08:16:31 Øyvind Harboe wrote:
  This patch breaks debugging on the DM37x.  It appears that the debug
  base and APID is not sufficient to identify problematic processors
  since the DM37x on the Beagleboard XM incorrectly passes the checks in
  arm_adi_v5.c:
  
 for (i = 0; i  sizeof(broken_cpus)/sizeof(struct broken_cpu);
  i++) if (broken_cpus[i].dbgbase == dbgbase 
 broken_cpus[i].apid == apid) {
 LOG_WARNING(Found broken CPU (%s), trying to
  fixup  ROM Table location from 0x%08x to 0x%08x,
  broken_cpus[i].model, dbgbase,
 broken_cpus[i].correct_dbgbase);
 dbgbase = broken_cpus[i].correct_dbgbase;
 break;
 }
  
  Is there another way that these problematic CPUs can be identified?
 
 Anyone?

Ah I see it now ... I don't have DM37x based board, but I can try getting one. 
Otherwise, can someone (with DM37x) help me fixing this ?

Thanks in advance, Cheers
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development


Re: [Openocd-development] Automatic detection of debugbase for cortex A8

2010-11-12 Thread Karl Kurbjun
On Sat, Nov 6, 2010 at 8:42 AM, Øyvind Harboe oyvind.har...@zylin.com wrote:
 I've merged Marek's work:

 http://repo.or.cz/w/openocd/cortex.git

 I'm pleased not only with the result, but how the set of patches
 came about through a great discussion on the list and
 improvement of Marek's original solution!

 (I haven't actually been able to try it, though it looks great
 to me, and it is reported as working.)

 --
 Øyvind Harboe

 Can Zylin Consulting help on your project?

 US toll free 1-866-980-3434 / International +47 51 63 25 00

 http://www.zylin.com/zy1000.html
 ARM7 ARM9 ARM11 XScale Cortex
 JTAG debugger and flash programmer
 ___
 Openocd-development mailing list
 Openocd-development@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/openocd-development


This patch breaks debugging on the DM37x.  It appears that the debug
base and APID is not sufficient to identify problematic processors
since the DM37x on the Beagleboard XM incorrectly passes the checks in
arm_adi_v5.c:

for (i = 0; i  sizeof(broken_cpus)/sizeof(struct broken_cpu); i++)
if (broken_cpus[i].dbgbase == dbgbase 
broken_cpus[i].apid == apid) {
LOG_WARNING(Found broken CPU (%s), trying to fixup 
ROM Table location from 0x%08x to 0x%08x,
broken_cpus[i].model, dbgbase,
broken_cpus[i].correct_dbgbase);
dbgbase = broken_cpus[i].correct_dbgbase;
break;
}

Is there another way that these problematic CPUs can be identified?

-Karl
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development


[Openocd-development] Automatic detection of debugbase for cortex A8

2010-11-06 Thread Øyvind Harboe
I've merged Marek's work:

http://repo.or.cz/w/openocd/cortex.git

I'm pleased not only with the result, but how the set of patches
came about through a great discussion on the list and
improvement of Marek's original solution!

(I haven't actually been able to try it, though it looks great
to me, and it is reported as working.)

-- 
Øyvind Harboe

Can Zylin Consulting help on your project?

US toll free 1-866-980-3434 / International +47 51 63 25 00

http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development