Philip Howard

I think this has since been fixed to raise a more suitable error, but the TLDR is that supplying pins as numbers is no longer supported. They must be named...

Agreed. I just ported these to a new MicroPython library and they seem to work well! I *think* it might be possible to abstract away the UART and GPIO access...

To be frank the Python library is 133 lines of code, very concise and is about the most accurate documentation you're likely to see. I can't spare the time to...

The interrupt pin is active-low and, from what I can tell, is cleared on read. I haven't the foggiest clue what `FREAD` and `FWRITE` are or were, but they might...

This is very much an odd duck of a breakout- I appreciate you taking the time to grapple with it!

If you shim `I2C` with your own implementation, or just replace the function calls, then you should be able to use this code: https://github.com/pimoroni/pimoroni-pico/blob/0bda2abd2acd4269725efb81ffd3f33621a8e176/drivers/trackball/trackball.cpp

Good spot- I'm also unsure if it's the first or third (little or big endian data I guess) and currently don't have a Pi set up to test this. Glancing...

Sorry, seem to have missed this request. Have you managed to get it working since?

I believe the HyperPixel4 i2c port is available on bus 3, but you can find which by running `ls /dev/i2c-*` Then when you create an instance of the TrackBall class,...

We do not- we don't have first party support for those devices for better or worse. Ordinarily I'd be up for helping you get it up and running- the library...