Open hwater opened 4 years ago
Hello, i just found an Workaround, after setting the Signalgenerators Task to CPU1 it works in my Configuration:
` xTaskCreatePinnedToCore( LedC_Task, / Task function. / "LedC_Task", / name of the task, a name just for humans / 8192, / Stack size of task / NULL, / parameter of the task / 1, / priority of the task / &LedC_Gen, / Task handle to keep track of the created task / 1); /cpu core number where the task is assigned/
xTaskCreatePinnedToCore( SigmaDelta_Task, / Task function. / "SigmaDelta_Task", / name of task, a name just for humans / 8192, / Stack size of task / NULL, / parameter of the task / 1, / priority of the task / &SigmaDeltaGen, / Task handle to keep track of the created task / 1); /cpu core number where the task is assigned/`
Ciao, Holger
Worked for me as well.
Awesome work!!!
Thank you for this fix! How did you diagnose this issue? Black magic? The error gave no hint...!
Describe the bug Reboots all 4 Seconds on M5Stack Core, 4MB STD Module
To Reproduce Steps to reproduce the behavior:
12:03:20.208 -> Rebooting... 12:03:20.281 -> ets Jun 8 2016 00:22:57 12:03:20.281 -> 12:03:20.281 -> rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT) 12:03:20.281 -> configsip: 0, SPIWP:0xee 12:03:20.281 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 12:03:20.281 -> mode:DIO, clock div:1 12:03:20.281 -> load:0x3fff0018,len:4 12:03:20.281 -> load:0x3fff001c,len:1216 12:03:20.281 -> ho 0 tail 12 room 4 12:03:20.281 -> load:0x40078000,len:9720 12:03:20.281 -> ho 0 tail 12 room 4 12:03:20.281 -> load:0x40080400,len:6352 12:03:20.281 -> entry 0x400806b8 12:03:20.448 -> M5Stack initializing...OK 12:03:25.940 -> E (11169) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: 12:03:25.940 -> E (11169) task_wdt: - IDLE0 (CPU 0) 12:03:25.940 -> E (11169) task_wdt: Tasks currently running: 12:03:25.940 -> E (11169) task_wdt: CPU 0: SigmaDelta_Task 12:03:25.940 -> E (11169) task_wdt: CPU 1: loopTask 12:03:25.940 -> E (11169) task_wdt: Aborting. 12:03:25.940 -> abort() was called at PC 0x400dced7 on core 0 12:03:25.940 -> 12:03:25.940 -> Backtrace: 0x4008bf70:0x3ffbe170 0x4008c1a1:0x3ffbe190 0x400dced7:0x3ffbe1b0 0x40084df9:0x3ffbe1d0 0x4008205c:0x3ffb5f50 0x40082d5f:0x3ffb5f70 0x400816c3:0x3ffb5f90 0x40081703:0x3ffb5fb0 0x400d1759:0x3ffb5fd0 0x40088a6d:0x3ffb5ff0 12:03:25.940 -> 12:03:25.940 -> Rebooting... 12:03:25.989 -> ets Jun 8 2016 00:22:57 12:03:25.989 -> 12:03:25.989 -> rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT) 12:03:25.989 -> configsip: 0, SPIWP:0xee 12:03:25.989 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 12:03:25.989 -> mode:DIO, clock div:1 12:03:25.989 -> load:0x3fff0018,len:4 12:03:25.989 -> load:0x3fff001c,len:1216 12:03:25.989 -> ho 0 tail 12 room 4 12:03:25.989 -> load:0x40078000,len:9720 12:03:25.989 -> ho 0 tail 12 room 4 12:03:25.989 -> load:0x40080400,len:6352 12:03:25.989 -> entry 0x400806b8 12:03:26.178 -> M5Stack initializing...OK
Seems to be an Watchdog TimeOut, but i dont know where to fix it.
Otherwise GREAT Work & many Greetings from Austria. Holger