At 320 MHz, no meaningful 10 second benchmark is possible due to the u32 ticks overflowing.
Normally, this would be solved, by changing in benchmark-coremark/freedom-metal/core_portme.c
#define TIMER_RES_DIVIDER 1
to a higher value, but the function is not implemented.
(The behaviour does not change)
Also: Where can I tell freedom metal that the CPU is now running at 320M? With Freedom Metal,
EE_TICKS_PER_SEC divides the ticks by 16M to calculate the passed seconds, even @320MHz
At 320 MHz, no meaningful 10 second benchmark is possible due to the u32 ticks overflowing.
Normally, this would be solved, by changing in benchmark-coremark/freedom-metal/core_portme.c
#define TIMER_RES_DIVIDER 1to a higher value, but the function is not implemented. (The behaviour does not change)Also: Where can I tell freedom metal that the CPU is now running at 320M? With Freedom Metal,
EE_TICKS_PER_SECdivides the ticks by 16M to calculate the passed seconds, even @320MHz