Try this version - PicoMiteRP2350. Add ",QVGA" to the open command and you will get a 320x240 image when you run CAPTURE. I've also tweaked the colours a bit to brighten the image. Motion detect will also work in the higher resolution mode but you need to allocate a big enough buffer 320*240/8-1

PicoMite.zip

@Peter,

I tested the RP2040 VGA version rc19 today, and I am very pleased to see that all programs I tried (mainly games) work flawless. rc19 is a winner.

Also pleased with the file manager. I like the fact that when you run a program from the filemanager, and close it, you return to the FM at exactly where you left.
very nice. If there is one minor complaint about it, it is the fact that I frequently needed the help screen to learn what keys to press for certain functions (i.e. copy)

But it works very nice.

Thank you

Harm(Volhout).
Edited 2026-06-15 00:35 by Volhout

  matherp said  

V6.03.00RC19

PicoMiteRP2040V6.03.00RC19.zip
PicoMiteRP2350V6.03.00RC19a.zip
PicoMiteRP2350V6.03.00RC19b.zip

Various little tweaks.

Harm: I think this finally fixes the PIO bug. It was a real bug and nothing to do with the MIN version. Just a fluke whether it was seen or not.

The HDMIWEB version now supports:
640x480 at 252MHz, 315MHz and 378MHz, modes 1,2 and 5
720x400 modes 1,2 and 5
800x480 Modes 1 and 2
848x480 Modes 1 and 2
800x600 Modes 1 and 2
1024x600 modes 1,2 and 3

Normal RP2350 HDMI and VGA versions reserve 320x240x2 bytes (153600) for the framebuffer. This allows all the normal resolutions that have been supported. Web functionality requires a lot of RAM so the HDMI WEB reduces the framebuffer to 320x240x1 bytes (76800) which restricts the resolutions and modes available. However there is still a good selection there including all the critical ones (320x240x16colour). Personally I find 1024x600 mode 3 is perfect for the cheap 1024x600 HDMI displays with touch. This gives 16-colours @ 512x300 resolution perfect for editing.

Hi Peter, two questions:
1) Is there any chance of an HDMIWEB version with 1280x720 resolution being released? (e.g. for the MageDok T090A)
2) Do you think it’s possible to output sound via HDMI? As seen here: https://github.com/fliperama86/pico_hdmi/blob/main/docs/hdmi.md

No and No. 1: not enough memory, 2: Impossible as all cpu cycles are used with processing tiles, colour maps and layers

@Peter,

Some minor remarks on the built in file manager. Tested on RP2040 VGA using rc19.

a/ since FM is a command you only use at commandline, could it be excluded from the keywords ? I had several programs that used the variable "fm" that needed renaming.

b/ is there a reason why FM diverts from MMBasic ? Command line F4 starts EDIT (has been that way over a decade). In FM it is F2. MMBasic uses F2 to RUN. F1 to save.

c/ the editor in FM makes a backup file. the editor in MMBasic does not. I was editing a file on a near full A:/ drive.....

d/ I have several (text) demo programs that help me with calculations. I input some data, they show the result on screen and exit. When I start these from the file manager, I never see the result, because at exit the FM takes the screen. OK, this  may not be how you should create programs, but I did. Maybe others as well. Is there a way to prevent this FM kicking in brute force ?

Again, minor annoyances on a good filemanager. But maybe simple improvements exist.

Volhout
Edited 2026-06-15 06:18 by Volhout

a:
No: it is a command, the tokeniser is used both at the command prompt and in a program and that is how it gets executed.
b:
No right answer. F3 in the editor is search and it is in FM. Seems odd to then use F2 to clear the search (filter) but I could swap F2 and F4 - don't have a view/care
c:

  Quote  

the editor in MMBasic does not

Yes it does if you edit a file (edit fname$) which is what FM is doing.
d:
Again no right answer. For programs that already do an inkey$ loop to exit you would than have to press twice and programs that just end (Petscii) it would also be an irritation. I decided to not do it and leave it up to the programmer to put an inkey loop at the bottom of programs where it is relevant. Not going to change this one.
Edited 2026-06-15 07:47 by matherp

Peter,

Other FM (javavi, twofingers, dddns) are invoked with a function key (F9/F5) from commandline. No keyword. But I understand that MMBasic has keywords (RUN/EDIT) that are invoked by F2 and F4.

Since these mimick NC, the use of F4 to edit, and F3 to view, it may be coincidental that F4 is used for EDIT.

I noticed that in FM you (bottom, orange text) show error messages that have been produced by the running program.

It may be an option to add an optional parameter to FM (i.e. FM D) to allow a stopped program to remain at commandline. So you have the option to debug the error (what was the content of a certain variable when the program failed ?). To return to FM you type FM (or FM D) again.

OPTION F5 "FM D"+chr$(13) would give you the function key to return to FM in debug mode.

