V6.03.01 is now available at https://github.com/UKTailwind/PicoMite/releases/latest

New in this release

WEB PING (WebMite and HDMIWEB) — WEB PING address$ [, count] [, timeout] [, avgvar] sends ICMP echo requests to a hostname or IP address, prints a line per reply plus a summary, and can return the average round-trip time in ms (-1 if there were no replies) in a floating point variable.

OV5640 camera support (RP2350) — CAMERA OPEN OV5640 gives a 320x240 RGB565 preview, motion detection (CAMERA CHANGE) and JPEG capture (CAMERA CAPTURE JPEG) at VGA, XGA, SXGA, UXGA, QXGA and 5MP with HIGH/MEDIUM/LOW quality. White balance is frozen at the preview's converged setting so stills match the preview, and the pixel clock adapts to the CPU speed (378/315/252MHz).

Camera capture without a display — CAMERA OPEN no longer requires a panel: CAMERA CAPTURE JPEG and CAMERA CHANGE work headless, and the simple CAMERA CAPTURE now accepts any display with at least RGB565 colour (including SSD1963 types).

TURTLE colour commands accept the COLOR spelling — PEN COLOUR, PEN COLOR, PENCOLOUR, PENCOLOR and PC are all equivalent; likewise for FILL COLOUR and CURSOR COLOUR.

USB mice are decoded from their own HID report descriptor — with OPTION MOUSE SENSITIVITY set, mice with non-standard report layouts (extra buttons, padding, report IDs, wider movement fields) now work; the firmware falls back to the standard boot report if the mouse declares no usable movement.

PICO COMPUTER 3 is detected and configured automatically at boot (RP2350).

Fixes

CIRCLE with an aspect greater than 1 and a line width of 1 no longer leaves gaps in the outline.

A mouse click or screen tap in the full screen editor now lands on the right character on lines that have scrolled horizontally.

A misconfigured or disconnected camera reports an error naming the stalled signal instead of freezing; camera capture no longer disturbs the PSRAM/flash controller (fixes rare hard faults on PSRAM builds); faster capture loops.

Bluetooth console and keyboard fixes.

Corrected the embedded pin-status program for the WEB builds and the OLIMEXUSB platform string; keyboard map updates.

Documentation

The user manual is updated for all of the above (including a Pico Computer 3 section and the reworked camera and mouse entries) and is attached as PicoMite_User_ManualV6.03.01.pdf, with per-command outline bookmarks.

Binaries

Pre-built .uf2 images for all supported RP2040 and RP2350 variants are available on github. Flash the file matching your board and configuration.
Edited 2026-08-04 22:25 by matherp

---

I had understood that V6.03.00 was the last official version of MMBasic. However, this version appears to include not only bug fixes but also new features.
What does the future hold for MMBasic?

They are all "the final version" until the next beta release. :)

To paraphrase matherp: Time to start making stuff  

I was reading on a forum, regarding FX pedals for guitar; they have an amazing device (£1000+) that does everything except play the guitar. Firmware updates have ceased and so now they want to buy a newer model where the FW is still being debugged  
Edited 2026-08-05 00:24 by PhenixRising

  Quote  

What does the future hold for MMBasic?

I was asked for PING and it made sense to include in a bug fix release
I had already done the camera update but was waiting the actual camera to test.
Everything else is just trivia that was asked for or bugs found since the release.
Nothing I'm aware of now outstanding.
Note: no betas or RCs - just the release.
MMBasic now indefinitely stable pending any further bugs found.

Peter,

I need to look at the example PIO code in the manual, got a report that SETPIN needs to move to start of program, detected at 2350. Maybe 2350 is different from 2040.

So this may be an update for the manual.

Volhout
Edited 2026-08-05 01:47 by Volhout

Trivia maybe, but worthwhile. Thanks Peter. :)

Peter,

The PIO manual examples are sound (except from the use of "`" in some locations where "'" should be used for comments.

Tested on V60301, both 2040 and 2350

Regards,

Volhout
Edited 2026-08-05 05:31 by Volhout

@Peter

The regex code for curly braces is not working correctly.
The output should be 5 and 3 in both cases. I think that should be easy to fix.



BTW. The manual says:

AFAIK "Qualifiers" should be "Quantifiers".

If I could wish for something, it would be an enhancement of the regex function -specifically, return values ​​for groups, e.g., `mm.regex(1)`.
But I have a lot of wishes (regarding MMBasic) ...

Regards
Michael

How come you don't mention that on the 6.03.00 thread BEFORE I make a change

  matherp said  

How come you don't mention that on the 6.03.00 thread BEFORE I make a change

That is due - among other things - to the fact that I am no longer familiar with the rules regarding when corrections should be reported. There used to be set guidelines for submitting correction requests; those rules - and the frequency of new features - have changed, and I always felt like I was too late. And, of course, it is entirely up to you whether to incorporate the suggestions or ignore them.
Best regards
Michael

Corrections/bugs should always be reported immediately on the thread for the current release. If you found this sometime ago then if it had been reported on the 6.03.00 thread it would have been in this release.

Peter,

"A mouse click or screen tap in the full-screen editor now lands on the correct character on lines that have been horizontally scrolled."

I applied the firmware update using release PicoMiteRP2350V6.03.01.uf2.
Then I ran a test.


The '1' appears at position 99; after entering ten '*' characters, the final '"' is at position 110.

If you move the cursor over the '*' characters using the arrow keys, or click the mouse before the '1', everything works correctly.
However, if you move the cursor past the '1', the banner display kicks in; the positions remain accurate when using the arrow keys or mouse *until* the mouse button is pressed. At that point, the cursor jumps to the left—shifting by the number of positions that existed prior to the click—landing where the mouse cursor was previously located.
Try this test: use the arrow keys to return to the start of the line, then position the mouse cursor over the '1' and left-click; the cursor lands at position 99.
Run the test again, but first use the arrow keys to move to the end of the line (position 110), then position the mouse cursor over the '1' and left-click; the position is now 87.

Jan.
Edited 2026-08-06 21:17 by JanVolk

What display or are you talking about a mouse on the connected computer?

Peter,

A normal standard Raspberry Pi Pico 2 mounted on a MAKER PI PICO board and controlled with Tera Term.

All this is printed on a single line, separated by spaces.


Jan.
Edited 2026-08-06 22:27 by JanVolk

So it is the mouse on the computer running teraterm that displays the issue? The fix in 6.03.01 was for a locally connected mouse - wasn't aware of this issue - on the list....

That’s right, Peter. So the problem exists when using just TeraTerm and a mouse, and also with a standalone system using a mouse and HDMI or VGA—though it might be resolved in V6.03.01, albeit untested?

Jan.

@Peter,

The problem is identical on Putty. It is not Teraterm related.

Volhout

Found and fixed

A small suggestion for the PicoMite User Manual Ver 6.03.01
Would it be possible to make the list of Chr$(32) to Chr$(255) on page 82 easier to read by placing numbers in front of or above the entries? See the example below.


This could be done using three columns, allowing for the alignment of fonts and image sizes within each individual cell, after which the grid lines could be made white or invisible.

The same applies to page 106; the "Implementation Characteristics" section at the beginning would be more readable if presented in a table.

Jan.