SpacehuhnTech/esp8266_deauther

NodeMCU 1.0 bootlooping problem

Open

#1688 opened on Jan 19, 2024

View on GitHub
 (3 comments) (1 reaction) (0 assignees)C (14,772 stars) (2,758 forks)batch import
help wanted

Description

Have you searched for existing (open and closed) issues describing the same problem?

Yes, but there wasn't anyone with the same problem.

Describe the error The ESP8266 resets every ~8 seconds. I don't know whats causing the problem. Down is the console output (from https://serial.huhn.me/)

 ets Jan  8 2013,rst cause:4, boot mode:(3,4)



wdt reset

load 0x4010f000, len 3584, room 16 

tail 0

chksum 0xb0

csum 0xb0

v2843a5ac

~ld



Mounting SPIFFS...OK

Loading settings...OK

Device names loaded from /names.json

SSIDs loaded from /ssids.json

Scan results saved in /scan.json

Serial interface enabled

Started AP

[WiFi] Path: '/web', Mode: 'AP', SSID: 'pwned', password: 'deauther', channel: '1', hidden: false, captive-portal: false

STARTED! \o/

2.6.1

To Reproduce Steps to reproduce the behavior:

  1. Plug it into your computer
  2. Go into the console
  3. See error

Expected behavior Expected it to not bootloop

Environment (please complete the following information):

  • OS: Windows 10
  • Browser: Chrome
  • Hardware: DIY

Attempts Reflashing the software a couple of times, searching the error.

Additional context Used the bin file and the https://esp.huhn.me/ website for flashing the esp

Contributor guide

Tech stack
c
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
ESP8266 experienceC programmingdebugging firmware
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the watchdog timer (WDT) reset indicated by 'wdt reset' and boot mode (3,4). Examine the firmware's main loop and potential infinite loops or memory corruption, focusing on SPIFFS mounting and settings loading. Check the repository's source files for known issues with boot loops. Since the problem may be hardware specific or related to specific flash settings, reproducing it on different ESP8266 modules could help isolate the cause.