Open misterb0407 opened 1 year ago
@misterb0407 is the target esp32
in both the setups?
Hi @vikramdattu , yes , the target was esp32 for both setup. As a work around I just disable watchdog for now from the idf.py menuconfig
@misterb0407 okay, thanks! I will certainly check for newer IDF branch and update you on the same.
@misterb0407 I saw your issue on IDF: https://github.com/espressif/esp-idf/issues/11678 Does having that particular change for I2S setup help with this example?
Hi @vikramdattu , it is hard to say as the example here uses legacy I2S driver but the https://github.com/espressif/esp-idf/issues/11678 uses the new I2S driver. Do you have any config (in this legacy driver) you would like me to try?
Steps:
cd to root of project files (not examples/micro_speech) so that 'component folder is recognized by system
Build the sample under 'micro_speech' examples by using docker ESP-IDF version 5.2
$docker run --rm -v $PWD:/project -w /project -it espressif/idf:release-v5.1
Then inside the docker prompt:$ idf.py build
Then flash and monitor, you would see the following in the log: `E (434939) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time: E (434939) task_wdt: - IDLE (CPU 0) E (434939) task_wdt: Tasks currently running: E (434939) task_wdt: CPU 0: tensorflow E (434939) task_wdt: CPU 1: IDLE E (434939) task_wdt: Print CPU 0 (current core) backtrace
Backtrace: 0x400E614F:0x3FFB0D50 0x40082905:0x3FFB0D80 0x400D6122:0x3FFC0200 0x400D5D8D:0x3FFC0240 0x400D5916:0x3FFC0270
Heard unknown (205) @434600ms Heard unknown (205) @438300ms Heard unknown (224) @439900ms Heard unknown (213) @441500ms Heard unknown (232) @443100ms Heard unknown (215) @444700ms Heard unknown (203) @448100ms`
This was not observed when building the same code with ESP-IDF version
release-v4.4