Home
JAQForum Ver 24.01
Log In or Join  
Active Topics
Local Time 09:51 04 Apr 2026 Privacy Policy
Jump to

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.02.01 betas

     Page 8 of 8    
Author Message
toml_12953
Guru

Joined: 13/02/2015
Location: United States
Posts: 586
Posted: 05:37am 02 Mar 2026
Copy link to clipboard 
Print this post

  toml_12953 said  
  Geoffg said  
  toml_12953 said  What this will do is to allow the comma in a PRINT statement to act like other BASICs and move the cursor to the next print zone rather than just print a single space.

Something is not right here... the comma should advance the output to the next tab stop (default 8 char).

Geoff


You're right about the comma outputting tabs. My bad. The default is 2. I'd like to decouple it from the tab key, though so I could have print zones wider than 8 characters. Maybe allowing a larger range for the tab key would be OK.


I just added 10 and 12 to the allowed values of OPTION TAB and recompiled. Setting it to 10 seems to be the best compromise on a 40 column screen. I left the default at 2, though.
I'd still like the print zones to be independent of the tab stops as in other BASICs since I like to use the TAB key to indent when coding and 10 characters is way too much.
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 11131
Posted: 08:40am 02 Mar 2026
Copy link to clipboard 
Print this post

For lizby

PSRAM will allow you to create a framebuffer at any resolution. The only limitations are on layer buffers that must be in main memory so if you wanted a layer then you should create that before anything else but framebuffers will use any ram available
 
dddns
Guru

Joined: 20/09/2024
Location: Germany
Posts: 815
Posted: 08:50am 02 Mar 2026
Copy link to clipboard 
Print this post

@lizby

My program runs in 1024x768 Mode3 with framebuffer on PicoMiteHDMI MMBasic USB RP2350B Edition V6.02.01b7 without PSRAM:
> memory
Program:
 86K (46%) Program (2418 lines)
  1K ( 0%) 1 Embedded Fonts
 97K (54%) Free

Saved Variables:
 16K (100%) Free

RAM:
104K (45%) 434 Variables
  0K ( 0%) General
126K (55%) Free

Maybe there is some other problem with your code?!

Edit: You could try without option modbuff 192
Edited 2026-03-02 19:02 by dddns
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 11131
Posted: 09:09am 02 Mar 2026
Copy link to clipboard 
Print this post

The issue is that he is using lots of ram for his application. ram memory is a finite resource, you can't use it twice! The size of the modbufffer has no relevance to ram. If he defined the framebuffer before his other ram use then, of course it would work, but then he would get the message when his application was initialising and using ram.
 
dddns
Guru

Joined: 20/09/2024
Location: Germany
Posts: 815
Posted: 09:12am 02 Mar 2026
Copy link to clipboard 
Print this post

Ok..was just a thought as his memory report shows lower values than mine
Thanks for clarifying modbuff
 
Volhout
Guru

Joined: 05/03/2018
Location: Netherlands
Posts: 5823
Posted: 01:12pm 02 Mar 2026
Copy link to clipboard 
Print this post

@Peter,

Not sure if this has been issued before.
W.r.t. ONESHOT

Can handle "rising" and "positive" but not "pos"
Maybe a keyword conflict.

Volhout
PicomiteVGA PETSCII ROBOTS
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 3726
Posted: 02:13pm 02 Mar 2026
Copy link to clipboard 
Print this post

  dddns said  Maybe there is some other problem with your code?!

Edit: You could try without option modbuff 192


As I said, The problem is 2700+ lines of library code and 1500+ lines of program, and lots of large arrays (string arrays all have LENGTH sizing, String, Float, and Integer arrays reduced to necessary size). Not a problem but a feature.

I already had Gemini go through the code to see if anything could be further reduced in size. Until I get HDMI hardware with PSRAM, I'd like to see if I can get framebuffers to work at any resolution above 320x240. I will see if I can squeeze things down any more. Even 400x300 would be an improvement.

Re modbuff, I had thought from the description of it resizing drive A: that it was using flash. If it is actually using ram, I can get rid of it entirely.

EDIT: I did OPTION MODBUFF DISABLE, and there was no subsequent change in the mm.info(heap)

~
Edited 2026-03-03 01:04 by lizby
PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on FOTS
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 11131
Posted: 03:18pm 02 Mar 2026
Copy link to clipboard 
Print this post

Lizby

Don't bother trying 400x300. 800x600 steals memory on reboot before you even load a program. PSRAM is the solution
 
Martin H.

Guru

Joined: 04/06/2022
Location: Germany
Posts: 1439
Posted: 03:19pm 02 Mar 2026
Copy link to clipboard 
Print this post

I have a question regarding the current situation.
Is there a chance that the IMAGE RESIZE_FAST Command from CMM2 will be implemented to Picomite?
'no comment
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 11131
Posted: 03:54pm 02 Mar 2026
Copy link to clipboard 
Print this post

Things like that don't work with the limited rgb121 colour palette. So probably not worth it.
Edited 2026-03-03 03:08 by matherp
 
lizby
Guru

Joined: 17/05/2016
Location: United States
Posts: 3726
Posted: 04:06pm 02 Mar 2026
Copy link to clipboard 
Print this post

  matherp said  Don't bother trying 400x300. 800x600 steals memory on reboot before you even load a program. PSRAM is the solution


Ok, thanks. I had tried that, and it said it was out of heap before it even got to the framebuffer command.
PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on FOTS
 
thwill

