On Saturday 30 October 2010 07:24:08 Marek Vasut wrote:
> On Friday 29 October 2010 09:37:36 Øyvind Harboe wrote:
> > > Oyvind sorry, I just can't find it ... could you tell me where it is
> > > please ?
> > 
> > Start here:
> > 
> > https://lists.berlios.de/pipermail/openocd-development/2010-September/016
> > 48 2.html
> 
> Hey,
> 
> I went through all of this stuff tonight ... and I came to a conclusion,
> that MEM-AP contains register called BASE whose top 20 bytes should
> contain the debug
> 
> base address. From my observation, if I run:
> > dap info 1
> 
> AP ID register 0x04770002
>         Type is MEM-AP APB
> AP BASE 0x80000000
>         ROM table in legacy format
>         CID3 0x00, CID2 0x00, CID1 0x00, CID0 0x00
>         MEMTYPE System memory not present. Dedicated debug bus.
>         ROMTABLE[0x0] = 0x0
>                 End of ROM table
> 
> I get no data. Though if I artificially adjust the dbgbase to 0x60000000 in
> arm_adi_v5.c, I get the following stuff. So, is the processor just making
> fun of me and misreporting the debug base or did I just miss something?
> This is what I get after the adjustment
> 
> > dap info 1
> 
> AP ID register 0x04770002
>         Type is MEM-AP APB
> AP BASE 0x60000000
>         ROM table in legacy format
>         CID3 0xb1, CID2 0x05, CID1 0x10, CID0 0x0d
>         MEMTYPE System memory not present. Dedicated debug bus.


--SNIP--

So it turns out (by reading Freescale iMX515 errata), ENGcm09395 to be exact 
that the chip misreports the ROM Table address (it reports 0x8000_0000, but it 
should report 0x6000_0000). On the other hand, the contents of the ROM Table is 
then correct.

Oyvind, this technically makes the autodetection complementary to manual 
approach. There is a solution I see now -- implement the autodetection, which 
will work on most chips (modulo iMX515 ...) and add an option to manually 
specify the ROM Table base.

But that being the case, I'd prefer to make an incremental patch on top of the 
patches I submitted.

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

Reply via email to