Posted on October 09, 2016 at 05:38Marcin,
From my article that will be going out next week:
''I don’t particularly care for ST’s code style, I find putting my code into their slots pretty restrictive, so I would replace line 25 with a function call to my mainline code in another file.
24 /* USER CODE BEGIN WHILE */
25 ThermostatMain();
26 {
27 /* USER CODE END WHILE */
Even if you rerun the code generation phase of Cube, line 25 will be preserved. Then in my code, probably in a file called thermostat.c in my
source
directory, I would have a function called ThermostatMain() which would contain my normal FOREVER loop structured code.''
Well, at least I thought it would be preserved.
So, my suggestion is to create your own source and include directories and put all of your code there instead of the Src and Inc directories that Cube creates.
In main, get out as soon as possible, replace the while (1) with a subroutine call and don't ever touch the Cube generated files again.
Frankly, and I've said this before here, the generated code from Cube should not create main(). Some RTOS' provide main and take care of a bunch of stuff before giving the processor over to your application. Cube should have generated stuff that my code calls. But, too late now. Let's work around it.
Andrei from The Great White North
(as seen on the embedded.fm podcast and blog)
