grisou:
I agree with you steve… It shouldn’t take so long time… And it’s not related to the debugger device since it is the case with both JLink and usbprog… I gave up on openocd for flashing and I use sam7utils (http://oss.tekno.us/sam7utils) to flash the device and I debug the program with openocd… It was a bit tricky for me to compile it but once I did it worked like a charmHope tis will help you
Did you try to download into RAM? (SRAM) It is works faster, you can use working_area
Yes, I did try to debug in SRAM as well and no difference there (speedwise)…
It does not matter if I reduce/increase the j-tag speed and whether I use usbprog or j-link pods or debug in RAM/ROM or alter my cfg-files or even change computer… It’s always the same speed (around 300 bytes/s)…
I’ve read somewhere that it could be a USB-frame problem… That openOCD does not fully exploite the USB frame when sending/recieving data to the debugger pod which results in that the USB-link speed is automatically reduced… That might explain a lot of stuff…
I’ve given up on using openOCD to upload code to the MCU… I use sam7utils program for that (my program grew beyound the RAM size so → I debug in ROM now)… But I still debug using using openocd though…
What is the dump_image rate? And what is the rate when you download into ram?
