-->
Page 1 of 2

Suspected stuck in FIRST STAGE bootloader

PostPosted: Sun Oct 21, 2018 4:07 am
by Eli Lurie
Hi
1. We have a board with ESP8266 chip that is connected on a battery
2. We suspect that the first stage bootloader is stuck once in few hundreds of times without loading the eboot (Arduino framework) from flash
3. We have verified that GPIO15 is connected to GND with 10Kohm resistor and GPIO0 and GPIO2 are connected to 3.3V via 10Kohm
4. Is anyone familiar with such a phenomena
5. If positive is there any workaround?
Best Regards

Re: Suspected stuck in FIRST STAGE bootloader

PostPosted: Mon Oct 22, 2018 10:48 am
by AcmeUK
Have you looked at the 74880 baud messages from the boot loader to see what the error code is?

Re: Suspected stuck in FIRST STAGE bootloader

PostPosted: Mon Oct 22, 2018 1:08 pm
by Eli Lurie
Thank you for respond
1. We cant monitor the messages of bootloader at 74880 because the hang happens occasionally not in all our units and the units are installed at our client premises
2. The hang happens occasionally once in many days and not on all units
3. However, we added a code to the Serial library that writes every output byte from Serial to log file on SPIFF. The log file is size limited and we restart it after it reaches some maximum size.
Unfortunately, this library does not handle the display of the serial output from first stage
bootloader or from eboot so we have a dump only from our application sketch.
4. By looking at the log after the unit was hung we have verified that the stuck does not happen in our application and we have assumed that it happens in the bootloader. (no other choices)
5. If it helps the logic of our application is: Wake up every hour, read some data from I2C, send the data to the server, go to sleep for 3600 sec
Thanks

Re: Suspected stuck in FIRST STAGE bootloader

PostPosted: Mon Oct 22, 2018 5:52 pm
by AcmeUK
You do not say if you are using the Arduino IDE or the ESP8266 SDK.

From your description it sounds as if you are having problems when the device awakes from a deep sleep, not on booting.

As the problem happens after a few days, and presumably is cleared by a power down rest, have you tried to do a restart from within the program say every 24 hours.

This may give a work around for your customer until you can identify the problem.