On Monday 25 January 2010, Alan Carvalho de Assis wrote:
> Hi Dave,
>
> On 1/23/10, David Brownell wrote:
> > On Monday 18 January 2010, Alan Carvalho de Assis wrote:
> >>
> >> What could I investigate now to fix this error?
> >
> > Unfortunately I think you're starting to hit some of the ways
>
Hi Dave,
On 1/23/10, David Brownell wrote:
> On Monday 18 January 2010, Alan Carvalho de Assis wrote:
>
>> When I type halt the prompt get blocked and about 1 minute after I
>> receive this error:
>>
>> > halt
>> AHBAP Cached values: dp_select 0x10, ap_csw 0xa202, ap_tar 0x54011080
>> JTAG-DP
On Monday 18 January 2010, Alan Carvalho de Assis wrote:
> When I type halt the prompt get blocked and about 1 minute after I
> receive this error:
>
> > halt
> AHBAP Cached values: dp_select 0x10, ap_csw 0xa202, ap_tar 0x54011080
> JTAG-DP OVERRUN - check clock or reduce jtag speed
> Read ME
Hi David,
On 1/18/10, David Brownell wrote:
> On Sunday 17 January 2010, Alan Carvalho de Assis wrote:
>> Now I need to find a way to place the processor on halt mode. I tried
>> many commands, including "imx51.cpu arp_halt" with no success.
>
> Use plain old "halt".
>
> "arp_halt" looks to be un
On Sunday 17 January 2010, Alan Carvalho de Assis wrote:
> Now I need to find a way to place the processor on halt mode. I tried
> many commands, including "imx51.cpu arp_halt" with no success.
Use plain old "halt".
"arp_halt" looks to be unused. Certainly it's not documented
as anything more th
On Sunday 17 January 2010, Alan Carvalho de Assis wrote:
> I'm reading the "CoreSight Technology System Design Guide", but there
> is poor information about DAP.
See:
ARM Debug Interface v5 Architecture Specification
for DAP info...
___
Openocd-develop
Hi David,
On 1/16/10, David Brownell wrote:
> On Saturday 16 January 2010, Alan Carvalho de Assis wrote:
>> I'm trying to figure out what DAP is waiting for.
>
> Sorry, cant help there. But surely turning on the debug
> output options (there's a separate JTAG I/O option too)
> should provide mor
On Saturday 16 January 2010, Alan Carvalho de Assis wrote:
> I'm trying to figure out what DAP is waiting for.
Sorry, cant help there. But surely turning on the debug
output options (there's a separate JTAG I/O option too)
should provide more than enough clues for you. :)
_
On Saturday 16 January 2010, Alan Carvalho de Assis wrote:
> > And I don't see any event code to *enable* the DAP using SJC, so there
> > is no point in requesting that it be enabled. If it's not already
> > present on the scan chain, you'd need to write SJC code to enable it.
> >
>
> Unfortunate
Hi David,
On 1/15/10, David Brownell wrote:
>> OpenOCD detects all TAPs, but I receive a Timeout:
>>
>> Warn : imx51.SDMA: nonstandard IR value
>> RCLK - adaptive
>> Info : device: 4 "2232C"
>> Info : deviceID: 67353760
>> Info : SerialNumber: 0100480 A
>> Info : Description: Signalyzer A
>> Info
On Friday 15 January 2010, Alan Carvalho de Assis wrote:
> Hi Fabio,
>
> On 1/15/10, Fabio Estevam wrote:
> > Hi,
> >
> > Has anyone used OpenOCD on a Freescale MX51 processor so far?
> >
>
> I'm trying to get it working.
>
> OpenOCD detects all TAPs, but I receive a Timeout:
>
> Warn : imx51.
Hi Fabio,
On 1/15/10, Fabio Estevam wrote:
> Hi,
>
> Has anyone used OpenOCD on a Freescale MX51 processor so far?
>
I'm trying to get it working.
OpenOCD detects all TAPs, but I receive a Timeout:
Warn : imx51.SDMA: nonstandard IR value
RCLK - adaptive
Info : device: 4 "2232C"
Info : deviceID
Hi,
Has anyone used OpenOCD on a Freescale MX51 processor so far?
Thanks,
Fabio Estevam
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
13 matches
Mail list logo
