matherp said  

No idea, your circuit is far more complex than mine

I checked it several times, everything is OK with my scheme.
When configuring PS/2 mouse on ports GP0, GP1 it does not work, but it works on ports GP2, GP3.
PS/2 keyboard can work on any of these ports.

By the way, thank you very much for the PS/2 Keyboard setup OPTIONS PS2 PINS, with them it is now easy for me to configure the firmware for my hardware.
And also special thanks for the PS/2 Mouse
Edited 2024-12-04 10:53 by javavi

Do you also power the unit via the same usb connector.
Maybe mouse and USB’s parallel causes the issue

Try if the problem follows the usb socket you use to power.

Volhout
Edited 2024-12-04 15:53 by Volhout

  Quote  

When configuring PS/2 mouse on ports GP0, GP1 it does not work, but it works on ports GP2, GP3.

That was the bit of information I needed. Just to confirm, the mouse is working perfectly on GP2,GP3?

  Volhout said  

Do you also power the unit via the same usb connector.
Maybe mouse and USB’s parallel causes the issue
Volhout

I do not use USB connectors, they are shown as optional on the diagram.
I use a Y-shaped cable to connect two devices to one PS/2 connector.

  matherp said  

That was the bit of information I needed. Just to confirm, the mouse is working perfectly on GP2,GP3?

As I have already found out, the PS/2 mouse does not work when configured for ports GP0, GP1, but it works when configured for ports GP2, GP3.
At the same time, by swapping them, the PS/2 Keyboard works on any of these pairs of ports.
Edited 2024-12-04 18:38 by javavi

A single USB-A socket on a PC is within spec if it can supply 500mA. If you power a mouse and keyboard via a Y cable from a single socket then in a few cases it may not work (old keyboards could be power hungry). I'm not saying this is the case here, but it's worth a thought.

javavi

Which version (VGA, HDMI ?) are you running - I'll post a fixed version for you to test

  matherp said  

javavi
Which version (VGA, HDMI ?) are you running - I'll post a fixed version for you to test

I checked this on both firmware versions, for both VGA and HDMI.
I also checked the VGA variant on both RP2040 and RP2350 chips.

If you check the port configuration, it gives this:

Edited 2024-12-04 19:00 by javavi

Here is a VGA version RP2040 - should now work with GP0/GP1 - please report. Typically boundary condition: what is the GP no of pin 1?


PicoMite (2).zip

By the way, maybe make OPTIONS for uniformity something like this

or something like this:


This also occurs in other options for configuring device pins!
Edited 2024-12-04 19:07 by javavi

  matherp said  

Here is a VGA version RP2040 - should now work with GP0/GP1 - please report. Typically boundary condition: what is the GP no of pin 1?]

Yes, it seems to work as it should here.

V6.00.01RC5 revisited

Fixes use of GP0 for PS2 mouse clock
Fixes MM.INFO(PIN ...) to correctly reflect MOUSE usage

PicoMiteRP2040V6.00.01RC5.zip

PicoMiteRP2350V6.00.01RC5.zip

  matherp said  

V6.00.01RC5 revisited
Fixes use of GP0 for PS2 mouse clock
Fixes MM.INFO(PIN ...) to correctly reflect MOUSE usage

Tested on several firmware versions
PicoMiteVGA MMBasic RP2040 Edition V6.00.01RC5
PicoMiteVGA MMBasic RP2350A Edition V6.00.01RC5
PicoMiteHDMI MMBasic RP2350A Edition V6.00.01RC5
PS/2 The mouse is now configured on pins GP0, GP1 normally, but works in the editor only with firmware PicoMiteVGA MMBasic RP2040 Edition V6.00.01RC5

  matherp said  

Changes default speed on a number of VGA configurations to 252MHz

In Firmware
PicoMiteVGA MMBasic RP2040 Edition V6.00.01RC5
PicoMiteVGA MMBasic RP2350A Edition V6.00.01RC5
don't show cpu speed option,
although it is displayed in the HDMI version of the firmware

Edited 2024-12-04 20:35 by javavi

  Quote  

but works in the editor only with firmware PicoMiteVGA MMBasic RP2040 Edition V6.00.01RC5

What about on other pins?

  Quote  

In Firmware
PicoMiteVGA MMBasic RP2040 Edition V6.00.01RC5
PicoMiteVGA MMBasic RP2350A Edition V6.00.01RC5
> OPTION LIST
don't show cpu speed option,

Correct because it is the default 126MHz. My comment refers to things like OPTION RESET VGA DESIGN 1

  matherp said  

What about on other pins?

Yes, if you swap the keyboard and mouse (A4tech SWOP-35) and configure them accordingly, the mouse starts working as it should.
I noticed that one of my three PS/2 mice gives this effect, I checked that the others can work on GP0, GP1.
But for some reason this A4tech SWOP-35 mouse doesn't want to work. This is very strange.
PS:
Maybe there's just something wrong with this particular Mouse! Maybe the wire is broken and when I reconnect it the contact is lost or the circuit handles the levels for PS/2 a little differently....
Edited 2024-12-04 21:15 by javavi

I've now got the opposite RP2350 HDMI and VGA work on GP0 and GP1 but RP2040 doesn't. Everything works on GP2,GP3 or GP1,GP2. Its almost as though there is something odd with GP0 because I've fixed the original GP0 issue

AND it works with GP1,GP0 but not GP0,GP1
Edited 2024-12-04 22:14 by matherp

There is something strange after all!
I rechecked the operation of this A4tech SWOP-35 mouse on a PC and it works perfectly. Then I checked its operation on the same circuit but with Pico1 RP2040 on firmware PicoMiteVGA MMBasic RP2040 Edition V6.00.01RC5 and here it also works fine in the EDITOR....
Moreover, I checked the operation at all permissible CPU speeds for this VGA RP2040 firmware.
Edited 2024-12-04 22:27 by javavi

It should be noted that this is how one (A4tech SWOP-35) of my three PS/2 mice behaves!
The other two PS/2 mice work fine on ports GP0, GP1 of my scheme, on all firmware versions of RC5.
Edited 2024-12-04 22:32 by javavi

Javavi,

Could you try to change the value of the 1k pullup resistors to 4.7k ?
It is possible that you do not reach the logic zero level for the mouse.

1k pullup to 5V, 100 ohm in series, and the Pico output is also 50 ohm-ish.
That means that the low level on the PS2 line is 750mV.

Old TTL chips require lower than 800mV for low, and 2.2V for high).

Volhout

  Volhout said  

Could you try to change the value of the 1k pullup resistors to 4.7k ?
It is possible that you do not reach the logic zero level for the mouse.

I tried replacing the pull-up resistors of my 1k circuit with 4.7k, I tried reducing 100 Ohm - it didn't change anything.
At the same time, those mice that worked continued to work, except this one.
I looked at it with an oscilloscope, the peculiarity of this mouse is that after power is supplied, it does not remain silent, but sends a request all the time, at some point during PicoMite loading, initialization occurs, but apparently it crashes.
How this Mouse has tormented me today!
Maybe I should throw it out and forget all this?
Edited 2024-12-05 01:59 by javavi

Just a quick PS/2 mouse test, may not be relevant.
Disabled PS/2 keyboard to test mouse in kb socket.
All functions work with a variety of mice using the Mouse functions at the command line.
None of the mouses work in the editor. Without a PS/2 kb configured, perhaps that is expected?
Edit
Using the second version of RC5
Edited 2024-12-05 07:13 by phil99