Chat about current Lua tools and IDEs

User avatar
By timg11
#77752 I have a D1 Mini that had been working fine. After uploading a small change to a file, it would not boot.

The serial output at 74880 baud is simply this:
Code: Select all ets Jan  8 2013,rst cause:2, boot mode:(3,6)


After that no response.

I tried to re-flash NodeMCI with PyFlasher.
It shows this output
Code: Select allConnecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0x0, SizeID=0x0), defaulting to 4MB
Flash params set to 0x0240
Compressed 410448 bytes to 264293...


After that nothing.

If I select "Erase Flash" the last status reported is
Code: Select allErasing flash (this may take a while)...


I've let it sit for hours, and it never proceeds beyond that message.

What is the next step to resolve?
User avatar
By timg11
#77753 I tried power up while holding down the reset button.

Now the serial console gets this text repeated continually:

Code: Select all ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 26356, room 16
tail 4
chksum 0x0b
load 0x3ffe8000, len 2192, room 4
tail 12
chksum 0x1f
ho 0 tail 12 room 4
load 0x3ffe8890, len 136, room 12
tail 12
chksum 0x09
csum 0x09
rf_cal[0] !=0x05,is 0x00



Where can I learn of the interpretation of these messages?
User avatar
By timg11
#77754 I disconnected my analog input from the A0 pin, and now the D1 board will flash and boot into NodeMCU.

The module has a 220K/100K voltage divider from the A0 input to the ADC pin. I had a 100K pot connected between 3.3V and ground, with the wiper going to A0.

From my reading of ESP8266 boot modes, the ADC input is not one that affects booting, so I'm puzzled why having it connected affects booting.

Has anyone seen this behavior, or know why it might occur?