Posted on May 17, 2011 at 13:00Hello, I've seen this behaviour when using the IWDG: if you refresh it continously, it doesn't work properly, even if you're checking first the IWDG_SR_RVU flag. My testing program is just: Code:IWDG_Init() while(1) { ...
Posted on May 17, 2011 at 12:53Indeed I haven't also been able to see the internal watchdog activation while debugging through jtag. Looking at the DBGMCU_CR register it's all cleared but the behaviour is the same if the set the DBG_IWDG_STOP bit. P...
Posted on May 17, 2011 at 12:53Quote:On 28-11-2008 at 20:29, Anonymous wrote: Re: Watchdog refresh We too would like to know ''how close'' we come to WD ''firing.'' As a work-around - can't you reduce the watchdog period by a small percentage - and...
Posted on May 17, 2011 at 12:53I'm also working with the IWDG, do you know if it's possible to read the internal counter value? I haven't seen the way in the Reference Manual. I want to know if any refresh op is done dangerously close to the counter...
Posted on May 17, 2011 at 12:31Hi, I want to add error handling in the I2C example 1. So I've add the error interrupt: I2C_ITConfig(I2C1, I2C_IT_EVT | I2C_IT_BUF | I2C_IT_ERR, ENABLE );If I don't connect the master & slave, I expect an Acknowledge f...
