I think the only hope of implementing something like that with the Pico would be to have a C implementation of the typical I2C interface with a number of registers - and have that read data from the registers or write it to them, and then fire off JS callbacks... which is very limited, so I'm not sure it would be very useful.
On the other hand... what about clock stretching? Is there a maximum time you're allowed to stretch the clock for? I mean, the Espruino I2C wrapper seems to wait for eons before declaring the attempt at communication to have timed out...
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
I think the only hope of implementing something like that with the Pico would be to have a C implementation of the typical I2C interface with a number of registers - and have that read data from the registers or write it to them, and then fire off JS callbacks... which is very limited, so I'm not sure it would be very useful.
On the other hand... what about clock stretching? Is there a maximum time you're allowed to stretch the clock for? I mean, the Espruino I2C wrapper seems to wait for eons before declaring the attempt at communication to have timed out...