Programming external flash speed

What parts specifically are we talking about?

What modes of connectivity does your board provide?

sorry, my English is not very well​.

​

I mean if I have finish my project, I went to download the code to my MCU and external QSPI flash.

How can I get fast?

Clive asks you, what is the type of QSPI, and how is the board connected to PC.

JW

Sorry!!!​ I misunderstood what you mean!!

​

I use "MT25QL01GBBB" QSPI Flash,that is "Serial NOR Flash Memory".

MY  board is use ST-Link to connected to PC. and use ST-LINK Utility to programming.

My English is not very well,If have anything not clear please tell me.

Thank All !

Which STM32 part?

What other connectivity? MicroSD card? Ethernet?

Is the data compressible?

Have you tried one of the significantly faster Segger pods?

The erase performance is relatively slow, you'd want to do that at the 64KB block level (400KBps).

The write speed is supposedly 2MBps, so sending the data via the ST-LINK would seem to be the primary bottleneck here.

In other designs we've provided headers/test-points for connecting memory payload devices (large flash or memory devices as plug-ins) where a small amount of code loaded on the STM32 side can pull the data and burn onto the local memory. Where Ethernet is available part of the test can allow for connectivity to a file server, and large data payloads can be pulled over the network.

HiHi @Community member​ 

thanks your answer,

​

I use STM32 QSPI interface to enable QSPI,

​

I also use MicroSD card and Ethernet !

​

I try the J-Link, but the speed is almost same.

​

​I don't know how to compression the data.... have any reference ?

​

Use Ethernet to programming can make the program fast? Why?

or that is my wrong understanding of your point

Thanks!!!

Did you try a J-Link Pro or Ultra ? The faster modes not the standard one.

https://www.segger.com/products/debug-probes/j-link/models/j-link-pro/

>>Use Ethernet to programming can make the program fast? Why? or that is my wrong understanding of your point

I suspect your bottle-neck is the speed at which you can deliver the data.

You can experiment with the QSPI from your own code, time how long it takes to erase and write 15MB from the application, use a data pattern you have available locally.

Use PKZIP in WinRAR on the data in the FLASH, see if it compresses, and how small it gets. you're trying to determine if there is significant benefit to moving/storing less data.