this works,should it?
> option list
PicoMite MMBasic Version 6.00.00RC11
OPTION SYSTEM SPI GP18,GP19,GP16
OPTION AUTORUN  ON
OPTION FLASH SIZE 4194304
OPTION CPUSPEED  378000 'KHz
OPTION LCDPANEL ILI9341, LANDSCAPE,GP15,GP14,GP13
OPTION TOUCH GP12,GP11
GUI CALIBRATE 0, 3891, 3866, -893, -647
OPTION SDCARD GP

Yes, that would make sense. It's the "standard" version of the firmware, not the HDMI version. The VGA version also accepts OPTION CPUSPEED.

Is it possible on a RP2350B to use GPs > 29 for VGA output? I tried to use GP28,30,31
for system SPI on bus 1 which can be setup, but when used no data gets through. Same problem for DC,WR,RD with a ssd1963

In contrast a sdcard with all pins individually assigned does work for me (GP39-42)

Before I re-solder and try it I wonder if VGA output would work like sdcard does on GPs between GP30 to GP47?

When you specify all pins on a SD card it runs in bit-bang mode and isn't using any of the modules on the chip. That's why it will work on any pins. I don't think anything else will work that way offhand.

VGA requires consecutive pins, but I can't see why, at least in theory, it shouldn't be possible to use it on high pin numbers.

I suspect that many drivers have maximum pin number limits because they are part of MMBasic and are expected to run on the 2040 and 2350A chip. Remove that limit and you would need some sort of system to recognize if the chip was A or B version so that the limit should be used. Otherwise you have to introduce even more versions of MMBasic!

I'd consider it sensible to design a PCB where connections are to the accepted "standard" GPIO numbers, even when using the RP2350B. It makes code more portable and reduces complication. Ok, it may be a little more work in designing the board but I'll accept that. I certainly wouldn't sacrifice GP40-GP47 to use for any sort of display. They are valuable as ADC pins as well as an 8-bit IO port.

Thank you Mixtel!

I was thinking the same. This is just a experimental build on a strip-board as I'm clutching at straws and use my last possible resource :)

  Mixtel90 said  

I suspect that many drivers have maximum pin number limits because they are part of MMBasic and are expected to run on the 2040 and 2350A chip. Remove that limit and you would need some sort of system to recognize if the chip was A or B version so that the limit should be used. Otherwise you have to introduce even more versions of MMBasic!

Supposedly, MMBASIC already has the code in it to recognize the B variant and will allow programs to access the extra pins if one is present.

I vaguely recall Peter mentioning a complication with devices accessing GPIO above 31.
It is probably in this thread somewhere but can't find it.

  Quote  

If I can fix a current limitation everything will work on all PINS except VGA and I2S on VGA firmware versions. I've just got I2S working on GP33,GP35 under HDMIUSB. I now need to try and rework the rest of PIO functionality to behave the same although the current PIO interface may limit my success on that so user PIO on PINS ABOVE GP31 may  not be possible.

Many thanks for this info! ..saved me at least 3 hours of useless work

The chips in the RP2350A and B are the same. They have the same number of IO bonding pads. The bonding wires are connected to pins in the package where they fit best and the IO decoder matrix makes them look like the appropriate GPIO numbers. Unless there is also some register or other on the die I'm not sure how you tell the difference between the two chips.

  Quote  

Unless there is also some register or other on the die I'm not sure how you tell the difference between the two chips.

Thank you. :)

Gentlemen,

Can anyone confirm that with the latest version PicoMiteVGA MMBasic USB RP2040 Edition V6.00.02RC24 in combination with PCM5102A I2S DAC that there is only mono sound?

I built my first VGA board with a RP2040-PIZERO with existing components on a hole print 70x30 mm and 3mm nylon bushings.
The dimensions of the whole: L:70mm W:30mm H:36mm and everything is easily accessible. I am still testing but so far everything seems to work fine.

PicoMiteVGA MMBasic USB RP2040 Edition V6.00.02RC24
OPTION SERIAL CONSOLE COM2,GP8,GP9
OPTION SYSTEM I2C GP16,GP17
OPTION FLASH SIZE 16777216
OPTION COLOR CODE ON
OPTION KEYBOARD US
OPTION HEARTBEAT OFF
OPTION PICO OFF
OPTION RESOLUTION 640x480 @ 252000KHz
OPTION SDCARD GP21, GP18, GP19, GP20
OPTION VGA PINS GP11,GP22
OPTION AUDIO I2S GP13,GP15', ON PWM CHANNEL 6
OPTION RTC AUTO ENABLE

