Hi,
I am using a ft2232 based jtag device with a mips board and the
performance is really terrible:
57344 bytes in 3119.897949s (0.018 kb/s)
It seems to work ok in that I can halt, resume, read/write memory etc,
but every operation is very slow, halting takes almost 3 seconds.
I pulled the code
On Tue, Mar 22, 2011 at 12:14 PM, Michael Schwingen
wrote:
> Øyvind Harboe wrote:
>>
>> I'm wondering if it would be better to ditch the automatic fixup
>> code and use parameters to target in config script.
>>
>> Default would be to use the automatic detection per ARM's
>> specification.
>>
>
> S
Øyvind Harboe wrote:
I'm wondering if it would be better to ditch the automatic fixup
code and use parameters to target in config script.
Default would be to use the automatic detection per ARM's
specification.
Since auto-detecting the broken devices seems to be problematic, I think
that wou
I'm wondering if it would be better to ditch the automatic fixup
code and use parameters to target in config script.
Default would be to use the automatic detection per ARM's
specification.
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / Internationa
On Tue, Mar 22, 2011 at 9:18 AM, Tomek CEDRO wrote:
>
> On Tue, Mar 22, 2011 at 6:22 AM, Øyvind Harboe
> wrote:
> > cortex a8 and a9 are very similar, so they should be merged and
> > conditional code used + configuration options.
> >
> > cortex m3 is more mature(hence breakage is more of an iss
On Tue, Mar 22, 2011 at 6:22 AM, Øyvind Harboe wrote:
> cortex a8 and a9 are very similar, so they should be merged and
> conditional code used + configuration options.
>
> cortex m3 is more mature(hence breakage is more of an issue) and
> much more different so merging *all* cortex code is furthe
