On Thu, Jul 4, 2013 at 9:32 PM, [email protected] <[email protected]>wrote:
> I'm using an Olimex ARM-USB-OCD. Target is a MIPS based router chip?
> openocd seems to be working, it is just painfully slow. It took 15
> minutes to download uboot.
>
> > load_image /home/apps/u-boot/uboot.bin 0x80200000 bin
> 99772 bytes written at address 0x80200000
> downloaded 99772 bytes in 900.955444s (0.108 KiB/s)
>
>
>
> source [find interface/arm-usb-ocd.cfg]
>
For one thing, you should be using the ftdi adapter driver instead of the
ft2232. If you configured OpenOCD with --enable-ftdi, it's a simple matter
of sourcing interface/ftdi/olimex-arm-usb-ocd.cfg instead.
But for this level of (non-)performance, there's a bigger problem than the
adapter driver. Post a -d3 debug log and we'll try to see where all the
time is spent.
What is at 0x80200000? At 0x80040000? Is it slow if you load something to
the latter (make sure not to overlap with the working area)? How about
dump_image reads?
Also make sure you're using a recent enough openocd, including any relevant
pending MIPS patches in gerrit (I have no idea what's relevant, though).
I have no experience with MIPS but if I understand correctly, there are
different methods to access memory. Is the fastest one available in use?
/Andreas
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
