Provider confusion for Pi5

[Ir3nicuz]

I'm heavily confused about the latest provider concept for Raspberry 5.

I want to access the Gpio and the I2C bus on a Raspberry 5.
The provider PiGpio is supporting gpio and i2c, but not Raspberry 5.
The provider LinuxFs is supporting Raspberry 5 and I2C but not Gpio.
The provider GpioD is supporting Raspberry 5 and Gpio but not I2C.

And at beginning of supporting Raspberry 5 with version 2.5.0 just one single provider is allowed to be loaded.

I am correct that pi4j actually not support the usage of Gpio and Bus-systems on Raspberry 5 at the same time?!?!

[taartspi]

The change was a single provider for an IO_TYPE. Prior to this you could load pigpio AND linuxfs-i2c both with an I2C provider. In your example you can add to your pom file linuxfs for i2c and gpiod for gpio pins. Does that explain the present implementation?

[Ir3nicuz]

To me it was not clear what "IO-Type" in the documentation means. So IO-Type relates to the hardware modules like "Gpio" or "I2C" and not to the access concept like "PiGpio", "LinuxFs" or "Gpiod".
Then its strange that my Pi4jContext = Pi4J.newAutoContext(); throws an service configurration error on "Gpiod" and "LinuxFs".

app.log

Its the same build pipeline as before working with "PiGpio" at a Raspberry 4. The provider files are present in the package:

[Ir3nicuz]

I found the problem. My build pipeline creates a combined service file for a fat jar container.
The script just merges all service files. The newly added "GpioD" service seems to provide a original service file with too less linebreaks. :(
It leads to a combined line for both providers which cannot be determined as single providers:

I will later think about solution.

[FDelporte]

We have a documentation page about FAT JARs, maybe this can help?
https://www.pi4j.com/documentation/building/fat-jar/

[Ir3nicuz]

Thanks for the hint, but I use Gradle. I don't know how the "maven-shade-plugin" handles the merging of the service files for Fat-Jars. But at my gradle script I added an additional linefeed after every services-file's text content at merging to fix the missing linefeed:

zipTree(file).matching{ include 'META-INF/services/*' }.each { f ->
                new File(serviceDir, f.name) << (f.getText("UTF-8") + "\n")
            }

That changed the result from:

to (and it works again):

The source service files differ in the amout of line feeds:
PiGpio:

GpioD:

[TobiasReich]

Sorry for hijacking this post but I'm facing similar issues using GPIO and i2c at the same time.
So how can I add both providers to my project? I understand it would be possible to use gpiod for my GPIO DigitalInput/Output and LinuxFs for i2c at the same time?

I know I'm asking for much but if anyone could provide a simple hint on how to do this, that would be amazing. I somehow seem to have trouble combining this.

[Ir3nicuz]

After correcting the service file creation of my gradle build script the combined usage works well as with RPI4 / pigpio-digital-input.
The providers can be used in the same application:

    private DigitalInput buildDigitalInput(int gpioNumber, PullResistance pullMode, long debounceTimeMs) throws Exception {
        return Pi4jContext.create(DigitalInput.newConfigBuilder(Pi4jContext)
            //.provider("pigpio-digital-input") // rPi4
            .provider("gpiod-digital-input")    // rPi5
            .address(gpioNumber)
            .pull(pullMode)
            .debounce(debounceTimeMs));
    }
    private I2C buildI2CHandler(int busNumber, int address, String deviceName) throws Exception {
        return Pi4jContext.create(I2C.newConfigBuilder(Pi4jContext)
            .provider("linuxfs-i2c")
            .id("I2C-" + busNumber + "@" + address)
            .name(deviceName)
            .bus(busNumber)
            .device(address)
            .build());
    }