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
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
