Open KonssnoK opened 1 year ago
Can reproduce this problem. It happens due to stack overflow. In v5.0 the stack size for the tasks was increased https://github.com/espressif/esp-idf/commit/02f6b83f4708f68bf8727e595af372060cf29b5d#diff-5e35b069c93e046316c229df63fa26c51b822f6ab98598808f090e39ffee2298R159
@gerekon my current crash is related to the interrupts not being taken correctly by CPU, but i see also that part was changed in 5.0 without backporting
if !CONFIG_APPTRACE_SV_TS_SOURCE_TIMER_10
example_timer_init(TIMER_GROUP_1, TIMER_0, 2000);
#else
#warning "Timer (Group 1, Timer 0) is used by sysview module itself!"
#endif
#if !CONFIG_APPTRACE_SV_TS_SOURCE_TIMER_00
example_timer_init(TIMER_GROUP_0, TIMER_0, 4000);
#else
#warning "Timer (Group 0, Timer 0) is used by sysview module itself!"
#endif
to
for (int i = 0; i < portNUM_PROCESSORS; i++) {
gptimer_config_t timer_config = {
.clk_src = GPTIMER_CLK_SRC_APB,
.direction = GPTIMER_COUNT_UP,
.resolution_hz = 1000000,
};
ESP_ERROR_CHECK(gptimer_new_timer(&timer_config, &event_data[i].gptimer));
event_data[i].period = 1000000 * (i + 1);
}
Answers checklist.
IDF version.
v4.4.3-354-gb3e8121fb0
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
PowerShell
Development Kit.
ESP32S3-WROOM N8R2
Power Supply used.
USB
What is the expected behavior?
Run sysview
What is the actual behavior?
continuous crash on timer installation
Steps to reproduce.
Debug Logs.
More Information.
on master branch it works, some backport is missing. I remind you v4.4 is still an active stable branch supporting esp32s3.