My preliminary description:  
RP2040-PiZero V3.pdf


Greetings,

Jan

Update:
Sorry for interrupting the time but the problem was not the firmware but was on the hardware on my side.
Found the problem of audio mono.
Was the audio plug connector on the PCM5102A I2S DAC board that gave the problems.

Now I have a great universal RP2040 board with all possibilities for PicoMite, PicoMiteUSB and PicoMiteVGAUSB with extra flash and an SD card.
Was a nice challenge to build this and find out and test it. For the community the RP2040-PIZERO is a great alternative. The above description (pdf) is still correct.

Greetings,

Jan.

@Peter, has the GP0 issue for 16bit displays been resolved already?

I apologise if this has been dealt with, but I couldn't find any mention.

Trevor


I am looking to use the Pico2350Dil.
Edited 2025-05-28 00:32 by TrevorH

G'day All,
Not sure how many are using PS2 keyboard / mice now but I think this needs looking at, can anyone else confirm?

Using VGA 2040 with PS2 mouse, it appears the mouse cursor defaults to 16 pixels high whilst the font is 12 pixels high. The cursor also moves in 16 pixel increments so except the top line it doesn't line up.

HDMI firmware is ok, only VGA shows problem at both 640 and 720 resolution.
Tested with real PS2 mouse, still working on USB-PS2 keyboard / mouse adaptor....

Also, not sure if this is by design or something odd using Win7 / TeraTerm 4.100 and Win XP / TeraTerm 4.91
The "NUMLOCK" key works as "ESCAPE"
The keypad "/" key works as "F2" / RUN
The keypad "*" key works as "F3" / LIST
The keypad "-" key works as "F4" / EDIT

Tried on MicroMite 5.05.08 and PicoMite 6.00.02 and same result.
Not really a problem but been cursing the XP laptop to hell for dropping out of the editor before finally realising hitting the NUM LOCK key was causing it.  
It is a tiny laptop / keyboard but the desktop does it as well (Win7 normal 104 keyboard)

Regards,
Lyle.

  Quote  

In the manual I find nothing about controlling the brightness,

Can't test/fix for the next couple of weeks. Can anyone else confirm the issue?

  mozzie said  

G'day All,
Also, not sure if this is by design or something odd using Win7 / TeraTerm 4.100 and Win XP / TeraTerm 4.91
The "NUMLOCK" key works as "ESCAPE"
The keypad "/" key works as "F2" / RUN
The keypad "*" key works as "F3" / LIST
The keypad "-" key works as "F4" / EDIT

Tried on MicroMite 5.05.08 and PicoMite 6.00.02 and same result.
Not really a problem but been cursing the XP laptop to hell for dropping out of the editor before finally realising hitting the NUM LOCK key was causing it.  
It is a tiny laptop / keyboard but the desktop does it as well (Win7 normal 104 keyboard)

Regards,
Lyle.

Does the keyboard default to UK? You might try changing it to your country and see if that helps. When I first ran PicoMite, I had a few keys that didn't work properly and OPTION KEYBOARD US fixed it.

  mozzie said  

G'day All,
Not sure how many are using PS2 keyboard / mice now but I think this needs looking at, can anyone else confirm?

Using VGA 2040 with PS2 mouse, it appears the mouse cursor defaults to 16 pixels high whilst the font is 12 pixels high. The cursor also moves in 16 pixel increments so except the top line it doesn't line up.

Regards,
Lyle.

Hi Lyle,

I cannot confirm this. Running 6.00.02rc24 on a RP2040 VGA platform.
I breadboarded a 3V3/5V level shifter and added a USB/PS2 compatible mouse.
OPTION MOUSE gp0,gp1

The cursor in the editor is 8x12, and moves character per character. In below picture, the mouse cursor is mid screen right. It is a block cursor.




Volhout
.

P.S. the pico on the breadboard is just supplying 3V3 and 5V for the mouse and level shifter circuit. The 2040 VGA board is behind the DB9 connectors, below the VGA LCD screen. The 2040 VGA board has never been in widescreen mode. It is 640x480 60Hz.
Edited 2025-05-28 05:28 by Volhout

Hello Peter,

I want to give some feedback on the



feature.

In my WS2812B LED example I needed to declare a 16 color array, which is approx. 3 whole lines of code which must be in one single line to be accepted by the interpreter. In the past I used the "trick"
with backspace, but this way some information / data is invisible if it's longer...

I use the picoMite as a stand alone computer and this feature is so much appreciated!
Now - finally - everything is clear and readable!

So please keep this feature! Can't imagine how awful it would be with even longer strings / data...

Greetings
Daniel