@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

I don't find the flash erase file on Geoff's site--either in the current release or beta test zips, or in the Archive. It might be a good idea to include that.

Meanwhile, where is that available?

  PhenixRising said  

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

I think it's Peter's VGA Design 2 (as he posted).

John
Edited 2025-05-05 23:32 by JohnS

  lizby said  

...Meanwhile, where is that available?

2024-11-03_203836_clear_flash RP2350.zip

For RP2350!

Regards
Michael

  lizby said  

Meanwhile, where is that available?

For the RP2040, I found it here: https://geoffg.net/Downloads/picomite/Archive/PicoMite_Firmware%20V5.07.02.zip

@Peter,

I can also duplicate it on the VGA design 2. Connecting the WII classic to GP14/GP15, with the RTC placed and using V6.00.02RC21.

It only takes more time. In all cases, the screen is filled with dots (the code prints these), and the final character before the crash is always en "E", not a dot.

Please let the code run for 20 minutes, and check for silence (sound stopped) and an "E" on screen.

Regards,

Volhout

I've been testing this to destruction and I'm beginning to believe it is a bug in the Pico SDK I2C routines.
When you finally get a readable error message it says that a function isn't found which is clearly part of the source.
Neither the system stack not the user heap are showing any issues.
The next step is to try recoding the I2C routines using the bitbang versions and see what happens.......

Hi Peter,

This is the essential code.



I will also try to see if there is a relation with the mod file.

I've tried with different mod files and also replicated on RP2350 VGA AND RP2350 HDMI
That eliminates USB and VGA interrupts. I've also replicated with I2S audio. I've also removed the modsample. I haven't yet tried with playing WAV, FLAC or MP3.

@Peter,

When you do not play a modfile (no sound at all, just comment out the "PLAY MODFILE" line) it also crashes, but more impressive, with corrupted VGA screen.
So just repeating the DEVICE(WII B) is sufficient to crash the pico eventually.

Volhout

DEVICE(WII B) does nothing other than read a preset memory area - the interrogation of the Wii takes place in the background every 20mSec. In which case it should crash without that as well - please try.
This is why I'm suspecting the underlying I2C sdk code.
Edited 2025-05-06 03:11 by matherp

Harm and anyone else: Please try the attached VGA RP2040 code and report.

PicoMite.zip

Thanks

Original RC21. Confirmed that just WII CLASSIC OPEN is sufficient to crash the pico eventually.

I will try above version later tonight.

Volhout

V6.00.02RC22 is available on

https://geoffg.net/Downloads/picomite/PicoMite_Beta.zip

Fixes a bug in scrolling in the editor when loading a file which creates continuation lines.
Adds a check in the editor which won't let you save and exit if continuation characters create a line longer than 255 characters.
Makes changes to handling Wii Classic and Wii Nunchuck to try and circumvent what appears to be an sdk issue where I2C commands return before completing.

Github updated

@Peter,

Just tested the 5:50 vga only release, and that does not fix it.
I will look at the RC22 now.

Volhout