run into a problem with WEMOS D1 and B4R Version 2.51
Same results if the WEMOS D1 is supply by external power or USB.
Uploading the a program let the LED blinking runs as expected.
Starting the AP or searching for networks does not work any longer. The AP of the WEMOS is not listed now.
Since that time the LOG shows garbage characters starting the application like this (blinking LED example)
(NOT possible to copy and paste the garbage characters as plain text)
Any idea what is going wrong?
Looking forward any hints
In the meantime I tried to get more information about this garbage characters.
It is something like
"ets Jan 8 2013,rst cause:4, boot mode: (3,0)"
I found out that the rst cause:4 is a watchdog reset.
http://espressif.com/sites/default/...uses_and_common_fatal_exception_causes_en.pdf
What could be the reason? Possible to take influence on the hardware watch dog?
I am using a ESP8266-12E on a WEMOS D1R1
looking forward any hints
Same results if the WEMOS D1 is supply by external power or USB.
Uploading the a program let the LED blinking runs as expected.
Starting the AP or searching for networks does not work any longer. The AP of the WEMOS is not listed now.
Since that time the LOG shows garbage characters starting the application like this (blinking LED example)
(NOT possible to copy and paste the garbage characters as plain text)
Any idea what is going wrong?
Looking forward any hints
In the meantime I tried to get more information about this garbage characters.
It is something like
"ets Jan 8 2013,rst cause:4, boot mode: (3,0)"
I found out that the rst cause:4 is a watchdog reset.
http://espressif.com/sites/default/...uses_and_common_fatal_exception_causes_en.pdf
What could be the reason? Possible to take influence on the hardware watch dog?
I am using a ESP8266-12E on a WEMOS D1R1
looking forward any hints
Last edited: