Beyond the Turn of one LED and check for the press of a button… The limitations in xojo make it bad for the GPIO. If you really need the main part to be in xojo, your bes option it is to make the GPIO app in another languaje and make it comunicate with xojo.
I’m running Windows 10 on an Aaeon Up Board (same form factor and GPIO header as RPi) and I can control all GPIO via calls to a dll supplied by Aaeon. Looks like they also support I2C, not sure about SPI. One bad thing is they have no Windows COM port driver for UART1 on the HAT header, but UART0 does work.
Sometimes with custom things like this (pylogix, PLC comms) I have found it easier to call a python script to do the work using shell.execute, or using TCP Comms between the apps, since python can both run on the pi and has native libs.
they wrote is compatible with tcp.
at tcp one pc open a port and listen for incomming connection, then it allow or block this connection.
at xojo you have a control which can connect to it.
to read non realtime gpio state its possible in many ways. (Remote GPIO)
interact with python should be possible if you start a script via xojo shell class. text output can received in xojo.
or in python you can use tpc too.
in phython it is possible to register for a signal change, it will call a method then.
Hi I little ping from my side.
I made the 1st tests with raspi and Xojo running on my m1.
Works… also I can talk to gpio,
I have now purchased a canboard based on Arduino and the can pi board pi can 3.
And again I got many links and examples.Hope these links will also help others