ESP8266 Community Forum

- Sat Nov 04, 2017 12:07 pm #71528 Hi there,


I was tracing some wdt reset events by using the ESP exception decoder tool, and the first occurence were at the esp8266_wiring_digital.c local file at line 116, whose instructions are slightly shifted from the up to date version of this file. I suspected of some indexing issue, but it was not the case; there are indded minnor differences on my local file and the one at the official webpage, commited less than 2 months ago:

https://github.com/esp8266/Arduino/blob ... _digital.c

Interestingly, the last change seems having fixed the issue that I'm facing to ( mask GPIO interrupts while attaching/detaching ISR handler ), once those wdt resets started to happen after I have added an I/O interruption on my code, which were apparently being called reentrantly.

But, I did everything that is shown at https://github.com/esp8266/Arduino webpage, I have added the following parameter into sub-menu Additional Board Manager URLs field. Once I have added this URL many months ago, I presume that the IDE have downloaded the actual version just once, perhaps the reason of not reflecting the last version.

http://arduino.esp8266.com/stable/packa ... index.json

Am I missing some thing on that, or I have to force some updating ?

"part of the world that you live in, you are the part that you're giving" - Renaissance

- Sat Nov 04, 2017 1:46 pm #71533

Hi there,


I was tracing some wdt reset events by using the ESP exception decoder tool, and the first occurence were at the esp8266_wiring_digital.c local file at line 116, whose instructions are slightly shifted from the up to date version of this file. I suspected of some indexing issue, but it was not the case; there are indded minnor differences on my local file and the one at the official webpage, commited less than 2 months ago:

https://github.com/esp8266/Arduino/blob ... _digital.c

Interestingly, the last change seems having fixed the issue that I'm facing to ( mask GPIO interrupts while attaching/detaching ISR handler ), once those wdt resets started to happen after I have added an I/O interruption on my code, which were apparently being called reentrantly.

But, I did everything that is shown at https://github.com/esp8266/Arduino webpage, I have added the following parameter into sub-menu Additional Board Manager URLs field. Once I have added this URL many months ago, I presume that the IDE have downloaded the actual version just once, perhaps the reason of not reflecting the last version.

http://arduino.esp8266.com/stable/packa ... index.json

Am I missing some thing on that, or I have to force some updating ?

It only downloads the arduino core for the board when you ask it to. And rightly so, otherwise you would get potential updates/changes that you were unaware of. You have to download any new core (I.e. The stuff defined in the boards manager).

- Sat Nov 04, 2017 7:24 pm #71546

It only downloads the arduino core for the board when you ask it to. And rightly so, otherwise you would get potential updates/changes that you were unaware of. You have to download any new core (I.e. The stuff defined in the boards manager).

But the Arduino board manager indicates that ESP8266 core is updated to the last version.
Sorry if I did not undertand, but could you elaborate a bit ?

"part of the world that you live in, you are the part that you're giving" - Renaissance

- Sat Nov 04, 2017 8:13 pm #71548 http://arduino.esp8266.com/stable/packa ... index.json is the latest release. But it is more than a year old.

There were other options before. Newer than release, I forget what it was called. Stable but not 100%. And then there was GIT. And that I believe was what was the latest development copy. What was available at that moment in time.

If you want to see what releases versions (not git) then look at the release folder.
https://github.com/esp8266/Arduino/releases

I am now running 2.4.0-rc2. It is pre-release. But for quite a while I was using git because I needed some of the changes that were made not yet released.

What I have said is what I understand to be how it is, and it might not be 100% correct.

Some of the problems are the number of issues and the required testing, the lack of resources.
viewtopic.php?f=31&t=12000