On Fri, Sep 11, 2009 at 8:22 AM, Øyvind Harboe <oyvind.har...@zylin.com> wrote: > On Fri, Sep 11, 2009 at 6:54 AM, michal smulski <michal.smul...@ooma.com> > wrote: >> >> Attached: >> 1. debug output for load_image without and with memburst write on >> arm1136. See the slow load time on first and error on the other one. > > Try "help arm11" and tinker with memrw_no_increment and > memwrite_error_fatal options. > > If manage to get load_image to succeed run a "verify_image" check > if the error is a red herring or not. You may need to fill the memory > with garbage to avoid verify_image succeeding when in fact > the last memory position wasn't touched.
I've tried memwrite_burst enable here and I can download without getting the error message you see. Tried with a different file though... Modified size to fit in the debugger, still not reproducable. > reset init .... > load_image /config/firmware.phi 0x80000000 bin 1121390 byte written at address 0x80000000 downloaded 1121390 byte in 34.139999s > memwrite_burst enable Enabled memory write burst mode. > load_image /config/firmware.phi 0x80000000 bin 1121390 byte written at address 0x80000000 downloaded 1121390 byte in 84.540001s > idea on improving arm11 burst memory performance: add option to > make download open loop, i.e. do not check for completion of instructions... Strike that last one... already done in arm11 code. -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
