Specify entry point (tiny flash size after project import)

[WoodyWoodsta]

Hey guys

Decided to give Visual Studio a go today along with VisualGDB for embedded dev using the STM32F0.  I imported a generated RTOS project from STM32CubeMX and (after a bit of a struggle making sure all the directories were accounted for) everything appears to play nice as far as linting is concerned. In the process, I obviously replaced the default “main” file, named LEDBlink.cpp (or something) with the generated one. Now when I build the project, the resulting flash footprint is roughly 200 bytes and when debugging, there is nothing running (VS can’t pick up the context).

I’m assuming this is an entry point specification problem, but cannot find where to set this detail.

Any help would be appreciated!!

 

FYI: I’m running VS Community 2015 RC, VisualGDB 5 Beta 2 Trial Version

 

Thanks!

Sean

[WoodyWoodsta]

Turn’s out, STM32CubeMX generates a startup_xxxx.s file, which was subsequently not imported when I brought all the files in using the “Import Files Recursively” functionality.

Simply imported the correct startup.c file and all is working well! My bad!

[Author]

Posts