Guru

Joined: 16/09/2019
Location: United Kingdom
Posts: 4365
Posted: 04:25pm 02 Mar 2026
Copy link to clipboard 
Print this post

  matherp said  This like that don't work with the limited rgb121 colour palette. So probably not worth it.


Why would resizing images care about the colour palette?

I assume Martin wants it to stretch or compress columns of pixels to use in his ray-casting routine ?

Best wishes,

Tom
MMBasic for Linux, Game*Mite, CMM2 Welcome Tape, Creaky old text adventures
 
Martin H.

Guru

Joined: 04/06/2022
Location: Germany
Posts: 1439
Posted: 05:01pm 02 Mar 2026
Copy link to clipboard 
Print this post

  matherp said  This like that don't work with the limited rgb121 colour palette. So probably not worth it.

if I have understood the CMM2 manual correctly, IMAGE RESIZE_FAST uses nearest neighbor, this even works with black and white images. so no mix of RGB Values requires.
In addition, picomiteHDMI also has video modes with more than 16 colours. Therefore, I think it would be worth considering.
  thwill said  I assume Martin wants it to stretch or compress columns of pixels to use in his ray-casting routine ?
Exactly, and the method I am currently using to calculate ‘on foot’ works just as well with a kind of "nearest neighbor" in the RGB121 space, only much too slowly. Other things include Leo's upcoming Outrun project.
I could also imagine simply extending the BLIT command by adding an optional output size parameter.
Edited 2026-03-03 03:17 by Martin H.
'no comment
 
Volhout
Guru

Joined: 05/03/2018
Location: Netherlands
Posts: 5823
Posted: 10:36am 03 Mar 2026
Copy link to clipboard 
Print this post

@Peter,

Not sure if this is a legacy something (from MM2 ?), but there is an inconsistency in Pico with the backlight of an LCD.

If you do an OPTION LIST, there (can be) an entry OPTION LCD BACKLIGHT xx
But you cannot change the option.
You must change it with a direct command

BACKLIGHT xx           'to change it commandline, or in a program
BACKLIGHT xx,DEFAULT   'to change the OPTION LCD BACKLIGHT during startup.

It is working, it is documented in the user manual, so there is no problem. But it is strange you cannot change it with typing OPTION LCD BACKLIGHT xx.

Volhout
PicomiteVGA PETSCII ROBOTS
 
Frank N. Furter
Guru

Joined: 28/05/2012
Location: Germany
Posts: 1063
Posted: 08:51pm 03 Mar 2026
Copy link to clipboard 
Print this post

@Volhout:

Don't you mean "OPTION BACKLIGHT LCD xx" instead of "OPTION LCD BACKLIGHT xx"?

This command appears to be for the PicoCalc!

Frank
Edited 2026-03-04 06:59 by Frank N. Furter
 
Frank N. Furter
Guru

Joined: 28/05/2012
Location: Germany
Posts: 1063
Posted: 08:59pm 03 Mar 2026
Copy link to clipboard 
Print this post

I noticed a minor “problem”:

I used MM.STARTUP in the library to redefine the prompt with the drive letter and path.

When I remove the SD card while I am in the editor, reinsert the SD card, and exit the editor, only the default prompt is displayed. Only after turning the Pico off and on again is my defined prompt displayed again.

Frank
 
phil99

Guru

Joined: 11/02/2018
Location: Australia
Posts: 3106
Posted: 09:10pm 03 Mar 2026
Copy link to clipboard 
Print this post

That happens with most things in MM.Startup.
The Editor uses most, if not all, RAM so things that were setup in MM.Startup get erased.
After exiting the editor you need to call MM.Startup again, as it only gets automatically called at startup. (There may be a clue there somewhere ;)
 
toml_12953
Guru

Joined: 13/02/2015
Location: United States
Posts: 586
Posted: 10:42pm 03 Mar 2026
Copy link to clipboard 
Print this post

  Frank N. Furter said  I noticed a minor “problem”:

I used MM.STARTUP in the library to redefine the prompt with the drive letter and path.

When I remove the SD card while I am in the editor, reinsert the SD card, and exit the editor, only the default prompt is displayed. Only after turning the Pico off and on again is my defined prompt displayed again.

Frank


Why are you not using MM.PROMPT to redefine your prompt? I'm not being facetious, I'd like to know if there's some advantage to it.
 
dddns
Guru

Joined: 20/09/2024
Location: Germany
Posts: 815
Posted: 09:07am 04 Mar 2026
Copy link to clipboard 
Print this post

Good morning,

you announced the support of the Pimoroni Pico Plus 2 W with V6.02.01b6
I'm interested in the Pimoroni Pico LiPo 2 XL W. I took a look at the scheme and it seems that it could work as well.
What would you suggest?

Many thanks
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 11131
Posted: 10:00am 04 Mar 2026
Copy link to clipboard 
Print this post

  Quote  I'm interested in the Pimoroni Pico LiPo 2 XL W. I took a look at the scheme and it seems that it could work as well.
What would you suggest?

Should work if the Pimoroni Pico Plus 2 W works and it wires the wifi/bluetooth the same. If the Pimoroni Pico Plus 2 W works and this doesn't then it won't be supported. I won't be buying one to test. I will fix any bugs found in the Pimoroni Pico Plus 2 W
 
     Page 8 of 8    
Print this page


To reply to this topic, you need to log in.

The Back Shed's forum code is written, and hosted, in Australia.
© JAQ Software 2026