just ignored overwritten the Keypress in the startscreen sub:

EDIT:
I just tested it again in the B3 version, and now the screen freezes here too. It seems to be a fault with my Pico. When I have the patience, I'll unsolder it and replace it.
Edited 2025-08-27 22:08 by Martin H.

Martin,

I have the b4 running endless on a 2040, and have spotted an error.
"too many nested loops" in the "flower" routine. So I expect there is something wrong now with the direct jump (goto !!) in the repeat routine.
This may take longer to happen in a 2350

Volhout
Edited 2025-08-28 00:29 by Volhout

Hi Harm,
I've got my new portable MMBasic console running and with the tip that Peter gave me about limiting resolution, it's running Pico Frog, with music at the correct speed, it would almost do it, at full screen, but once I limited it, it's now looking and sounding good.


The box is 3D printed, poorly :-( and the mini keyboard is wireless USB, obviously I'll use a proper keyboard for editing....
Internally it's based on Peters original V1.0 HDMIUSB board, but I've modified it to drive a ST7796S LCD, and incorporated a Lithium Battery charger/monitor, with 2X 18650 3Ahr batteries, as ballast down the bottom, so it'll run for quite a long time :-)

Anyway, as long as the resolution bodge continues to works ok, I should be able to test 240x320 or 480x320 games reasonably easily, plus I get a lot of lines in the editor, ;-) and now I can view lines longer than a screen width easily, it's very functional. :-)
Regards Kevin.
Next job is to swap the 2040 to a 2350 on my game*mite, easier said than done :-(
Edited 2025-08-28 05:14 by Bleep

Kevin, Martin,

The endless run ending in an error "too deep nesting of SUB's" can be fixed by replacing

in line 212

with



Now I can look at fixing the problem with filling all 5 nests...

By the way, you really have a nice setup there. I like the battery operation. You do not need to use it, but you can in case it is needed. And the screen is big enough for some elementary editing. Different from a Game*Mite.

Volhout
Edited 2025-08-28 18:12 by Volhout

@Martin,

Fixed the bugs in b4. The "white screen + lockup" in GameOver was most likely caused by a FRAMEBUFFER WRITE N (direct write to LCD) happening during a FRAMEBUFFER MERGE. I haven't seen it since I fixed that. So the game should play well now, including fly behaviour.

Here is b5. The only known problem is that at game over the highscore is lost. But that is easily fixed by a VAR SAVE, low prio...

picofrog_GM_6b5.zip

Volhout
Edited 2025-08-29 20:27 by Volhout

As I said, I don't have a Game*Mite at the moment. I had to destroy the old Pico to desolder it. Now, once I've cleaned the board, I'll put a socket on it and then I'll use a Pico 2. I'll probably do all this over the weekend. Thanks for your efforts, I'm excited to see how your new Version turns out.
Cheers
Martin

Hi Harm,
I have now sucesfully converted my GameMite to a 2350, with a lot of solder suck, I even think the original 2040 is still working ;-)
Anyway, I've re-set it up a a GameMite, with added games, Flappy Bird etc. but also  including your latest PicoFrog and it's all working great. :-)
Thanks, Kevin.

Thanks for the update.
Good news that the surgery has worked out.
But (for my part) you would not need to make that change. I will make sure all Game*Mite games work on 2040. The 2350 may just run a bit smoother (or -like with picofrog- have slightly better music quality).

I hope Martin's fixing goes well also.

Volhout

P.S. For those expecting a VGA version in this thread. It will come, be patient, but I will iron out all problems and add additions to the Game*Mite version before upgrading the VGA version. For Game*Mite I have 2 enthusiastic beta testers :-)..So..patience...
Edited 2025-08-30 18:26 by Volhout

All,

Please find attached version b6.
Version b6 was focussed on platform compliance.
Version b6 will run both VGA and Game*Mite and 9341 LCD equipped 2040 or 2350 platforms. It may also work on HDMI, but I cannot test that. There are simply to many platforms and one can only adopt 1 or 2, maybe 3.

picofrog6_b6.zip

Development plan:
b7             = implement WII (and maybe NES (*)) controllers for PicoGameVGA compliance
                then all envisioned platform compliance work should be finished.
b8 and further = work on additional game features (i.e. diving turtles/croco/levels).

Volhout

(*) Problem is that NES controllers are hard to auto-detect, as they where not designed by Nintendo with this in mind, and PicoGameVGA hardware is not helping in that perspective.
Edited 2025-09-08 17:37 by Volhout

All,

This is picofrog6_b7. b7 supports some controllers
- A WII classic controller connected to system I2C (either I2C or I2C2)
- A WII nunchuck controller connected to system I2C (either I2C or I2C2)
- A NES controller connected to GPIO pins GP1/GP2/GP3 as in PicoGameVGA and PicoGameHDMI boards.

Besides that keyboard control (PS2 or console) is possible. USB keyboard is not tested, but should work as well.

The Game*Mite uses it's own 8 keys to control the game.

The Game*Mite, NES and WII classic controller use the arrow keys and the A button
The nunchuck uses the joystick and the Z button to control the game.
Keyboard controls are cursor keys, and the space bar.

picofrog6_b7.zip

This game works on LCD and VGA

Volhout

P.S. in case the NES controller support confuses your PicoMite, there is a variable called no_nes% that can be set to 1 to skip all NES controller support.
Edited 2025-09-12 04:42 by Volhout

Hi Harm,
I'm using Pico Frog on a GameMite, but with a WII controler plugged in, so I've temporarily told the program it's not a GameMite by setting gm%=0.
However then the WII controler is not being recognised, dummy% is zero in sub find_wii, so for now I've made the case statement for dummy% look for 0 instead of &hA4200101 then everything works fine, I can play the game using the WII.
Just to be sure I temporarily added the lines below to find_wii

and it did print &HA4200101, so the WII is working fine.
It looks to me like there is some problem with the way you are detecting the WII?
I am using I2C2, and I have checked that that is detected, which it is.
Regards, Kevin.