Brilliant For-loop Bug
Hi Everyone,
I’ve got a brilliant situation in which a second and third ‘for’ is simply ignored when being flashed to an STM32F103C8T6. I call this brilliant because of the obvious looks of a compiler bug or at least some speciality that shouldn’t be there because I’m only re-using the same ‘for’ a second and third time.
So by who and why was the second and third ‘for’ swallowed in the process of compiling and flashing to the STM32F103C8T6?
Please no guesses nor ‘should’ or protocols in your helping since it is a simple c test. Thanks.
The initial template was created with CubeMX, all used pins have been configured and port clocks enabled and of course the system clock configured. If this wasn’t the case not one pin would blink.
The result is that PC14, PC15 and PC13 toggle synchroneously as if the second and third ‘for’ doesn’t exist. It should be step sequencing but it is not. And yes everything was updated, saved and compiled before flashing. I have gone through all necessaties before calling on the forum.
Find screenshot attached.
Good luck!
Greets,
Ben