WDT fires if setup() takes more than 1 sec

[Sermus]

Should WDT be disabled during setup()?
It's quite common situation when setup() executes quite long time.

[tomaja]

Yes, I also have this problem. I would like to disable WDT during setup() because setup waits for WiFi connection that is used to deliver settings for further operation.
ets_wdt_disable() is reported as undefined external...

[igrr]

Can you call yield() or delay() in your setup function periodically in the
same way it is done in the sample sketches for the ESP8266WiFi library?
Both will indirectly reset the watchdog.
On Apr 2, 2015 10:36 AM, "tomaja" notifications@github.com wrote:

Yes, I also have this problem. I would like to disable WDT during setup()
because setup waits for WiFi connection that is used to deliver settings
for further operation.

Reply to this email directly or view it on GitHub
#34 (comment).

[tomaja]

Oh, yes - delay works! Sorry for that, I didn't get that from README :(
Спасибо, Иван!

[igrr]

@Sermus
Maybe adding methods to enable/disable WDT would be sufficient for most cases?

[Sermus]

Not sure this is a way out because i got it in a 3rd party library which i tried to use as is. Its initialization tooks long time. In that sense if we want to have one-to-one Arduino library portability we must let them initialize as long as they need. Otherwise i'd have to modify a lib inserting watchdog feeds (if it's possible at all)

[igrr]

I meant something like this:

void setup() {
  wdt_disable();
 /// some initialization
  ThirdPartyLibrary.begin();
/// more stuff
  wdt_enable();
}

Would that work?

What exactly is this library doing, by the way? I have added workarounds for some of the common usage patterns like while (!wifiClient.available()){} which detect such blocking loops and call yield() internally.

[Sermus]

it's ILI9341 lib and it fills the screen black in quite a longy way.
What is the issue with nesting setup() call in these wdt_disable()/wdt_enable(), except not working WDT itself?

[tomaja]

delay() doesn't seem enough. I probably have more than 1s in between two delay calls.
Yes, your proposition looks good (adding wdt_enable and wdt_disable).
Can you add those two functions?

Thanks!

[anteph]

It would also be usefull to have a function to set the wtd reset time!
Thanks!

[tomaja]

@igrr Do you think this feature will be added?

void setup() {
  wdt_disable();
  /// some initialization
  ThirdPartyLibrary.begin();
  /// more stuff
  wdt_enable();
}

[igrr]

@tomaja Added WDT APIs: ESP.wdtEnable(), ESP.wdtDisable(), ESP.wdtFeed().
You can either grab the latest version from git, or download the full .zip when it is ready from https://ci.appveyor.com/project/igrr/Arduino/build/artifacts

[tomaja]

Great! Thanks, @igrr !
I just built Mac version from source and I checked that I can use ESP.wdtDisable() - script compiles just fine.
My Prolific USB to Serial stopped working after OSX update this morning so I'm unable to flash the new image to ESP8266 until I resolve that. I'll let you know how it works.

[igrr]

@tomaja I have also installed the Yosemite update today and had to reinstall the FTDI driver to make serial uploads work. I suppose the driver got replaced by Apple's version during the upgrade.

Edit: ignore this, you're using Prolific not FTDI...