Arduino for STM32

So with libmaple Roger core F407 @168MHz, with FPU on (gcc directives and asm), I 've got with default -Os MFLOPS 79 57 17 and MWIPS 95 and similar with -O1. It crashed (no serial) with -O2 and -O3. That is identical with bingo's -Os with STM core and 407. We may assume therefore the ART and FPU is ...

This is Roger's core Black407ZET @168MHz I cannot get it work with -O2 and -O3 -Os ########################################## Single Precision C Whetstone Benchmark Calibrate 0.11 Seconds1.00 Passes (x 100) 0.53 Seconds5.00 Passes (x 100) 2.64 Seconds25.00 Passes (x 100) Use94 passes (x 100) Single ...

It looks to me the STM experts have to look at it. With ART enabled the 411 shows 2x lower MWIPS. :? There could be a doublecheck - to run it with libmable core - ag123 did above and posted the code, even the print is a crap at least you may to see the 3 MFLOPS and final MWIPS. It could be there is ...

So with the ART enabled you got lower numbers??
There is an issue somewhere..

It looks like the ART function is reversed

I do not understand that piece of code.
Simply enable the ART and that's it.

The Chrom-ART is not available on all devices - but that is about DMA blobs manipulation.

All F4xx ever have got the ART.
It has to be enabled, then it does not matter how many ws you have (the ART accelerate the flash access).
You may overclock to 2ws @96MHz, it may or may not work.

Thanks!
We have got plethora of flash in F4xx, no problem with printf!!

When looking at the historical whetstone result data - the big CPUs get higher MWIPS, but much lower MFLOPs at the same clock. Also I do not understand you got 100 MWIPS @96MHz (411) and @168MHz (407) we get 98. There must be a subtle bug in the code somewhere. The historical results show nice linea...

I have got BlackF407 board with 407ZET (144pin) on it (plus 512kB 10ns sram soldered in).
I do upload via J-Link (clone) with J-flash utility (set to SWD @4MHz).
Then I have to unplug/plug the USB cable, the RST does not start the stuff after upload..
It seems USB code needs some fix.

What device have you selected for the Discovery F407?
Try with BlackF407ZE

It could be the boards have different gcc setting..