STM32F103RBT6 + Unusual code behavior

roman23 · ‎2011-01-28

Posted on January 28, 2011 at 14:00

Tesla DeLorean · ‎2011-05-17

Posted on May 17, 2011 at 14:23

Have you looked at the generated code? Does turning off optimization change the behaviour?

Is 'a' being set in an interrupt or other asynchronous routine. If so perhaps you should define it as being volatile?

Do TRUE and FALSE have the values you expect? Also check the values for SET and RESET, people have broken those before and the library doesn't work properly.

Tips, buy me a coffee, or three.. PayPal Venmo Up vote any posts that you find helpful, it shows what's working..

ColdWeather · ‎2011-05-17

Posted on May 17, 2011 at 14:23

Stop the peripheral while debugging. See DBGMCU_CR register.