ESP8285 Development Board

[kriswiner]

Please fill the info fields, it helps to get you faster support ;)

if you have a stack dump decode it:
https://github.com/esp8266/Arduino/blob/master/doc/Troubleshooting/stack_dump.md

for better debug messages:
https://github.com/esp8266/Arduino/blob/master/doc/Troubleshooting/debugging.md

----------------------------- Remove above -----------------------------

Basic Infos

Hardware

Hardware: ?ESP-12?
Core Version: ?2.1.0-rc2?

Description

Problem description

Settings in IDE

Module: ?Generic ESP8266 Module?
Flash Size: ?4MB/1MB?
CPU Frequency: ?80Mhz?
Flash Mode: ?qio?
Flash Frequency: ?40Mhz?
Upload Using: ?OTA / SERIAL?
Reset Method: ?ck / nodemcu?

Sketch

#include <Arduino.h>

void setup() {

}

void loop() {

}

Debug Messages

messages here

Just want to confirm that I exposed pins 9 and 10 on my ESP8285 Development Board (https://www.tindie.com/products/onehorse/esp8285-development-board/) and was able to use either one to blink an led or serve as an interrupt from a sensor, etc. I will do more testing but it seems these two pins are indeed available GPIOs. Not sure if they come with a special function; the ESP82XX seems to have an internal MUX to allow any pin to express the available peripherals.

How can I arrange to have my ESP8285 Development Board included in the list of available boards?

[igrr]

Which reset method do you use, ck or nodemcu? We have an ESP8285 entry in the list already, does it work with your board?

[kriswiner]

I use ck; if you have an ESP8285 Dev Board already listed you don't need
mine I suppose.

-----Original Message-----
From: Ivan Grokhotkov [mailto:notifications@github.com]
Sent: July 10, 2016 4:11 PM
To: esp8266/Arduino
Cc: Kris Winer; Author
Subject: Re: [esp8266/Arduino] ESP8285 Development Board (#2257)

Which reset method do you use, ck or nodemcu? We have an ESP8285 entry in
the list already, does it work with your board?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2257 (comment) , or
mute the thread
<https://github.com/notifications/unsubscribe/AGY1qsAqOUQU2lMT3jyHq-z12Np_k5
W0ks5qUXvpgaJpZM4JI78Y> .
<https://github.com/notifications/beacon/AGY1qkpcO2NjV9p32Uat1H-ZMf3ziI-7ks5
qUXvpgaJpZM4JI78Y.gif>

[ghost]

Hi!
I have modelu ESP8285 WEMOS? D1 mini, but need Reset Method: nodemcu. How do it this? In Arduino only ck method.

[kriswiner]

No idea... maybe ask the guy you bought it from?

…

On Mon, Sep 18, 2017 at 4:35 PM, Oleg Perevyshin ***@***.***> wrote: Hi! I have modelu ESP8285 WEMOS? D1 mini, but need Reset Method: nodemcu. How do it this? In Arduino only ck method. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2257 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGY1qsetV9VXBT2TIazfCDfjAESbovGYks5sjv4ugaJpZM4JI78Y> .

[ghost]

I figured out how to fix the problem!
You must change the settings in the file boards.txt. The file is on the path (for Windows)
C: \ Users \ *** \ AppData \ Local \ Arduino15 \ packages \ esp8266 \ hardware \ esp8266 \ 2.3.0
It is necessary to add a reset method in the corresponding section.

I'm in the Generic ESP8285 module add:

esp8285.menu.ResetMethod.ck = ck
esp8285.menu.ResetMethod.ck.upload.resetmethod = ck
esp8285.menu.ResetMethod.nodemcu = nodemcu
esp8285.menu.ResetMethod.nodemcu.upload.resetmethod = Nodem

[devyte]

@kriswiner said:
or serve as an interrupt from a sensor

Did you actually test that interrupts work on these pins? Ref: #3549

[kriswiner]

Which pins? I have used interrupts on most of the pins on the ESP8266/85, yes.

…

On Sat, Oct 14, 2017 at 10:04 PM, Develo ***@***.***> wrote: @kriswiner <https://github.com/kriswiner> said: or serve as an interrupt from a sensor Did you actually test that interrupts work on these pins? Ref: #3549 <#3549> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2257 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGY1qtjgW-_jfJs7OktxSdkTDf_lEWrmks5ssZJAgaJpZM4JI78Y> .

[devyte]

Your issue is about pins 9 and 10.

[kriswiner]

Yes, I have used interrupts on pins 9 and 10.

…

On Sun, Oct 15, 2017 at 8:55 AM, Develo ***@***.***> wrote: Your issue is about pins 9 and 10. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2257 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGY1qiuMmlcgckZyWjjAJ0pG-0xC_-aZks5ssir4gaJpZM4JI78Y> .

[devyte]

Those pins are usually not ready for interrupts. How did you init them? I ask because of #3549 .

[kriswiner]

Nothing special, they work just fine. Not sure what your problems is. What ESP8285 board are you using?

…

On Sun, Oct 15, 2017 at 9:01 AM, Develo ***@***.***> wrote: Those pins are usually not ready for interrupts. How did you init them? I ask because of #3549 <#3549> . — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2257 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGY1qtQUIBAT0MqYMxkFFbiLCyWjTsUQks5ssixbgaJpZM4JI78Y> .

[devyte]

@kriswiner not my problem (I don't use the 8285 board), but what was reported in #3549 . It was reported there that pins 9 and 10 didn't work with interrupts, and looking at the pin init code in our core, they are in fact not even initialized as input on startup.1
Hence, I wondered how you got them to work.

[devyte]

@kriswiner your original request seems to be to just make sure a board is added in boards.txt, except that this is a variant that has pins 9 & 10 available in addition to the others. Is this correct?

[kriswiner]

Yes, and the board was added months ago so safe to close this issue.

…

On Wed, Jan 10, 2018 at 1:06 PM, Develo ***@***.***> wrote: @kriswiner <https://github.com/kriswiner> your original request seems to be to just make sure a board is added in boards.txt, except that this is a variant that has pins 9 & 10 available in addition to the others. Is this correct? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2257 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGY1qrVwNYDAFA33DZIJMZX6Z9OtJHKgks5tJSZHgaJpZM4JI78Y> .

[devyte]

Awesome. Closing.