External Loader in ST-LINK works very slowly. 66MB in 25 minutes.

[MPole]

Hello. I have writed external loaders for 2 flash memories: W25N01GV - 1Gb and GD25Q127C - 128Mb. They are working correctly but too slow. For example, programming 66MB of data take time about 25 minutes! That's horrible long. What can I do to make programming faster(or is it possible at all)? 

I've tried one thing. I make the write function in my program empty, it doesn't write anything. But in this situation the programming process is also as long as with the normal write function. So the problem is in the ST-link. 

int Write (uint32_t Address, uint32_t Size, uint16_t * Buffer)

{

//sFLASH_WriteBuffer((uint8_t *)Buffer, Address-START_ADDR, Size);

return 1;

}

[Tesla DeLorean]

SD Cards get chewed up pretty quick. With a code-load dongle one could export SDIO or QSPI to a pin header/pads and make a super-cheap chip-on-a-board dongle to program a system.

Ethernet works well if you have it, stream/broadcast content from a server, can be done as part of final/functional test stage.

[Uwe Bonnes]

Well, I do not count texane or the rantings in OpenOCD as reference for the Fswd < Fclk/2 myth.

Look at the contributor list of texane ;)

B.t.w. have a look at https://github.com/UweBonnes/bl*ckm*gic/tree/stlinkv2 for bl*ckm*gic running on the PC with original STLINK firmware.

[AVI-crak]

Probably use links to github is prohibited ....

For interface SWD and jtag - there are no clear restrictions on the maximum frequency. But there are restrictions on the ratio of external frequency to internal core bus frequency arm.