I see this (not automatic returning to FM) as the most important improvement.

Volhout
P.S. for people that run working programs, the FM is a perfect browser. For me, development/debugging is 99% of the time. So for me FM D would be the preferred mode. Or I would need Claude to help me write flawless code first time.
Edited 2026-06-15 16:36 by Volhout

This is the change I intend to make to FM - comments?


Edited 2026-06-15 18:19 by matherp

@Peter,

just playing around with a ST7789P3 LCD panel. So far got it working, but:

LINE AA seems to have an issue with this driver, as running the code below

> list
Poke display hres 302
Poke display vres 157
CLS
Line 18,82, 301,157
Pause 200
Line aa 18,82, 301,157
>

I get an error:

[6] Line aa 18,82, 301,157
Error : Display not configured

interestingly, the "normal" LINE command (in line 4) runs without any problems, just the AA forces the error. Has nothing to with POKE DISPLAY settings btw.

Environment is:

> option list
PicoMite MMBasic RP2350A V6.03.00RC19
OPTION SYSTEM SPI GP2,GP3,GP4
OPTION SYSTEM I2C GP0,GP1
OPTION FLASH SIZE 16777216
OPTION COLOURCODE ON
OPTION HEARTBEAT OFF
OPTION CPUSPEED (KHz) 252000
OPTION DISPLAY 40, 145
OPTION LCDPANEL ST7789, LANDSCAPE,GP5,GP6,GP7,GP8,INVERT
OPTION SDCARD GP11
OPTION PLATFORM ST7789-Test

The ST7789 driver does not support reading from the framebuffer which is required for LINE AA. You could try modifying the ST7789_320 driver instead

  matherp said  

Try this version - PicoMiteRP2350. Add ",QVGA" to the open command and you will get a 320x240 image when you run CAPTURE. I've also tweaked the colours a bit to brighten the image. Motion detect will also work in the higher resolution mode but you need to allocate a big enough buffer 320*240/8-1

It runs perfect now, my main problem was a faulty connection on the data bus. That didn't cause a software error but messed up the colours..sorry my fault.

Never the less your tweaking gives a real nice picture. Many thanks!
Image taken with save image and QVGA resolution:

Edited 2026-06-15 18:41 by dddns

@Peter,

I think the changes match MMBasic better. Thanks.

What about FM D parameter ? Can that be done ?

Volhout

No, I don't even know it could be done. You could try a mm.end subroutine in the library

The camera support is very nice and with the QVGA resolution useful for e.g. a selfmade webcam or QR scanner. I tried option lcdpanel ILI9341buff, SSD1963 and virtual_c which are not supported.
Would it be possible having an option to let it stream into memory and use blit to display/save?

Buffered drivers can't work - wrong resolution. You really don't want 153600 bytes permanently allocated to a buffer which is why the ILI9341 is used. Then just use image save to copy the image to disk. In any case, this is complex timing critical code and I'm not making any more changes.
Edited 2026-06-15 21:07 by matherp

Hi Peter, I think your proposed F key changes in FM are a good idea, so that  run, list & edit match the command prompt functionality :-) Thanks.

Peter,

I don't know if it is possible to get LIST PINS ALL to work?

Jan.

  Volhout said  

@Peter,

Some minor remarks on the built in file manager. Tested on RP2040 VGA using rc19.

a/ since FM is a command you only use at commandline, could it be excluded from the keywords ? I had several programs that used the variable "fm" that needed renaming.

...

Again, minor annoyances on a good filemanager. But maybe simple improvements exist.

Volhout

@Peter, I don't recall exactly, but I thought I had already mentioned this:

Perhaps you could consider renaming the file manager command after all? Using just two characters for a non-standard BASIC command is risky, as two-character variables are quite common; this makes conflicts with existing programs inevitable and ensures they will likely crop up frequently in the future.

How about "MM.FM" or simply "MMFM" for the file manager command?

Otherwise, I think the file manager is great!  
I did briefly test the last version three weeks ago, though — I’ve been on vacation since then.

Best regards.
bfwolf

Edit:
Another idea for different name: How about "FMAN" ?  
"MMFM" would be easier and faster to type though..  
Edited 2026-06-16 06:10 by bfwolf

V6.03.00RC20
PicoMiteRP2040V6.03.00RC20.zip
PicoMiteRP2350V6.03.00RC20a.zip
PicoMiteRP2350V6.03.00RC20b.zip
PicoMite_User_Manual.pdf

UI changes to the FM command - see the chapter in the manual
Fixes bug in LIST SYSTEM I2C
Camera command now supports 320x240 capture for applicable RP2350 versions (now including HDMI and HDMIUSB)

Peter,

Thanks. This also solves the problem with LIST PINS.
And the explanation in help(F1) in FM is much clearer now. Are F7 and F8 missing?

Jan.