When I upload the template_esp8266 code provided, my serial moniter not displaying the proper things. But in the video provided by the blynk wifi network creates and it shows on the serial monitor. Why is that? I have mentioned the code showing on my serial monitor. Please help

load 0x4010f000, len 3456, room 16
tail 0
chksum 0x84
csum 0x84
[564] Hardware v1.0.0
[565] Firmware v1.0.1
ISR not in IRAM!

User exception (panic/abort/assert)
Abort called


ctx: cont
sp: 3ffffeb0 end: 3fffffc0 offset: 0000
3ffffeb0: 4020a15c 3ffef7c0 3ffffefd 0000000a
3ffffec0: 000000fe 00000000 00000000 00000000
3ffffed0: 00000000 00000000 00000000 00ff0000
3ffffee0: 5ffffe00 5ffffe00 3ffef484 00000000
3ffffef0: 00000003 00000000 3ffef7c0 4020cf5a
3fffff00: 4010057a 00028ece 4020934e 4020cf6c
3fffff10: 00000001 00000064 3ffef7c0 4020d4a5
3fffff20: 00000000 00000000 00000020 402020ee
3fffff30: 00000000 00000000 00000000 3ffef8f0
3fffff40: 3fffdad0 00000000 3ffef7c0 4020d554
3fffff50: 4020a15c 3ffef7c0 00000000 40201821
3fffff60: 3fffdad0 00000000 3ffef7c0 402021d4
3fffff70: 3fff0700 000f000f 80007620 2e302e00
3fffff80: 00010031 8000001c 00000000 4020d046
3fffff90: 3fffdad0 00000000 3ffef8b0 40202221
3fffffa0: feefeffe feefeffe feefeffe 4020cb68
3fffffb0: feefeffe feefeffe 3ffe8524 40100e99

ets Jan 8 2013,rst cause:2, boot mode:(3,6)````

This error is now generated by the more recent versions of the ESP core. The solution is to change line 19 on the ResetButton.h tab of the sketch from:

void button_change(void)


void ICACHE_RAM_ATTR button_change(void)


1 Like

Thank you sir. Now the wifi is showing but the serial monitor displays nothing.

Thank you sir. Everything is working now

I too was having the same problem.
Your fix did indeed resolve the Reset loop.
As a newbie to Blynk, I notice that the last update to the library was February 2019 - V0.6.1?
Is the library no longer getting updates and bug fixes?

The current version of Blynk is in “bugfix only” mode, as the developers are focusing on Blynk 2.0 development.
Technically, this is a bug, but as it’s easily fixable without any input from Blynk staff I doubt that it would warrant a new release of the entire library to fix it.
Having said that, I don’t know if it has actually been reported as a bug - I certainly haven’t.


I wasn’t aware of that.
18 months without a bug fix release helps me in my decision making whether to proceed or not.

There have been many bug fix releases to the Android and iPhone apps, but TBH the Blynk library hasn’t needed any - but they would no doubt have been issued if they were needed.