Posted on September 24, 2014 at 13:32Dear Jason,
I had exactly the same problem. The bug is that when you start the STMCube, the first generation dont include the startup file. If you generate second, third,.... project then they is produced correctly.
Please also take care that the SRMCube add additional files to the project C/C++ include file list. This will grow every time you generate a new project. You have to check this after each 10-15 generation cycles and cleanup the C/C++ include paths else Keil will fail with ununderstandable errors.
In addition you have to take care about the debug setting of your project. If you have a SWD debugger (like in all STMxxxDiscovery products), sometimes Cube will change the debugger type to JTAG which will fail next time you want to debug.
You need also to take care about the FULL_ASSERT option in the generation options. This will randomly call assert (if you use complex timers) without any reason because some of the values are randoly from last ram access from other program parts but they will not cleared correctly by init sequence but will be check at assert. This will cause to searching a phantom error.
I hope this could help you.
