Freeze issue in DigDug after few seconds

[retronicdesign]

Awesome job! Nice little project to build!

I sucessfully built it from an ESP-WROOM-32 board, Red TFT, custom LM324 amp and a DB9 Atari joystick connector. I'll retrofit it in a small cabinet in the end.

One issue though; DigDig is hanging after few second. I suspect something with the Watchdog. Here is the Traceback I hit:

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13924
ho 0 tail 12 room 4
load:0x40080400,len:3600
entry 0x400805f0
Galagino
ESP-IDF 40404
Free heap: 334444
Main core: 1
Main priority: 1
Free heap: 329804
E (36368) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (36368) task_wdt:  - IDLE (CPU 0)
E (36368) task_wdt: Tasks currently running:
E (36368) task_wdt: CPU 0: emulation task
E (36368) task_wdt: CPU 1: IDLE
E (36368) task_wdt: Aborting.

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


Backtrace: 0x40084109:0x3ffbeb2c |<-CORRUPTED

Anyone has an idea? My DigDug ROM is from MAME and converted sucessfully.
I see graphics, sound things are moving around normally for about 5 seconds, no mather i'm in the title screen or in game.
@harbaum

[harbaum]

I have been seeing the same in early versions. This is due to Digdug having a rather high CPU demand. Yes, the watchdog fires. But this is due to the CPU task running too slow/too long and getting out of sync with the video task which finally results in some inter process lock not being released. It might be possible to make this issue to disappear and the game to run even when CPU power is not sufficient. But instead I'd prefer to have the game run fast enough.

One possible reason for that happening now may be an updated ESP32 SDK which in turn may be more CPU consuming here and there pushing DigDug over the edge.

I reported this bug back then: espressif/arduino-esp32#8467. So I am pretty sure I used the SDK versions mentioned there like e.g. 2.0.9. You might try to downgrade to that version and see if that fixes DigDug

[retronicdesign]

Thank you for your reply! That makes lot of sense. Any possibility to obliterate this watchdog?Maybe in the Z80 library?I need to better understand how this emulator works. You triggered my curiosity…Cheers!Francis Gradel, B.Eng.Lead architectRetronic Design TeamLe 28 janv. 2025 à 15:47, Till Harbaum ***@***.***> a écrit : I have been seeing the same in early versions. This is due to Digdug having a rather high CPU demand. Yes, the watchdog fires. But this is due to the CPU task running too slow/too long and getting out of sync with the video task which finally results in some inter process lock not being released. It might be possible to make this issue to disappear and the game to run even when CPU power is not sufficient. But instead I'd prefer to have the game run fast enough. One possible reason for that happening now may be an updated ESP32 SDK which in turn may be more CPU consuming here and there pushing DigDug over the edge. I reported this bug back then: espressif/arduino-esp32#8467. So I am pretty sure I used the SDK versions mentioned there like e.g. 2.0.9. You might try to downgrade to that version and see if that fixes DigDug —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>