![]() My project translates over fine, except I'm having an issue with the Deep Sleep wakeup on the ESP-M3. Long version I have a little remote sensor project that I've been working on for a while using a Wemos D1 Mini, and I was hoping to downsize it to an ESP-M3/ESP8285. Does seem to work if I use my finger to touch one of the leads on the resistor I have between GPIO16 and RST. Serial.print(String("\nResetInfo.reason = ") (*rinfo).reason ": " ESP.Short version On an ESP-M3/ESP8285, connecting GPIO16 to RST is causing what appears to be rapid resets, instead of waking up after the set interval. I can cause a different boot mode by holding down the Bootloader button:Įts Jan 8 2013,rst cause:2, boot mode:(1,6) When it happens, I can hit reset and the code does not restart normally.Ī normal start from sleep looks like this:Įts Jan 8 2013,rst cause:2, boot mode:(3,6)īut now that the fail has occured, no matter what I do I just get a single boot line. I seem to be getting more fail conditions today. Great tips about using a default of 74880 baud. I allways default baud to 74880 to make this "garbage" and debug readable. I chose to ESP.deepSleep(941000000ul, RF_NO_CAL) on successful connection and ESP.deepSleep(931000000ul, RF_CAL) if there was a problem. I turn off wifi in setup and only after successful measurement enable wifi (all fixed IP parameters) and send to thingspeak, disconnecting and disabling wifi afterwards. It is realized with an esp-01, BME280 (i2c on gpio0,2) and a single LiFePO4 cell. This is solved now as one can choose wifi credentials to not be persistent.Īs you can see, I'm doing exactly what you described for about one year with recent downtimes only when it rained on my board (still breadboard on my windowsill), the battery ran down or thingspeak changed their api/IP. The problems I experienced were with defective flash caused by the repeated writing of wifi credentials at every reboot, leading to similar problems for the start and total fail after some more time. Unfortunately I can't give any specific hint to solve your problem allthough I remember this kind of symptom from the early days of esp arduino ide. Has anyone got any concrete suggestions that explain what I'm seeing, or what I can do about it? I've also tried adding a cap to the reset line, but it still fails. I've tried different restart connections (GPIO16-res) like a resistor and a diode. However, this was happening even back when I had the 1.5.6 version. I'm using the Arduino IDE and I just downloaded the latest Arduino 1.8, and the latest ESP core (3.0 as I recall). If I measure GPIO2, I see 1.8V which explains why the LED is lit I guess. If I hit reset, I just get the same burst of garbage. ![]() If I have the terminal attached I can see the typical garbage when the wake occurs, but nothing after that. This happens whether I have the terminal attached or not. In fact, the only way to get it out is to power it down. When the bad wake-up occurs, the RED LED is lit at half brightness (like in bootloader mode) but it won't load a program, AND pressing the reset button does NOT take it out of that state. This may happen after 10 minutes or 10 hours. My specific problem is that every now and then, when the 8266 wakes from it's deepsleep, instead of doing a restart, it goes into a mode that resembles the bootloader state, although it's not actually running the bootloader. ![]() So GPIO0
0 Comments
Leave a Reply. |