ESP8266 Community Forum

- Sat Apr 11, 2015 7:48 am #14170 Good. I mean good to know I am not alone - bad for you

I will keep playing with the hardware, so far I added pull-ups (10k) everywhere possible but this did not help. Tried different power sources - no beef. Different voltages - same.

Good luck

- Sat Apr 11, 2015 5:38 pm #14224

Good. I mean good to know I am not alone - bad for you

I will keep playing with the hardware, so far I added pull-ups (10k) everywhere possible but this did not help. Tried different power sources - no beef. Different voltages - same.

Good luck

Moin,

is that you here? http://forum.makehackvoid.com/t/esp8266 ... ent/286/29
Looks like you did a lot of experiments.

I would like to separate hardware issues from software issues. Your experiments seems to indicate
caps may improve stability. What are your current findings/thoughts? I think to add a 100n + 470u combo
just to rule out hardware a little more.
I was able to change exception 29 to exception 0 by intercepting call to call of pm (power management?)
related function. But I don't think that gets us any further.
I try to make my mind how much of the exception info is real and what is garbage.
You need the app/mapfile to find out what function the exception pc is related to.
I try to collect information what functions are involved when exceptions pop up in startup/deep sleep
scenarios. All my values point to the function mentioned above.

Carsten

Get your modules here:

https://www.banggood.com/custlink/KvGGhGF4wG

- Sun Apr 12, 2015 6:27 am #14268 I did add caps on the power strip (100n+470u) but I still get the exceptions.

I have a few modules. The two fully configured modules (a nodeMCU board and a dev kit http://www.aliexpress.com/item/-/32242633472.html) seem very stable. This is why I think that there is a "right" way to set up the hardware to make it stable.

An esp-01 fails less (not much one can do to it) but the esp-07 and esp-201 (that have many pins to set up) fail rather regularly. The -07 is the worst right now, but I did have go for over a month a while back (I wish I knew what was different then, but I needed to update my app).

Software wise I run with SDK v1.0.1b1 and my own built noidemcu-firmware. The only change is an added module for access to the RTC memory.

If anyone has any suggestions, or an idea to try, do let me know.

[edit] should mention that replacing the dsleep with restart still fails in the same way.

- Tue Apr 14, 2015 4:30 pm #14518

I did add caps on the power strip (100n+470u) but I still get the exceptions.

If anyone has any suggestions, or an idea to try, do let me know.

[edit] should mention that replacing the dsleep with restart still fails in the same way.

Moin,

can you please note the number of the exception, the epc1 value and lookup the next lowest value to the epc1 in the app/mapfile of the firmware you run?
That is the function where the exception was thrown.
And the other values of the exception message maybe useful, too

Carsten

Get your modules here:

https://www.banggood.com/custlink/KvGGhGF4wG