Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

watchdog got triggered - reboot #54

Closed
slimline33 opened this issue Sep 26, 2022 · 0 comments
Closed

watchdog got triggered - reboot #54

slimline33 opened this issue Sep 26, 2022 · 0 comments

Comments

@slimline33
Copy link

slimline33 commented Sep 26, 2022

Hi, now in english 🗡️

after a successfully activating of a chroma74 display i can't send anything. my serial log says RX_TIMEOUT!!! sending a text and sending a picture over draw.html the system is crashing and the esp reboot.

My system is on a esp32wroom

input bitmap size: 640 x 384
Entering encode_raw_image; width=640, height=384
1282858 : Count: 4
1282960 : Mode changed to Sync
1282960 : Sync
Len 7 Data: 0x07 0xfe 0x0e 0x00 0x00 0x00 0x00
1283779 : short SYNC done
1283983 : Mode changed to Idle
1283983 : Idle
1284086 : Count: 4
1284086 : Mode changed to Sync
1284188 : Sync
Len 7 Data: 0x07 0xfe 0x0f 0x00 0x00 0x00 0x00
1285007 : Count: 3
1285007 : something wrong, back to idle
1285109 : Mode changed to Idle
1285211 : Idle
1286132 : Count: 0
1286133 : Mode changed to Sync
1286235 : Sync
Len 7 Data: 0x07 0xfe 0x11 0x00 0x00 0x00 0x00
1286951 : short SYNC done
E (1289748) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (1289748) task_wdt:  - async_tcp (CPU 1)
E (1289748) task_wdt: Tasks currently running:
E (1289748) task_wdt: CPU 0: IDLE
E (1289748) task_wdt: CPU 1: IDLE
E (1289748) task_wdt: Aborting.

abort() was called at PC 0x400fdfc8 on core 0

Backtrace:0x40083b01:0x3ffbebcc |<-CORRUPTED

ELF file SHA256: 0000000000000000

Rebooting...

any tipps for me? :)

I think it's the async dependency. However, I do not know how I can change the versions. Googling for the error tells me that a delay should be avoided as much as possible.

greetings

Christoph

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant