On 24 January 2011 19:29, Peter Stuge <pe...@stuge.se> wrote:
> Aaron Carroll wrote:
>> +# GDB target: Cortex-A9, using DAP
>> +#
>> +# The debugger can connect to either core of the A9, but currently
>> +# not both simultaneously. Change -coreid to 1 to connect to the
>> +# second core.
>> +#
>> +set _TARGETNAME $_CHIPNAME.cpu
>> +target create $_TARGETNAME cortex_a9 -chain-position $_CHIPNAME.dap -coreid >> 0
>
> Should the coreid be a parameter of some kind?
What sort of parameter? Ideally there would be second target with
"-coreid 1" here,
but that's not quite working yet.
>
>
>> +#
>> +# M3 targets, separate TAP/DAP for each core
>> +#
>> +target create $_CHIPNAME.m30 cortex_m3 -chain-position $_CHIPNAME.m30_dap
>> +target create $_CHIPNAME.m31 cortex_m3 -chain-position $_CHIPNAME.m31_dap
>
> Huh? Are there two Cortex-M3 cores in the A9?
The OMAP4430 has two M3's, independent to the A9's. Nominally one controls the
still image processor, and the other the video processor, but they are
more-or-less
general purpose.
-- Aaron
>
>
> //Peter
> _______________________________________________
> Openocd-development mailing list
> Openocd-development@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/openocd-development
>
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
