On 13.03.2018 10:40, Uwe Bonnes wrote:
Just for reference: Can anybody test what number gdb reports for the "load" command in that circumstances? Thanks
Good point, Uwe. Here you go: FT2232, JTAG, STM32F722-nucleo: > reset init ... > adapter_khz adapter speed: 3000 kHz > dap memaccess memory bus access delay set to 8 tck > load_image 64kib.bin 0x20000000 65536 bytes written at address 0x20000000 downloaded 65536 bytes in 0.637129s (100.451 KiB/s) FT2232, SWD, STM32F722-nucleo, now with 'dap memaccess': > reset init ... > adapter_khz adapter speed: 3000 kHz > dap memaccess memory bus access delay set to 8 tck > load_image 64kib.bin 0x20000000 65536 bytes written at address 0x20000000 downloaded 65536 bytes in 0.552768s (115.781 KiB/s) > flash write_image 64kib.bin 0x08030000 not enough working area available(requested 76) ... error writing to flash at address 0x08000000 at offset 0x00030000 > dap memaccess 9 memory bus access delay set to 9 tck > flash write_image 64kib.bin 0x08070000 not enough working area available(requested 76) no working area available, can't do block memory writes couldn't use block writes, falling back to single memory accesses wrote 65536 bytes from file 64kib.bin in 0.629446s (101.677 KiB/s) ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
