v1.2.0 to match new ESP8266 core v3.0.0

### Releases v1.2.0

1. Update to match new ESP8266 core v3.0.0

Author: khoih-prog

CONTRIBUTING.md

@@ -15,7 +15,7 @@ If you don't find anything, please [open a new issue](https://github.com/khoih-p
 Please ensure to specify the following:
 
 * Arduino IDE version (e.g. 1.8.13) or Platform.io version
-* `ESP8266` Core Version (e.g. ESP8266 core v2.7.4)
+* `ESP8266` Core Version (e.g. ESP8266 core v3.0.0)
 * Contextual information (e.g. what you were trying to achieve)
 * Simplest possible steps to reproduce
 * Anything that might be relevant in your opinion, such as:
@@ -27,9 +27,9 @@ Please ensure to specify the following:
 
 ```
 Arduino IDE version: 1.8.13
-ESP8266 Core Version 2.7.4
+ESP8266 Core Version v3.0.0
 OS: Ubuntu 20.04 LTS
-Linux Inspiron 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
+Linux Inspiron 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
 
 Context:
 I encountered a crash while trying to use the Timer Interrupt.

README.md

@@ -16,6 +16,7 @@
   * [Important Notes about using ISR](#important-notes-about-using-isr)
   * [Currently supported Boards](#currently-supported-boards)
 * [Changelog](#changelog)
+  * [Releases v1.2.0](#releases-v120)
   * [Releases v1.1.0](#releases-v110)
   * [Releases v1.0.2](#releases-v102)
   * [Releases v1.0.1](#releases-v101)
@@ -100,6 +101,10 @@ This [**ESP8266_ISR_Servo** library](https://github.com/khoih-prog/ESP8266_ISR_S
 
 ## Changelog
 
+### Releases v1.2.0
+
+1. Update to match new ESP8266 core v3.0.0
+
 ### Releases v1.1.0
 
 1. Fix bug. See [Fixed count >= min comparison for servo enable](https://github.com/khoih-prog/ESP32_ISR_Servo/pull/1)
@@ -124,7 +129,9 @@ This [**ESP8266_ISR_Servo** library](https://github.com/khoih-prog/ESP8266_ISR_S
 ## Prerequisites
 
 1. [`Arduino IDE 1.8.13+`](https://www.arduino.cc/en/Main/Software)
-2. [`ESP8266 core 2.7.4+`](https://github.com/esp8266/Arduino#installing-with-boards-manager) for ESP8266 boards.
+2. [`ESP8266 Core 3.0.0+`](https://github.com/esp8266/Arduino) for ESP8266-based boards. [![Latest release](https://img.shields.io/github/release/esp8266/Arduino.svg)](https://github.com/esp8266/Arduino/releases/latest/). To use ESP8266 core 2.7.1+ for LittleFS. 
+3. [`Blynk_WM library v1.5.0+`](https://github.com/khoih-prog/Blynk_WM) to use with some examples. To install. check [![arduino-library-badge](https://www.ardu-badge.com/badge/Blynk_WM.svg?)](https://www.ardu-badge.com/Blynk_WM).
+4. [`ESP_DoubleResetDetector library v1.1.1+`](https://github.com/khoih-prog/ESP_DoubleResetDetector) to use with some examples. To install. check [![arduino-library-badge](https://www.ardu-badge.com/badge/ESP_DoubleResetDetector.svg?)](https://www.ardu-badge.com/ESP_DoubleResetDetector).
 
 ---
 
@@ -459,10 +466,10 @@ void loop()
 
 
 ```
-Starting ESP8266_BlynkServoControl using LITTLEFS with SSL on ESP8266_NODEMCU
-Blynk_WM v1.1.0
+Starting ESP8266_BlynkServoControl using LITTLEFS with SSL on ESP8266_NODEMCU_ESP12E
+Blynk_WM v1.5.0
 ESP_DoubleResetDetector v1.1.1
-ESP8266_ISR_Servo v1.1.0
+ESP8266_ISR_Servo v1.2.0
 [290] Hostname=8266-Master-Controller
 [309] LoadCfgFile 
 [309] OK
@@ -487,7 +494,7 @@ ESP8266_ISR_Servo v1.1.0
    / _ )/ /_ _____  / /__
   / _  / / // / _ \/  '_/
  /____/_/\_, /_//_/_/\_\
