Board Not Responding
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- arduino, cpp
- Domain
- embedded-iot
Research direction
No repository file or test is identified. Start by reproducing the failure with the D1 mini Pro, Arduino IDE, and the Blink example, including the “Erase: All Flash Contents” option; done means identifying a reliable recovery or hardware cause and confirming the sketch continues working after reset and power cycling.
Written by the indexing model from the issue text.
Description
I have a D1 mini Pro that I purchased a few months ago, but the board recently stopped working.
When I plug in the board or press reset, the LED blinks to indicate the board is on, but nothing happens with the sketch. I have tried with the LOLIN and Arduino example sketches and not just my custom sketch.
If I upload a sketch, the upload works without error from the IDE (I am using the Arduino IDE) and the LED on the board blinks like normal during upload. However, after that nothing happens with the sketch.
Once or twice I have been able to get some response from the board by leaving it off for a few days and then uploading the "Blink" example sketch with the IDE option "Erase: All Flash Contents". The onboard LED will then blink according to the blink sketch pattern during the initial run. However as soon as I reset or power off the board, it stops working again.
Anyone have any idea what the problem is? Is there a way to reset something to make this board functional again? Thanks!
- Dominant language
- C++
- Stars
- 560
- Forks
- 226
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wemos/D1_mini_Examples
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
wemos/D1_mini_Examples#61 ·
-
w5100 y esp8266Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
wemos/D1_mini_Examples#60 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
wemos/D1_mini_Examples#59 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
wemos/D1_mini_Examples#58 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
wemos/D1_mini_Examples#57 · 2 comments ·
All issues in wemos/D1_mini_Examples
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
espressif/esp-matter#1867 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
cuAmpcorParameter.cpp (CPU pycuampcor) does not compile with libc++: EXIT_FAILURE is undeclaredOpen
Difficulty 1/5 Under an hour Newbie friendliness 92/100
isce-framework/isce3#387 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
conan-io/conan-center-index#31055 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day