Page 2 of 2
Re: Debug / Trace Software / Hardware WDT
Posted:
Mon Apr 20, 2020 11:58 pmby Pablo2048
Oh, come on - for debugging such kind of errors there is EspSaveCrash library, which saves all the need information to the (simulated) EEPROM and can be lately used with Exception Decoder. There is also modification of this library for storing the info to SPIFFS. You can find it with simple Google search...
Re: Debug / Trace Software / Hardware WDT
Posted:
Tue Apr 21, 2020 7:31 amby martin010
@pablo2048,
Thank you for the nice comment.. EspSaveCrash does not help me, as I use the EEPROM.
I Did not know there was a SPIFFS version, so thank you for kindly pointing this out...
Re: Debug / Trace Software / Hardware WDT
Posted:
Tue Apr 21, 2020 9:21 amby Pablo2048
You use whole 4096 bytes of EEPROM? I'm also using EEPROM for parameter storage and using small area (512 bytes) for crash save area with my own save crash implementation. EspSaveCrash constructor has 2 parameters - one is offset from begin of the EEPROM and the second one is size. I prefer to use EEPROM instead of SPIFFS because of custom_crash_callback limitations.
Re: Debug / Trace Software / Hardware WDT
Posted:
Tue Apr 21, 2020 10:29 amby martin010
Pablo2048 wrote:You use whole 4096 bytes of EEPROM? I'm also using EEPROM for parameter storage and using small area (512 bytes) for crash save area with my own save crash implementation. EspSaveCrash constructor has 2 parameters - one is offset from begin of the EEPROM and the second one is size. I prefer to use EEPROM instead of SPIFFS because of custom_crash_callback limitations.
I couldn't get the EspSaveCrash working with a custom offset. Will give it another go.