-        /___/ v0.6.1 on NodeMCU
+        /___/ v0.6.1 on ESP8266_NODEMCU_ESP12E
 
 [22618] NTP time: Sun Jan  3 07:08:22 2021
 [22619] BlynkArduinoClient.connect: Connecting to account.duckdns.org:9443
@@ -503,11 +510,11 @@ Setup Servo3 OK
 ```
 ---
 
-### 2. ESP8266_MultipleRandomServos on ESP8266_NODEMCU
+### 2. ESP8266_MultipleRandomServos on ESP8266_NODEMCU_ESP12E
 
 ```
-Starting ESP8266_MultipleRandomServos on ESP8266_NODEMCU
-ESP8266_ISR_Servo v1.1.0
+Starting ESP8266_MultipleRandomServos on ESP8266_NODEMCU_ESP12E
+ESP8266_ISR_Servo v1.2.0
 [ISR_SERVO] ESP8266FastTimerInterrupt: _fre = 5000000.00 , _count = 50
 [ISR_SERVO] Starting  ITimer OK
 Setup OK Servo index = 0
@@ -606,12 +613,12 @@ Servos idx = 5, act. pos. (deg) = [ISR_SERVO] Idx = 5
 
 ---
 
-### 3. ESP8266_ISR_MultiServos on ESP8266_NODEMCU
+### 3. ESP8266_ISR_MultiServos on ESP8266_NODEMCU_ESP12E
 
 
 ```
-Starting ESP8266_ISR_MultiServos on ESP8266_NODEMCU
-ESP8266_ISR_Servo v1.1.0
+Starting ESP8266_ISR_MultiServos on ESP8266_NODEMCU_ESP12E
+ESP8266_ISR_Servo v1.2.0
 [ISR_SERVO] ESP8266FastTimerInterrupt: _fre = 5000000.00 , _count = 50
 [ISR_SERVO] Starting  ITimer OK
 Setup Servo1 OK
@@ -678,6 +685,10 @@ Sometimes, the library will only work if you update the board core to the latest
 
 ## Releases
 
+### Releases v1.2.0
+
+1. Update to match new ESP8266 core v3.0.0
+
 ### Releases v1.1.0
 
 1. Fix bug. See [Fixed count >= min comparison for servo enable](https://github.com/khoih-prog/ESP32_ISR_Servo/pull/1)
@@ -716,6 +727,7 @@ Submit issues to: [ESP8266_ISR_Servo issues](https://github.com/khoih-prog/ESP82
 2. Add functions `getPosition()` and `getPulseWidth()`
 3. Optimize the code
 4. Add more complicated examples
+5. Update to match new ESP8266 core v3.0.0
 
 ---
 ---

examples/ESP8266_BlynkServoControl/Credentials.h

@@ -25,20 +25,11 @@
   if the interrupt changes a multi-byte variable between a sequence of instructions, it can be read incorrectly.
   If your data is multiple variables, such as an array and a count, usually interrupts need to be disabled
   or the entire sequence of your code which accesses the data.
-  
-  Version: 1.1.0
-  
+
   The ESP8266 timers are badly designed, using only 23-bit counter along with maximum 256 prescaler. They're only better than UNO / Mega.
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
-  Version Modified By   Date      Comments
-  ------- -----------  ---------- -----------
-  1.0.0   K Hoang      04/12/2019 Initial coding
-  1.0.1   K Hoang      05/12/2019 Add more features getPosition and getPulseWidth. Optimize.
-  1.0.2   K Hoang      20/12/2019 Add more Blynk examples.Change example names to avoid duplication.
-  1.1.0   K Hoang      03/01/2021 Fix bug. Add TOC and Version String.
  *****************************************************************************************************************************/
 
 #ifndef Credentials_h

examples/ESP8266_BlynkServoControl/ESP8266_BlynkServoControl.ino

@@ -10,35 +10,33 @@
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
-  Now these new 16 ISR-based PWM servo contro uses only 1 hardware timer.
+
+  Now with these new 16 ISR-based timers, the maximum interval is practically unlimited (limited only by unsigned long miliseconds)
   The accuracy is nearly perfect compared to software timers. The most important feature is they're ISR-based timers
   Therefore, their executions are not blocked by bad-behaving functions / tasks.
   This important feature is absolutely necessary for mission-critical tasks.
-  
-  Notes:
-  Special design is necessary to share data between interrupt code and the rest of your program.
-  Variables usually need to be "volatile" types. Volatile tells the compiler to avoid optimizations that assume
-  variable can not spontaneously change. Because your function may change variables while your program is using them,
-  the compiler needs this hint. But volatile alone is often not enough.
-  When accessing shared variables, usually interrupts must be disabled. Even with volatile,
-  if the interrupt changes a multi-byte variable between a sequence of instructions, it can be read incorrectly.
-  If your data is multiple variables, such as an array and a count, usually interrupts need to be disabled
-  or the entire sequence of your code which accesses the data.
-  
-  Version: 1.1.0
+
+  Loosely based on SimpleTimer - A timer library for Arduino.
+  Author: [email protected]
+  Copyright (c) 2010 OTTOTECNICA Italy
+
+  Based on BlynkTimer.h
+  Author: Volodymyr Shymanskyy
   
   The ESP8266 timers are badly designed, using only 23-bit counter along with maximum 256 prescaler. They're only better than UNO / Mega.
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
+
+  Version: 1.2.0
+
   Version Modified By   Date      Comments
   ------- -----------  ---------- -----------
   1.0.0   K Hoang      04/12/2019 Initial coding
   1.0.1   K Hoang      05/12/2019 Add more features getPosition and getPulseWidth. Optimize.
   1.0.2   K Hoang      20/12/2019 Add more Blynk examples.Change example names to avoid duplication.
   1.1.0   K Hoang      03/01/2021 Fix bug. Add TOC and Version String.
+  1.2.0   K Hoang      18/05/2021 Update to match new ESP8266 core v3.0.0
  *****************************************************************************************************************************/
 
 /****************************************************************************************************************************

examples/ESP8266_BlynkServoControl/defines.h

@@ -26,19 +26,10 @@
   If your data is multiple variables, such as an array and a count, usually interrupts need to be disabled
   or the entire sequence of your code which accesses the data.
   
-  Version: 1.1.0
-  
   The ESP8266 timers are badly designed, using only 23-bit counter along with maximum 256 prescaler. They're only better than UNO / Mega.
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
-  Version Modified By   Date      Comments
-  ------- -----------  ---------- -----------
-  1.0.0   K Hoang      04/12/2019 Initial coding
-  1.0.1   K Hoang      05/12/2019 Add more features getPosition and getPulseWidth. Optimize.
-  1.0.2   K Hoang      20/12/2019 Add more Blynk examples.Change example names to avoid duplication.
-  1.1.0   K Hoang      03/01/2021 Fix bug. Add TOC and Version String.
  *****************************************************************************************************************************/
 
 #ifndef defines_h
@@ -90,8 +81,8 @@
 #define CONFIG_TIMEOUT_RETRYTIMES_BEFORE_RESET    5
 // Those above #define's must be placed before #include <BlynkSimpleEsp8266_WM.h>
 
-#define USE_SSL   true
-//#define USE_SSL   false
+//#define USE_SSL   true
+#define USE_SSL   false
 
 #if USE_SSL
 #include <BlynkSimpleEsp8266_SSL_WM.h>

examples/ESP8266_BlynkServoControl/dynamicParams.h

@@ -26,19 +26,10 @@
   If your data is multiple variables, such as an array and a count, usually interrupts need to be disabled
   or the entire sequence of your code which accesses the data.
   
-  Version: 1.1.0
-  
   The ESP8266 timers are badly designed, using only 23-bit counter along with maximum 256 prescaler. They're only better than UNO / Mega.
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
-  Version Modified By   Date      Comments
-  ------- -----------  ---------- -----------
-  1.0.0   K Hoang      04/12/2019 Initial coding
-  1.0.1   K Hoang      05/12/2019 Add more features getPosition and getPulseWidth. Optimize.
-  1.0.2   K Hoang      20/12/2019 Add more Blynk examples.Change example names to avoid duplication.
-  1.1.0   K Hoang      03/01/2021 Fix bug. Add TOC and Version String.
  *****************************************************************************************************************************/
 
 #ifndef dynamicParams_h

examples/ESP8266_ISR_MultiServos/ESP8266_ISR_MultiServos.ino

@@ -10,35 +10,33 @@
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
-  Now these new 16 ISR-based PWM servo contro uses only 1 hardware timer.
+
+  Now with these new 16 ISR-based timers, the maximum interval is practically unlimited (limited only by unsigned long miliseconds)
   The accuracy is nearly perfect compared to software timers. The most important feature is they're ISR-based timers
   Therefore, their executions are not blocked by bad-behaving functions / tasks.
   This important feature is absolutely necessary for mission-critical tasks.
-  
-  Notes:
-  Special design is necessary to share data between interrupt code and the rest of your program.
-  Variables usually need to be "volatile" types. Volatile tells the compiler to avoid optimizations that assume
-  variable can not spontaneously change. Because your function may change variables while your program is using them,
-  the compiler needs this hint. But volatile alone is often not enough.
-  When accessing shared variables, usually interrupts must be disabled. Even with volatile,
-  if the interrupt changes a multi-byte variable between a sequence of instructions, it can be read incorrectly.
-  If your data is multiple variables, such as an array and a count, usually interrupts need to be disabled
-  or the entire sequence of your code which accesses the data.
-  
-  Version: 1.1.0
+
+  Loosely based on SimpleTimer - A timer library for Arduino.
+  Author: [email protected]
+  Copyright (c) 2010 OTTOTECNICA Italy
+
+  Based on BlynkTimer.h
+  Author: Volodymyr Shymanskyy
   
   The ESP8266 timers are badly designed, using only 23-bit counter along with maximum 256 prescaler. They're only better than UNO / Mega.
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
+
+  Version: 1.2.0
+
   Version Modified By   Date      Comments
   ------- -----------  ---------- -----------
   1.0.0   K Hoang      04/12/2019 Initial coding
   1.0.1   K Hoang      05/12/2019 Add more features getPosition and getPulseWidth. Optimize.
   1.0.2   K Hoang      20/12/2019 Add more Blynk examples.Change example names to avoid duplication.
   1.1.0   K Hoang      03/01/2021 Fix bug. Add TOC and Version String.
+  1.2.0   K Hoang      18/05/2021 Update to match new ESP8266 core v3.0.0
  *****************************************************************************************************************************/
 
 /****************************************************************************************************************************

examples/ESP8266_MultipleRandomServos/ESP8266_MultipleRandomServos.ino

@@ -10,35 +10,33 @@
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
-  Now these new 16 ISR-based PWM servo contro uses only 1 hardware timer.
+
+  Now with these new 16 ISR-based timers, the maximum interval is practically unlimited (limited only by unsigned long miliseconds)
   The accuracy is nearly perfect compared to software timers. The most important feature is they're ISR-based timers
   Therefore, their executions are not blocked by bad-behaving functions / tasks.
   This important feature is absolutely necessary for mission-critical tasks.
-  
-  Notes:
-  Special design is necessary to share data between interrupt code and the rest of your program.
-  Variables usually need to be "volatile" types. Volatile tells the compiler to avoid optimizations that assume
-  variable can not spontaneously change. Because your function may change variables while your program is using them,
-  the compiler needs this hint. But volatile alone is often not enough.
-  When accessing shared variables, usually interrupts must be disabled. Even with volatile,
-  if the interrupt changes a multi-byte variable between a sequence of instructions, it can be read incorrectly.
-  If your data is multiple variables, such as an array and a count, usually interrupts need to be disabled
-  or the entire sequence of your code which accesses the data.
-  
-  Version: 1.1.0
+
+  Loosely based on SimpleTimer - A timer library for Arduino.
+  Author: [email protected]
+  Copyright (c) 2010 OTTOTECNICA Italy
+
+  Based on BlynkTimer.h
+  Author: Volodymyr Shymanskyy
   
   The ESP8266 timers are badly designed, using only 23-bit counter along with maximum 256 prescaler. They're only better than UNO / Mega.
   The ESP8266 has two hardware timers, but timer0 has been used for WiFi and it's not advisable to use. Only timer1 is available.
   The timer1's 23-bit counter terribly can count only up to 8,388,607. So the timer1 maximum interval is very short.
   Using 256 prescaler, maximum timer1 interval is only 26.843542 seconds !!!
-  
+
+  Version: 1.2.0
+
   Version Modified By   Date      Comments
   ------- -----------  ---------- -----------
   1.0.0   K Hoang      04/12/2019 Initial coding
   1.0.1   K Hoang      05/12/2019 Add more features getPosition and getPulseWidth. Optimize.
   1.0.2   K Hoang      20/12/2019 Add more Blynk examples.Change example names to avoid duplication.
   1.1.0   K Hoang      03/01/2021 Fix bug. Add TOC and Version String.
+  1.2.0   K Hoang      18/05/2021 Update to match new ESP8266 core v3.0.0
  *****************************************************************************************************************************/
 
 /****************************************************************************************************************************