Hi, please do someone knows if is it possible to read the logs -after- a crash?
every 3 or four days my espeasy locks, with the red led blinking fast (4 lamps per second at least), unit not reachable on it's IP, the only way is to switch off.
I've some device connected:
I2C with PCF 8574 to read I/O
MQTT to communicate with Home assistant
and some native GPIO
After the reboot is it possible to read a log to debug the problem? wher can I find it?
thank you!
logs on board crash
Moderators: grovkillen, Stuntteam, TD-er
Re: logs on board crash
Can you check the checkbox on the tools->Advanced page next to "Try clear I2C bus when stuck:" and see if this may help here?
Also, not sure what build you're running, but maybe you can try one of the latest test builds: https://github.com/letscontrolit/ESPEas ... 3696900440
Also, not sure what build you're running, but maybe you can try one of the latest test builds: https://github.com/letscontrolit/ESPEas ... 3696900440
Re: logs on board crash
Ok, flagged
And what about the log?
And what about the log?
Re: logs on board crash
Only way to get some stack trace is when you connect the board via USB to the PC and collect the stack dump from the serial port.
Then you also need to have the .elf file and the source code of the built binary to interpret it.
But this is actually only practical when running the monitor function via the programming IDE and this is highly impractical for something that happens only every so many days.
Stack decoding from just the stack trace dump is hardly ever useful... sadly
Then you also need to have the .elf file and the source code of the built binary to interpret it.
But this is actually only practical when running the monitor function via the programming IDE and this is highly impractical for something that happens only every so many days.
Stack decoding from just the stack trace dump is hardly ever useful... sadly

Who is online
Users browsing this forum: No registered users and 13 guests