@Peter,

This is a stripped section of PETSCII that will crash in 2 minutes 16 seconds (1360 loops).
It is not 1 minute 42 seconds, but I fixed the game loop in this test to 100ms (10fps), and the actual game is slightly faster.

As there is almost no memory usage, heap is not important. If anything, then C-stack.

This code only prints dots on the screen while playing music and scanning WII classic remote. Nothing else.


wii_test.zip

Volhout
Edited 2025-05-05 16:37 by Volhout

Harm

Please give me the full option list you are running with



Mouse only works in mode 1 as it uses tiles

  Quote  

When the long line is the line before the last line, I can't see the last line in EDIT. List works properly. I'm running this on a bare RP2350.

Thanks for the report - will check - update: found and fixed. Will be in next release.
Edited 2025-05-05 17:10 by matherp

Hi Peter,

This is the option list for the PicoGameVGA platform (very similar to the VGA design 2). Using GP26/27 for I2C for RTC and WII.



When I run PETSCII from commandline, or run it from the filemanager, has the same problem. F5 invokes the filemanager in my platforms.

Volhout
Edited 2025-05-05 17:36 by Volhout

Harm

We knew this was going to happen.  Your test program doesn't crash for me. Running on a "genuine" vga design 2 board. The only difference is that I'm using GP14,GP15 for the system i2c and have the RTC module plugged into the board.
Have you tired different CPU speeds? Can you correlate the crashes with the mod file looping round? Can you run the test on and RP2350 to see if it makes a difference?



Edited 2025-05-05 19:08 by matherp

Is that a Mick (Mixtel90) board?...dammit more stuff that I missed.

No, that's not my design. Mine is the PicoGameVGA that Volhout is having a problem with. (It might actually be a PicoGAME Mini, using those pins for I2C).
.
Edited 2025-05-05 20:12 by Mixtel90