Looks like you need to update the Toolchain location in Flowcode settings. Flowcode is still pointed at 4.2

Yes, understood, you are correct, that does need changing. I think that just informs the device list info.
The section I quoted is what controls the build/linker.

Glad to hear it now works!

For info: The fcd clock defaults assume 8MHz for the (excellent) Nucleo boards.

I've now had chance to have a look... The fcdx looks correct (where it matters) ... <parameters> <lscript value = 'stm32f.ld' /> <romsize value = '256K' /> <ramsize value = '64K' /> </parameters> The project clock setup has issues, please could you try the following changes to your settings (this wi...

It's a tricky balance between testing every device, and thereby having a reduced set, or creating untested fcds for the gaps with the risk of a bug.

OK, there might be other things to change too, I will know better once I get to my PC
Unless Matrix get there first

I don't think that list comes from the fcd.
It will be worth trying your modified version anyway.
Just also ensure that <root> is the very first thing in the fcdx file.

No doubt someone at Matrix will update the system soon

Yes, the live data is in a Windows hidden directory
C:\ProgramData\MatrixTSL\FlowcodeV10\FCD\

V9 not V10 in your case

Try deleting the header from the fcd file, down to just before the <root> tag

The CubeMX is just useful for seeing the resultant clock rates as you set the various dividers and multipliers. It also highlights any out of range settings. The validated settings can then be copied to the Flowcode project settings. You could try editing the device fcdx file, the 512 to 256 edit sh...

Thanks for the zip, nothing leaps out at me from what I can see.
But I don't currently have access to my Flowcode PC so can't check much at the moment.
Have you checked your clock configs with STM32CubeMX?
It would be easy to overclock something with that 25MHz crystal.