-
Notifications
You must be signed in to change notification settings - Fork 0
0 WDTracks
A general way of specifying build options for a sketch. There are other active PRs pursuing this effort. This PR needs to be held back and updated after one of those is finalized. For testing this PR, a limited method for the Arduino IDE/Linux OS environment is provided.
A problem with both Hardware WDT and Soft WDT resets, there is no indication of where the processor is stuck.
This solution uses the GCC Program Instrumentation Options' "instrument-functions" to call our tracking functions to capture the most recent functions called. It stores the last caller, callee, and Stack Pointer at each function entry and exit.
Files needed:
-
build_opt.txt
- compiler "instrument-functions" options file in the sketch folder -
platform.local.txt
- (temporary) causes the compiler to use the sketch'sbuild_opt.txt
file -
WDTracks.cpp
- Added to the sketch folder. Handles tracking and printing/reporting.
The overhead is very high with this option. The functions __cyg_profile_func_enter
and __cyg_profile_func_exit
are used to track execution. Every function entry and exit is instrumented by the compiler with a call to the respective tracking function. This increases code size and execution time. To reduce overhead, there are three ways to specify the code to exclude from the instrumentation: build options -finstrument-functions-exclude-function-list=...
and -finstrument-functions-exclude-file-list=...
; and function attribute __attribute__((no_instrument_function))
. Note, if we limit the coverage too much, we may miss the event that caused the WDT. For an idea of sketch code size increase, a sketch with a code size of 520973 bytes, grew to 803566 bytes when recompiled with the instrument-functions options shown below.
Both -finstrument-functions-exclude-function-list=...
and -finstrument-functions-exclude-file-list=...
exclude when an item in the list matches as a substring in the actual symbol name or file name, respectively. This feature implementation can easily capture and exclude more functions than you intended. A challenge with this approach is the overhead and tuning the excludes, to reduce overhead without losing too many of the activity tracking calls. Use and modify with caution.
For reporting, we have two times that we can expand on the WDT reset reporting.
- Hardware WDT - For this HWDT or HWDT_NO4KEXTRA must be enabled from the "Arduino IDE Tools->Debug Level". The newly added tracking results are printed by callback function
hwdt_pre_sdk_init
. This call is made early during the startup process before any substantial initialization occurs that would overwrite interesting information. Care still has to be taken to exclude functions from calling "instrument-functions" at startup leading up to the call tohwdt_pre_sdk_init
. Otherwise, our tacking information will be lost. - Soft WDT - this occurs during postmortem report when
custom_crash_callback
is called. If you already have acustom_crash_callback
you will need to disable it for this debugging session.
Both of these callback functions are predefined as weak allowing for simple override replacements without the need for registration calls.
After a WDT reset, two or more lines starting with "epc1=0x40..." will appear after the stack dump. When you copy-paste this block into the Exception Decoder, it will only process the first one in the list. The Exception Decoder result of the first "epc1=0x40..." will show as the 1st line of the decode starting with "PC: 0x40...". If the results are not meaningful, you can get the decoder to use the next line by deleting the first "epc1=0x40..." line and press return. The decode results will update. Repeat the process as needed.
Minimum suggested contents for file, build_opt.txt
, (build options) to use the "-finstrument-functions" option.
-finstrument-functions
-finstrument-functions-exclude-function-list=app_entry,stack_thunk_get_,ets_intr_,ets_post,Cache_Read_Enable
-finstrument-functions-exclude-file-list=umm_malloc,hwdt_app_entry,core_esp8266_postmortem,core_esp8266_app_entry_noextra4k
Additional exclusions may be needed when using functions that have critical code timing loops, like I2C or high-priority interrupt routines, etc.
Various efforts are already under development for specifying build options for a sketch in an IDE and OS flexible manner.
For now, under Arduino IDE and Linux OS, I have been using a platform.local.txt
file with these lines to utilize my sketch build_opt.txt
file.
custom.flags_txt.source.pathname={build.source.path}/build_opt.txt
custom.flags_txt.build.pathname={build.path}/build_opt.txt
compiler.c.extra_flags=-include "{custom.flags_txt.build.pathname}.h" @{custom.flags_txt.build.pathname}
compiler.cpp.extra_flags=-include "{custom.flags_txt.build.pathname}.h" @{custom.flags_txt.build.pathname}
recipe.hooks.prebuild.1.pattern=mkdir -p "{build.path}/custom"
recipe.hooks.prebuild.2.pattern=bash -c "if [ -f {custom.flags_txt.source.pathname} ]; then if [ {custom.flags_txt.source.pathname} -nt {custom.flags_txt.build.pathname} ]; then cp -u {custom.flags_txt.source.pathname} {custom.flags_txt.build.pathname}; touch {custom.flags_txt.build.pathname}.h; fi; fi;"
recipe.hooks.prebuild.3.pattern=bash -c "if [ ! -f {custom.flags_txt.source.pathname} ]; then if [ -s {custom.flags_txt.build.pathname} ]; then rm {custom.flags_txt.build.pathname}; touch {custom.flags_txt.build.pathname} {custom.flags_txt.build.pathname}.h; fi; fi;"
recipe.hooks.prebuild.4.pattern=bash -c "if [ ! -f {custom.flags_txt.build.pathname} ]; then touch -t 170001010000 {custom.flags_txt.build.pathname}; fi;"
recipe.hooks.prebuild.5.pattern=bash -c "if [ ! -f {custom.flags_txt.build.pathname}.h ]; then touch -t 170001010000 {custom.flags_txt.build.pathname}.h; fi;"
Copy WDTracks.cpp
from this example to your sketch folder.
WDTracks.cpp contents
#include <Arduino.h>
#include <hwdt_app_entry.h>
#include <user_interface.h>
extern "C" {
struct WDTracksLastCall {
struct {
void *this_fn;
void *call_site;
void *sp;
} enter;
struct {
void *this_fn;
void *call_site;
void *sp;
} exit;
bool in;
};
struct WDTracksLastCall wd_tracks;
IRAM_ATTR void __cyg_profile_func_enter(void *this_fn, void *call_site) __attribute__((no_instrument_function));
IRAM_ATTR void __cyg_profile_func_exit(void *this_fn, void *call_site) __attribute__((no_instrument_function));
void print_wdtracks(void) __attribute__((no_instrument_function));
void custom_crash_callback(struct rst_info * rst_info, uint32_t stack, uint32_t stack_end) __attribute__((no_instrument_function));
/*
* Printing from hwdt_pre_sdk_init() requires special considerations. Normal
* "C" runtime initialization has not run at the time it is called. For
* printing from this context, we use umm_info_safe_printf_P. It is capable of
* handling this situation and is a function included in umm_malloc.
*/
int umm_info_safe_printf_P(const char *fmt, ...);
#define ETS_PRINTF(fmt, ...) umm_info_safe_printf_P(PSTR(fmt), ##__VA_ARGS__)
#if defined(DEBUG_ESP_HWDT) || defined(DEBUG_ESP_HWDT_NOEXTRA4K)
void hwdt_pre_sdk_init(void) __attribute__((no_instrument_function));
// Called from HWDT just before starting SDK
// Serial speed has been initialized for us.
void hwdt_pre_sdk_init(void) {
if (REASON_WDT_RST == hwdt_info.reset_reason) {
/*
Note, we rely on the previous values of the wd_tracks structure, still
being set from before the crash. At the time we are called here, the SDK
has not been started. The "C" runtime code that will zero the structure
does not run until later when the SDK calls user_init().
*/
print_wdtracks();
}
}
#endif
// Called from Postmortem
void custom_crash_callback(struct rst_info * rst_info, uint32_t stack, uint32_t stack_end)
{
(void)stack;
(void)stack_end;
if (REASON_SOFT_WDT_RST == rst_info->reason) {
print_wdtracks();
}
}
/*
Called at function entry after stackframe setup and registers are saved.
*/
void __cyg_profile_func_enter(void *this_fn, void *call_site)
{
wd_tracks.enter.this_fn = this_fn; // The address of the function called
wd_tracks.enter.call_site = call_site; // The saved return address "a0" of the callee
asm volatile (
"s32i a1, %[wd_tracks], %[enter_sp]\n\t"
: // No output constraints
: [wd_tracks]"a"(&wd_tracks), [enter_sp]"I"(offsetof(struct WDTracksLastCall, enter.sp))
:);
wd_tracks.in = true;
}
/*
Called at function exit just before saved registers and stackframe are
restored.
*/
void __cyg_profile_func_exit(void *this_fn, void *call_site)
{
wd_tracks.exit.this_fn = this_fn; // The address of the function called
wd_tracks.exit.call_site = call_site; // The saved return address "a0" of the callee
asm volatile (
"s32i a1, %[wd_tracks], %[exit_sp]\n\t"
: // No output constraints
: [wd_tracks]"a"(&wd_tracks), [exit_sp]"I"(offsetof(struct WDTracksLastCall, exit.sp))
:);
wd_tracks.in = false;
}
void print_wdtracks(void)
{
if (NULL == wd_tracks.enter.this_fn) {
// Compiler flags -finstrument-functions, etc. are most likely missing.
return;
}
if (wd_tracks.in) {
ETS_PRINTF("\nepc1=%p\nepc1=%p\n",
wd_tracks.enter.this_fn, wd_tracks.enter.call_site);
if (wd_tracks.exit.this_fn != wd_tracks.enter.this_fn &&
wd_tracks.exit.this_fn != wd_tracks.enter.call_site)
ETS_PRINTF("epc1=%p\n", wd_tracks.exit.this_fn);
if (wd_tracks.exit.call_site != wd_tracks.enter.this_fn &&
wd_tracks.exit.call_site != wd_tracks.enter.call_site)
ETS_PRINTF("epc1=%p\n", wd_tracks.exit.call_site);
} else {
ETS_PRINTF("\nepc1=%p\nepc1=%p\n",
wd_tracks.exit.this_fn, wd_tracks.exit.call_site);
if (wd_tracks.enter.this_fn != wd_tracks.exit.this_fn &&
wd_tracks.enter.this_fn != wd_tracks.exit.call_site)
ETS_PRINTF("epc1=%p\n", wd_tracks.enter.this_fn);
if (wd_tracks.enter.call_site != wd_tracks.exit.this_fn &&
wd_tracks.enter.call_site != wd_tracks.exit.call_site)
ETS_PRINTF("epc1=%p\n", wd_tracks.enter.call_site);
}
ETS_PRINTF("\n--------- OR FOR WDT, CUT HERE FOR EXCEPTION DECODER ---------\n");
if (wd_tracks.in) {
ETS_PRINTF("\nLast function entered:\n"
" called function: %p\n"
" callee return: %p\n"
" SP: %p\n",
wd_tracks.enter.this_fn, wd_tracks.enter.call_site, wd_tracks.enter.sp);
} else {
ETS_PRINTF("\nLast function exited:\n"
" called function: %p\n"
" callee return: %p\n"
" SP: %p\n",
wd_tracks.exit.this_fn, wd_tracks.exit.call_site, wd_tracks.exit.sp);
}
}
};
- Keeping the Lights On - how to manage GPIO state across reboots and crashes
- Boot fails when SPI Bus used
- GPIO Drive Strength and Ringing
- LDO Regulators WIP
- ESP8266 Power Considerations This is only a rough outline, needs a lot of development.
- Upgrading Flash Chips, QIO, and DIO
- Dodgy Extra 2K of DRAM or CONT - WIP
- WDTracks - Print last call before WDT
- 5V Tolerant I/O?
Arduino IDE specific
Misc.
- Exception Causes
- ESP8266 will not boot
- Stacks sys and cont
- WIP Boot ROM and SDK Notes
- Multi-segment Boot ROM Loader, notes
- Cache_Read_Enable How to turn off and on instruction cache execution.