2017-10-30 10:45 PM
STM32F0 command execution speed
2017-10-31 06:54 AM
Can we please try to leave the entire question out of the title. Edit to put the question into the question field, and a summary in the title....
200ns is rather slow, how are you measuring this?
What are you measuring? One C line may translate into many assembler instructions, it is those that nominally take 1 cycle.
The problem at 48MHz is that it isn't 24MHz x2 in terms of performance, the wait state from the flash predominates.
2017-10-31 06:41 PM
SRAM is no wait state, so if you're trying for fastest instruction rate run the code from there. From flash make sure the prefetch is turned on, Vcore at right voltage range, and latency set properly. Are you using an HSE with a crystal? Don't use an internal RC oscillator for SYSCLK, you build in a 1% error that way.
If you're toggling GPIO pins to generate a signal that's an unreliable measurement. Run a loop with 100,000 iterations or some count under the ppm rating on your HSE crystal, do a before and after timer capture with timer clocked from system bus. That'll give you a better metric.
Jack Peacock
2017-11-07 02:27 AM
,
,
Hii Jack,
Thank You For your reply, Can you please guide me with the procedures of how to switch ,–mlong-calls , ,in specific compiler on ,System Workbench for STM so that i can use, ' , , ♯ define RAMFUNC __attribute__ ((long_call, section ('.ramfunctions'))) , ,'.