 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : PicoMite V6.03.01 release
| Author | Message | ||||
| matherp Guru  Joined: 11/12/2012 Location: United KingdomPosts: 11709 |
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 |
||||
PilotPirx Senior Member  Joined: 03/11/2020 Location: GermanyPosts: 129 |
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? |
||||
Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 9003 |
They are all "the final version" until the next beta release. :) Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| PhenixRising Guru Joined: 07/11/2023 Location: United KingdomPosts: 2040 |
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 |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 11709 |
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. |
||||
| Volhout Guru Joined: 05/03/2018 Location: NetherlandsPosts: 6011 |
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 PicomiteVGA PETSCII ROBOTS |
||||
| Mixtel90 Guru Joined: 05/10/2019 Location: United KingdomPosts: 9003 |
Trivia maybe, but worthwhile. Thanks Peter. :) Mick Zilog Inside! nascom.info for Nascom & Gemini Preliminary MMBasic docs & my PCB designs |
||||
| Volhout Guru Joined: 05/03/2018 Location: NetherlandsPosts: 6011 |
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 PicomiteVGA PETSCII ROBOTS |
||||
twofingers Guru Joined: 02/06/2014 Location: GermanyPosts: 1769 |
@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. > ? mm.ver 6.0301 > sz!=0:? INSTR(1,"AABBAAAABAAAAAAA","[A][A][A]",sz!):? sz! 5 3 > sz!=0:? INSTR(1,"AABBAAAABAAAAAAA","[A]{3}",sz!):? sz! 5 4 BTW. The manual says: Qualifiers * 0 or more (not escaped) + 1 or more ? 0 or 1 {3} Exactly 3 {3,} 3 or more {,5} 5 or less {3,5\} 3,4 or 5 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 causality ≠ correlation ≠ coincidence |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 11709 |
How come you don't mention that on the 6.03.00 thread BEFORE I make a change  |
||||
| twofingers Guru Joined: 02/06/2014 Location: GermanyPosts: 1769 |
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 causality ≠ correlation ≠ coincidence |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 11709 |
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. |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2026 |
