dddns said  

Hello,

the latest RP2350 HDMI and VGA firmware gives me an error when executing files command. This happens only for Resolution 800 and 848 for A: and B: drive, all others work:

> files
A:/
Error : Not enough Heap memory
> option list
PicoMiteVGA MMBasic RP2350B Edition V6.01.00b11
OPTION FLASH SIZE 16777216
OPTION COLOURCODE ON
OPTION KEYBOARD US
OPTION PICO OFF
OPTION RESOLUTION 800x600 @ 360000KHz
OPTION DISPLAY 50, 100
OPTION SDCARD GP24, GP25, GP26, GP27
OPTION VGA PINS GP32,GP34

The problem with "files" command still exists for me in b12.
I can confirm that files get corrupt, when

file1.txt will be corrupted and a large part gets cut off at the top. If the file is small it will result in a 0 byte file.

  Quote  

The problem with "files" command still exists for me in b12.

Will have to reduce the maximum number of files in those modes from 1000 to say 750

  Quote  

I can confirm that files get corrupt, when

Was as a result of the "fix" for zero length files b13 should solve this

@Peter,

The 2040 test version also solves the problems (file copy problem, and framebuffer merge problem) for the 2040 Game*Mite.

Volhout

@Peter,

Will you also update the other (VGA/HDMI) b12 versions with this fix ?

Volhout

V6.01.00b13


PicoMiteV6.01.00b13.zip


Fixes the zero length file bug WITHOUT bu....ing anything else (I hope)

New experimental drivers for the SSD1963 (WIP)

@Peter,

Can you share more info regarding the SSD1963 drivers as very curious…..

Hi Peter,
is it the desired behavior that an entry in the command line - after running a program with `Option Explicit` - produces an error message about an undeclared variable? I would have expected the lifetime of `Option Explicit` to be limited to the program itself. (V6.01.00b5e)

Kind regards
Michael

Has always been this way AFAIK

Thanks!
Okay, so that means that to disable "Option Explicit" on the command line, I have to start a program that doesn't contain "Option Explicit"?

From manual p91:

If i recall correctly, I encountered this behavior, and "new" at the command line undid OPTION EXPLICIT. Of course, you lose your variable values, but you also would if you started a new program.

~
Edited 2025-09-21 03:26 by lizby

@matherp

In the MMInKey() function in the PicoMite.c file, there is this non-sensical code.
It doesn't hurt anything, but it can't ever be true.   Perhaps it should be || instead of &&  ?



Edited 2025-09-21 07:45 by EDNEDN

Peter,
B13 seems pretty good. I have hoever one thingI havenot been able to quantify.
For picofrog, I toy around with sprites, that occasionally are shown outside the lcd screen when I make a mistake.
I remember this was very robust, but in b13, the pico crashes. White screen, no console.

Is anything changed in the protection of screen coordinates? Or is my memory false. This is on 2040 game mite.

I have not found a simple way to reproduce yet.

Volhout

It shouldn't crash but it should error. Can you create a simple test program so I can investigate?

  Quote  

there is this non-sensical code.
It doesn't hurt anything, but it can't ever be true.   Perhaps it should be || instead of &&  ?

Hmmm...
Edited 2025-09-22 02:47 by matherp

@Peter - I am using one of your RP2350B DIL modules (with b13 firmware) connected to one of the latest batch of 5” IPS panels arrived form BuyDisplay (exactly the same module you link to on your PicoPalm thread).

Using 8-bit data connection. The issue I am seeing is a reversal of the Red and the Blue colours (green is ok). OPTION LCDPANEL SSD1963_5,L,,,,GP1 is set.
Using GP13-GP16 for D/C, WR, RD, RST.

Note option 5A does not work (splits the screen), and other sizes tried too without success.
Everything else works as expected.

Is there some kind of ‘undocumented invert’ parameter to resolve this issue in a similar manner as on the SPI screens?

Also FYI, lots of time was lost attempting to use GP40-GP47 for the 8-bit data link (and using GP40 as the last parameter in the OPTION).
It did not work - several DILs used, and three sets of wiring for each and all failed; only worked when I moved to GP1-GP8. Could there be a bug when using high PIN numbers?

Also - tried on 6.0..3 and same issue with blue and red colours reversed.

Manual page 60

  Quote  

16-bit Parallel LCD Panels
SSD1963 panels can also be enabled for 16-bit parallel operation. In this case, by default, pins GP0-GP15 are
used for the data connections and, by default, pins GP16 to GP19 are used for the control signals DC, WR, RD
and RESET.
For systems using the RP2350B only the data pins used can be selected by using the optional DB0pin parameter
in the configuration command.

  Quote  

SSD1963_5ER_16 For the 5 inch EastRising panel

Edited 2025-09-22 07:55 by matherp

@Peter - I did see this in the manual regarding 16-bit mode, but I was ideally needing to use 8-bit mode.

Are you saying the red and blue will switch round with the 5ER_16 (and that I can’t therefore use 8-bit comms)?

I would try it but I’m away from PicoMite until this evening so curiosity has got to me….

Could there be a 12 bit mode too as you’ve eluded to in b13 (for the ER I mean)? Be useful to know so I can save some pins!!
Edited 2025-09-22 15:04 by WhiteWizzard

You can use POKE DISPLAY to change the colour order after the display is initialised when there is not a specific config for it. see this this thread

V6.01.00b14


PicoMiteV6.01.00b14.zip


Fixes a couple of types in PIO
Fixes a typo in reading escape sequences#


WhiteWizzard

Only the 16-bit drivers support changing the SSD data pins. There is quite a lot of overhead in processing this and with 3 transfers per pixel for 8-bit mode that would slow things down too much.

The release does include 3 buffered drivers for the 5" BuyDisplay IPS display on the RP2350 BUT they are all 400x240 resolution. They do allow the data pins to be assigned as the updates take place on the 2nd processor. Feel free to try them.

SSD1963_5_BUFF, SSD1963_5_12BUFF and SSD1963_5_16BUFF. Parameters are as per the manual

@Peter - Thanks for explaining, although FYI, I do have remapped 8-bit data working when DB0-DB7 are assigned to GP1-GP8 (since GP0 is used for the PSRAM CS on your DIL module).

VERY HAPPY with the massive improvement over 8-bit speed when using 16-bit comms set with OPTION ....5ER_16,L,,GP17,,GP1

Can confirm too the Red/Blue are sorted too making the colours in the EDITOR look normal once again!

Thanks for the heads up on the 12-bit buffer; will try that on another unit later.........

  matherp said  

Fixes a typo in reading escape sequences#

If you are talking about serial, an observation on 2350VGA:

Since long ago, scrolling in the editor in a long program leaves sometimes rests of escape sequences like "[" or "~" from the cursor keys. This only happens beyond the first let's say 40Kb. The scrolling slows down and immediately these errors occur.
Sometimes it crashed the Pico and hard reset is necessary.
And if a program executes an inkey$ command and looks for e.g. chr$(129) like the FM then it crashed for me fore sure.

With b13 this is gone for all directions of the cursor keys! For the first time since half a year. Only Page Up/down leaves a "~"

With b14 it came back. I reverted to b13 and it's fine again.

I'm using as well inkey$ and even stressing serial by accidentally uploading a program while the basic program is running doesn't crash it.

I've used b13 now two days intensively and found, that it runs best since long




Saying it "crashes" it is maybe too much but it doesn't respond anymore
Edited 2025-09-23 05:17 by dddns